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-create-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-create-user-guide)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-create-user-guide"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-create-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 | $0.00000 | $0.05991 |
| Opus 5 | $0.00000 | $0.02995 |
| Sonnet 5 | $0.00000 | $0.01198 |
| Haiku 4.5 | $0.00000 | $0.00599 |
Grade A, and why
documentation-create-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 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.
How it starts
The opening of the file, as written. The whole thing — 900 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Guide and Tutorial Documentation Creation
This prompt generates comprehensive user-facing documentation including step-by-step tutorials, FAQ sections, troubleshooting guides, and onboarding flows with focus on user experience and accessibility.
🎯 USER DOCUMENTATION OBJECTIVES:
- ANALYZE user journeys and identify documentation needs across all user types
- CREATE task-oriented guides with clear step-by-step instructions
- DEVELOP tutorial sequences for progressive skill building
- GENERATE comprehensive FAQ addressing common user questions
- ESTABLISH troubleshooting resources for effective problem resolution
👥 USER AUDIENCE ANALYSIS:
STEP 1: User Persona and Journey Mapping
User Persona Discovery:
# Analyze user types and create personas
echo "👥 Identifying User Personas..."
cat > "user-personas.md" << 'EOF'
# User Personas for Documentation
## Primary Users
### 1. New User (First-time)
**Characteristics:**
- No prior experience with the application
- Needs clear onboarding and setup guidance
- Prefers visual aids and step-by-step instructions
- Easily overwhelmed by technical jargon
**Goals:**
- Complete initial setup quickly
- Understand core functionality
- Achieve first success/value
**Pain Points:**
- Complex setup processes
- Unclear navigation
- Missing prerequisites information
### 2. Regular User (Intermediate)
**Characteristics:**
- Familiar with basic functionality
- Seeks to expand usage and efficiency
- Comfortable with moderate complexity
- Values quick reference materials
**Goals:**
- Learn advanced features
- Improve workflow efficiency
- Troubleshoot occasional issues
**Pain Points:**
- Finding advanced features
- Understanding feature relationships
- Lack of workflow examples
### 3. Power User (Advanced)
**Characteristics:**
- Deep application knowledge
- Seeks customization and integration options
- Comfortable with technical details
- Often helps other users
**Goals:**
- Maximize application potential
- Integrate with other tools
- Customize workflows
**Pain Points:**
- Limited advanced documentation
- Missing API/integration details
- Insufficient customization guidance
### 4. Administrator/Manager
**Characteristics:**
- Responsible for team setup and management
- Needs governance and compliance information
- Focuses on security and control features
- Requires reporting and analytics guidance
**Goals:**
- Configure team settings
- Manage user permissions
- Generate reports and insights
- Ensure compliance
**Pain Points:**
- Complex admin interfaces
- Unclear permission models
- Missing governance documentation
EOF
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.
- 4d ago First seen · 900 lines · 0 tokens per session scan A 069cdf013136
documentation-create-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 5,991 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
technical-writer-intelligent
Technical writing and content creation specialist for documentation projects. Apply this rule when working on user guides, tutorials, README files, getting started documentation, architecture documentation, design documents, code comments, inline documentation, content accessibility improvements, information…
figma-performance
Handling large documents efficiently in the Plugin API.
mermaid
Diagram Creator. Load when the user requests "Create a diagram".
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.