菜单
Guard cross-package architecture for RaidenShinBoot. Use when changes affect API contracts, bot/server conversation behavior, Drizzle schema, vector memory, shared persona logic, environment variables, or validation gates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Refine, parallelize, and verify a draft task specification into a fully planned implementation-ready task. Also triggered by SDD模式, sdd:plan, or /plan-task.
LobeHub Zustand store conventions: public/internal/dispatch action layers, optimistic update pattern, slice composition via `flattenActions`, and class-based action migration. Use whenever working under `src/store/**`, adding a `createXxxSlice`, writing `internal_*` or `internal_dispatch*` actions, designing `messagesMap`/`topicsMap` reducers, refactoring a `StateCreator` object slice into a `XxxActionImpl` class, or debugging stale store reads. Triggers on `useChatStore`/`useUserStore`/`useGlobalStore`, `createStore`, `flattenActions`, `StoreSetter`, `internal_dispatch`, 'add an action', 'zustand selector', 'store slice', 'class action', 'optimistic update'.
Navigate the RaidenShinBoot TypeScript monorepo. Use for package ownership, entry points, workspace scripts, dependency placement, environment files, and validation command selection across shared, database, server, bot, and panel.
Refine, parallelize, and verify a draft task specification into a fully planned implementation-ready task. Also triggered by SDD模式, sdd:plan, or /plan-task.
Standards for RaidenShinBoot admin panel work. Use for React 19, Refine v4, Tailwind CSS v4, Hono typed client integration, runtime status UX, resource tables, dashboard components, and panel validation.
| name | raiden-project-spec |
| description | Guard cross-package architecture for RaidenShinBoot. Use when changes affect API contracts, bot/server conversation behavior, Drizzle schema, vector memory, shared persona logic, environment variables, or validation gates. |
Use this skill for cross-package changes where behavior must stay aligned between bot, API, database, shared types, and panel.
packages/server/src/app.ts through export type AppType = typeof app.hono/client and AppType, not duplicate response types by hand.packages/shared/src/schemas.ts when used by more than one package.packages/shared/src/persona.ts and packages/shared/src/boot.ts.packages/boot/src/index.ts.packages/database.Expected flow, implemented through packages/boot so bot and server do not drift:
If bot and server both need the same behavior, move orchestration into packages/boot or lower shared/database packages instead of letting implementations drift.
memories.embedding uses halfvec(3072); embedding model changes must be checked against dimension.CREATE EXTENSION IF NOT EXISTS vector; before halfvec usage./api/health should remain cheap and not require a DB connection.DATABASE_URL, but panel must handle missing DB gracefully.packages/panel/src/lib/apiClient.ts is the typed API boundary.packages/panel/src/lib/dataProvider.ts is the Refine integration boundary.pnpm --filter @raiden/shared checkpnpm --filter @raiden/boot checkpnpm --filter @raiden/database check and pnpm db:generatepnpm --filter @raiden/server checkpnpm --filter @raiden/bot checkpnpm --filter @raiden/panel check and pnpm --filter @raiden/panel buildpnpm check and pnpm buildFinal answers for cross-package work should mention: