Create Theory (THY) documents that capture integrated understanding. Triggers on "capture theory", "document understanding", "write theory", "explain why this works", "record the mental model".
Reviews existing specifications for ambiguity and missing decision points - uses structured taxonomy to detect gaps, generates prioritized clarification questions, reduces specification uncertainty.
Design the structural and emotional architecture for nonfiction books. Use when an author has a validated book concept and needs to create the blueprint before drafting. Triggers include requests to structure a book, create a chapter outline, design a table of contents, map the reader's journey, or plan book organization. Requires upstream documents from book-ideation (Book Concept Document) and optionally from idea-validator (Validation Report) and market-research (Market Research Report).
Router for 3D building game mechanics in Three.js. Use when creating survival games, sandbox builders, base builders, or any game with player-constructed structures. Routes to 9 specialized skills for performance, physics, multiplayer, terrain, decay, UX, platform support, and design reference. Start here for building mechanics projects.
Complete catalog of 130+ Effect-TS patterns from EffectPatterns repository. Use when looking for specific implementation patterns, best practices, or real-world examples. Complements other skills with concrete, curated patterns.
Decision framework for React Three Fiber projects. Routes to specialized R3F skills (fundamentals, geometry, materials, performance, drei) based on task requirements. Use when starting an R3F project or needing guidance on which R3F skills to combine.
Audits skills for discoverability and triggering effectiveness. Use when reviewing skill descriptions, checking trigger coverage, validating progressive disclosure, fixing invocation issues, or learning skill best practices.
Self-improving learning system that detects friction signals and proposes rule updates. This skill should be used when Claude needs to learn from mistakes, when users repeatedly correct behavior, when tool failures indicate missing knowledge, or when reviewing learning candidates via /coach commands.
Master game engines - Unity, Unreal Engine, Godot. Engine-specific workflows, systems architecture, and production best practices.
This skill should be used when creating professional software documentation (SRS, PRD, OpenAPI, user manuals, tutorials, runbooks) from templates (greenfield) or reverse-engineering documentation from existing code like Spring Boot or FastAPI (brownfield). Also handles documentation audits/reviews, format conversion (Markdown, DOCX, PDF), and diagram generation (C4, Mermaid, PlantUML, ER, sequence). Use when asked to "create documentation", "document my code", "write SRS", "generate PRD", or "documentation specialist".
Answers questions about HyperFleet architecture, design patterns, versioning strategies, cluster lifecycle, event-driven architecture, adapter framework, and git workflow by fetching docs from the openshift-hyperfleet/architecture GitHub repository.
Guide security incident response, investigation, and remediation processes. Use when you need to handle security breaches, classify incidents, develop response playbooks, gather forensic evidence, or coordinate remediation efforts. Trigger with phrases like "security incident response", "ransomware attack response", "data breach investigation", "incident playbook", or "security forensics".
Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation. Use when a user asks to investigate, root-cause, or plan changes, or when an Issue or PR is referenced and needs a plan.
This skill should be used when the user asks to "brainstorm", "design a feature", "think through an idea", "help me plan", or has a vague concept that needs refining into a technical specification through collaborative dialogue.
Use when creating technical specifications for features, systems, or architectural designs. Creates comprehensive specification documents using the Wrangler MCP issue management system with proper structure and completeness checks.
Use this skill when creating or editing issues on Github or when asked to write user-stories or record bugs.
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
Extract and consolidate key learnings, insights, and actionable takeaways from the current conversation session. Use when the user wants to capture, summarize, or document what was learned during the chat, create study materials from discussions, or save important discoveries and decisions for future reference. Triggers include requests like "capture learnings," "summarize what we discussed," "create notes from this conversation," "what did I learn today," or "document our key findings."
Gather structured information from the user through framework-aware questioning. Use when you need to elicit process context, requirements, constraints, or decisions. Triggers on "gather requirements", "elicit context", "structured questions", "need to understand".
Plan and architect a single chapter at beat-level granularity. Use when you have a chapter from the Architecture Document and need to create a detailed outline before drafting. Produces a Chapter Outline Document for use by draft-coach or ghostwriter.
Use when discussing architecture, adding features, or understanding fancai project structure. Provides technology overview and conventions.
This skill should be used when writing or reviewing technical documentation such as READMEs, API documentation, quickstart guides, or any user-facing documentation. Apply editorial principles focused on leading with value, cutting redundancy, and creating scannable, actionable content. Use when the user requests help writing docs, improving existing documentation, or creating user guides.
Best practices for documenting APIs and code interfaces, eliminating redundant documentation guidance per agent.
Develop ebook ideas into structured concepts ready for architecture. Use when the user has an ebook idea (from a brainstorm document, existing content to repurpose, a book section to extract, or a fresh concept) and wants to develop it into a clear, validated concept. Produces an Ebook Concept Document with reader, transformation, promise, content source, scope/format, and key topics. Handles multi-session development with living documents.
