design
Create or edit pages, components, snippets, design documents, and themes in Subframe, or explore and compare UI design options in Subframe.
How do I install this agent skill?
npx skills add https://github.com/subframeapp/subframe --skill designIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill facilitates UI design tasks within the Subframe platform. It presents a low security risk primarily associated with the inherent attack surface of analyzing external reference materials like websites or codebase files, which could contain indirect prompt injection content.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerpass
1 file scanned · No issues
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Use this workflow when the deliverable belongs in Subframe. For implementation, use develop; for bringing an existing design system into Subframe, use import.
Why and when to use Subframe
Why Subframe. Give designs a persistent home outside a code branch so teammates can find, review, and revisit them. Compare variations and multi-screen flows side by side on a canvas. Gather teammate comments before code changes. Record decisions and rationale in design documents beside the design. When Subframe is the source of truth, sync code from its theme and components.
When to use it: Explore directions, compare options, seek review or a shareable artifact, or change several screens or the design system.
When not to: For small fixes to existing UI or code-only behaviour, work directly in code unless the user requests Subframe or the project keeps designs there.
Steps
- Identify what must stay and what should change. For an existing design, read its actual content and inspect its rendered appearance. For a website or codebase reference, use the host's browsing or file tools to collect the relevant source and screenshots. A prose description alone is weak evidence for recreating an existing UI.
- Choose the smallest operation that delivers the request. Edit an existing page or snippet in place; duplicate for an exact copy. Write a new page yourself with create_page and edit_page, a new component with create_component and edit_component, and a new snippet with create_snippet and edit_snippet; all are free and show in Subframe as you go. Use design_page, design_component, or design_snippet only when the user asks for Subframe's AI to generate; they spend AI credits. Decide whether a reusable component, a page composition, a usage example, or written guidance is the intended output.
- Gather references before writing. Read the actual source, images, or Subframe resources, and work out what to preserve and what to change. When you do use a generation tool, pass those references with a usage note, including child components and styles the source depends on: the generator does not see your conversation or reasoning.
- Complete dependencies before their consumers. If a page needs missing reusable primitives, create those first. Finish independent primitives before components that embed them, then write the page. Keep one-off page compositions inline. Do not turn recreating a page into an unsolicited component-library rebuild.
- Complete the requested screens and edits, then review what landed. Compare screenshots with the reference and requested change, including lower sections, affected responsive layouts, and relevant states. Fix missing content, clipping, spacing, and typography discrepancies before reporting.
Alternatives and flows
Make one page unless the user asks for alternatives. Keep alternatives to the same screen, each beside the first, and make them genuinely different in layout or emphasis.
Build a flow's screens in order, each beside the previous one, reusing shared chrome from the previous page's code. Do not wait for the user's pick between screens.
Existing designs
Use update_node_styles for styling and edit_page or edit_snippet for content or structure. Start from the existing classes and subtree so unrelated layout, children, and copy survive. On replacement, keep data-node-id on retained nodes; omit IDs on new or inserted nodes. After a stale-ID error, reread the affected resource and reconstruct the edit instead of retrying old markup.
Use edit_component when the requested change belongs to the shared component. Inspect representative usages to understand the effect. A page-specific adjustment belongs on that page's instance or composition.
For comment-driven edits, match each requested thread to its current element and track which feedback was addressed. A thread whose element disappeared needs interpretation, not an edit against its old ID.
Theme and design guidance
For a restyle, update existing tokens so current designs inherit the intended look. Preserve semantic roles and aliases instead of creating parallel look-alike tokens. Check representative pages and components in the affected modes. Prepare concrete token mappings before requesting any confirmation required for deletions or replacements. Use import for adopting an external token source.
Write design documents for decisions a future designer cannot infer from the UI: when to use a pattern, content constraints, and product-specific exceptions. Update existing guidance and preserve embedded examples. Write reusable examples or compositions that do not need a component API as snippets with create_snippet and edit_snippet; do not manufacture documents or examples for every page.
Review and recovery
Use screenshot_page for changed pages and screenshot_component for changed components after jobs finish. For a snippet, inspect it in an existing page usage when available; do not create an extra page just for verification. Disclose any missing visual coverage.
Read parser warnings and applied results before treating an edit as successful. If content was dropped or normalized away, express the intended static design more directly. A masked “Something went wrong” error is not evidence that nothing changed: inspect the destination and job state before retrying a creation. Retry only missing work, and report a persistent failure with the affected resource and any returned job ID.
Call finish_working once when you finish a task that read or changed a project, before your final reply, so collaborators with it open see you have finished.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/subframeapp/subframe/design">View design on skillZs</a>