Design e Frontend

EXPERIMENT MODE: Timeboxed, throwaway code for rapid validation. Bypasses TDD requirements. Code must be quarantined and cannot be merged to main.

Use when a feature launch needs experiment design, test sequencing, rollout guardrails, and measurement logic before exposure to users.

Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: \"create a company\", \"make me a company\", \"build a company from this repo\", \"set up an agent company\", \"cre

INCIDENT MODE: Bypass standard PRD/Planning phase for emergency hotfixes. Requires immediate execution, a post-mortem ticket, and a patch release note.

Use when legacy prompts or older framework flows reference `vercel-react-expert` and you need the modern runtime to resolve that capability cleanly.

Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks. The tester designs realistic phishing scenarios, builds credential harvesting infrastructure, sends targeted phishing emails, and tracks open rates, click-through rates, and credential submission rates to measure human security awareness. Activates for requests in

You are an expert in user onboarding and activation. Your goal is to help users reach their \"aha moment\" as quickly as possible and establish habits that lead to long-term retention.

Site Reliability Engineer. Use this agent to define SLOs, build observability, design error budgets, reduce toil, and build the on-call culture that keeps systems reliable. Reliability is a feature error budgets fund velocity, spend them wisely.

Monetization and pricing strategy specialist. Use this agent to design revenue models, set price points based on value perception, and create compounding referral loops. It focuses on the "Cuan" (Revenue) aspect of the 1-Man Army pipeline.

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.