agent-kit / rules
agent-kit-startup/agent-kit/.cursor/rules/cursor-skills-sql.mdc
Rules for Postgres SQL (DDL, DML, indexes, constraints). Aligned with the sql-postgres skill.
The rules real projects give Cursor's agent, from .cursor/rules.
agent-kit-startup/agent-kit/.cursor/rules/cursor-skills-sql.mdc
Rules for Postgres SQL (DDL, DML, indexes, constraints). Aligned with the sql-postgres skill.
lacymorrow/paperclip-hub/.cursor/rules/supabase-db-create-migrations.mdc
Guidelines for writing Postgres SQL
lacymorrow/paperclip-hub/.cursor/rules/supabase-db-styleguide.mdc
Guidelines for writing Postgres SQL
brettdavies/cursor-template/.cursor/rules/sql/sql-format.mdc
Supabase Postgres SQL Style Guide
brettdavies/cursor-template/.cursor/rules/sql/sql-functions.mdc
Supabase Postgres SQL Function Guide
brettdavies/cursor-template/.cursor/rules/sql/sql-migrations.mdc
Supabase Postgres SQL Migration Guide
lacymorrow/paperclip-hub/.cursor/rules/supabase-db-rls.mdc
Guidelines for writing Postgres Row Level Security policies
brettdavies/cursor-template/.cursor/rules/sql/sql-rls-policies.mdc
Supabase Postgres SQL RLS Row Level Security Guide
edhoferdian/EEF/.cursor/rules/data-layer-patterns-edho-ferdian.mdc
Design and setup guidance for the data layer — Postgres schema design, Prisma ORM patterns, Redis caching/queue patterns, and cross-ORM migration strategy (expand-contract). A design-time companion to code-review-edho-ferdian's database-lens (which reviews existing SQL/ schema/migrations) — use this when SETTING UP or DESIGNING a data layer, not when reviewing one. Trigger phrases: \"desain schema untuk X\", \"setup Prisma/Redis\", \"bagaimana strategi migration yang aman\", \"cache invalidation strategy\".
mchittineni/cloud-platform-skills/.cursor/rules/skills/aws-cloud-migration-strategies.mdc
AWS migration planning: the 6Rs framework (rehost, replatform, refactor, repurchase, retain, retire), discovery and wave planning, MGN server migration, DMS data cutover with CDC, and rollback criteria. Use when planning a datacenter exit or lease expiry, deciding whether a legacy monolith should be rehosted or refactored, or moving a large Oracle, SQL Server or Postgres database with minimal downtime.
mchittineni/cloud-platform-skills/.cursor/rules/skills/database-devops-lifecycle.mdc
Database DevOps: expand/contract zero-downtime schema migration, migration-as-code with Flyway, Liquibase and Atlas, connection pooling, replication lag, and rollback strategy. Use when adding, renaming or dropping a column on a large Postgres or MySQL table without downtime, running migrations from a deploy pipeline, or diagnosing read replicas lagging behind the primary and serving stale data.
dirnbauer/webconsulting-skills/.cursor/rules/postgres-best-practices.mdc
Use the postgres-best-practices Agent Skill when relevant; read the full skill directory before acting.
PostHog/posthog/.cursor/rules/rust.mdc
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
cohnen/mcp-google-ads/.cursor/rules/fastmcp.mdc
Use it to get full context on fastmcp
SaynaAI/sayna/.cursor/rules/axum.mdc
Comprehensive best practices for Axum 0.8+ development with WebSocket support
przeprogramowani/ai-rules-builder/.cursor/rules/supabase-migrations.mdc
description: globs: supabase/migrations/**/*.sql alwaysApply: false --- # Database: Create migration You are a Postgres Expert who loves creating secure database schemas. This project uses the migrations provided by the Supabase
danielvm-git/bigpowers/.cursor/rules/deepen-architecture.mdc
Find deepening opportunities in a codebase, informed by the domain language in specs/tech-architecture/tech-stack.md and the decisions in specs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
danielvm-git/bigpowers/.cursor/rules/migrate-spec.mdc
Detect GSD, spec-kit, or BMAD spec artifacts and transform them into bigpowers YAML layout (state.yaml, release-plan.yaml, epics/, requirements/, plans/, ADRs). Use when migrating foreign spec docs.
danielvm-git/bigpowers/.cursor/rules/model-domain.mdc
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates specs/tech-architecture/tech-stack.md and specs/adr/ inline as decisions crystallise. Use when user wants to stress-test a plan against their project's domain language and documented decisions.
danielvm-git/bigpowers/.cursor/rules/spike-prototype.mdc
Throw-away prototype for unknown problem spaces. Output is learning notes in specs/archive/spikes/SPIKE-<name>.md, not production code. Use when the domain or technology is unexplored, when estimates are impossible without experimentation, or when user says \"spike\", \"prototype\", or \"proof of concept\".
Instruction files for Cursor's agent, kept in .cursor/rules/ as .mdc files.
A rule can apply only to files matching a pattern, or only when the agent asks for it. AGENTS.md always applies.
Copy the .mdc file into your project's .cursor/rules/ directory and adjust its globs.
Open a rule to see its discussion. Reports from people and their agents are coming.