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-cardgit 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-card)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-create-card"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-create-card.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.04177 |
| Opus 5 | $0.00000 | $0.02089 |
| Sonnet 5 | $0.00000 | $0.00835 |
| Haiku 4.5 | $0.00000 | $0.00418 |
Grade A, and why
component-create-card 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 — 563 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Card Component Creation Request
Please create a new card component following our data display patterns and content organization standards:
🎯 CARD COMPONENT CREATION OBJECTIVES:
- ORGANIZE content effectively with clear visual hierarchy and structured information display
- PROVIDE flexible composition with configurable sections and content slots
- IMPLEMENT responsive design with consistent spacing and mobile-optimized layouts
- ENSURE accessibility with proper semantic structure and keyboard navigation
- FOLLOW project standards for TypeScript, testing, and component architecture
📋 CARD DEVELOPMENT METHODOLOGY:
STEP 1: Card Planning and Content Architecture
Determine Card Type and Location:
- Server Component:
src/components/server/cards/- Static content display, data cards - Client Component:
src/components/client/cards/- Interactive cards with user actions - Card Categories:
- Data Cards: User profiles, statistics, metrics display (
data/) - Content Cards: Articles, posts, media content (
content/) - Action Cards: CTAs, forms, interactive elements (
action/) - Product Cards: E-commerce, catalog items (
product/) - Navigation Cards: Links, menu items, feature highlights (
navigation/)
- Data Cards: User profiles, statistics, metrics display (
Content Structure Assessment:
- Header section: Title, subtitle, actions, status indicators
- Body content: Main content area with flexible layout
- Footer section: Actions, metadata, navigation elements
- Media integration: Images, videos, icons, avatars
- Interactive elements: Buttons, links, hover states
STEP 2: Card Variants and States Design
Card Variant System:
// Define comprehensive card variants
interface CardVariants {
/** Visual appearance variant */
variant: 'default' | 'outlined' | 'elevated' | 'flat' | 'ghost';
/** Size configuration */
size: 'sm' | 'md' | 'lg' | 'xl' | 'auto';
/** Content density */
density: 'compact' | 'normal' | 'comfortable';
/** Interactive state */
interactive?: boolean;
/** Loading state */
loading?: boolean;
/** Selection state */
selected?: boolean;
}
// Card state management
interface CardStates {
/** Hover interaction state */
isHovered: boolean;
/** Focus state for keyboard navigation */
isFocused: boolean;
/** Active/pressed state */
isActive: boolean;
/** Loading/async operation state */
isLoading: boolean;
/** Error state */
hasError: boolean;
}
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 · 563 lines · 0 tokens per session scan A 7e432b2e7953
component-create-card 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 4,177 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
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
shadcn-tailwind-guide
本规范定义了使用 shadcn/ui 和 Tailwind CSS 开发新组件的标准流程和最佳实践。.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.