adapter-react

Files (1)

• SKILL.md

SKILL.md (first lines)

# Adapter: React

## Focus

- Component readability and reusable patterns.
- Hook correctness and state lifecycle handling.
- Accessible interaction behavior.

## Starter Checklist

- [ ] Component structure follows existing app patterns.
- [ ] Hook dependencies and effect boundaries are correct.
- [ ] Loading/empty/error states are explicit.
- [ ] Accessibility basics are preserved.

## Implementation Pattern

Evidence: 3-repo field extraction (Next.js x2, Vite SPA x1) — see `.ai/MERGE_REPORT.md`.

- Keep components presentational; push orchestration, data fetching, and multi-step async logic
  into custom hooks, not inline in render/component bodies.
- Give complex feature hooks an explicit typed return contract — a named object, not a
  positional array or an untyped, heterogeneous bag. (Reconfirmed in a 5th, unrelated repo —
  see `.ai/MERGE_REPORT.md`.)
- Keep shared design primitives (buttons, inputs, cards) as one reusable set with controlled
  variants; never rebuild the same primitive styling ad hoc per page/feature.

If the current project already has an established pattern for any of these, follow the existing
pattern instead of this default.

From JahacksV1/day-one-agent-kit, MIT.

More from JahacksV1/day-one-agent-kit