Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Rust documentation practices for HASH codebase. Use when writing doc comments, documenting functions/types/traits/modules, creating error sections, using intra-doc links, following rustdoc conventions, or exploring crate APIs with cargo doc.
Generate comprehensive data model documentation with ERD, DTOs, and data flow diagrams
Fetch Hono web framework documentation via llms.txt for up-to-date API references
Use when creating new skills, editing existing skills, initializing skill structure, packaging skills for distribution, or verifying skills work before deployment. This skill applies TDD methodology to documentation.
Describes how to get usage instructions for a Nuget package.
Technical documentation for Rust projects. Creates API docs, README files, architecture guides, and contributor documentation. Follows Rust documentation conventions with strict quality standards.
Google Docs ドキュメントを新規作成する。「ドキュメント作成」「Docs 作成」「新しいドキュメント」「ドキュメントを作って」などで起動。
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Maintain documentation for IntelliFill following Diátaxis framework. Use when creating or updating docs, API references, or guides.
NatSpec documentation standards and best practices for Solidity contracts. Use when documenting code or reviewing documentation quality.
Reverse engineers and generates comprehensive technical specifications from pseudocode, algorithms, or code snippets. Produces detailed requirements documents, functional specifications, API documentation, data models, and workflow diagrams. Use when analyzing pseudocode, extracting requirements from algorithms, documenting undocumented code, reverse engineering specifications, creating specifications from implementation details, or when users mention "pseudocode to spec", "reverse engineer specification", "generate spec from code", "document algorithm", "extract requirements from pseudocode", "code to specification", or "specification from implementation".
Expert UI/UX design and frontend development guidance. Use when designing interfaces, creating design systems, improving user experience, implementing accessible components, or building responsive layouts. Covers WCAG compliance, design patterns, and CSS/component best practices.
Guides product development from requirements through design specifications. Covers product requirements, technical requirements, architecture, and interface contracts with iterative review loops. Use when planning new features, services, CLI tools, APIs, or infrastructure. Run software-engineering skill after to implement.
Creates detailed technical specifications including architecture, data models, APIs, and technology choices. Use when you need to document technical implementation details, system design, or API contracts. Provides concrete technical guidance for implementation.
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.
Expert in documentation structure, audience targeting, and information architecture. Covers technical docs for Software, Hardware, Robotics, and Data Science.
Technical documentation architect that creates comprehensive technical documentation (both short-form guides and long-form manuals) with architecture diagrams, design rationale, and implementation guides. Explains the what and the why.
Interactive Java/Spring Boot learning skill for experienced Go developers. Use when the user wants to learn Java, practice Spring Boot, work on Java exercises, or asks for Java explanations in Go terms. Supports mood-aware pacing with "low energy" mode for difficult days. Teaches through iterative project building rather than passive learning.
Provides guidance and explanations on Python code structure, organization, and architectural patterns tailored for students and beginners.
Educational code development skill that teaches programming concepts while building applications. Use when the user wants to learn how code works, understand programming concepts, or build an app with detailed explanations. Provides line-by-line breakdowns, explains the 'why' behind code patterns, uses pedagogical teaching methods, and builds apps incrementally with educational commentary at each step.
Modern Python coaching covering language foundations through advanced production patterns. Use when asked to "write Python code", "explain Python concepts", "set up a Python project", "configure Poetry or PDM", "write pytest tests", "create a FastAPI endpoint", "run uvicorn server", "configure alembic migrations", "set up logging", "process data with pandas", or "debug Python errors". Triggers on "Python best practices", "type hints", "async Python", "packaging", "virtual environments", "Pydantic validation", "dependency injection", "SQLAlchemy models".
