timbenniks-cursor-rules
This repository also configures its own agents. See what timbenniks-cursor-rules tells them →
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Audit the accessibility of this component/page. Check WCAG compliance, semantic HTML usage, keyboard navigation, ARIA attributes, and color contrast. Provide specific fixes for any issues found. Ensure all fixes maintain functionality.
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Clean up this code. Remove unused imports, dead code, console.log statements, and fix any formatting issues. Ensure the code still builds, lints, and typechecks correctly after cleanup.
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Find the root cause of this issue by analyzing error messages, logs, and code flow. Propose a minimal fix that follows project rules. Implement the fix, then validate via definition of done (build passes, lint clean, types correct). Ensure the fix doesn't introduce regressions.
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Review dependency changes in package.json. Justify each new dependency or remove unnecessary ones. Ensure dependencies align with project rules (Next.js 16, TypeScript, shadcn/ui, lucide-react, Tailwind CSS v4). Check for security vulnerabilities and prefer minimal dependency footprint.
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Verify the implementation. Ensure build passes, eslint has zero warnings, types are correct, and accessibility is respected.
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Implement this feature in small, safe diffs following all project rules. Use server components by default, justify any client components, use shadcn/ui components, ensure full type safety, and validate all inputs on the server. Ask clarifying questions if requirements are ambiguous. Keep changes minimal and focused.…
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Create a short implementation plan for this feature/task. Break it down into clear steps, identify required routes, components, data models, and acceptance criteria. Ask clarifying questions if requirements are ambiguous. Keep the plan actionable and minimal. Do not start coding until the plan is approved.
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Prepare this code for a pull request. Verify build passes, eslint has zero warnings, types are correct, accessibility is respected, and all project rules are followed. Generate a clean PR summary with.
timbenniks/timbenniks-cursor-rules
Command Claude CodeCursor
Refactor the code to make it DRY, concise, with clarity and great architecture, without changing behavior. Keep changes minimal and safe.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: