App Mockup Generation

VerifiedSafe

Generate a quick visual mockup of an app screen from DESIGN.md, published via the Artifact tool.

Sby Skills Guide Bot
DevelopmentBeginner
209/9/2026
Claude Code
#mockup#app-design#html#design-system#prototyping

Recommended for

Our review

Generates a static visual mockup of an app screen as a single self-contained HTML file, using design tokens from DESIGN.md.

Strengths

  • Enforces consistency with the design system via victory-* variables.
  • Mobile-first layout with bottom nav for realistic preview.
  • Realistic placeholder content instead of lorem ipsum.
  • Immediately viewable in the browser via an HTML artifact.

Limitations

  • Mockup is not interactive and has no functionality.
  • Requires an existing DESIGN.md with relevant tokens.
  • Limited to individual screens, not full user flows.
When to use it

When you need quick visual validation of a proposed app screen that stays true to an established design system.

When not to use it

When you need a clickable prototype or production-ready UI backed by real data.

Security analysis

Safe
Quality score85/100

The skill instructs generating a static HTML mockup and publishing via the Artifact tool. It explicitly avoids data fetching or dynamic behavior, uses only inline CSS with provided hex values, and does not involve shell commands, external resource loading, secret exfiltration, or destructive actions. No meaningful execution risk.

No concerns found

Examples

Home screen mockup
/mockup-app-skill Home screen for the fit-track app — include today's step count, a progress ring, and the bottom nav.
Onboarding welcome screen
/mockup-app-skill Onboarding welcome screen with a gradient hero, headline, and primary/secondary buttons.
Profile tab mockup
/mockup-app-skill Profile tab with avatar, stats row, settings list, and bottom nav.

/mockup-app-skill

Generate a quick visual mockup of an app screen for: $ARGUMENTS

  1. Read DESIGN.md first — use its tokens, components, and patterns exactly (colors, spacing, buttons, cards, empty states, page header/shell). Never invent new colors or fall back to generic Tailwind defaults.
  2. Render the mockup as a single self-contained HTML file (inline CSS using the victory-* hex values from DESIGN.md) and publish it with the Artifact tool so it's viewable in the browser.
  3. It's a static visual mockup, not a working page — no real data fetching or routing. Use realistic placeholder content instead of lorem ipsum.
  4. Match the mobile-first frame: max-width: 32rem centered, dark victory-bg background, bottom nav bar if the screen is a primary tab (Home/Train/Feed/Profile/etc).

Output: one Artifact link. Don't dump the markup in chat.

Related skills