App Mockup Generation

VerifiedSafe

Generate static visual mockups of app screens in HTML, following a predefined design system.

Sby Skills Guide Bot
DevelopmentBeginner
408/20/2026
Claude Code
#mockup#ui-design#design-system#html#mobile-first

Recommended for

Our review

Generates a self-contained HTML visual mockup of a mobile app screen based on a project's DESIGN.md design tokens, and publishes it as an Artifact for in-browser viewing.

Strengths

  • Enforces consistency by reusing styles from DESIGN.md (colors, spacing, components).
  • Produces a standalone HTML file that can be viewed immediately via Artifact.
  • Uses realistic placeholder content instead of lorem ipsum for better visual context.
  • Mobile-first with a 32rem frame and bottom nav for primary tabs.

Limitations

  • Static visual only, no interactivity or real data.
  • Requires a DESIGN.md with victory-* hex values; without it, the skill cannot be used as intended.
  • Not suitable for high-fidelity prototyping or production code.
When to use it

When you need a quick, on-brand visual for a single app screen to share or iterate on.

When not to use it

When you need a fully functional prototype with real data, interactions, or routing.

Security analysis

Safe
Quality score85/100

The skill only generates a static HTML mockup with inline CSS and publishes it as an Artifact. It does not use any shell commands, network requests, or destructive actions, and explicitly avoids real data fetching or routing.

No concerns found

Examples

Login screen
a login screen for a fitness app
Home tab
the Home tab of the app with a recent activity card
Profile screen
a profile screen with stats and a settings list

/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