agentsclimarketplace
Sign in

Etch a sketch

Skill jawsublime-byte/simon-says/skills/etch-a-sketch

Create a visible, disposable UI wireframe or prototype, review it against explicit requirements, and erase the temporary draft completely before drawing a fresh alternative when it fails. Use only when the user explicitly invokes Etch A Sketch for interface exploration. Never move a sketch into production without explicit approval.From its SKILL.md

Install
npx -y skills add jawsublime-byte/simon-says --skill etch-a-sketch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, 503 tokens by cl100k_base, as published. Nobody here has run it

Etch A Sketch

Draw first. Keep only an approved drawing.

Freeze the brief

  1. Lock the user goal, audience, required screens, essential controls and data, target viewports, design constraints, and acceptance criteria.
  2. Ask only questions that block a meaningful drawing, with a maximum of three.
  3. Choose the fastest available visual medium that produces a visible artifact, such as an HTML/CSS preview, UI component preview, Figma draft, or wireframe.
  4. Work only in a clearly identified temporary canvas.

Draw

  1. Create one visual draft. Do not substitute a prose description when a visual preview tool is available.
  2. Use mock data and an interface shell only.
  3. Do not add a backend, authentication, persistence, dependencies, production integration, or unrequested features.
  4. Render or preview the draft at every target viewport.
  5. Compare the draft with every acceptance criterion and present it for user review.

Output:

ETCH A SKETCH: DRAFT [number]
Canvas: [temporary location or artifact]
Meets: [criteria met]
Misses: [criteria missed]
Decision needed: keep | shake | amend brief

Shake

When the user rejects a draft or it fails the acceptance criteria:

  1. Preserve only the frozen brief, user feedback, and acceptance criteria.
  2. Erase or discard only the files and artifacts created inside the identified temporary canvas.
  3. Never delete or overwrite a pre-existing project file.
  4. Output SHAKE SHAKE SHAKE.
  5. Draw a fresh composition from the brief. Do not keep patching the rejected layout.

Stop after three rejected drafts unless the user authorizes more. After the third rejection, ask one question that would most improve the next attempt.

Graduate

Only an explicit instruction such as keep this or approve may graduate a sketch.

Before copying any part into the project:

  • State the production files, dependencies, and integrations that would be required.
  • Ask before adding dependencies or changing production files, databases, APIs, or authentication.
  • Distinguish approval of the visual direction from approval to implement it.
  • Never claim that a wireframe is accessible, responsive, secure, or production-ready until those properties are verified.

Completion

Finish with one of these states:

  • an approved sketch and a clear implementation handoff;
  • a cleanly discarded temporary canvas; or
  • a pause after the iteration limit.

What ships with it: 1 file

244 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.