The preview and package must describe the same product
A gallery card sets an expectation. The installed files must reproduce the same core sections, design tokens, interactions, assets, and responsive behavior without relying on an undisclosed service or proprietary builder.
The registry should enumerate every file and dependency so the installer can make the result predictable.
Installation must protect the destination
A responsible CLI previews the files it will add, validates target paths, refuses silent overwrites, and explains conflicts. It should leave the project with readable source and a clear way to customize content and tokens.
- Use Coordiation classes and official icon components.
- Include local assets with explicit licenses.
- Keep runtime dependencies minimal and declared.
- Provide setup, customization, and removal guidance.
Quality lives beyond the hero
A useful theme includes complete navigation, forms, long content, empty states, footers, narrow screens, keyboard behavior, and reduced-motion treatment. These are the places where a visual imitation usually breaks.
Installability is therefore a product contract: what you preview is what you own, and what you own is prepared for real content.