Do not use unless the user explicitly requests it. Dispatch each requested task to a new Codex session in a newly allocated dedicated worktree, then coordinate rebasing and fast-forward integration into local main without implementing, reviewing, or archiving the task in the coordinator session.
Use only when explicitly requested by the user or, during an explicit debugging session, after other relevant checks such as typecheck, lint, and tests have been exhausted.
Use only when the user explicitly requests this skill.
Use when building greenfield React SPA UI with Lisse (`@lisse/react` or `@lisse/core`) for Figma-style smooth/squircle corners, choosing `SmoothCorners` vs `useSmoothCorners`, configuring corner smoothing, borders, gradient borders, shadows, styling hooks, auto-effects, client-side path generation, performance, or limitations.
Use React Aria and React Stately hooks to build accessible custom React components, including choosing the right hook, wiring refs/state/props, preserving ARIA and keyboard behavior, excluding React Aria i18n and SSR utilities, and checking hook-specific guidance in bundled category docs.
Design, review, and optimize PostgreSQL and SQLite schemas, queries, migrations, transactions, indexes, and data-access code, especially when SQL should remain portable between both engines.
Use when building React animations with Motion primitives, including motion components, animation props, gestures, layout/scroll/SVG animation, transitions, variants, Motion values, core React Motion hooks/components, and occasional vanilla JavaScript Motion APIs when React APIs are less appropriate or less capable.
Use Fallow as scoped TypeScript/JavaScript codebase evidence after nontrivial JS/TS edits, before deleting exports/files/dependencies, or when considering Fallow cleanup fixes. Run audit and dead-code trace commands, read JSON output, and act only on findings introduced by or clearly related to the current task.