general

A general set of project rules for a web application built with Next.js, Tailwind CSS, PostgreSQL, and related tools. It covers code quality, consistency, testing, documentation, and the main project structure.

In plain words
What is it for?
Use it as a baseline when building or editing frontend pages, server actions, database code, authentication, and deployment-related work.
Why use it?
It gives a coding agent shared expectations for how to make changes that fit the existing application and are easier to maintain.

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/materialize-labs/ai-optimized-starter-app/general
Clone the repo
git clone --depth 1 https://github.com/materialize-labs/ai-optimized-starter-app

Made for: Cursor.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 759 The whole file, excluding the scripts and references it only reads on demand.
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.00007 $0.00759
Opus 5 $0.00003 $0.00380
Sonnet 5 $0.00001 $0.00152
Haiku 4.5 $0.00001 $0.00076

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

Security

Grade A, and why

general 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.

.cursor/rules/general.mdc · 112 lines

How it starts

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

Project Guidelines

These guidelines serve as the foundation for our application development. Adhere to these principles to ensure consistency and quality across the codebase.

Core Principles

  • Complete Implementation: Write thorough, complete code for every feature
  • Consistency: Follow established patterns throughout the codebase
  • Quality: Focus on writing clean, maintainable, and tested code
  • Documentation: Include appropriate comments and documentation

Tech Stack Overview

Our application uses a modern, full-stack architecture:

  • Frontend:

    • Next.js with App Router
    • Tailwind CSS for styling
    • Shadcn UI component library
    • Framer Motion for animations
  • Backend:

    • PostgreSQL via Supabase
    • Drizzle ORM for type-safe database access
    • Next.js Server Actions for API layer
  • Infrastructure:

    • Authentication via Clerk
    • Deployment on Vercel

Project Structure

/
├── actions/             # Server actions
│   ├── db/              # Database-related actions
│   └── ...              # Other action categories
├── app/                 # Next.js app router
│   ├── api/             # API routes
│   └── [route]/         # App routes
│       ├── _components/ # Route-specific components
│       ├── layout.tsx   # Route layout
│       └── page.tsx     # Route page
├── components/          # Shared components
│   ├── ui/              # UI components
│   └── utilities/       # Utility components
├── db/                  # Database
│   └── schema/          # Database schemas
├── lib/                 # Library code
│   └── hooks/           # Custom hooks
├── prompts/             # Prompt files
├── public/              # Static assets
└── types/               # Type definitions

General Coding Standards

File & Folder Naming

  • Use kebab-case for all files and folders (e.g., user-profile.tsx)
  • Component files should match their component names in kebab-case

Import Conventions

  • Use @/ alias for imports from the app root
    // Correct
    import { Button } from "@/components/ui/button"
    
    // Incorrect
    import { Button } from "../../components/ui/button"
    
  • Group imports logically (React/Next.js, third-party, internal)

Read the full file on GitHub · 112 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 · 112 lines · 7 tokens per session scan A a049e635c170

Subscribe to this mod's changes

general is a cursor rule published in the GitHub repository materialize-labs/ai-optimized-starter-app (16 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 759 once invoked, about $0.0000 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-30.