skill-acquisition
Create, document, or revise Codex skills, including deciding when to add scripts/references/assets, structuring SKILL.md content, enforcing the 500-line rule, and updating repo references (AGENTS.md, kanban evi...
Discover research technical docs skills, compare source repositories and read the instructions for each workflow.
Create, document, or revise Codex skills, including deciding when to add scripts/references/assets, structuring SKILL.md content, enforcing the 500-line rule, and updating repo references (AGENTS.md, kanban evi...
Automated HTML architecture documentation generator that produces navigable, searchable technical documentation from codebase analysis.
This skill should be used when the user asks to "implement code", "write feature", "create function", "develop component", "code the solution", or requests actual code implementation based on a design. Use for...
This skill should be used when the user asks to "write documentation", "create README", "document API", "add comments", "explain code", "generate docs", or requests documentation creation and maintenance. Use f...
Writing clear, maintainable documentation for code, APIs, and vault documents
Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get w...
Generate comprehensive end-user documentation from application codebases
Rust documentation conventions (RFC 1574). Apply when writing doc comments on Rust items. Covers summary sentences, section headings, type references, and examples.
Documentation patterns for technical writing. Auto-loads when creating API docs, README files, JSDoc comments, or user guides.
Storybook stories, CSF3 format, autodocs. Use for component documentation.
Check if recent changes need documentation updates and suggest which docs to update.
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 t...
Maintain and update architecture documentation in docs/architecture/. Uses tool-based inspection first, falling back to CLI only when needed.
Provide repository-wide documentation guidelines under `docs/`. Use tool-based inspection first, and keep `README.md` and `docs/` in sync with the current state of the app.
Use when design is complete and you need detailed implementation tasks - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming minimal codebas...
Keeps narrative framing in docs while keeping code comments structural and stable.
Automated API documentation generation with support for OpenAPI/Swagger specifications, endpoint analysis, request/response examples, authentication methods, rate limiting, and integration guides. Use when Clau...
Create and maintain clear, useful documentation. Use when writing docs, README, API docs, guides, or ADRs.
Skill for documenting new functionalities. Ensures Swagger/OpenAPI decorators are present in code and updates external documentation files like .docs/GENERAL.md and .docs/INTEGRATION_TESTS.md.
Documentation specialist that writes and maintains technical docs, JSDoc/TSDoc comments, README files, API docs, and guides. Has file access (Read, create_file, edit_file). Use when creating or updating documen...
Deep module investigation using Amp's Search for discovery, oracle for expert analysis, and mermaid for visualization. Use when you need to understand complex code, prepare for refactoring, or debug issues.
STAR+I 기법으로 이력서/경력기술서 작성이 필요할 때
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow help...
Code implementation standards, patterns, and best practices. Use when writing code, implementing features, following coding conventions, or need guidance on code structure, naming, error handling, and testing.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.