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.
git 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-update-card)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/component-update-card"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/component-update-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.05007 |
| Opus 5 | $0.00000 | $0.02504 |
| Sonnet 5 | $0.00000 | $0.01001 |
| Haiku 4.5 | $0.00000 | $0.00501 |
Grade A, and why
component-update-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 7d 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 — 754 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Update: Card Components
Specialized prompt for updating existing card components with advanced patterns, enhanced accessibility, performance optimizations, and modern UX features while maintaining backward compatibility.
🎯 UPDATE OBJECTIVES
1. FEATURE ENHANCEMENT
Add new capabilities to existing card components:
- Advanced interaction patterns (hover states, click behaviors, selection)
- Enhanced content slots (header actions, footer controls, overlay content)
- Dynamic sizing and layout (auto-height, aspect ratios, responsive breakpoints)
- Loading and skeleton states (progressive loading, shimmer effects)
- Animation and transitions (entrance effects, state changes, micro-interactions)
2. ACCESSIBILITY IMPROVEMENTS
Enhance existing accessibility implementation:
- Advanced ARIA patterns (live regions, expanded states, selected states)
- Keyboard navigation enhancements (arrow key navigation, focus trapping)
- Screen reader optimizations (meaningful announcements, content structure)
- High contrast and reduced motion support
- Focus management for interactive cards and card collections
3. PERFORMANCE OPTIMIZATION
Optimize existing card performance:
- Virtualization support for large card lists
- Image optimization (lazy loading, responsive images, placeholder states)
- Bundle size reduction (tree shaking, dynamic imports)
- Render optimization (memo patterns, stable references)
- Layout stability (CLS prevention, dimension management)
4. UX PATTERN MODERNIZATION
Update user experience patterns:
- Interactive card behaviors (selection, multi-select, drag and drop)
- Advanced filtering and sorting integration
- Contextual actions (quick actions, overflow menus)
- Status indicators (badges, progress bars, notifications)
- Responsive design improvements (mobile-first, touch interactions)
5. INTEGRATION ENHANCEMENTS
Improve system integration capabilities:
- Enhanced Catalyst compatibility (design token updates, theme integration)
- Form integration (card-based form layouts, validation display)
- Data loading patterns (suspense boundaries, error boundaries)
- Analytics integration (interaction tracking, performance metrics)
- Testing infrastructure (component testing, accessibility testing)
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.
- 7d ago First seen · 754 lines · 0 tokens per session scan A fea6ff889cef
component-update-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 5,007 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
pages
Source: docs/agents/pages.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
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.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
web-pages-e2e-test-maintenance
Keep web pages end-to-end coverage current.
tanstack-react-router_routing
TanStack Router: Routing.