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.
npx agentmods add rules/oakensoul/nextjs-cursor-prompts/documentation-update-user-guidegit clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsWrote 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.
[](https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-update-user-guide)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-update-user-guide"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-update-user-guide.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02557 |
| Opus 5 | $0.00000 | $0.01278 |
| Sonnet 5 | $0.00000 | $0.00511 |
| Haiku 4.5 | $0.00000 | $0.00256 |
Grade A, and why
documentation-update-user-guide 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Guide Documentation Update Guide
This prompt systematically updates user-facing documentation to reflect current features, user workflows, interface changes, and user experience patterns while maintaining accessibility and usability standards.
🎯 OBJECTIVES:
- UPDATE user workflows to reflect current application features and interface
- SYNCHRONIZE screenshots and visual guides with current UI implementation
- MAINTAIN accessibility standards in all user documentation
- ENSURE tutorial accuracy for current user experience flows
- VALIDATE help content for current feature set and user needs
📋 USER GUIDE UPDATE PROCESS:
STEP 1: Current User Experience Assessment
Application State Analysis:
echo "👥 Current User Experience Assessment"
echo "===================================="
# Check current application features
echo "Application Features Analysis:"
find src/app -name "page.tsx" | sort
# Verify user interface components
echo "UI Components Review:"
find src/components -name "*.tsx" | grep -E "(Button|Form|Modal|Navigation)" | head -10
# Check user flow implementations
echo "User Flow Analysis:"
find src/app -type d | grep -E "(auth|dashboard|profile|settings)" | sort
# Review accessibility implementations
echo "Accessibility Features:"
find src/ -name "*.tsx" | xargs grep -l "aria-\|role=\|alt=" | head -5
# Check user feedback and help features
echo "Help and Support Features:"
find src/ -name "*.tsx" | xargs grep -l "help\|support\|tutorial" | head -5
User Experience Changes:
- New features added since last documentation update
- Interface modifications affecting user workflows
- Navigation changes impacting user experience flow
- Feature deprecations requiring documentation updates
- Accessibility improvements requiring guide updates
Documentation Gap Analysis:
- Outdated screenshots not reflecting current interface
- Missing feature documentation for new capabilities
- Broken workflow guides that no longer match user experience
- Incomplete accessibility guides missing current features
- Outdated troubleshooting that doesn't address current issues
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.
- 5d ago First seen · 337 lines · 0 tokens per session scan A 54fc09699080
documentation-update-user-guide 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,557 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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.