toptop-design-system

Implements interactive UI prototypes using TopTop Kit component specs and design tokens.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill toptop-design-system-mjlike123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: toptop-design-system
Source: https://github.com/Mjlike123/ui-prototype-workbench/tree/main/.agents/skills/toptop-design-system
Command: npx skills add https://github.com/Mjlike123/ui-prototype-workbench --skill toptop-design-system-mjlike123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building product pages from product descriptions, screenshots, or Figma designs often leads to ad-hoc components that drift from the design system. This Skill guides an agent to implement runnable, interactive prototypes that strictly reuse TopTop Kit components, tokens, and interaction contracts, with traceable component stacks and verification results. ## Core Features & Use Cases - Kit-First Implementation: Reads principles, foundations, and component YAML specs, then maps page layers to existing componentIds before writing any code. - Component Mapping & Gap Tracking: Produces a JSON component mapping with explicit kitGaps instead of disguising missing components as similar ones, and hands off to toptop-prototype-studio for hybrid prototypes when the Kit is incomplete. - Design MVP Manifest & Verification: Delivers a manifest covering intent, component stack, interaction states, and references, then validates with specs:validate, portal:test, and portal:build. - Use Case: Given a Figma frame of a message list page, the Skill maps navigation, search, list, and tab bar to Kit components, implements all interaction states with real content, and outputs a traceable manifest. ## Quick Start Ask the agent to build an interactive prototype of your page from a product description, screenshot, or Figma link using the TopTop design system Kit.

Frequently Asked Questions about toptop-design-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a UI prototype from a Figma design with a design system?

Provide the Figma frame or screenshot and the target platform. The Skill reads the Kit's principles, foundations, and component YAML specs, outputs a component mapping first, then implements a runnable prototype reusing existing components and tokens.

What happens when the design system Kit lacks a needed component?

Missing components are recorded as kitGaps rather than disguised as similar existing components. For prototypes, the workflow switches to toptop-prototype-studio hybrid mode using base UI primitives and clearly marked prototype modules.

Does this Skill support both H5 and iOS platforms?

Yes, prototypes target H5, iOS reference, or cross-platform scopes. H5 pages are verified across common mobile viewports, keyboard, and accessible names; iOS on-device Lookin audits only start when explicitly requested.

How is a finished prototype verified against the design system?

Verification runs npm run specs:validate, portal:test, and portal:build, plus checks that components and tokens are traceable, main tasks complete, states are visible, and no new lint or type errors exist.

What are the limitations of Kit-based prototype implementation?

The Skill does not modify component YAML lifecycles, does not force arbitrary screenshot regions into existing components, and does not treat the Portal /canvas as the main coding environment. Production tasks treat missing Kit capabilities as blockers.