Setting up Rules for Claude Code

Create Claude Code rules that anchor implementation work to CreatorCommerce canonical references.

Configure Claude Code rules so the model uses the right CreatorCommerce references instead of inventing field names or relying on duplicated summaries.

What Your Rules Should Enforce

• Reference pages are canonical for facts.
• The glossary is canonical for terminology.
• Creator resolution should follow the documented Liquid pattern.
• Custom field access should respect creator, drop, and product scope.
• Unified API work should use the published API and authentication references.

Recommended Rule Topics

• Creator data access:
  • Referencing Creator Content
• Custom fields:
  • 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.

Refer to your Claude Code documentation for the exact config location and syntax in your environment.

Related Resources

• Coding in Claude Code
• Documentation Contract
• Referencing Creator Content