documentation-update-developer

documentation-update-developer is a cursor rule for Cursor from oakensoul/nextjs-cursor-prompts. It costs 0 tokens per session (2,392 once invoked), scanned A, original, MIT.

A guide for updating developer documentation covering coding standards, setup instructions, development workflows, and technical implementation details. It checks the written guidance against the current tools and codebase.

In plain words
What is it for?
Use it to inspect the technology stack, verify setup and development tools, update coding guidance, and check implementation examples.
Why use it?
It reduces confusion caused by outdated commands, dependency versions, editor settings, or development procedures.

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-update-developer
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-update-developer

README.md
[![agentmods](https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-update-developer.svg)](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-update-developer)
Your own site
<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-update-developer"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-update-developer.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 2,392 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.02392
Opus 5 $0.00000 $0.01196
Sonnet 5 $0.00000 $0.00478
Haiku 4.5 $0.00000 $0.00239

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

Security

Grade A, and why

documentation-update-developer 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 3d 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-update-developer.mdc · 333 lines

How it starts

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

Developer Documentation Update Guide

This prompt systematically updates developer-focused documentation to reflect current coding standards, development workflows, setup procedures, and technical implementation details.

🎯 OBJECTIVES:

  1. UPDATE coding standards to reflect current development practices
  2. SYNCHRONIZE setup procedures with current development environment
  3. MAINTAIN workflow documentation for current development processes
  4. ENSURE technical accuracy of implementation guides and examples
  5. VALIDATE development tool documentation and configurations

📋 DEVELOPER DOCUMENTATION UPDATE PROCESS:

STEP 1: Development Environment Assessment

Current Development Stack Analysis:
echo "💻 Development Environment Assessment"
echo "===================================="

# Check current technology versions
echo "Technology Stack Versions:"
node --version
npm --version
if [ -f "package.json" ]; then
    echo "Package.json dependencies:"
    cat package.json | grep -E "(next|react|typescript|vitest)" -A 1
fi

# Verify development tools
echo "Development Tools:"
ls -la .vscode/ .cursor/ 2>/dev/null || echo "No editor configs found"

# Check build and development scripts
echo "Available Scripts:"
if [ -f "package.json" ]; then
    grep -A 10 '"scripts"' package.json
fi

# Verify environment configuration
echo "Environment Configuration:"
ls -la .env* 2>/dev/null || echo "No environment files found"
Development Workflow Changes:
  • New development tools added to the development stack
  • Updated dependencies affecting development workflow
  • Changed build processes requiring documentation updates
  • Modified testing strategies affecting developer workflow
  • Updated deployment processes impacting development practices
Documentation Gap Analysis:
  • Missing setup steps for new development tools
  • Outdated configuration examples not reflecting current setup
  • Incomplete workflow documentation missing recent processes
  • Broken code examples that no longer work with current stack
  • Missing troubleshooting guides for common development issues

Read the full file on GitHub · 333 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. 3d ago First seen · 333 lines · 0 tokens per session scan A a3d7a56f4d27

Subscribe to this mod's changes

documentation-update-developer 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 2,392 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.