Skill guide

UI system implementation

Build or refine browser screens and reusable components with responsive, accessible behavior.

Carry the intended use and experience into composition, behavior, appropriate product copy, and relevant verification. Resolve open design decisions within an authorized build. Preserve achieved qualities when fixing defects, and exercise sustained or interrupted input when it shapes the experience. Work can cover one screen or a shared system; actual consumers determine the needed abstractions.

Package version 0.1.0-beta.6

Included with Faye UI System Engineer

See an example View package

When to use

Use this when you want actual UI changes, from improving one page to migrating a shared control and its callers.

What to provide

The screen, component, or accepted plan to implement.
The intended behavior and visual direction, supported viewports, and constraints on framework, dependencies, or existing edits.

Expected results

Implemented UI changes and any necessary consumer migrations.
Evidence from source checks and rendered interaction or layout checks matched to the changed surface, with remaining gaps stated.

Example requests

Try this request

Codex

$ui-system-implementation Refine our browser drawing tool so strokes track direction changes reliably. Preserve its layered ink character, existing controls, and undo behavior. Check continuous drawing, repeated passes, interruption, and touch input where supported.

Grok

/ui-system-implementation Refine our browser drawing tool so strokes track direction changes reliably. Preserve its layered ink character, existing controls, and undo behavior. Check continuous drawing, repeated passes, interruption, and touch input where supported.

Antigravity

/ui-system-implementation Refine our browser drawing tool so strokes track direction changes reliably. Preserve its layered ink character, existing controls, and undo behavior. Check continuous drawing, repeated passes, interruption, and touch input where supported.

Requirements and limits

Before you start

A writable repository and a clear implementation scope.
A runnable page or browser evidence is needed to verify the rendered result.

Scope and limitations

The skill preserves the host framework and established ownership; dependency changes need their own authorization.
Screenshots alone do not prove interaction behavior.
Native application UI and general backend development are outside this skill's browser UI scope.

Technical source

The hosted file belongs to the package version shown on this page.

plugins/faye-ui-system-engineer/skills/ui-system-implementation

Open source file