database

database is a cursor rule for Cursor from lacymorrow/paperclip-hub. It costs 0 tokens per session (772 once invoked), scanned A, original, MIT.

Database guidelines cover data modeling, field types, indexes, naming, and compatibility with external services.

In plain words
What is it for?
Use them when designing tables, choosing fields, adding indexes, integrating payment or other providers, and preserving older data formats.
Why use it?
They help prevent unclear schemas, slow queries, lost provider data, and breaking changes when data moves between systems.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use them when designing tables, choosing fields, adding indexes, integrating payment or other providers, and preserving older data formats.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/lacymorrow/paperclip-hub/database
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.

Clone the repo
git clone --depth 1 https://github.com/lacymorrow/paperclip-hub

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for database

README.md
[![agentmods](https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/database/github.svg)](https://agentmods.dev/rules/lacymorrow/paperclip-hub/database)
Your own site
<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/database"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/database/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for database

Your own site · 80×15
<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/database"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/database.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 772 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00772
Opus 5.5 $0.00000 $0.00309
Sonnet 5.5 $0.00000 $0.00154
Haiku 4.5 $0.00000 $0.00077

Measured yesterday against content hash f1c22f0441ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

database 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 yesterday.

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/database.mdc · 127 lines

How it starts

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

Database Best Practices

Data Modeling

  • Use meaningful and consistent naming
  • Define clear relationships between entities
  • Use appropriate data types
  • Implement proper indexing
  • Consider query patterns
  • Plan for scalability
  • Document schema design

Field Types

  • Use dates instead of booleans
    • ❌ isActive: boolean
    • ✅ activeAt: Date
    • ❌ isDeleted: boolean
    • ✅ deletedAt: Date
  • Use enums for fixed values
  • Use JSON for flexible structures
  • Use proper numeric types
  • Consider storage implications

Field Consistency and Provider Integration

  • ALWAYS store critical data in multiple compatible fields when dealing with external providers
  • NEVER assume external systems use your field naming conventions
  • Use fallback logic when reading data that could exist in multiple fields
    • ✅ payment.orderId || payment.processorOrderId || ""
    • ❌ payment.orderId ?? ""
  • Document which providers populate which fields in src/server/providers/
  • Test complete data flow from provider import to UI display
  • Maintain backward compatibility when adding new fields
  • Example from payments table:
    // Store in both fields for compatibility
    orderId: processorOrderId,           // For display compatibility
    processorOrderId: processorOrderId,  // For provider-specific operations
    

Relationships

  • Define foreign key constraints
  • Use junction tables for many-to-many
  • Consider denormalization when needed
  • Document relationship types
  • Plan for cascading operations
  • Handle circular references
  • Consider query performance

Webhook Data Patterns

  • Store webhook event IDs for idempotency checks
  • Use database transactions for atomic webhook processing
  • Implement proper indexes on webhook event lookup fields
  • Store webhook processing status and timestamps
  • Use proper data types for webhook payload storage (JSON/JSONB)
  • Implement webhook event deduplication at database level
  • Create audit trails for webhook-triggered data changes
  • Handle webhook event ordering and dependencies
  • Use database locks to prevent race conditions in webhook processing
  • Store webhook retry attempts and failure reasons

Read the full file on GitHub · 127 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. yesterday First seen · 127 lines · 772 tokens per session scan A f1c22f0441ab

Subscribe to this mod's changes

database is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 772 tokens. 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-11-10.

Related

database compared with cursor rules from other repositories

database next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
databaselacymorrow/paperclip-hubCursor rule15yesterdayMITA0Cursor
databasefirst-fluke/fullstack-starterCursor rule2262d agoMITA0Cursor
database-designvibestackdev/vibe-stackCursor rule8yesterdayMITA0Cursor
supabase-auth-securityvibestackdev/vibe-stackCursor rule8yesterdayMITA0Cursor
supabase-ssr-onlyvibestackdev/vibe-stackCursor rule8yesterdayMITA0Cursor
supabase-rlsvibestackdev/vibe-stackCursor rule8yesterdayMITA0Cursor
server-actionskrivoox/agent-stack-templateCursor rule301mo agoMITA0Cursor