jazz-schema-design
Jazz Data Modelling and Schema Design
When to Use This Skill
- Designing data structures for Jazz applications
- Defining CoValue schemas and relationships
- Configuring permissions at the schema level
- Planning schema evolution and migrations
- Choosing between scalar and collaborative types
- Modeling relationships between data entities
Do NOT Use This Skill For
- Writing tests for Jazz applications (use the
jazz-testingskill) - General framework integration questions (use the
jazz-ui-developmentskill) - Permissions topics outside the schema. Use the
jazz-permissions-securityskill.
Key Heuristic for Agents: If the user is asking about how to structure their data model, define relationships, configure default permissions, or evolve schemas, use this skill.
Core Concepts
More from garden-co/classic-jazz
spec
Implement features using Spec Driven Development (SDD) workflow. Creates design and task documents with approval gates.
1jazz-testing
Use this skill when you need to write, review, or debug automated tests for applications built on the Jazz framework. This skill provides the correct architectural patterns for simulating local-first synchronization and multi-user environments without resorting to invalid mocking strategies.
1benchmarking
Use this skill when writing or running performance benchmarks for Jazz packages. Covers cronometro setup, file conventions, gotchas with worker threads, and how to compare implementations.
1jazz-ui-development
Use this skill when building, debugging, or optimizing Jazz applications. It covers Jazz's bindings with various different UI frameworks, as well as how to use Jazz without a framework. Look here for details on providers and context, hooks and reactive data fetching, authentication, and specialized UI components for media and inspection.
1jazz-permissions-security
Use this skill when designing data schemas, implementing sharing workflows, or auditing access control in Jazz applications. It covers the hierarchy of Groups, Accounts, and CoValues, ensuring data is private by default and shared securely through cascading permissions and invitations.
1