Claude Skills
SkillsResultsReplayCollectionsGuidesNominate
© 2026 Curated Agent SkillsBrowse skillsHistorical indexAbout this guide·Learn more about Agent Skills
← All curated skills

Prototyping · Emil Kowalski

Prototype by Emil Kowalski

Builds genuinely different UI variants behind a visual picker so design direction can be compared in context.

View original skill instructionsEmil Kowalski Design Skills

Setup and compatibility

Part of Emil Kowalski Design Skills. This is a specialist collection, not a complete product-development lifecycle. Its animation opinions are intentionally strong, some guidance is tied to Emil’s preferred libraries, two lookup skills require explicit invocation, and the Swift reference sits outside the otherwise focused design-and-motion arc.

Editorial compatibility guidance: Claude Code · Codex · Cursor. This is not an executed compatibility test; see the review for source and run evidence.

Read Prototype instructions and prerequisites · Read Emil Kowalski Design Skills setup documentation

Independent review

Prototype addresses a common agent failure: converging on the first plausible UI and presenting cosmetic variants as exploration. By requiring materially different directions in a live picker, it turns subjective design choice into a fast comparison rather than a long prompt negotiation.

Read the Prototype review and usage guide

Try this skill

InstallGet starter request

Install · Individual skill

Run in a terminal from your target project. Requires Node.js 22.20+, npm/npx, Git and network access.

npx skills@latest add emilkowalski/skills --skill prototype -a claude-code

Command / route checked 30 October 2026. Upstream installationCLI optionsAgent support

Setup requirements and caveats

Run in a terminal from the target project. Requires Node.js 22.20+ (current skills CLI), npm/npx, Git and network access. Review the installer summary before confirming. Keeps this skill’s supporting files.

These are documented requirements; installation has not been tested here.

Your agent needs its own account, runtime and model access. Usage charges depend on your plan; unrecorded costs are unknown.

Run the example

Start a fresh session in the target project. Provide the relevant files or diff. This is the review’s example request, not a record of your execution.

Use the prototype skill. Prototype three genuinely different approaches to a hold-to-delete control and put them behind a picker so we can choose by feel.

Check your result · Successful first run

Three working hold-to-delete variants with a picker for comparison.

Confirm the agent loaded the named skill, inspect the output and run the relevant checks. Installation alone does not prove a successful run.

Something not working?

The skill is missing from my agent

Check that the skill is installed for the selected agent and project/global scope. Open a fresh session in that project and check the agent’s skill list. Plugin installs may also need to be enabled.

The wrong skill runs, or nothing happens

Start a fresh conversation, explicitly name the skill using the request above, and provide the requested inputs. Ask the agent to confirm which skill it loaded. Check for duplicate installed copies or overlapping instructions.

The skill runs but the result is poor

Compare the result with the successful-first-run check above. Supply the missing files, reproduction steps or constraints, then ask for one focused correction. If the skill addresses a different problem, return to the task guide and compare alternatives.

Installation troubleshooting · missing dependencies

If npx fails, check the Node/npm versions in setup requirements, Git and network access. For skills CLI installs, run npx skills list (add -g for global). If a route changed, follow upstream instructions.

Collection background and tradeoffs

This is a specialist collection, not a complete product-development lifecycle. Its animation opinions are intentionally strong, some guidance is tied to Emil’s preferred libraries, two lookup skills require explicit invocation, and the Swift reference sits outside the otherwise focused design-and-motion arc.

Source maintained by Emil Kowalski. Read original skill. Compatibility guidance and published showcase runs remain separate from your first run.

Related workflows

  • Design Skill Collection
  • Interface Design and Prototyping