Loading...
Loading...
Found 23 Skills
Generate project documentation from codebase analysis — ARCHITECTURE.md, API_ENDPOINTS.md, DATABASE_SCHEMA.md. Reads source code, schema files, routes, and config to produce accurate, structured docs. Use when starting a project, onboarding contributors, or when docs are missing or stale. Triggers: 'generate docs', 'document architecture', 'create api docs', 'document schema', 'project documentation', 'write architecture doc'.
Guide for creating and maintaining project documentation (README, guides, API specs). Emphasizes doc/code synchronization, consistency checks, and use of the docs-excellence-architect subagent.
Coordinates project documentation creation. Gathers context once, detects project type, delegates to 5 L3 workers (ln-111-115). L2 Coordinator invoked by ln-100.
Maintain `*-skills` README standards and checklist-style roadmap docs through one canonical maintenance entrypoint. Use when a repo needs profile-aware README maintenance, checklist roadmap validation or migration, or a bounded audit-first doc workflow with Markdown and JSON reporting.
Creates 4 root documentation files (CLAUDE.md, docs/README.md, documentation_standards.md, principles.md). L3 Worker invoked by ln-110-project-docs-coordinator.
Creates 4 core project docs (requirements.md, architecture.md, tech_stack.md, patterns_catalog.md). L3 Worker invoked by ln-110-project-docs-coordinator. ALWAYS created.
Documentation-driven project development workflow. Intelligently determines task types, executes existing plans or generates new plans using feature-dev. **Use Cases:** - Complete project documentation exists, need to execute development tasks - User specifies to execute a certain plan (e.g., "Execute plan 001") - User requests to develop new features (automatically uses feature-dev to generate plans) **Prerequisites:** - The project should already have a docs/ documentation structure (PRD, SAD, etc.) - For new projects, it is recommended to first use the project-docs-setup skill to create complete documentation - If plan formulation is needed, it is recommended to use the project-planning skill **Relationship with Other Skills:** - project-docs-setup: Creates project documentation structure - project-planning: Formulates development plans (requirement clarification + design discussion + plan writing) - project-workflow: Executes development plans + updates documentation - Recommended workflow: project-docs-setup → project-planning → project-workflow **Trigger Methods:** - "Execute plan 001" / "Continue 001-user-authentication" - "Start development" / "Execute plan" / "Continue last task"
Use this skill when the user asks to add documentation, add docs, add references, or install documentation about Neon. Adds Neon best practices reference links to project AI documentation (CLAUDE.md, AGENTS.md, or Cursor rules). Does not install packages or modify code.
Update and maintain CLAUDE.md, README.md, agents, skills, and rules to match current project state. Use when docs are stale, the project structure changed, agents, skills, or rules reference outdated paths, or the user asks to update project documentation.
Use when starting work on any project to produce or update living documentation (TechStack.md, ProjectStructure.md) that bootstraps context for any AI agent session. Run before any feature work, or periodically to keep docs current.
Production-grade README.md patterns for any project type. Use when creating project documentation, writing README files, or improving existing docs. Covers hero sections, quick start examples, comparison tables, troubleshooting guides, and limitation transparency. Triggers on README, documentation, project setup, open source.
Generates comprehensive README files with badges, installation, usage, API docs, and contribution guidelines. Use when users request "README", "project documentation", "readme template", "documentation generator", or "project setup docs".