Add suitable Suspense boundaries to Sanity Studio custom form components.
Warum wir es empfehlen
Task-specific guidance from Sanity’s repository.
Wobei es hilft
Add suitable Suspense boundaries to Sanity Studio custom form components.
Vor der Nutzung
A coding agent and a relevant Sanity or headless CMS project. Some tasks require Sanity access, a compatible package version or current online documentation.
Quellen und Referenzen
Die Originalquellen sind unten verlinkt. Praktische Einstiegsideen sind redaktionelle Vorschläge von SkillHey.
Use whenever the user wants to build or modify a chat, agent, or tool-calling UI in a React 19 + Tailwind v4 project — especially if the code imports from `@/components/agent-elements/*` or the project has that folder on disk. Triggers: "agent chat", "tool call UI", "streaming chat", "plan approval", "AgentChat", "InputBar", "tool renderer", mentions of Agent Elements, or requests to add a new agent surface with shadcn. Do NOT use for plain chat UIs that don't need tool/plan/approval cards, or for projects already committed to a different agent UI kit.
Use when the user's task involves Ant Design (antd) — writing antd components, debugging antd issues, querying antd APIs/props/tokens/demos, migrating between antd versions, or analyzing antd usage in a project. Triggers on antd-related code, imports from 'antd', or explicit antd questions.