Generates and maintains a standard docs folder structure with four topic areas: architecture (how the system works), codebase (where things live), code standard (team conventions), and project PDR (product requirements). It scans your project, infers whether you need initial setup or an incremental update, then writes or refreshes markdown files with actual content pulled from your code. The Agent Context Guide it adds to SUMMARY.md is deliberately narrow, just loading instructions for other AI agents. Useful when you inherit an undocumented repo or want to keep docs synced without rewriting everything from scratch each time. It won't invent requirements or pad empty projects with placeholder text.
$ npx -y skills add buiducnhat/agent-skills --skill docs --agent claude-codeInstalls into .claude/skills of the current project.
Create and maintain project documentation in docs/ with a consistent, lightweight structure.
Maintain these outputs:
docs/SUMMARY.md — documentation entry point with an Agent Context Guide (always regenerated)docs/architecture/ — system design, infrastructure, component interactions, data flows, feature flows. Focus on how the system works, not file/code structure.docs/codebase/ — file organization, directory structure, entry points, key modules and their responsibilities. Focus on where things live in the code.docs/code-standard/ — coding conventions, naming rules, style guides, environment setup, custom rules and patterns the team follows. Focus on how to write code that fits in with the existing codebase, best practices, and team conventions, very important for maintaining consistency.docs/project-pdr/ — product goals, use cases, business rules, constraints, and decision rationale. Nice to have many use case/requirements filesAlso keep README.md aligned with current docs links and project summary.
Scan the project to understand what needs documenting:
Sponsors