@tickernelz/paperclip-pro-skills-catalog 2026.925.0

package/catalog/bundled/paperclip-operations/task-planning/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: task-planning
+description: Turn a Paperclip issue or request into a structured implementation plan with child task graph, blockers, owners, and acceptance criteria, then save it as the issue `plan` document.
+key: paperclipai/bundled/paperclip-operations/task-planning
+recommendedForRoles:
+  - manager
+  - engineer
+  - product
+tags:
+  - paperclip
+  - planning
+  - issues
+  - delegation
+---
+
+# Task Planning
+
+Produce implementation plans that the Paperclip executor can actually run: explicit child issues, real blockers, named owners, and a defined acceptance bar. Avoid plans that read well but cannot be split into work.
+
+## When to use
+
+- An issue asks you to "plan", "scope", "break down", "design the rollout", "propose the work", or similar.
+- A user wants a written plan before approving implementation.
+- A manager needs to delegate non-trivial work and the shape of the work is not obvious yet.
+- You inherited an issue too large to deliver in one heartbeat and need to split it.
+
+## When not to use
+
+- The issue is a single small change you can ship in the same heartbeat. Just ship it.
+- The issue is forensic ("why did this break"). Use a diagnosis skill first; plan only after the root cause is named.
+- A current `plan` document already exists and the change is minor. Update that document; do not start fresh.
+
+## Outputs
+
+1. An updated issue document with key `plan` (markdown).
+2. A short comment on the issue that links to the plan document and names the next action.
+3. Where the plan requires approval, an issue-thread interaction of kind `request_confirmation` bound to the latest plan revision.
+
+Do not create implementation subtasks until the plan is accepted.
+
+## Plan structure
+
+Required sections, in order:
+
+1. **Goal** — one paragraph. What changes for the user, the operator, or the system once this work lands.
+2. **Context reviewed** — bullet list of documents, files, and prior issues you read. Lets reviewers spot missing inputs.
+3. **Constraints and non-goals** — what must hold (compatibility, security, performance) and what this plan deliberately will not do.
+4. **Approach** — the chosen path, with a short rationale. If you considered alternatives, name them and why you rejected them.
+5. **Work breakdown** — ordered list of child issues. Each child has:
+   - Title in imperative form.
+   - Owner specialty (Engineer, QA, Designer, Security, DevRel, Manager, etc.).
+   - Scope and deliverables.
+   - Acceptance criteria.
+   - Blocks/blocked-by relationships expressed by phase letter or child title.
+6. **Acceptance** — the bar for the parent issue. How the user knows the whole thing is done.
+7. **Risks and mitigations** — short list. Skip if there are none.
+8. **Deferrals** — what is intentionally pushed to follow-up issues, with why.
+
+## Rules of thumb for splitting
+
+- One child issue, one specialty. If two specialties have to coordinate inside the same issue, split it.
+- One child issue, one acceptance verdict. If a reviewer would say "this is half done", split it.
+- A child must be checkout-able by the owner from its title and description alone. Reviewers should not have to re-read the parent plan to understand a child.
+- Order children by real blocker chains, not by author preference. Parallel children should explicitly say `blockers: none`.
+- Avoid `polish` or `cleanup` child issues without acceptance criteria — they never close.
+
+## Filing the plan
+
+Use the Paperclip API to write the plan document, then comment:
+
+- `PUT /api/issues/{issueId}/documents/plan` with the markdown body. If `plan` already exists, include the latest `baseRevisionId`.
+- `POST /api/issues/{issueId}/comments` with a short summary that links the plan: `/<prefix>/issues/<issue-id>#document-plan`.
+- If approval is required: `POST /api/issues/{issueId}/interactions` with `kind: request_confirmation`, `targetRevisionId` set to the new plan revision, `continuationPolicy: wake_assignee`, and `idempotencyKey: "confirmation:{issueId}:plan:{revisionId}"`.
+- Set the issue to `in_review` after creating the confirmation. Stay assigned so the acceptance wakes the planner.
+
+When the plan is accepted, see the companion skill for converting accepted plans into Paperclip executable tasks. Key requirements covered there: produce a compact task matrix (task, owner, initial status, blockers); encode every hard dependency as `blockedByIssueIds` — parent/child nesting alone does not block execution; and verify the created issue graph before closing the source planning issue.
+
+## Anti-patterns
+
+- Plan disguised as a description edit. Use the `plan` document.
+- "Phases A–Z" with no work breakdown inside the phases.
+- Children with descriptions that say "see parent" — they fail at delegation time.
+- Acceptance written as "code review approval". Reviewers need a behavior bar, not a process bar.
+- Plans that bury blocker chains in prose. Use explicit blocked-by lines.

package/catalog/bundled/product/paperclip-capsules/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: paperclip-capsules
+description: Generate, implement, or review Paperclip capsule visuals. Use for capsule art, agent capsules, heartbeat status capsules, identicons, capsule banks, or brand-usage validation.
+key: paperclipai/bundled/product/paperclip-capsules
+recommendedForRoles:
+  - designer
+  - product
+  - engineer
+  - marketing
+tags:
+  - paperclip
+  - brand
+  - capsules
+  - agents
+  - visual-design
+  - hyperframes
+---
+
+# Paperclip Capsules
+
+Use this skill when creating or checking Paperclip capsule visuals. The central rule is simple: **the capsule is the agent**. A capsule is not generic chrome, a button shape, a random status pill, or background decoration.
+
+The one approved decorative exception is the canonical hero capsule bank. Treat it as a specific Paperclip brand surface, not a license to make arbitrary capsule wallpaper.
+
+## When to Use
+
+- Generating Paperclip capsule art, agent avatars, capsule fields, hero capsule banks, or seeded capsule identicons.
+- Implementing an individual agent capsule in product UI.
+- Rendering heartbeat status capsules for agent status.
+- Building Paperclip feature videos or marketing graphics that use the capsule motif.
+- Reviewing a design for capsule brand correctness.
+
+## When Not to Use
+
+- Generic rounded pills, badges, buttons, tags, nav items, or decorative blobs.
+- Non-agent illustrations where capsules would only be visual texture.
+- Product UI color choices unrelated to agents or heartbeat status.
+- Replacing the app's existing `AgentCapsule` or status-color helpers from memory.
+
+## Non-Negotiable Rules
+
+- **Capsules represent agents.** If the surface does not involve agents, do not add capsules.
+- **Do not use the agent capsule palette outside capsules.** Never apply agent gradients to buttons, text, page backgrounds, cards, or generic UI chrome.
+- **Keep capsule families separate.** App individual capsules, heartbeat status capsules, website marketing capsules, video capsules, seeded identicons, and the hero bank have different data.
+- **Hero bank is the only decorative exception.** Use the canonical bank spec; do not hand-roll a new bank.
+- **Record reproducibility data.** For generated assets, record seed, template, palette, dimensions, and source workflow.
+- **Respect reduced motion.** Any pulsing, blinking, breathing, wave, or fill-rise animation needs a static reduced-motion fallback.
+
+## Choose the Right Capsule Surface
+
+Use **individual agent capsules** when one capsule equals one agent in product UI, onboarding, org surfaces, or avatars. Read `references/individual-status-capsules.md` before implementing or changing UI behavior.
+
+Use **heartbeat status capsules** for small solid status markers: idle/active gray, running blue pulse, paused amber, error red blink. These are not tall gradient identity capsules.
+
+Use the **hero capsule bank** only for brand hero imagery, feature-video hero scenes, or approved marketing motif work. Read `references/hero-capsule-bank.md` before drawing it.
+
+Use **graphic-generator layouts** when the task asks for capsule graphics such as blend rows, chains, grids, icon marks, or hero compositions. Prefer seeded tools and exportable workflows; read `references/generator-workflows.md`.
+
+Use **seeded identicons/profile pills** when an agent needs a reproducible personal capsule mark. Read `references/identicon-prototyper.md` before choosing variants, color schemes, dither algorithms, density, sheen, aurora, mesh, motion, or exports.
+
+## Implementation Workflow
+
+1. Identify which capsule family you are working in: individual agent, status capsule, hero bank, generator layout, or identicon.
+2. Load the matching reference file from this skill.
+3. Prefer existing source implementations:
+   - Product UI: `ui/src/components/AgentCapsule.tsx`, `ui/src/index.css`, and `ui/src/lib/status-colors.ts`.
+   - Hero bank: canonical spec in `references/hero-capsule-bank.md`.
+   - Video work: pair this skill with the Paperclip feature-video HyperFrames skill when available.
+4. If generating an artifact, choose a reproducible workflow and write down the seed/config.
+5. Verify that the result still reads as agent-related. Remove capsules if they became decoration.
+6. Attach or otherwise expose generated deliverables when doing issue work, and name the exact workflow used.
+
+## Output Expectations
+
+For any generated capsule asset, include:
+
+- Capsule family: `individual-agent`, `heartbeat-status`, `hero-bank`, `graphic-generator`, or `identicon`.
+- Source workflow or implementation path.
+- Seed and config where available.
+- Dimensions, format, and renderer.
+- Any divergence from canonical Paperclip rendering.
+
+For code changes, include targeted checks that exercise the edited surface. For visuals, include screenshots or inspectable SVG/PNG/HTML when possible.
+
+## Validation Checklist
+
+- Does each capsule represent an agent, agent state, or the canonical hero-bank exception?
+- Are gradients confined to capsule shapes?
+- Are app, website, video, identicon, and hero-bank palettes kept separate?
+- Is motion reduced or removed under reduced-motion settings?
+- Is the source path or reproducible seed/config recorded?
+- Are generated files attached or linked as inspectable deliverables for issue work?
+
+## References
+
+- `references/individual-status-capsules.md` - product app capsules, heartbeat status capsules, palette caveats, and reduced-motion rules.
+- `references/hero-capsule-bank.md` - canonical hero-bank geometry, palette, grain, wave, crop, and rendering checklist.
+- `references/generator-workflows.md` - website generator and external graphic-generator workflows.
+- `references/identicon-prototyper.md` - deterministic profile-pill variants, color schemes, dither algorithms, density behavior, motion, export/share controls, and recommended combinations.

package/catalog/bundled/product/paperclip-capsules/references/generator-workflows.md

@@ -0,0 +1,120 @@
+# Generator Workflows
+
+Use this reference when the request is to generate Paperclip capsule graphics, capsule identicons, or reusable visual assets.
+
+## Source Precedence
+
+1. Brand authority: app, website brand guide, feature-video references, and hero-bank spec.
+2. Deterministic identicon/profile-pill prototype:
+   - `paperclip-content/design/PAP-11825/paperclip-capsule-identicon-prototyper/README.md`
+   - `src/identicon.ts`
+   - `src/App.tsx`
+3. Website embedded generator:
+   - `paperclip-website/public/brand/generator.js`
+   - `paperclip-website/src/components/brand/sections/08-imagery.html`
+4. Mirrored graphic-generator contract in this file.
+
+The mirrored contract below was source-mined from the external prototype at commit `36a8a092c6ea6aa85bd0862bafb35ff9b9fab852`, but this skill must not depend on that personal repository being reachable. Treat the mode, palette, and control lists in this reference as the durable workflow contract.
+
+## Choose a Workflow
+
+| Need | Preferred workflow |
+| --- | --- |
+| Canonical hero brand image | Hero capsule bank reference |
+| One agent's profile mark | Seeded identicon/profile-pill prototype; read `identicon-prototyper.md` |
+| Repeatable marketing motif | External graphic-generator with explicit seed |
+| Quick public-doc example | Website embedded generator |
+| Product UI state | Existing `AgentCapsule` and status helpers |
+
+## Website Embedded Generator
+
+Templates:
+
+- `blend-row`
+- `chain`
+- `bar-stack`
+- `grid`
+- `hero`
+- `icon`
+
+Palettes:
+
+- `rainbow`
+- `warm`
+- `cool`
+- `mono`
+- `signal`
+- `duotone`
+
+Behavior:
+
+- Uses a Mulberry32 seeded PRNG internally.
+- Supports count, width, height, jitter, gap, and background parameters.
+- Good for understanding public brand-guide templates and palettes.
+- Weaker for issue deliverables because the UI does not expose seed/config as a first-class copyable control.
+
+## Mirrored Graphic Generator Contract
+
+Use this when the task needs reproducible generated capsule art beyond the small embedded website tool. The contract here is intentionally mirrored into Paperclip so agents can proceed if the original prototype repository is renamed, deleted, or private.
+
+Known modes/templates:
+
+- `blendRow`
+- `icon`
+- `chainLinks`
+- `hero`
+- `barStack`
+- `grid`
+- `wildcard`
+- `manualBlend`
+- `2d` and `3d` modes
+
+Useful controls:
+
+- Explicit numeric seed and reroll controls.
+- Anchor palette override panel.
+- Dither panel.
+- Logo overlay panel.
+- Background controls including images.
+- PNG and SVG export.
+
+If an implementation needs source code, prefer the Paperclip website embedded generator or a Paperclip-owned tool. Use any external prototype link only as optional historical context, not as required task input.
+
+Palette caution:
+
+- The `duotones` palette matches the website 12-preset capsule palette.
+- Experimental palettes such as vaporwave, cyberpunk, ocean, and jewel are generator options, not canonical Paperclip brand palettes.
+- Do not use experimental palettes when the request asks for strict Paperclip brand work.
+
+## Deterministic Identicon / Profile Pill
+
+Use `identicon-prototyper.md` when generating a reproducible capsule identity for one agent. That reference carries the detailed variant ids, HSL/OKLCH color schemes, dither algorithms, density/tone behavior, motion, share/export controls, and recommended combinations from the PAP-11825 prototype.
+
+## Artifact Record Template
+
+When generating assets for issue work, record this next to the attachment or deliverable:
+
+```md
+Capsule artifact
+
+- Family: identicon | graphic-generator | hero-bank | individual-agent | heartbeat-status
+- Workflow: website-generator | external-graphic-generator | identicon-prototype | hand-coded-svg | app-component
+- Source path or tool commit:
+- Seed:
+- Template / variant:
+- Palette / theme:
+- Color space / color scheme:
+- Density / count / dimensions:
+- Motion / gradient angle:
+- Output: SVG | PNG | HTML | MP4 | WebM
+- Divergence from canonical Paperclip rendering:
+```
+
+## Review Checklist
+
+- Is the output agent-related or the canonical hero-bank exception?
+- Does the palette match the selected surface?
+- Is the seed/config sufficient to reproduce the result?
+- Are exports non-empty and inspectable?
+- Are generated gradients confined to capsule shapes?
+- If motion is included, is there a static/reduced-motion alternative?

package/catalog/bundled/product/paperclip-capsules/references/hero-capsule-bank.md

@@ -0,0 +1,189 @@
+# Hero Capsule Bank
+
+The hero capsule bank is the one approved decorative exception to the rule that capsules represent individual agents. It is a canonical Paperclip brand surface. Do not improvise a different capsule bank.
+
+## Source Precedence
+
+1. `paperclip-content/td/capsules.md` - byte-accurate technical source for geometry, gradients, grain, crop, and wave.
+2. Paperclip feature-video HyperFrames skill:
+   - `references/capsule-bank-spec.md`
+   - `references/brand-tokens.md`
+   - `references/composition-recipes.md`
+3. `paperclip-content/videos/wireframe-skill-launch/src/HeroCapsuleBank.tsx` - working Remotion implementation.
+
+## Coordinate System
+
+| Property | Value |
+| --- | --- |
+| ViewBox | `0 0 1200 675` |
+| Background | `#141413` |
+| Square crop | `viewBox="250 -19 700 700"` |
+| Columns | 8 |
+| Capsules per column | 12 |
+| Total capsules | 96 |
+
+## Capsule Shape
+
+| Property | Value |
+| --- | --- |
+| Width | 70 |
+| Height | 170 |
+| Radius | 35 |
+| Rect anchor | `x=-35`, `y=-85` |
+| Positioning | translate each rect to center `(cx, cy)` |
+
+The capsule body is rigid. Never deform the capsule shape for wave motion.
+
+## Layout
+
+| Column | `tx` | `ty0` |
+| --- | --- | --- |
+| 0 | 355 | 154.464 |
+| 1 | 425 | 161.240 |
+| 2 | 495 | 101.067 |
+| 3 | 565 | 111.908 |
+| 4 | 635 | 137.808 |
+| 5 | 705 | 181.764 |
+| 6 | 775 | 150.630 |
+| 7 | 845 | 123.362 |
+
+Formula:
+
+```txt
+STRIDE_Y = 380 / 11
+cx = tx[column]
+cy = ty0[column] + slot * STRIDE_Y
+```
+
+Drawing order is column order 0..7, and within each column slot order 0..11. Higher slot indices draw later and cover lower ones.
+
+## Gradient Palette
+
+Each gradient is a two-stop linear gradient with a rotation angle in degrees.
+
+| id | angle | top | bottom |
+| --- | --- | --- | --- |
+| g0 | 90.000 | `#3c23fb` | `#fb8b24` |
+| g1 | 90.000 | `#6721fa` | `#f85f1c` |
+| g2 | 90.000 | `#921ff8` | `#f53215` |
+| g3 | 90.000 | `#bd1df7` | `#f10e18` |
+| g4 | 90.000 | `#e81bf5` | `#e4103e` |
+| g5 | 90.000 | `#f419d3` | `#d7135f` |
+| g6 | 90.000 | `#f217a4` | `#ca147b` |
+| g7 | 90.000 | `#f11575` | `#be1692` |
+| g8 | 90.000 | `#ef1346` | `#b217a4` |
+| g9 | 90.000 | `#ec1217` | `#9919a6` |
+| g10 | 90.000 | `#e83913` | `#79199a` |
+| g11 | 90.000 | `#e36414` | `#5c1a8f` |
+| g12 | 118.000 | `#9a031e` | `#ced51c` |
+| g13 | 118.727 | `#9a0547` | `#d2bd1c` |
+| g14 | 119.455 | `#9a0770` | `#ce9f1c` |
+| g15 | 120.182 | `#9a0997` | `#cb821c` |
+| g16 | 120.909 | `#770b9a` | `#c8661c` |
+| g17 | 121.636 | `#520d9a` | `#c44b1c` |
+| g18 | 122.364 | `#2e0f9a` | `#c1311c` |
+| g19 | 123.091 | `#12189a` | `#be1c1f` |
+| g20 | 123.818 | `#143e9a` | `#bb1b37` |
+| g21 | 124.545 | `#16629a` | `#b71b4e` |
+| g22 | 125.273 | `#198599` | `#b41b64` |
+| g23 | 126.000 | `#1b998b` | `#b11b79` |
+| g24 | 127.818 | `#940540` | `#dbd81a` |
+| g25 | 137.636 | `#8e065f` | `#e1d419` |
+| g26 | 147.455 | `#88077a` | `#e7cf17` |
+| g27 | 157.273 | `#720982` | `#ebc817` |
+| g28 | 167.091 | `#520a7c` | `#edbf19` |
+| g29 | 176.909 | `#360b77` | `#f0b71a` |
+| g30 | 186.727 | `#1c0c71` | `#f2ae1c` |
+| g31 | 196.545 | `#0d146c` | `#f4a51e` |
+| g32 | 206.364 | `#0e2a66` | `#f79d20` |
+| g33 | 216.182 | `#0e3c61` | `#f99422` |
+| g34 | 226.000 | `#0f4c5c` | `#fb8b24` |
+| g35 | 93.273 | `#dc8f15` | `#671a92` |
+| g36 | 96.545 | `#d5b716` | `#721a95` |
+| g37 | 99.818 | `#c1ce17` | `#7d1a98` |
+| g38 | 103.091 | `#93c718` | `#891b9b` |
+| g39 | 106.364 | `#68c018` | `#951b9e` |
+| g40 | 109.636 | `#41b919` | `#a11ba1` |
+| g41 | 112.909 | `#1db31a` | `#a41b9a` |
+| g42 | 116.182 | `#1aac38` | `#a81b92` |
+| g43 | 119.455 | `#1aa657` | `#ab1b8a` |
+| g44 | 122.727 | `#1b9f72` | `#ae1b82` |
+
+SVG template:
+
+```xml
+<linearGradient id="g0" gradientUnits="objectBoundingBox"
+  x1="0" y1="0" x2="1" y2="0"
+  gradientTransform="rotate(90 0.5 0.5)">
+  <stop offset="0%" stop-color="#3c23fb" />
+  <stop offset="100%" stop-color="#fb8b24" />
+</linearGradient>
+```
+
+## Per-Column Gradient Sequences
+
+Each sequence lists slots 0..11.
+
+| Column | Sequence |
+| --- | --- |
+| 0 | `g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 g10 g11` |
+| 1 | `g12 g13 g14 g15 g16 g17 g18 g19 g20 g21 g22 g23` |
+| 2 | `g11 g10 g9 g8 g7 g6 g5 g4 g3 g2 g1 g0` |
+| 3 | `g23 g22 g21 g20 g19 g18 g17 g16 g15 g14 g13 g12` |
+| 4 | `g12 g24 g25 g26 g27 g28 g29 g30 g31 g32 g33 g34` |
+| 5 | `g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 g10 g11` |
+| 6 | `g11 g35 g36 g37 g38 g39 g40 g41 g42 g43 g44 g23` |
+| 7 | `g0 g1 g2 g3 g4 g5 g6 g7 g8 g9 g10 g11` |
+
+## Grain Overlay
+
+Grain is part of the motif. Do not omit it for canonical hero-bank renders unless the output medium cannot support it.
+
+| Property | Value |
+| --- | --- |
+| SVG primitive | `feTurbulence type="fractalNoise"` |
+| Base frequency | `2.95` |
+| Octaves | 5 |
+| Seed | 9 |
+| Opacity | 0.86 |
+| Blend mode | `overlay` |
+| Mask | union of capsule shapes only |
+
+Overlay formula per channel:
+
+```txt
+overlay(b, o) = 2 * b * o                     if b < 0.5
+overlay(b, o) = 1 - 2 * (1 - b) * (1 - o)     otherwise
+final = mix(b, overlay(b, o), 0.86)
+```
+
+Background pixels stay clean `#141413`; grain is masked inside capsules.
+
+## Optional Wave Motion
+
+For motion, translate each capsule rigidly on y. Do not scale, bend, or morph the capsule.
+
+| Property | Value |
+| --- | --- |
+| Wave amplitude | 9 |
+| Per-capsule phase step | `PI / 3` |
+| Per-column phase factor | `2 * PI / 280` |
+| Loop period | 4 seconds |
+
+Formula:
+
+```txt
+dy(column, slot, t) =
+  9 * sin((2 * PI * t / 4) - (2 * PI / 280) * tx[column] - slot * (PI / 3))
+```
+
+For a static still that matches the captured spec, set amplitude to 0 and use the `ty0` values verbatim.
+
+## Rendering Checklist
+
+1. Paint background `#141413`.
+2. Draw 8 columns x 12 capsules using the layout and gradient sequence tables.
+3. Apply the grain overlay, masked to capsule shapes.
+4. For square exports, crop to `250 -19 700 700`.
+5. If animated, loop the wave over exactly 4 seconds and provide reduced-motion/static output.
+6. Do not add strokes, shadows, glow, extra gradients, or additional capsule rows.