agentleFS
WhatscheapWhatscheap/igly-canvas-plugin/skills/wireframe/SKILL.md

wireframe

Skill0 starsChanged 13 days agoMITView on GitHub

Sketch a low-fidelity wireframe or mockup of a web page, landing page, dashboard, form or mobile app screen on an editable Igly canvas. Use when the user wants to plan a layout, page structure or UI before designing it.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use make-tweakable.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bluzirSkill

    make-tweakable

    Add an in-artifact floating Tweaks panel that lets the user adjust colors, fonts, spacing, layout variants live in the preview. Persists via claude-pipe pattern (pending.yaml + apply-tweaks skill).

    Also in 3 projects that use this

The file

Files
SKILL.md

Wireframe

Low fidelity: grey boxes, real labels, no images. Use the clean font so it reads like a UI.

1. Pick the frame

  • Desktop page: frame 1440 wide. Mobile screen: 390 x 844. Dashboard: 1440 x 900.
  • List the sections top to bottom (nav, hero, features, pricing, FAQ, footer...) or the screen regions (sidebar, header, cards, table).

2. Create

create_canvas with title (e.g. "Pricing page wireframe") and, for a single screen, width/height of the frame. Keep canvas_id.

3. Elements (one add_elements call; set font_family: "Inter" on everything)

  • Frame: rectangle at (0, 0), frame size, fill: "#FFFFFF", stroke: "#1E1E1E", stroke_width: 2, corner_radius: 0 (mobile: 40).
  • Blocks: rectangles fill: "#F1F3F5", stroke: "#ADB5BD", corner_radius: 8, with the section name as text, text_color: "#495057".
  • Image placeholders: rectangle fill: "#E9ECEF" plus two type: "line" diagonals (corner to corner, stroke: "#ADB5BD").
  • Headings and copy: type: "text", color: "#1E1E1E", headline font_size: 44 bold, body 18 with a width to wrap.
  • Buttons: rectangle 180 x 52, corner_radius: 26, fill: "#1E1E1E", text_color: "#FFFFFF". Secondary: white fill, dark stroke.
  • Inputs: rectangle 360 x 48, white, stroke: "#ADB5BD", placeholder text left-aligned (align: "left").
  • Spacing: 24 inner padding, 80 between sections on desktop, 16 / 32 on mobile.
  • Annotate decisions with type: "sticky" notes outside the frame, connected by type: "arrow" with to_id the block they explain.

4. Check

  • get_canvas_summary; align columns with arrange (align_left, distribute_vertical with gap).
  • Offer a second variant beside the first (x + frame width + 200) for comparison, or export_png.

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.