docs-workflow

jezweb/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill docs-workflow
0 commentsdiscussion
summary

Four slash commands for creating, maintaining, and auditing project documentation with smart templates.

  • Provides /docs-init to scaffold CLAUDE.md, README.md, and docs/ structure for new projects, with auto-detection of project type (Cloudflare Workers, Next.js, or generic)
  • Includes /docs-update for full documentation audits covering date freshness, version accuracy, broken links, redundancy, and orphaned files
  • Offers /docs-claude for focused CLAUDE.md maintenance, checking tech stack
skill.md

docs-workflow

Last Updated: 2026-01-11 Purpose: Manage project documentation throughout its lifecycle


Overview

This skill helps you:

  • Initialize documentation for new projects (CLAUDE.md, README.md, docs/)
  • Maintain CLAUDE.md to match actual project state
  • Audit all docs for staleness, broken links, outdated versions

Commands

Command Purpose
/docs Main entry - shows available subcommands
/docs-init Create CLAUDE.md + README.md + docs/ structure
/docs-update Audit and maintain all documentation
/docs-claude Smart CLAUDE.md maintenance only

Quick Start

New Project

# In a new project directory
/docs-init

This will:

  1. Detect project type (Cloudflare Workers, Next.js, generic)
  2. Create CLAUDE.md from appropriate template
  3. Create README.md if missing
  4. Optionally scaffold docs/ directory

Existing Project

# Audit all documentation
/docs-update

# Or just maintain CLAUDE.md
/docs-claude

What Gets Created

CLAUDE.md

Project-specific context for Claude Code, including:

  • Project overview and tech stack
  • Development setup commands
  • Architecture overview
  • Key file locations
  • Common tasks and workflows

Templates available:

  • CLAUDE-cloudflare.md - Cloudflare Workers + Vite + D1 projects
  • CLAUDE-nextjs.md - Next.js App Router projects
  • CLAUDE-generic.md - Any other project type

README.md

Standard README with:

  • Project name and description
  • Installation/setup instructions
  • Usage examples
  • Configuration
  • Contributing guidelines

docs/ Directory (Optional)

Scaffolded documentation structure:

  • docs/ARCHITECTURE.md - System architecture
  • docs/API.md - API documentation
  • docs/DATABASE.md - Database schema

Smart Maintenance

/docs-claude Features

The CLAUDE.md maintenance command checks:

  1. Tech Stack Match

    • Does CLAUDE.md list technologies that match package.json?
    • Are versions mentioned still accurate?
  2. Referenced Files

    • Do paths mentioned in CLAUDE.md still exist?
    • Are there new important files not mentioned?
  3. Section Freshness

    • Is "Last Updated" date recent?
    • Are there outdated patterns or commands?
  4. Critical Rules

    • For detected tech stack, are important rules present?
    • E.g., Cloudflare project should mention wrangler.jsonc patterns

/docs-update Features

Full documentation audit including:

  1. Date Freshness

    • Compare doc dates against git history
    • Flag docs not updated in >30 days
  2. Version References

    • Check npm package versions mentioned
    • Suggest updates for outdated versions
  3. Broken Links

    • Verify internal markdown links
    • Check that referenced files exist
  4. Redundancy

    • Identify duplicate content across files
    • Suggest consolidation
  5. Orphaned Files

    • Find docs not referenced anywhere
    • Suggest archiving or deletion

Project Type Detection

The skill auto-detects project type by looking for:

Indicator Project Type
wrangler.jsonc or wrangler.toml Cloudflare Workers
next.config.js or next.config.ts Next.js
Neither Generic

Additional indicators influence template content:

  • package.json dependencies (React, Vite, etc.)
  • Database config files (drizzle.config.ts, prisma/schema.prisma)
  • Auth config (clerk, better-auth)

Integration with Other Skills

  • project-workflow: Use /docs-init after /plan-project to add documentation
  • project-planning: Generated IMPLEMENTATION_PHASES.md referenced in CLAUDE.md
  • cloudflare-worker-base: Cloudflare template includes Workers-specific patterns

Best Practices

When to Run Each Command

Situation Command
New project /docs-init
After major changes /docs-claude
Before release /docs-update
Monthly maintenance /docs-update

CLAUDE.md Guidelines

  1. Keep it current - Update "Last Updated" when making changes
  2. Focus on project-specific - Don't duplicate generic tech docs
  3. Include common tasks - Commands you run frequently
  4. Reference, don't duplicate - Link to docs/ for detailed content

Templates

Templates are located in templates/ within this skill:

templates/
├── CLAUDE-cloudflare.md    # Cloudflare Workers projects
├── CLAUDE-nextjs.md        # Next.js projects
├── CLAUDE-generic.md       # Generic projects
└── README-template.md      # Standard README

Templates use placeholders:

  • {{PROJECT_NAME}} - Detected from package.json or folder name
  • {{DATE}} - Current date
  • {{TECH_STACK}} - Detected technologies
how to use docs-workflow

How to use docs-workflow on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add docs-workflow
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill docs-workflow

The skills CLI fetches docs-workflow from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/docs-workflow

Reload or restart Cursor to activate docs-workflow. Access the skill through slash commands (e.g., /docs-workflow) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.758 reviews
  • Zaid Verma· Dec 28, 2024

    Registry listing for docs-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ganesh Mohane· Dec 24, 2024

    Useful defaults in docs-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Mia Shah· Dec 20, 2024

    Useful defaults in docs-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Arya White· Dec 16, 2024

    I recommend docs-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Hassan Sharma· Dec 12, 2024

    I recommend docs-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mia Garcia· Dec 12, 2024

    docs-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Nikhil Torres· Dec 8, 2024

    Keeps context tight: docs-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Mia Johnson· Nov 27, 2024

    I recommend docs-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sakshi Patil· Nov 15, 2024

    docs-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Hiroshi Ghosh· Nov 11, 2024

    docs-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 58

1 / 6