Skip to content
Skills Library
Design & UX · Building & coding

ui-implementation

/ui-implementation

Implement an agreed UI design in the project's existing stack, including responsive behavior, keyboard access, and empty/loading/error states. Use when the intended interface is already clear; do not invent a new design direction.

Licence
MIT
Last repository change
05.11.2026

Assessment and security

90/ 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.
Content25 / 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 05.11.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

Implement an agreed UI design in the project's existing stack, including responsive behavior, keyboard access, and empty/loading/error states. Use when the intended interface is already clear; do not invent a new design direction.

Original author description

Implement an agreed UI design in the project's existing stack, including responsive behavior, keyboard access, and empty/loading/error states. Use when the intended interface is already clear; do not invent a new design direction.

How it works

  1. Inspect the implementation context
  2. Build the interface
  3. Verify while building
Original SKILL.md headings · 47 lines, 284 words
SKILL.md preview
---
name: ui-implementation
description: "Implement an agreed UI design in the project's existing stack, including responsive behavior, keyboard access, and empty/loading/error states. Use when the intended interface is already clear; do not invent a new design direction."
---

# UI Implementation

Turn an agreed design into working interface code using the project's existing
components, tokens, and conventions. If the design direction is unresolved, route to
`ui-design-intelligence`; if the interface is visibly broken and the cause is unknown,
route to `browser-diagnostics`.

## Inspect the implementation context

Read the affected components, styles, data flow, tests, and build commands. Identify
the design tokens and primitives already in use. Reuse them before adding a wrapper or
dependency. Check the API states the UI must render: loading, empty, partial, error,
success, disabled, and permission-limited.

Preserve explicit user and design decisions. Do not silently redesign spacing, copy,
navigation, or interaction patterns while implementing a local change.

## Build the interface

- Use semantic HTML and native controls where possible.
- Implement keyboard order, visible focus, labels, names, and error associations.
- Make responsive behavior intentional: test narrow and wide viewports, not only the
  desktop screenshot.
- Implement empty, loading, and error states as first-class states, not afterthoughts.
- Keep destructive or financial actions explicit, reversible where possible, and
  clear about the affected record.
- Avoid layout shift, horizontal overflow, and color-only status signals.

For enterprise tables, filters, approvals, long forms, reconciliation, and dense
financial data, follow the selected profile in
[`ui-design-intelligence/references/enterprise-data-ux.md`](../ui-design-intelligence/references/enterprise-data-ux.md).

## Verify while building

Use the project's existing test setup. Add focused interaction tests for meaningful
behavior, not snapshots of every static element. Check at minimum:

- keyboard traversal and focus visibility;
- narrow and wide viewport behavior;
- empty, loading, and error states;
- the primary success path;
- no console errors or failed required requests.

Hand the result to `ui-quality-verification` when a visual/interaction audit is
requested or when the change affects a critical enterprise workflow.
Files in this package (3)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB
  • references/implementation-checklist.md 1 KB

Versions

RepositoryScoreLicence
This page · RaditteAnggoro/agent-doctor-for-your-devices90MIT
RaditteAnggoro/skill-for-lazy-developer90MIT

Database snapshot: 13.11.2026 · package version 381b39a35dae (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

  • 100design-system-implementation
    Implement or refine reusable design tokens and interface components that follow an existing product direction. Use when establishing tokens, component APIs, variants, states, or cross-screen consistency.
  • 100vectreal-brand-ux-design
    Use for any change a user can see in Vectreal: component styling, layout, spacing, color, typography, elevation, motion, empty/loading/error states, responsive behavior, accessibility, and marketing UI. Triggers: design, styling, className, Tailwind, token, theme, dark mode,…
  • 90pb-build-prototype
    ProductBridge stage 4. Build an isolated, reversible prototype of a chosen concept inside an authorized Next.js/React codebase, reusing its components and tokens and exercising loading, empty, error, success, responsive and keyboard behavior, then report exactly what was built…
  • 100rachnasutra-flow
    Review user journeys, information architecture, navigation, forms, empty/loading/error states and usability heuristics. Use for task-completion and usability questions.
  • 100fe-component
    Builds a new UI component the right way round in any stack - native semantics first, the keyboard model from the WAI-ARIA APG pattern, names and states, every visual state, responsive and reduced motion, the project helpers and tokens, tests by role, then the audit. Use when…
  • 90design-handoff
    Use when a design is ready for engineering — produce an implementation-ready spec covering layout, tokens, states, responsive behavior, edge cases, motion, and accessibility.

Feedback and reports

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