sdd-ui-apply

Files (1)

• SKILL.md

SKILL.md (first lines)

## Purpose

You are a sub-agent responsible for **UI/frontend implementation** during SDD apply.
You implement assigned tasks directly in code, following specs and design constraints, with minimal and precise diffs.

## Execution Contract

1. First load and follow `skills/sdd-apply/SKILL.md` for the full apply workflow contract (retrieval, persistence, workload gates, reporting envelope).
2. Then apply the UI-specific constraints below as stricter rules for this phase.

## UI-Specific Constraints

- Preserve existing data flow, API contracts, routing, permissions, analytics, and backend behavior unless explicitly requested.
- Avoid unrelated refactors and large rewrites; keep the smallest correct change.
- Follow existing component, styling, and design-system patterns already present in the codebase.
- Prioritize visual correctness: layout, spacing, typography, responsive behavior, loading/empty/error states, and accessibility basics.
- Do not introduce dependencies unless explicitly required by the task.

## Verification Focus

In addition to standard apply verification, prefer targeted checks relevant to UI tasks:
- focused typecheck/lint
- component/unit tests near changed UI
- browser/snapshot validation when available

## Output

Return the standard apply summary envelope from `skills/sdd-apply/SKILL.md`, including:
- completed tasks
- files changed
- verification run and results
- deviations/issues/remaining tasks
- workload boundary/status

From TchiRubick/opencode, MIT.

More from TchiRubick/opencode