Four slash commands for creating, maintaining, and auditing project documentation with smart templates.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondocs-workflowExecute the skills CLI command in your project's root directory to begin installation:
Fetches docs-workflow from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate docs-workflow. Access via /docs-workflow in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
695
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
695
stars
Last Updated: 2026-01-11 Purpose: Manage project documentation throughout its lifecycle
This skill helps you:
| 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 |
# In a new project directory
/docs-init
This will:
# Audit all documentation
/docs-update
# Or just maintain CLAUDE.md
/docs-claude
Project-specific context for Claude Code, including:
Templates available:
CLAUDE-cloudflare.md - Cloudflare Workers + Vite + D1 projectsCLAUDE-nextjs.md - Next.js App Router projectsCLAUDE-generic.md - Any other project typeStandard README with:
Scaffolded documentation structure:
docs/ARCHITECTURE.md - System architecturedocs/API.md - API documentationdocs/DATABASE.md - Database schemaThe CLAUDE.md maintenance command checks:
Tech Stack Match
Referenced Files
Section Freshness
Critical Rules
Full documentation audit including:
Date Freshness
Version References
Broken Links
Redundancy
Orphaned Files
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.)/docs-init after /plan-project to add documentationIMPLEMENTATION_PHASES.md referenced in CLAUDE.md| Situation | Command |
|---|---|
| New project | /docs-init |
| After major changes | /docs-claude |
| Before release | /docs-update |
| Monthly maintenance | /docs-update |
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 technologiesPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
jezweb/claude-skills
jezweb/claude-skills
jezweb/claude-skills
langchain-ai/deepagents
upstash/context7
zrong/skills
Registry listing for docs-workflow matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in docs-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in docs-workflow — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend docs-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend docs-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
docs-workflow reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: docs-workflow is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend docs-workflow for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
docs-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
docs-workflow is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 58