frontend-work

Files (5)

• SKILL.md
• keyboard-form-strategy.md · resources/
• list-screen-contract.md · resources/
• mobile-ergonomics.md · resources/
• ui-ux-polish.md · resources/

SKILL.md (first lines)

# Frontend Work

This is an internal meta skill. Humans should not need to reference it directly.

## Purpose

Keep frontend knowledge out of the human-facing `build` skill by routing screen, layout, interaction, and polish work through a dedicated internal frontend layer.

The goal is to preserve a narrow external API while allowing Darwin's frontend depth to grow over time.

## When To Use

Use for:

- new screens
- page and layout changes
- landing pages and first-run flows
- async interaction states
- UI/UX polish work
- mobile ergonomics and information hierarchy review

## Workflow

1. Identify the dominant frontend problem: structure, interaction, state handling, or polish.
2. Choose the smallest useful frontend resource for that problem.
3. If the work breaks into seams like state, layout, and copy, prefer parallel agents.
4. Apply the selected resource during implementation and review, not only at the end.
5. Return concise guidance or implementation summaries in terms of user outcomes.

## Resources

- `resources/ui-ux-polish.md` for hierarchy, first action, loading/empty/error states, and dead-content removal
- `resources/mobile-ergonomics.md` for tap targets, thumb reach, safe areas, and above-the-fold mobile usability
- `resources/keyboard-form-strategy.md` for input flows, keyboard handling, submission behavior, and validation recovery
- `resources/list-screen-contract.md` for loading, empty, error, refresh, and first-page list semantics

## Guardrails

- Do not turn `build` into the home for frontend judgment.
- Do not add a new human-facing command when an internal frontend resource is enough.
- Prefer one focused frontend resource over a vague catch-all design instruction.
- Keep frontend recommendations tied to the primary user task on the screen.

## Output

Summaries should emphasize:

- what the user is trying to do
- what changed in the UI to support that
- what was removed, demoted, or clarified

From tykowale/darwin, MIT.

More from tykowale/darwin