Skip to content
Skills Library
Design & UX · Planning

ui-composition

/ui-composition

Compose product screens, components, forms, tables, navigation, and landing or pricing sections from the existing design system with the fewest elements that let the user act. Use when building or changing a screen or flow, including small tweaks, and before adding a button, badge, card, filter, banner, or block of explanatory text, even when the request only names a feature. Not for the wording of labels, errors, and messages (ui-copy), module and API boundaries (software-design), or documentation (docs-writing).

Repository
skills ↗
Licence
MIT
Last repository change
19.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Compose product screens, components, forms, tables, navigation, and landing or pricing sections from the existing design system with the fewest elements that let the user act. Use when building or changing a screen or flow, including small tweaks, and before adding a button, badge, card, filter, banner, or block of explanatory text, even when the request only names a feature. Not for the wording of labels, errors, and messages (ui-copy), module and API boundaries (software-design), or documentation (docs-writing).

Original author description

Compose product screens, components, forms, tables, navigation, and landing or pricing sections from the existing design system with the fewest elements that let the user act. Use when building or changing a screen or flow, including small tweaks, and before adding a button, badge, card, filter, banner, or block of explanatory text, even when the request only names a feature. Not for the wording of labels, errors, and messages (ui-copy), module and API boundaries (software-design), or documentation (docs-writing).

How it works

  1. Start from what exists
  2. Give each view one next step
  3. Ask less in forms
  4. Gotchas
  5. Finish
Original SKILL.md headings · 36 lines, 562 words
SKILL.md preview
---
name: ui-composition
description: Compose product screens, components, forms, tables, navigation, and landing or pricing sections from the existing design system with the fewest elements that let the user act. Use when building or changing a screen or flow, including small tweaks, and before adding a button, badge, card, filter, banner, or block of explanatory text, even when the request only names a feature. Not for the wording of labels, errors, and messages (ui-copy), module and API boundaries (software-design), or documentation (docs-writing).
license: MIT
---

# Compose screens with less

Build each screen from what the project already has, give it one obvious next step, and remove every element that does not help the user act. Judge the composed screen at desktop and mobile widths, not components in isolation.

## Start from what exists

Read the project's design source of truth first: `DESIGN.md`, the design-system docs, or the interface guide. If none exists, say so before inventing conventions, because an undocumented system is the main reason agents improvise.

Use the design system's components and tokens. Before building a button group, table, filter, form, sign-in, pricing, or dashboard pattern, check the component library's upstream components and published examples or blocks, and adapt the closest one. Build new only when none fits, and put a shared component in the design-system package rather than the app.

When a shared component or token changes, apply it to every surface that consumes it and check each one. Match neighboring screens: the same shell, the same placement for the same control, and the same term for the same concept.

## Give each view one next step

Each view has one primary action. Before adding a button, decide whether it needs to exist, then take its variant and position from the library's pattern for that context. Group secondary actions in an overflow menu. Prefer a compact select, dropdown, or filter to a group of large buttons, and collapse options that do the same job into one control.

## Ask less in forms

Ask only for what the next step needs and show what remains later. Infer, default, and reuse what is already known; generate identifiers instead of asking users to type them. Constrain input types, validate with the project's form library, let users skip optional steps, and end long flows with an editable summary.

## Gotchas

- An icon carries an action or status whose meaning is clear without words; a logo replaces a partner's written name. Secondary explanation and technical detail go in a tooltip or disclosure, not on the resting screen.
- Each fact appears once: one total, one status, one disclaimer. Completed states drop deadlines, optional markers, and fields that no longer apply.
- Use a color only for the role the design system assigns it. Destructive styling is for destructive actions, and confirmations use the primary style.
- Badges and pills stay small, wallet and social buttons sit side by side, and status tabs filter with All as the default. When space runs out, remove content instead of shrinking text.
- Nothing is half-clipped, hidden behind an expander, or placed outside its card, and related items in a section share one alignment.
- Controls enable as soon as their input is valid, without a reload.

## Finish

Run the app and use the changed flow as a user would, at desktop and mobile widths, including empty, error, busy, and completed states. Capture the actual changed UI, fix what the captures show, and only then report the result; do not ask the user to inspect it for you. For each element added, confirm it has a role in the user's next step, and delete it otherwise.

Use `ui-copy` when available for the words on the screen. When the user corrects a composition choice that the project guide does not cover, propose recording it there so the next change starts from it.
Files in this package (3)
  • LICENSE 1 KB
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · gustavovalverde/skills100MIT
owl-listener/designpowers90MIT

Database snapshot: 13.11.2026 · package version f1730b4ffb7d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90ui-copy
    Write or review interface text such as labels, buttons, headings, field hints, empty states, errors, confirmations, tooltips, and onboarding messages. Use when building or changing a screen, component, or flow that shows text to users, even for a single label or message, and…
  • 100build-landing-page
    Build a landing page from a brief using only the registered sections of this design system — map the brief to sections, name what is missing, compose the page between Navbar and Footer with the brief's copy as props, check it at 375, 768 and 1440, follow docs/seo.md including…
  • 100better-writing
    UX writing and interface copy, from voice and button labels to error messages and empty states. Use when writing or reviewing any user-facing text: button and link labels, form errors, placeholders, settings labels, onboarding flows, notifications, or empty states. Triggers on…
  • 90app-baseline
    The baseline every Forge client app gets without anyone asking. Use for any frontend or UI work in a Forge client repo, including screens, layout, navigation, forms, tables and prototype demos, before building or changing it.
  • 100ui
    Builds UI components, landing page sections, hero sections, and contact forms. Use when creating front-end visual elements.
  • 100penpot-build-screen
    Design production-grade screens in Penpot from a brief, as a senior visual designer — reusing the existing design system (tokens + components) and assembling section by section, never one-shot. Use to create a screen/page/landing/dashboard from a description. NOT for translating…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.