UI Skills is a collection of skills and lessons for design engineers working on user interfaces. Developers and coding agents use it through a command-line interface or MCP tools to browse and retrieve design-engineering guidance. The catalogue add-ons contain selected UI skills and an instruction for using them.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ibelick/ui-skills --skill create-canvasgit clone --depth 1 https://github.com/ibelick/ui-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ibelick/ui-skills/create-canvas)<a href="https://agentmods.dev/skills/ibelick/ui-skills/create-canvas"><img src="https://agentmods.dev/badge/skills/ibelick/ui-skills/create-canvas/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ibelick/ui-skills/create-canvas"><img src="https://agentmods.dev/badge/skills/ibelick/ui-skills/create-canvas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.02602 |
| Opus 5.5 | $0.00008 | $0.01041 |
| Sonnet 5.5 | $0.00004 | $0.00520 |
| Haiku 4.5 | $0.00002 | $0.00260 |
Grade A, and why
create-canvas scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create canvas
Build a freeform workspace for exploration and iteration through conversation. The model changes content in source files. The canvas makes that content live, named, movable, and easy to reference.
Start with the project
- Read repository rules, routes, component APIs, themes, design tokens, and tests.
- Look for an existing canvas before creating another.
- Use the project's framework, components, typography, design tokens, themes, and access controls.
- Respect restrictions on edits, commands, and browser access.
- Ask before changing scope, adding dependencies, changing shared code, or exposing the canvas publicly.
- If safe isolation is unclear, ask before proceeding. Never mount an unsafe preview.
- Choose sensible defaults for other decisions. Do not ask the user to repeat clear requests.
- Keep canvas code together. Separate camera and placement logic from previews, test data, and their registry. Do not build a framework.
- Start with one safe live preview, a readable label, and a separate move handle. Make sure that it mounts.
- Add the registry and requested content next. Then add copying, camera controls, existing themes, and saved layout.
Keep content in source
A registry is a typed list of canvas items. Each entry defines a stable ID, unique readable name, component, safe test data, initial position, and dimensions.
- Keep the registry easy to find. Adding an item must not require changes to the camera or gesture code.
- Add, duplicate, rename, and remove items through source edits. Do not add runtime editor controls or delete shortcuts.
- Keep membership, names, dimensions, and implementations in source. Browser storage must not create or hide items.
- Never evaluate stored strings or model responses as code at runtime.
- Update the existing workspace for follow-up requests. Preserve names, IDs, positions, and unrelated experiments.
- If a reference is ambiguous, ask which item the user means.
- For “try another version,” preserve the original. Give each variation a new ID, unique readable name, and independent state.
- For “change this version,” update that item in place. Rename it only when asked.
- For removal requests, remove only the requested registry entry. Preserve shared components and unrelated work.
- When comparing one feature, keep other data, content, dimensions, and the global theme the same.
- For broader alternatives, name the layout differences. Do not create a full variant matrix unless requested.
- Place additions in nearby empty space using measured bounds. Reveal them with the camera without rearranging existing items or resetting the view.
- Preserve positions after content expansion, resizing, and reload. Allow intentional overlap. Keep move handles accessible when items overlap.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 163 lines · 19 tokens per session scan A a2043194d190
create-canvas is a skill published in the GitHub repository ibelick/ui-skills (10,113 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 2,602 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-21.
Other skills, from other repositories
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. Covers Glimmer design principles, workflows, and interaction models for the glasses form factor. Use this skill to build an Android XR Augmented Experience app with Jetpack Compose Glimmer.…
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
read
Fetches URLs and PDFs, then summarizes or returns clean Markdown; can also search the web through DeepSeek when built-in search is thin. Use when asked to read, fetch, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.
visual-edit
Open and collaboratively edit a running local app in Design, with shared fallback previews and source handoff. Use when the user asks to inspect, share, or edit a real local app in Design.
visual-plan
Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.