Demos in this repository are not throwaway prototypes. They are durable code artifacts that should teach people and other agents how to write Remix code well.
A good demo should:
exercise Remix framework behavior in a realistic way
push the target APIs through meaningful edge cases and composition points
model clean structure, naming, and accessibility
be code that a reader could adapt into a real application
Workflow
Read the target APIs and at least one or two existing demos before writing new code.
Choose a focused scenario that exists to demonstrate Remix behavior, not a generic app shell.
Build the demo under demos/<name>/ using the same conventions as the existing demos.
Treat the code as a reference artifact, not as temporary sample code.
Validate the demo locally before finishing.
Rules
Use Remix library packages for the demo's framework behavior. Do not introduce unrelated routers, component frameworks, state managers, or middleware stacks that distract from the Remix patterns being demonstrated.
Treat each demo as its own pnpm workspace consumer. Give it a normal package.json with remix as a dependency…
