Loading...
Loading...
Found 123 Skills
Create a comprehensive specification from a brief description. Manages specification workflow including directory creation, README tracking, and phase transitions.
Эксперт по README файлам. Используй для создания документации проектов, badges, installation guides и usage examples.
Agent-first project documentation. Scaffolds and maintains a documentation architecture designed for AI agents — ROADMAP, design-docs, logs, and more. Use when the user says "/docs", asks to set up project documentation, wants to update docs, or when starting a new project that lacks documentation structure. Also use when the user asks to plan a feature (creates a design doc) or review what's been done (updates logs/roadmap).
Manage template overrides for customizing Kata output formats. List available templates, copy defaults for local editing, edit overrides, validate template schemas. Triggers include "customize template", "override template", "edit template", "template overrides", "list templates", "show templates", "template customization", "manage templates", "what templates can I customize", "template schema", "custonmize Kata", "custom config".
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use when scope is large, requirements are mostly known, and work should be broken into validated phases before execution.
Generate a custom checklist for the current feature based on user requirements.
Create and update CLAUDE.md and AGENTS.md files. Use when: (1) setting up Claude documentation for a project, (2) updating agent instructions after codebase changes, (3) validating docs match current structure. Triggers: CLAUDE.md, AGENTS.md, agent instructions, project documentation.
[Manual Only] Record project learnings in FORyusuke.md. Structurally append lessons learned, pitfalls, debugging stories, and improvement points obtained during the session. It only works when explicitly called via /teach (it will not be triggered automatically in normal work).
Generate comprehensive scientific research-style documentation for completed coding projects. Use when the user requests project documentation, a technical breakdown, a study paper, a lecture document, or wants to understand everything about a project they just built. Triggers include phrases like "document this project," "create a study paper," "explain everything we did," "write up the full breakdown," "scientific documentation," or "I want to learn from this project." Produces formal Word documents (.docx) with academic structure, beginner-friendly explanations, and exhaustive code analysis.
Logs completed epics and significant accomplishments in reverse chronological order. Use after completing major features, releases, or architecture changes to maintain a project changelog.
Creates a new numbered issue document in docs/issue/ following the project's standard issue format, and simultaneously creates the corresponding Korean translation in docs/dev/issue/. Use this whenever starting new work — features, bug fixes, tasks, or investigations. The user may say "create an issue", "new issue", "이슈 만들어줘", or simply describe work they want to start.
Maintain project documentation with clear human/agent separation. Use when setting up a new project, auditing docs, creating plans, or managing agent working memory. Triggers include "set up docs", "create a plan", "audit documentation", "init project structure", or any task involving project documentation conventions.