Setting up Rules for Cursor

Create Cursor rules that point the model at canonical CreatorCommerce references instead of duplicated technical detail.

Configure Cursor rules so the model knows where CreatorCommerce truth lives and which implementation patterns it should follow.

What Your Rules Should Enforce

• Reference pages are canonical for facts.
• The glossary is canonical for terminology.
• Liquid creator resolution should follow the documented cc_creator pattern.
• Custom fields should be read from the correct level instead of guessed.
• API work should route through the Unified API references and authentication guidance.

Recommended Rule Topics

• Creator resolution and fallbacks:
  • Referencing Creator Content
• Custom field scoping:
  • Custom Fields Reference
• API and auth:
  • Unified API Reference
  • Authentication
• Documentation behavior:
  • Documentation Contract

Starter Rules File

# CreatorCommerce Development Rules

When working with CreatorCommerce:
- Treat `/references/*` pages as canonical for facts, fields, payloads, and stable implementation details.
- Use `/guides/glossary` as the canonical terminology source.
- Use `/references/sdk/referencing-creator-content` for creator resolution and Liquid access patterns.
- Use `/references/custom-fields-reference` for field naming and level-specific access.
- Use `/guides/authentication` and `/references/unified-api-reference` for Unified API work.
- Prefer summaries plus links over copying canonical technical detail into new docs.

See the Cursor documentation for tool-specific rule syntax and configuration options.

Related Resources

• Coding in Cursor
• Documentation Contract
• Referencing Creator Content