メニュー
Use when you are changing tRPC contracts, app-router shape, or client and server import order across the shared boundary. Do not use for provider runtime layout, remote operations, or generic route and UI work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Decision skill for choosing TDS React Native components and UI boundaries in MiniApp screens. Use when translating product requirements into TDS components, reconciling public docs with actual exports, or deciding controlled/uncontrolled state patterns. Do not use for route design, capability lookup, provider/runtime work, or non-TDS native module decisions.
Decide how to structure an optional backoffice React screen: pick list, detail, form, dashboard, or bulk-action archetypes; place query, component, and form state; split search, table, confirm, and export boundaries; and validate loading, error, empty, disabled, and permission states. Do not use for MiniApp route design, server-provider diagnosis, or shared contract changes.
Diagnose a Cloudflare Worker-backed server workspace: classify runtime, binding, env, local dev, and client-linkage drift; check D1/R2 and base URL alignment; and separate local diagnosis from remote-state or shared-boundary work. Do not use for deploy-only repair or generic UI work.
Diagnose a Firebase-backed server workspace: choose callable, HTTP, or trigger surfaces; check project, region, emulator, and client-linkage drift; and distinguish local linkage from remote readiness or shared-boundary work. Do not use for deploy, seed, or repair procedures.
Use when you are changing Granite route paths, page entries, params, or navigation flow in the MiniApp frontend. Do not use for capability lookup, provider runtime work, or TDS component selection.
Diagnose a Supabase-backed server workspace: separate DB, RLS, Edge Function, env, and project-ref drift; check frontend and backoffice alignment; and distinguish local linkage from remote project state or shared-boundary work. Do not use for remote db apply/deploy or generic route/UI work.
| name | trpc-boundary |
| description | Use when you are changing tRPC contracts, app-router shape, or client and server import order across the shared boundary. Do not use for provider runtime layout, remote operations, or generic route and UI work. |
| compatibility | Intended for create-rn-miniapp repositories with the optional Cloudflare+tRPC overlay. Assumes the generated packages/contracts, packages/app-router, frontend, backoffice, and server workspace boundary. |
| metadata | {"create-rn-miniapp.agentsLabel":"tRPC boundary 변경","create-rn-miniapp.category":"optional","create-rn-miniapp.order":"8"} |
Cloudflare + tRPC 조합에서 client-server 경계를 수정할 때 사용하는 Skill입니다.
packages/contracts, packages/app-router, server, frontend, backoffice 순서로 변경을 전파할 때cloudflare-workergranite-routingtds-uireferences/change-flow.md를 먼저 읽는다.docs/engineering/workspace-topology.md를 같이 확인한다.packages/contractsAppRouter는 packages/app-router