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-architecturegit 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-architecture)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-create-architecture"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-create-architecture.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.05380 |
| Opus 5 | $0.00000 | $0.02690 |
| Sonnet 5 | $0.00000 | $0.01076 |
| Haiku 4.5 | $0.00000 | $0.00538 |
Grade A, and why
documentation-create-architecture 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 6d 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 — 705 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Documentation Creation
This prompt generates comprehensive architecture documentation including system design overviews, architectural decision records (ADRs), design patterns, and visual diagrams for complex software systems.
🎯 ARCHITECTURE DOCUMENTATION OBJECTIVES:
- ANALYZE system architecture and create comprehensive design documentation
- GENERATE architectural decision records with rationale and consequences
- CREATE visual diagrams showing system relationships and data flow
- DOCUMENT design patterns and architectural principles used
- ESTABLISH architecture guidelines for future development
🏗️ SYSTEM ARCHITECTURE ANALYSIS:
STEP 1: Architecture Discovery and Mapping
System Component Analysis:
# Analyze system components and architecture
echo "🏗️ Analyzing System Architecture..."
# Service and application discovery
echo "## Application Components:"
[ -d "src/app" ] && echo "- Frontend application (Next.js App Router)"
[ -d "src/pages" ] && echo "- Frontend application (Next.js Pages Router)"
[ -d "api" ] || [ -d "src/app/api" ] && echo "- API layer (Next.js API routes)"
[ -d "server" ] && echo "- Backend server application"
[ -d "services" ] && echo "- Service layer architecture"
[ -d "workers" ] && echo "- Background worker processes"
# Database and storage
echo -e "\n## Data Layer:"
[ -f "prisma/schema.prisma" ] && echo "- Primary database with Prisma ORM"
[ -f "drizzle.config.ts" ] && echo "- Database with Drizzle ORM"
grep -q "redis" package.json 2>/dev/null && echo "- Redis for caching/sessions"
grep -q "elasticsearch" package.json 2>/dev/null && echo "- Elasticsearch for search"
# External integrations
echo -e "\n## External Integrations:"
grep -q "stripe" package.json 2>/dev/null && echo "- Stripe payment processing"
grep -q "sendgrid\|nodemailer" package.json 2>/dev/null && echo "- Email service integration"
grep -q "aws-sdk\|@aws-sdk" package.json 2>/dev/null && echo "- AWS services integration"
grep -q "google" package.json 2>/dev/null && echo "- Google services integration"
# Infrastructure
echo -e "\n## Infrastructure:"
[ -f "Dockerfile" ] && echo "- Docker containerization"
[ -f "docker-compose.yml" ] && echo "- Multi-container Docker setup"
[ -f "kubernetes" ] && echo "- Kubernetes orchestration"
[ -d ".github/workflows" ] && echo "- GitHub Actions CI/CD"
[ -f "vercel.json" ] && echo "- Vercel deployment configuration"
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.
- 6d ago First seen · 705 lines · 0 tokens per session scan A fd6b8905c999
documentation-create-architecture 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,380 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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.