cursorrules

A set of coding rules for a Next.js web application using TypeScript, Tailwind CSS, and shadcn/ui. It covers project instructions, page structure, server and browser code, components, and package-manager conventions.

In plain words
What is it for?
Use it when building or changing pages, layouts, components, and other full-stack TypeScript code in this Next.js project.
Why use it?
It gives an AI coding agent project-specific boundaries so new code matches the existing architecture and style. It also clarifies when browser-only code and interactive components are appropriate.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/rizkyhaksono/portfolio-v3/cursorrules
Clone the repo
git clone --depth 1 https://github.com/rizkyhaksono/portfolio-v3

Made for: Cursor.

Per session 673 This file is loaded in full into every session.
When invoked 673 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00673 $0.00673
Opus 5 $0.00336 $0.00336
Sonnet 5 $0.00135 $0.00135
Haiku 4.5 $0.00067 $0.00067

Measured 2d ago against content hash 57170484fd33, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 2d 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.

.cursorrules · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cursor Rules for Portfolio v3

Canonical cross-agent instructions: AGENTS.md
UI design system: docs/ui/README.md

You are an expert full-stack TypeScript engineer working on this Next.js project. Produce production-ready code that follows modern Next.js App Router patterns and best practices.

Core Directives

  1. Always refer to AGENTS.md and .cursor/rules/*.mdc (Next.js, project management, unit testing, UI layout consistency).
  2. Platform instruction map:
    • All agents: AGENTS.md
    • Cursor: .cursorrules + .cursor/rules/*.mdc
    • Claude: CLAUDE.md + .claude/
    • Gemini: .geminirules / GEMINI.md
    • Copilot: .github/copilot-instructions.md
    • UI docs: docs/ui/
  3. Adhere strictly to the Next.js 15+ App Router, TypeScript (strict mode), Tailwind CSS, and shadcn/ui.
  4. Use npm as the standard package manager.

Quick Reference

  • React Server Components (RSC): Default to Server Components. Add 'use client' only when hook/state/browser interactivity is necessary.
  • Components: Avoid inline styling. Rely wholly on Tailwind UI utilities and cn() from @/lib/utils.
  • Architecture: app/ is for routes and layouts. components/ui/ is for reusable Shadcn widgets. Feature logic in components/[feature]/ or app/_components/. Extricate reusable hook logic to lib/ or hooks/.
  • Quality: Keep functions modular, readable, and typed. Do not rely on any.
  • Progress: Read/update prd/feature.md and prd/progress.md for tracked work.

UI Layout (mandatory)

Monochrome, square, hairline borders. Three surface dialects only — see .cursor/rules/ui-layout-consistency.mdc, docs/ui/, and src/lib/design-system.ts:

Dialect Primitive Use
solid Card / FeatureCard / Surface Content boxes
glass MacWindow / Surface variant="glass" Window chrome only
inset Surface variant="inset" Nested rows / sidebar blocks

Read the full file on GitHub · 46 lines

Changes

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.

  1. 2d ago First seen · 46 lines · 673 tokens per session scan A 57170484fd33

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository rizkyhaksono/portfolio-v3 (6 stars, last pushed 3d ago), licensed MIT. It adds 673 tokens to every session, about $0.0034 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.