Identify skill coverage gaps and improvement opportunities. Use when analyzing missing skills for a task, creating skill gap issues, evaluating skill effectiveness, or refining skill progressive disclosure.
Generate clear, measurable, and curriculum-aligned learning objectives for any topic. Use when user asks to define goals, outcomes, or objectives for a lesson or course.
Establish or analyze brand identity guidelines. Creates comprehensive brand documentation that frontend-design, testing, and other skills automatically reference for consistent execution.
Esta skill debe usarse cuando el usuario pide "pensar esto a fondo", "analizar paso a paso", "evaluar opciones", "razonar sobre esto", "pensar detenidamente", "meditar", o ante problemas con descripciones extensas, múltiples soluciones posibles, alcance difuso, 3+ opciones a evaluar, o tras 2-3 intentos fallidos que requieren replantear estrategia. Esta skill tiene preferencia a usar sequential-thinking directamente.
Deep research and information gathering specialist for thorough investigation, pattern analysis, and knowledge synthesis
Extended reasoning analysis using sequential thinking. Use for deep exploration, comprehensive analysis, complex decisions, or when you need fresh perspectives on difficult problems.
Comprehensive guide for skill assessment, career evaluation, learning paths, knowledge testing, and professional development. Use when assessing technical skills, planning learning journeys, or evaluating career progress.
Derive technical development principles FROM user needs in product.md using evidence-based reasoning. Creates constitution.md with architecture decisions, tech stack choices, and development constraints - all traced back to specific user needs. Use when user mentions "technical principles", "constitution", "architecture decisions", or after creating product.md.
Detect cognitive biases, logical fallacies, and thought pattern vulnerabilities.
Create detailed implementation plans through interactive research and iteration
Personalized AI mentorship for learning any creative or technical skill. Adaptive teaching that meets you where you are and guides you to mastery. Premium skill for deep learning journeys.
This skill should be used when the user asks to "create a skill", "add a skill", "write a new skill", "improve skill description", "organize skill content", or "validate skill structure". Provides guidance on skill development best practices for OpenCode.
MANDATORY skill creation framework for ALL skill creation requests. USE WHEN user wants to create, validate, update, or canonicalize a skill, OR user mentions skill creation, skill development, new skill, build skill, OR user references skill compliance, skill structure, or skill architecture.
Categorize and display available skills. Use when listing or selecting skills.
Interactive catalog of all available skills. Use when: user asks for help, wants to discover skills, or asks what you can do.
Use when starting any conversation - establishes how to find and use Flutter development skills, requiring Skill tool invocation before ANY response including clarifying questions
Generate structured skill specifications for independent skill creators. Use when asked to ideate, brainstorm, or specify multiple skills for a domain, workflow, or problem space. Outputs self-contained specs with list-level context so each skill can be built independently. Triggers on requests like "what skills would help with X", "generate skill ideas for Y", "specify skills to cover Z workflow".
This skill should be used when the user asks to "perform standard task", "follow best practices", "implement common pattern", or needs comprehensive guidance. Demonstrates recommended skill structure with progressive disclosure.
Atomic Design methodology for React component architecture. Use for structuring component libraries, organizing UI hierarchies, and creating scalable design systems. Triggers on requests for component organization, design system structure, UI hierarchy, or questions about Atoms/Molecules/Organisms/Templates/Pages.
Lightweight tactical guidance during implementation. Just MCP suggestions and quick lookups, no heavy Graphiti searches.
Conduct technical interviews about project plans to uncover hidden assumptions and identify potential issues before implementation. Use when the user wants to be interviewed about a plan, spec, or project idea.
Design technical architecture from a PRD. Use when user wants to create an architecture document, define system design, plan technical implementation, or needs to translate product requirements into buildable technical specs. Reads from docs/PRD.md and outputs docs/ARCHITECTURE.md.
Archive of past customer interviews. Contains full transcripts, summaries, pain points, outcomes, and skills used. Use for referencing previous conversations with the same company or finding similar case patterns.
