Skip to main content
cursor-reference-architecture Reference architecture for Cursor IDE projects: directory structure, rules organization, indexing
strategy, and team configuration patterns. Triggers on "cursor architecture", "cursor project structure",
"cursor best practices", "cursor file structure".
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill cursor-reference-architectureEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Más de este repositorio Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
Explorador de archivos
8 archivos Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
name cursor-reference-architecture description Reference architecture for Cursor IDE projects: directory structure, rules organization, indexing
strategy, and team configuration patterns. Triggers on "cursor architecture", "cursor project structure",
"cursor best practices", "cursor file structure".
allowed-tools Read, Write, Edit, Bash(cmd:*) version 1.18.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","cursor","cursor-reference"] compatibility Designed for Claude Code, also compatible with Codex and OpenClaw
Cursor Reference Architecture
Reference architecture patterns for optimizing Cursor IDE project setup. Covers directory structure, rules organization, indexing strategy, and multi-project configuration for maximum AI effectiveness.
Project Layout for Cursor
A well-structured project makes AI features significantly more effective:
my-project/
├── .cursor/
│ └── rules/
│ ├── project.mdc # alwaysApply: true (stack, conventions)
│ ├── security.mdc # alwaysApply: true (security constraints)
│ ├── typescript.mdc # globs: "**/*.ts,**/*.tsx"
│ ├── api-routes.mdc # globs: "src/api/**/*.ts"
│ ├── database.mdc # globs: "src/db/**/*.ts,prisma/**"
│ └── testing.mdc # globs: "**/*.test.ts,**/*.spec.ts"
├── .cursorignore # Exclude from AI + indexing
├── .cursorindexingignore # Exclude from indexing only
├── .gitignore
├── src/
│ ├── api/ # API routes
│ ├── services/ # Business logic
│ ├── db/ # Database layer
│ ├── types/ # Shared TypeScript types
│ ├── utils/ # Utility functions
│ └── components/ # UI components
├── tests/
├── prisma/
├── docs/ # Architecture docs (good for @Docs)
└── package.json
Why This Structure Helps Cursor
Glob patterns work predictably : src/api/**/*.ts cleanly scopes API rules@Files references are intuitive : @src/types/user.ts is discoverableIndexing is focused : clear separation of code vs build output vs dataRules inheritance : project-level always-on + directory-scoped rules
Rules Architecture
Layer 1: Always-On Global Rules
---
description: "Core project context and conventions"
globs: ""
alwaysApply: true
---
Stack: Next.js 15 (App Router), TypeScript 5.7 ,
PostgreSQL
16
,
Prisma
6
Auth:
NextAuth.js
v5
with
GitHub
OAuth
Styling:
Tailwind
CSS
4
Testing:
Vitest
+
Playwright
Package manager:
pnpm
-
Server
Components
by
default,
"use client"
only
when
needed
-
Repository
pattern
for
database
access
-
Zod
schemas
for
all
external
input
validation
-
Result
types
for
error
handling
(never
throw
from
services)
Layer 2: Security (Always-On)
---
description: "Security constraints for all AI-generated code"
globs: ""
alwaysApply: true
---
- NEVER hardcode secrets, API keys, or passwords
- ALWAYS use parameterized queries (no string interpolation in SQL)
- ALWAYS validate and sanitize user input with Zod
- NEVER disable CORS, CSRF protection, or TLS verification
- Use httpOnly, secure, sameSite cookies for auth tokens
- Rate limit all public API endpoints
Layer 3: Technology-Specific (Glob-Scoped)
---
description: "React component patterns"
globs: "src/components/**/*.tsx,app/**/*.tsx"
alwaysApply: false
---
- Named exports only (no default exports)
- Props interface: {ComponentName }Props
- Use forwardRef for interactive components
- Colocate tests: Component.test.tsx next to Component.tsx
- Loading states: use Suspense boundaries, not conditional rendering
---
description: "API route handler patterns"
globs: "app/api/**/*.ts,src/api/**/*.ts"
alwaysApply: false
---
- All handlers wrapped in withAuth() middleware
- Input validation with Zod (parse body, params, query)
- Response shape: { data: T } or { error: string , code: string }
- HTTP status codes: 200 OK, 201 Created, 400 Bad Request, 401 , 403 , 404 , 500
- Structured logging with requestId for traceability
---
description: "Database access patterns"
globs: "src/db/**/*.ts,src/repositories/**/*.ts,prisma/**"
alwaysApply: false
---
- All queries via repository classes (never raw Prisma in API routes)
- Use transactions for multi-table writes
- Always include select/include to avoid over-fetching
- Pagination: cursor-based for lists, offset for admin tools
- Soft delete: use deletedAt timestamp, never hard delete user data
Layer 4: Manual Reference Rules
---
description: "Deployment and infrastructure patterns"
globs: ""
alwaysApply: false
---
- Vercel for frontend, Railway for API
- Environment variables managed in Vercel/Railway dashboards
- Database migrations: `prisma migrate deploy` in CI
- Feature flags via LaunchDarkly
Reference manually with @Cursor Rules in Chat when discussing deployment.
Indexing Strategy
Optimized .cursorignore # Build output
dist/
build/
.next/
out/
.vercel/
.turbo/
coverage/
# Dependencies
node_modules/
.pnpm-store/
# Generated
*.min.js
*.min.css
*.d.ts.map
*.tsbuildinfo
pnpm-lock.yaml
# Data / Assets
*.csv
*.sql
*.sqlite
*.png
*.jpg
*.gif
*.svg
*.ico
*.woff
*.woff2
*.ttf
# Environment
.env*
# IDE
.vscode/
.idea/
.cursorindexingignore for Large References # Not indexed, but accessible via @Files
docs/api-spec.yaml
tests/fixtures/
scripts/migration-data/
Monorepo Architecture
Turborepo / pnpm Workspaces monorepo/
├── .cursor/
│ └── rules/
│ ├── monorepo.mdc # alwaysApply: true (shared conventions)
│ ├── shared-types.mdc # globs: "packages/shared/**"
│ ├── api.mdc # globs: "apps/api/**"
│ └── web.mdc # globs: "apps/web/**"
├── .cursorignore
├── apps/
│ ├── api/
│ ├── web/
│ └── admin/
├── packages/
│ ├── shared/
│ ├── ui/
│ └── config/
├── turbo.json
└── pnpm-workspace.yaml
---
description: "Monorepo import conventions"
globs: ""
alwaysApply: true
---
- Import shared types: import { User } from '@myorg/shared'
- Import UI components: import { Button } from '@myorg/ui'
- NEVER use relative paths across package boundaries
- Each package has its own tsconfig.json extending root
Configuration Files Summary File Committed to Git Purpose .cursor/rules/*.mdcYes AI behavior rules (team-shared) .cursorignoreYes File exclusion from AI + indexing .cursorindexingignoreYes File exclusion from indexing only settings.json (Cursor)No (machine-local) Editor preferences keybindings.json (Cursor)No (machine-local) Custom shortcuts
Enterprise Considerations
Rules as code : Treat .cursor/rules/ changes like infrastructure changes -- require PR reviewTemplate repository : Create a company template repo with standard rules, ignore files, and onboarding docsCompliance mapping : Map security rules to specific compliance controls (SOC 2 CC6.1, etc.)Architecture documentation : Keep docs/ directory indexed so AI can reference architecture decisions via @Docs
Resources 