How To Write A Component

Use this skill to route component architecture decisions to its bundled references. Read only the references required by the current change.

Topic Routing

• Component moves, module boundaries, props, types, or owner placement: read [references/ownership.md][ownership].
• Jotai, form drafts, route identity, URL state, or persistence: read [references/state.md][state].
• Generated contracts, nullable API data, Query, mutations, SSR, auth, or workspace state: read [references/data.md][data].
• Hotkeys, focus, dialogs, menus, popovers, or other secondary surfaces: read [references/interactions.md][interactions] and the overlay guide it references when applicable. Also read [references/state.md][state] when the surface owns a draft or other local session state.
• Effects, navigation, memoization, preloading, or render cost: read [references/runtime.md][runtime].

Scope And Verification

Identify the behavior owner, state lifetime, and public contract from the nearby implementation and relevant references. Keep the change within that vertical slice unless the contract requires changes elsewhere. Verify the changed behavior and complete the owning package's required checks. For Web, read web/docs/test.md for test work and web/docs/lint.md for static checks. Dify UI verification is owned by packages/dify-ui/docs/testing.md.

Tailwind CSS