Faye Plugin Market
Skill guide

UI system architecture

Plan reusable UI layers, component contracts, and state ownership around the project's actual consumers.

Clarify which responsibilities belong to visual foundations, controls, interaction behaviors, patterns, and feature adapters. Justify contracts and state ownership through actual consumers and supported operations, preserving consequential design intent in the contracts it depends on. The skill uses the host framework and proposes a bounded migration where needed; conditional guidance does not require additional infrastructure.

Package version 0.1.0-beta.6

Included with Faye UI System Engineer

See an exampleView package

When to use

Use this before restructuring shared components, introducing reusable controls, or untangling state shared across views.

What to provide

  • The affected repository areas and examples of real consumers.
  • Current component APIs, state mechanisms, compatibility requirements, and the behavior that must remain stable.

Expected results

  • A proposed ownership model and component or state contracts.
  • A bounded migration sequence with compatibility decisions and verification criteria.

Example requests

Try this request

Codex
Codex request
$ui-system-architecture Plan a shared filter control for our React search and reporting screens. Keep the current state library and show which state belongs in the URL, feature, and control.
Grok
Grok request
/ui-system-architecture Plan a shared filter control for our React search and reporting screens. Keep the current state library and show which state belongs in the URL, feature, and control.
Antigravity
Antigravity request
/ui-system-architecture Plan a shared filter control for our React search and reporting screens. Keep the current state library and show which state belongs in the URL, feature, and control.

Requirements and limits

Before you start

  • Access to the relevant UI source is needed to substantiate a repository architecture proposal.
  • Identify any permitted dependency or framework changes explicitly.

Scope and limitations

  • Architecture proposals do not change files unless implementation is also requested.
  • An individual screen does not automatically require a reusable system.
  • Application chrome and authored content, such as an editor canvas, remain separate ownership decisions.
Technical source

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

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

Open source file