Build Tales Cursor Rules Pack

This directory holds a modular Cursor rules pack derived from the canonical .cursorrules file. The pack splits guidance into smaller, scoped instructions so Cursor can load just the context it needs.

⚠️ IMPORTANT: .cursorrules is the canonical source of truth. This modular pack is provided for convenience and newer Cursor versions that support scoped rules.

Layout

• rules/00-foundation.md – core mission, audience, and brand voice.
• rules/10-structure.md – canonical article structure, callouts, diagrams, and SEO rules.
• rules/20-payments.md – domain constraints for ACH, wires, crypto, and compliance-heavy articles.
• rules/30-leadership.md – direction for engineering culture, incident response, and leadership stories.
• rules/40-site-delivery.md – static-site stack details plus CI/CD and Netlify expectations.
• rules/50-workflow.md – research workflow, testing checklist, analytics, and contact-form behaviors.

Using the rules in Cursor

1. Create the Cursor directory if it does not exist:

   mkdir -p .cursor/rules
   

2. Copy or symlink this pack:

   rsync -av cursor/rules/ .cursor/rules/
   # or ln -sfn $(pwd)/cursor/rules $(pwd)/.cursor/rules
   

3. Restart Cursor (or run “Reload Rules” from the command palette) so it ingests the updated files.

Cursor will merge these scoped rules with any personal rules you keep in ~/.cursorrules.

Maintenance checklist

• Update .cursorrules first when the brand voice, stack, or guidelines change—it is the canonical source.
• Regenerate or manually sync the relevant modular rule files from .cursorrules as needed.
• Add new files (e.g., 60-ai-governance.md) instead of bloating existing ones past ~200 lines.
• Document any rule-specific commands, datasets, or tokens directly inside files so Cursor understands them without extra prompts.
• When in doubt, refer to .cursorrules as the authoritative reference.