Dexie.js

Implement Dexie as a production data layer, not as scattered table calls inside UI components.

Workflow

1. Classify runtime and rendering mode

• Confirm whether the target code runs only in browser or can run on server too.
• Prevent Dexie usage on server runtimes in Next.js, TanStack Start, and SvelteKit.
• Load references/framework-integration.md before writing framework-specific code.

2. Design schema from query shapes

• List read queries first (filters, sorts, ranges), then derive indexes.
• Use compound and multi-entry indexes when queries require them.
• Keep key strategy explicit (++id, custom IDs, or compound primary key).
• Load references/core-patterns.md sections 2 and 3.