agentleFS
hellocrossmanwildhellocrossmanwild/Claude-skills-tools/skills/sketch-it/SKILL.md

sketch-it

Skill0 starsChanged 38 days agoMITView on GitHub

Shows an app before any code: screen list, text wireframes, layout and flow options, then mockups. Use for 'wireframe', 'sketch my app', 'what screens do I need' or 'mockup'.

The file

Files
SKILL.md

Sketch it

You're helping someone who doesn't code see their app before it's built. Words hide gaps; sketches show them. Work from their brief if they have one.

1. List the screens

List every screen the app needs and what's on each one. Then push on the gaps: Is there a sign-in screen? What does each screen look like before there's any data? What does someone see after they've paid? What happens on an error? Show the list as options they can tick, and have them tick only what's in version one. The rest goes on the Later list.

2. Sketch them in text

Draw each version-one screen as a text wireframe using plain keyboard characters (boxes, lines, labels). Keep them ugly on purpose: you're judging what's on the screen and in what order, not colours or fonts. Do the key screens properly and rough out the rest.

3. Never take the first layout

For the most important screen, give three genuinely different layouts as text wireframes, side by side. Let them pick or mix ("option B's layout with option A's header").

4. Compare flows

Show two different ways someone gets from landing on the app to the main goal (for example, landing to paying), as simple step diagrams. For each, count the clicks and check for dead ends: points where someone wouldn't know what to do next (for example, "what if nothing's available this week?"). Recommend the shortest, clearest flow with no dead ends, and add any escape routes it needs.

5. Make the key pages look real

Take the winning layout and flow and turn the 2–3 most important pages into plain mockups (an artifact or design canvas if available), using standard, clean components. No brand, no colour scheme yet: you're judging the experience. Ask: can someone see what to do next? Is anything missing? Change them until it clicks.

6. Save everything

Gather the chosen sketches, the flow and the mockups into one file they can export and keep next to their brief. When building starts, these go into the project so Claude builds from pictures, not paragraphs.

Reuse this skill for every new feature later, smaller: list the screens it touches, sketch with options, one mockup, save.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.