toptop-design-bundle

Use toptop-prototype-studio when the Kit is incomplete and you need hybrid prototypes combining stable components, base primitives, and creative modules. Use toptop-design-system when a fairly complete Kit exists and you need strict production page implementation.

The Kit defines boundaries via YAML specs, a local Cursor Agent builds runnable prototypes, Skills perform visual and interaction acceptance, and H5 or iOS Lookin runtime audits close the loop. The Portal provides docs, previews, and a Catalog API but hosts no models.

No. The Portal is read-only and can be deployed externally to provide documentation, component previews, and the Catalog API. All inference and code changes run in the user's local Cursor or similar Agent IDE.

The specs/**/*.yaml files are the single source of truth, read in order: PROJECT.md, core-design-principles.yaml, foundations YAML, the relevant component YAML, its MDX content, and interaction specs. Skills must never invent components or tokens.

Do not use it for actual implementation or review work. It only provides package-level explanation and routing; concrete building goes to toptop-design-system or toptop-prototype-studio, and review goes to toptop-design-review.