Design e Frontend

This skill should be used when running competitive intelligence scans against tracked competitors, or auditing a peer skill-library repo via peer-plugin-audit. Produces structured knowledge-base reports.

Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. Invoked after implementation to identify simplification opportunities and ensure YAGNI adherence.

Orchestrates the support domain -- assesses support posture, recommends actions, and delegates to support specialist agents. Use individual support agents for focused tasks; use this agent for cross-cutting support strategy and multi-agent coordination.

Use this agent when you need to design outbound prospecting sequences, ICP targeting, lead scoring models, or multi-channel cadence strategies. Use copywriter for email copy and creative; use this agent for cadence strategy and audience targeting. Use cro for cross-cutting sales strategy.

Use this agent when reviewing code to ensure features are agent-native -- any action a user can take, an agent can also take, and anything a user can see, an agent can see. Enforces agent-user parity in capability and context.

Use when the user asks to copy, install, refresh, or update a repo-root AGENTS.md file from their canonical global instruction source. Also use when the user says "agent copy" or wants a repo-local AGENTS.md with global operating rules plus project-specific guidance.

This skill should be used when the user asks to "hush", "be quiet", "stop speaking", "silence narrator", "narrator hush", "shut up", or wants to immediately stop all current and queued speech output.

This skill should be used when writing Ruby and Rails code in DHH's 37signals style: REST purity, fat models, thin controllers, Current attributes, Hotwire patterns.

Generate audience-targeted release announcements. Specify the audience (customers, internal team, investors, social media) and optionally a version or scope. Use after shipping to announce what was built.

Invoke when the user wants to plan, execute, or analyze a structured playtest session with behavioral observation. Covers protocol design, observer guides, and data synthesis. Triggers on: "playtest", "player feedback", "usability test", "observation session", "playtest analysis". Do NOT invoke for QA bug testing (use game-qa-lead) or balance tuning (use game-balance-check). Part of the AlterLab G

Use this agent when running /plan to check whether community registries already have skills or agents with similar functionality to the feature being planned. Use agent-finder for stack-gap detection; use this agent to check if a planned feature already exists in registries.

Orchestrates the product domain -- assesses product strategy, validates business models, and delegates to specialist agents (spec-flow-analyzer, ux-design-lead, business-validator, competitive-intelligence). Use individual product agents for focused tasks; use this agent for cross-cutting product strategy and multi-agent coordination.