Explore skills

Convert Pencil `.pen` design files and named Pencil node IDs into production frontend code. Use when asked to implement, migrate, reproduce, or refine a Pencil/Figma-like visual design in code, especially for responsive artboards, glassmorphism, typography matching, background image layers, design tokens, or visual fidelity debugging against Pencil node IDs.

Final visual polish for an existing UI without redesigning it. Use after structure is clear, when asked to improve spacing, alignment, text hierarchy, readability, shadows, highlights, effects, action placement, or overall production feel. For screen structure, layer naming, code handoff, preview scenes, or animation planning, use pencil-ui-structure first.

Run multiple skills on the same task in parallel and compare outputs side by side. A creative pitch room -- give it a brief, and it finds skills (local + trusted community repos) to work on it independently, then presents all outputs for comparison. Use when asked to "skill battle", "compare skills", "run multiple skills", "pitch room", "get different takes", "split test this", "give me options",

Quick-reference card for shakespeare mode — all intensity levels, commands, and activation phrases. One-shot display, not a persistent mode. Use when the user types /shakespeare-help or asks "what shakespeare commands are there".

Framework based on April Dunford''s "Obviously Awesome" and "Sales Pitch". Use this skill whenever the user is discussing how to describe, frame, differentiate, sell, or talk about their product — even if they do not explicitly say "positioning," "pitch," or "messaging." Triggers include: (1) defining or evaluating product positioning using the five-component framework, (2) translating positioning

Framework based on April Dunford''s "Sales Pitch". Use this skill whenever the user is discussing sales conversations, pitch decks, demos, buyer messaging, or stalled deals — even if they do not explicitly say "sales pitch," "positioning," or "Dunford." Triggers include: (1) structuring a B2B sales conversation that builds buyer confidence rather than pushing features, (2) developing a pitch narra

Amazon''s Working Backwards product development method based on Colin Bryar and Bill Carr''s "Working Backwards". Use this skill whenever the user is discussing a new product, feature, pitch, or launch narrative — even if they do not explicitly say "PR/FAQ," "press release," or "working backwards." Triggers include: (1) writing or reviewing a PR/FAQ for a new product or feature, (2) drafting the l

Use when, just after abandoning or failing at something, you catch yourself concluding "that wasn't worth reaching anyway" — the post-mortem self-deception / motivated-reasoning anti-pattern. Fires when writing a post-mortem after a failure or rollback, recording a lesson after a retreat, or when an operator/agent's stated reason for quitting smells like comfort rather than analysis. The tell: a g

Use this skill when implementing features, writing code, creating functions or classes, refactoring existing code, or building any software component. Triggers on: "implement", "write the code for", "build this feature", "create a function", "refactor this", "add this to the codebase", "make this work", "write a class", "implement the logic". This skill enforces clean code principles, proper abstr

Use this skill for any production incident, outage, or critical system failure. Triggers on: "production is down", "outage", "incident", "something broke in prod", "users are affected", "SEV-1", "SEV-2", "rollback needed", "postmortem", "post-mortem", "RCA for incident", "system is down", "critical bug in production", "emergency deploy", "data issue in production". This skill coordinates the respo

Use this skill for anything related to managing or preparing a software release: release checklists, release notes, version bumping, release planning, go/no-go decisions, changelog maintenance, deployment coordination, or rollback planning. Triggers on: "prepare a release", "release notes", "write the changelog", "version bump", "deploy to production", "release checklist", "go/no-go", "rollback pl

Use this skill for any architecture, system design, or major technical decision task. Triggers on: "design the system", "architecture for", "how should we structure", "ADR", "architecture decision", "data model", "API design", "system diagram", "technical design", "non-functional requirements", "how should this be built", "what pattern should we use", "scalability", "integration design". Use befor