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