Automated summary
Generates a static visual mockup of an app screen from a DESIGN.md file, producing a self-contained HTML file with realistic placeholders.
Strengths
- Strictly adheres to the design system (colors, components, spacing) defined in DESIGN.md
- Produces a self-contained HTML file viewable directly in the browser via the Artifact tool
- Mobile-first optimized with centered container max-width: 32rem and bottom nav bar for primary tabs
Limitations
- Requires a pre-existing DESIGN.md file with all design specifications
- Does not generate a functional page (no real data or routing)
- Output is an Artifact link; the HTML code is not displayed in chat
Best for quickly prototyping an app screen while adhering to an existing design system.
Not suitable when you need an interactive page with dynamic data or backend functionality.
Security analysis
SafeThe skill only generates a static HTML mockup using a design file and the Artifact tool; no destructive or exfiltrating actions are instructed, and no dangerous tools are used.
No concerns found
How this analysis is madeExamples
Generate a quick visual mockup of an app screen for a fitness tracker home screen.Generate a quick visual mockup of an app screen for an e-commerce product detail page./mockup-app-skill
Generate a quick visual mockup of an app screen for: $ARGUMENTS
- Read
DESIGN.mdfirst — 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. - Render the mockup as a single self-contained HTML file (inline CSS using the
victory-*hex values fromDESIGN.md) and publish it with the Artifact tool so it's viewable in the browser. - It's a static visual mockup, not a working page — no real data fetching or routing. Use realistic placeholder content instead of lorem ipsum.
- Match the mobile-first frame:
max-width: 32remcentered, darkvictory-bgbackground, 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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/app-screen-mockup-generation-ms71b41r/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/app-screen-mockup-generation-ms71b41r' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/app-screen-mockup-generation-ms71b41r/download' --output '.skill-downloads/app-screen-mockup-generation-ms71b41r/SKILL.md.part' && mv '.skill-downloads/app-screen-mockup-generation-ms71b41r/SKILL.md.part' '.skill-downloads/app-screen-mockup-generation-ms71b41r/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/app-screen-mockup-generation-ms71b41r/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.