agents

Challenge and stress-test ideas through adversarial thinking. Use when user wants to "poke holes", "challenge this", "what could go wrong", "devil's advocate", "stress test", "red team", "pre-mortem", "review this", "validate", "audit", or needs to find weaknesses before they become problems. (project)

Go style and best practices guide synthesized from Google, Uber, and official Go documentation. This skill should be used when writing, reviewing, or refactoring Go code. Triggers on tasks involving Go packages, error handling, concurrency, interfaces, or performance optimization.

Generate creative ideas through structured brainstorming techniques. Use when user wants to "brainstorm", "generate ideas", "think creatively", "SCAMPER", "walt disney method", "reverse brainstorm", "come up with options", or needs to break out of conventional thinking.

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.

Explore problems from multiple perspectives through structured role-playing techniques. Use when user wants to "see different viewpoints", "consider perspectives", "what would X think", "six hats", "stakeholder view", "persona analysis", or needs to understand how different people would approach a problem.

Dig to fundamental truths and real causes behind problems. Use when user asks "why does this happen", "what's the real problem", "root cause", "first principles", "jobs to be done", "JTBD", "five whys", "fundamental reason", or needs to understand underlying causes rather than symptoms.

Analyze strategic positioning and explore future scenarios. Use when user wants "SWOT analysis", "competitive forces", "scenario planning", "what if", "strategic assessment", "market forces", "porter's", or needs to evaluate strategic options and potential futures.

Guide learning and deep understanding through proven methodologies (Socratic, Feynman, Problem-Based). Use when user says "help me understand", "teach me", "explain this", "learn about", "socratic", "feynman", "problem-based", "I don't understand", "confused about", "why does", or wants to truly grasp a concept.

Design and conduct user research to understand needs, behaviors, and experiences. Use when user wants "journey mapping", "user interviews", "survey design", "usability testing", "user research", "customer discovery", "card sorting", "information architecture", "accessibility audit", "design critique", "prototype testing", "requirements gathering", "discovery phase", "validation phase", "research planning", or needs to understand users deeply.