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/component-create-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/component-create-guide)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-create-guide"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-create-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.00011 | $0.05410 |
| Opus 5 | $0.00005 | $0.02705 |
| Sonnet 5 | $0.00002 | $0.01082 |
| Haiku 4.5 | $0.00001 | $0.00541 |
Grade A, and why
component-create-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 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.
How it starts
The opening of the file, as written. The whole thing — 723 lines — stays where its author put it; the contents beside it link to each section on GitHub.
title: Component Creation Guide description: Enhanced comprehensive prompt for creating new React components with intelligent routing to specialized domain prompts tags: [prompt, component-creation, react, typescript, testing, accessibility, routing] version: 2.0.0 lastUpdated: 2025-06-02 usage: Use when creating new React components from scratch - intelligently routes to specialized prompts or provides general guidance audience: [claude, ai-assistants] scope: [component-architecture, file-structure, testing, accessibility, documentation, prompt-routing] related_prompts:
- "component-workflow-integration.mdc"
- "component-troubleshooting-guide.mdc"
- "component-create-form.mdc"
- "component-create-ui.mdc"
- "component-create-layout.mdc"
- "component-create-card.mdc"
- "component-create-navigation.mdc"
- "component-create-marketing.mdc"
- "component-create-icon.mdc"
- "component-update-*.mdc"
Component Creation Guide
Enhanced general-purpose component creation prompt with intelligent routing to specialized domain prompts for optimal results.
🎯 INTELLIGENT PROMPT ROUTING
Use Specialized Prompts First (Recommended)
Before using this general guide, consider if your component falls into these specialized domains:
📝 Form Components → Use component-create-form.mdc
- Login/registration forms, contact forms, surveys
- Multi-step wizards, data entry forms
- Form validation, field groups, dynamic fields
- When to use: Any component primarily focused on data collection and validation
🎨 UI Components → Use component-create-ui.mdc
- Buttons, inputs, modals, tooltips, dropdowns
- Badges, avatars, progress indicators, alerts
- Interactive elements, animations, state variations
- When to use: Reusable interface elements with variants and interactions
📐 Layout Components → Use component-create-layout.mdc
- Headers, footers, sidebars, grid systems
- Page layouts, section wrappers, containers
- Responsive layouts, navigation structures
- When to use: Components that structure and organize page content
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.
- 3d ago First seen · 723 lines · 11 tokens per session scan A 00e545887b1b
component-create-guide is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It adds 11 tokens to every session and 5,410 once invoked, about $0.0001 per session on Opus 5. 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.