ci-templates
Use when setting up CI/CD pipelines. Teaches pipeline design principles and references platform-specific templates.
Use when setting up CI/CD pipelines. Teaches pipeline design principles and references platform-specific templates.
Use when a user asks for UI design tips or quick critique about layout, hierarchy, CTAs, forms, navigation, cards, tooltips, charts, or confirmation patterns.
This skill should be used when the user asks to "write documentation", "create docs", "document code", "improve documentation", "documentation best practices", "diataxis", "technical writing", "API documentation", "user guide", mentions documentation quality, documentation structure, or needs guidance on software documentation standards and frameworks.
Generates Bill of Materials (BOM) from project descriptions for Arduino/ESP32/RP2040 projects. Use when user needs component lists, parts shopping lists, cost estimates, or asks "what parts do I need". Outputs formatted BOMs with part numbers, quantities, suppliers (DigiKey, Mouser, Amazon, AliExpress), and compatibility warnings. Run scripts/generate_bom.py for xlsx/csv export.
Identify and resolve ambiguities in specifications through structured questioning. Use when specification has [NEEDS CLARIFICATION] markers, when user mentions unclear or ambiguous requirements, before creating implementation plans, or when planning reveals specification gaps.
(opencode-project - Skill) Template and guidelines for breaking features into implementation tasks
Create comprehensive implementation plans with bite-sized tasks. Use after brainstorming produces a design, before touching code. Documents exact files, complete code, commands, expected output.
Use for root cause analysis of bugs or issues. Systematically investigates problems to identify underlying causes.
"Domain vocabulary and entity relationships for {project}. Ensures consistent terminology and model understanding."
Structured workflow for co-authoring documentation, PRDs, technical specs, and decision docs. Use when writing substantial documentation, creating proposals, drafting specifications, or any structured content that benefits from iterative refinement. Provides context gathering, section-by-section building, and reader testing.
Reference and adhere to the project's technical stack including frameworks, languages, tools, and dependencies. Use this skill when choosing libraries, frameworks, or tools for implementing features. Use this skill when understanding which technologies are available and standardized in the project. Use this skill when making architectural or technology decisions. Use this skill when working with any part of the application to ensure consistency with the established tech stack. Use this skill when adding new dependencies or third-party services. Use this skill to maintain awareness of the project's runtime environment, database, testing tools, and deployment infrastructure.
Find conceptual gaps in plan/spec documents. Use when user explicitly asks start-gap-finder.
This skill should be used when the user wants to triage an issue, review a specification, or assess requirements completeness. Trigger when user mentions "triage", "review this spec", "is this requirement complete", "what questions should I ask", or provides a description/acceptance criteria that needs evaluation before implementation. The skill analyzes input against the codebase and project documentation to surface implicit requirements and generate clarifying questions.
Create design documents for Stapledons Voyage game features. Use when user asks to create a design doc, plan a feature, or document game mechanics. Handles both planned/ and implemented/ docs.
Master business documentation including BRD, FRD, specifications, and technical documentation for clear communication and requirements management.
Collaborative idea refinement - turns rough ideas into fully-formed designs through questioning, alternative exploration, and incremental validation. Use before writing code or implementation plans.
Catalogs recurring errors as pain points needing skills. Use when same error occurs multiple times.
Creates a NEW Architectural Decision Record (ADR) documenting a specific architectural decision. Use when the user requests "Create ADR for [topic]", "Document decision about [topic]", "Write ADR for [choice]", or when documenting technology choices, patterns, or architectural approaches. Do NOT use for reviews (use architecture-review or specialist-review), checking existing ADRs (use architecture-status), or general documentation.
Create and evaluate documentation using the Diátaxis framework. Use when writing, organizing, or auditing documentation to ensure it serves distinct user needs through four systematic categories (Tutorials, How-to Guides, Reference, Explanation). Ideal for diagnosing documentation problems, separating mixed content, and ensuring each piece serves a single, clear purpose.
Create, edit, and sync CV content using the knowledge base as source of truth. Unified skill for case studies, blog posts, experience updates, and variant content. Replaces cv-content-generator and cv-content-editor.
Master architectural design with SOLID principles, design patterns, microservices, and event-driven systems. Learn to design scalable backend systems.
Foundational SDK development patterns that domain-specific SDK skills extend. Use when building SDKs for APIs or specifications, creating SDK development skills, or establishing SDK architecture standards across languages.