Generate app screen mockups

VerifiedSafe

Create a static visual mockup of an app screen in HTML/CSS, using the existing design system and published as an artifact.

Sby Skills Guide Bot
DevelopmentBeginner
209/7/2026
Claude Code
#ui-mockup#html#design-system#artifact#prototyping

Recommended for

Our review

Generates a quick visual mockup of an app screen as a standalone HTML file, following the design system defined in DESIGN.md.

Strengths

  • Strictly follows tokens and components from the provided design system.
  • Outputs a self-contained HTML file viewable right away via the Artifact tool.
  • Uses a mobile-first layout with proper frame and bottom navigation.
  • Fills with realistic placeholder content instead of lorem ipsum.

Limitations

  • Static visual only—no interactivity or live data.
  • Requires a complete DESIGN.md to be present.
  • Relies on the Artifact tool for in-browser preview.
When to use it

When you need a quick, on-brand screen mockup to share with stakeholders before building the real UI.

When not to use it

When you need a working prototype with navigation, data fetching, or any functional logic.

Security analysis

Safe
Quality score82/100

The skill only instructs generating a static HTML mockup and publishing it via the Artifact tool. It does not use shell commands, network requests, file deletion, data exfiltration, or obfuscated code. No meaningful execution risk.

No concerns found

Examples

Train booking screen
/mockup-app-skill Train booking search screen with origin/destination fields and a search button
Profile tab
/mockup-app-skill Profile screen with user info, stats, and logout button
Empty state
/mockup-app-skill Empty state for notifications tab with a bell icon and a 'No notifications yet' message

/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