Skip to main content

how-to-write-component

Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data flow, effects, or interaction ownership. Do not use for review-only requests, test-only work, copy-only edits, or styling-only changes.

来源信息

仓库
langgenius/dify
最近来源活动
2026年10月10日 04:40
检测到的 SKILL.md 语言
英语
星标
158,150
分支
24,983

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
6 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
how-to-write-component
description
Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data flow, effects, or interaction ownership. Do not use for review-only requests, test-only work, copy-only edits, or styling-only changes.
# 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]. - Dify UI wrappers or primitive state styling: read the package's [Public API authoring] and [Styling] contracts. - 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 - Write canonical Tailwind v4 classes; prefer canonical utilities over equivalent arbitrary values. - Common forms include `w-105` instead of `w-[420px]`, `px-2.25` instead of `px-[9px]`, `bg-linear-to-b` instead of `bg-gradient-to-b`, `wrap-break-word` instead of `break-words`, and `field-sizing-content` instead of `[field-sizing:content]`. [Public API authoring]: ../../../packages/dify-ui/docs/authoring.md [Styling]: ../../../packages/dify-ui/docs/styling.md [data]: references/data.md [interactions]: references/interactions.md [ownership]: references/ownership.md [runtime]: references/runtime.md [state]: references/state.md
在 GitHub 查看