documentation-create-full

documentation-create-full is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (5,701 once invoked), scanned A, original, MIT.

A set of instructions for planning and creating a complete software documentation set, covering user help, developer guidance, APIs, and system architecture.

In plain words
What is it for?
Use it to assess documentation needs, organize creation work, combine specialized documents, define quality checks, and plan future maintenance.
Why use it?
It coordinates different kinds of documentation so they use consistent information and form one navigable reference instead of disconnected files.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/oakensoul/nextjs-cursor-prompts/documentation-create-full
Clone the repo
git clone --depth 1 https://github.com/oakensoul/nextjs-cursor-prompts

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for documentation-create-full

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-create-full.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-create-full)
Your own site
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-create-full"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-create-full.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 5,701 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.05701
Opus 5 $0.00000 $0.02851
Sonnet 5 $0.00000 $0.01140
Haiku 4.5 $0.00000 $0.00570

Measured 4d ago against content hash d31143e4460b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

documentation-create-full scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/prompts/documentation/documentation-create-full.mdc · 727 lines

How it starts

The opening of the file, as written. The whole thing — 727 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Comprehensive Documentation Creation Orchestrator

This prompt orchestrates complete documentation generation across all project dimensions including user guides, API documentation, developer resources, and architecture documentation with coordinated delivery and maintenance planning.

🎯 COMPREHENSIVE DOCUMENTATION OBJECTIVES:

  1. ORCHESTRATE multi-faceted documentation creation across all project stakeholders
  2. COORDINATE specialized documentation prompts with consistent methodology and standards
  3. CONSOLIDATE deliverables into cohesive, navigable documentation ecosystem
  4. ESTABLISH documentation baseline with quality metrics and maintenance workflows
  5. GENERATE documentation roadmap with priorities and resource planning

📋 DOCUMENTATION CREATION ORCHESTRATION:

STEP 1: Pre-Creation Assessment and Planning

Documentation Scope and Planning:
# Initialize comprehensive documentation creation
echo "📝 Initializing Comprehensive Documentation Creation"
echo "================================================="

# Create documentation workspace
DOCUMENTATION_DATE=$(date +"%Y%m%d_%H%M%S")
DOCUMENTATION_DIR="documentation_creation_${DOCUMENTATION_DATE}"
mkdir -p "$DOCUMENTATION_DIR"/{deliverables,artifacts,staging,final}

echo "📁 Documentation workspace: $DOCUMENTATION_DIR"
echo "📅 Creation date: $(date)"
echo "👤 Created by: $(git config user.name) <$(git config user.email)>"
echo "📂 Project: $(basename $(pwd))"

# Project documentation inventory
echo -e "\n🏗️ Project Documentation Overview:"
echo "Repository: $(git remote get-url origin 2>/dev/null || echo 'Local repository')"
echo "Current branch: $(git branch --show-current)"
echo "Last commit: $(git log -1 --oneline)"
echo "Files tracked: $(git ls-files | wc -l)"

# Existing documentation audit
echo -e "\n📚 Existing Documentation Audit:"
[ -f "README.md" ] && echo "- Main README found"
[ -d "docs/" ] && echo "- Docs directory exists ($(find docs/ -name "*.md" 2>/dev/null | wc -l) markdown files)"
[ -f "CHANGELOG.md" ] && echo "- Changelog present"
[ -f "CONTRIBUTING.md" ] && echo "- Contributing guidelines found"
[ -f "CODE_OF_CONDUCT.md" ] && echo "- Code of conduct present"
[ -f "LICENSE" ] && echo "- License file found"
[ -f "package.json" ] && echo "- Package.json with potential description"
[ -f "openapi.yaml" ] || [ -f "openapi.json" ] && echo "- OpenAPI specification found"

# Technology stack documentation requirements
echo -e "\n🛠️ Technology Stack Documentation Needs:"
[ -f "package.json" ] && echo "- Node.js/JavaScript documentation required"
[ -f "tsconfig.json" ] && echo "- TypeScript configuration documentation needed"
[ -f "next.config.js" ] && echo "- Next.js framework documentation required"
[ -f "tailwind.config.js" ] && echo "- Tailwind CSS documentation needed"
[ -f "vitest.config.ts" ] && echo "- Testing framework documentation required"
[ -f "cypress.config.js" ] && echo "- E2E testing documentation needed"
[ -f ".eslintrc*" ] && echo "- Code standards documentation required"
[ -f "docker-compose.yml" ] && echo "- Deployment documentation needed"

Read the full file on GitHub · 727 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 727 lines · 0 tokens per session scan A d31143e4460b

Subscribe to this mod's changes

documentation-create-full is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,701 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.