Loading...
Loading...
Found 50 Skills
Wave-based comprehensive project documentation generator with dynamic task decomposition. Analyzes project structure and generates appropriate documentation tasks, computes optimal execution waves via topological sort, produces complete documentation suite including architecture, methods, theory, features, usage, and design philosophy.
Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.
Generate MDX blog posts or recaps from session logs in `sessions/articles`. Use when the user asks to turn daily session notes into publishable blog posts, define writing style or linking rules for those posts, or produce MDX drafts that follow the project's standards and file location.
Generate DeepWiki-style source code documentation for local codebases, transforming engineering experience into reusable cognitive structures
Write Architectural Decision Records following MADR template. Applies Definition of Done criteria, marks gaps for later completion. Use when generating ADR documents from extracted decisions.
PRD 초안을 작성하고 형식을 검증한 뒤 GitHub PR 제출을 안내한다. "PRD 작성", "PRD 검증", "Day 6", "6일차", "PR 제출", "prd submit" 요청에 사용.
Generate reference documentation entry by entry for the public surface of a library (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental difference from guidedoc: guidedoc teaches you how to use something, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When the user says "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are discovered after feature-acceptance.
This skill should be used when the user asks to "create note", "capture thought", "save this", "document idea", "write note", "jot down", "quick note", "remember this", "capture this", or mentions wanting to save knowledge, ideas, or learnings for later reference in their secondbrain.
Workflow for Business Knowledge Acquisition and Skill Document Creation. Use this when you need to familiarize yourself with a new business module, retrieve documents from iWiki, generate architecture documents combined with code analysis, or institutionalize business knowledge as Skills.
Produce clear, accurate, and maintainable technical documentation for APIs, systems, and user workflows.
Create and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", "feature", or "Obsidian".
Update the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs