make-demo
Create or revise demos in the Remix repository. Use when adding a new demo under demos/, updating an existing demo, or reviewing demo code to ensure it showcases Remix packages, strong code hygiene, and production-quality patterns.
Best for Remix repository maintainersWorks with GitHubLow risk
⌘source
- author
@remix-run- repo
- remix-run/remix
- language
- TypeScript
★33kstars
2.8kforks
Apr 21, 2026
✦overview.md
Key Features
- ·Create new demos under demos/ directory
- ·Update existing demo code
- ·Review demo code for quality standards
- ·Ensure demos showcase Remix packages
- ·Maintain production-quality patterns
- ·Model clean structure and accessibility
Use Cases
- →Adding a new demo to demonstrate specific Remix framework behavior
- →Updating an existing demo to improve code quality or showcase new patterns
- →Reviewing demo code to ensure it meets repository standards before merging
- →Creating reference artifacts that teach others how to write Remix code effectively
Best for
- ✓Remix repository maintainers
- ✓Documentation contributors
- ✓Code reviewers
Not ideal for
- !Building production applications
- !One-off experimental code
- !Projects using non-Remix frameworks
FAQs
name
make-demo
description
Create or revise demos in the Remix repository. Use when adding a new demo under demos/, updating an existing demo, or reviewing demo code to ensure it showcases Remix packages, strong code hygiene, and production-quality patterns.
Make Demo
Overview
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.
$install
1-click copynpx skills add remix-run/remix --skill make-demoSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.