菜单
Build a polished MemOS dashboard component to the project design system (Next.js App Router, Tailwind, shadcn/ui, Framer Motion). Use for any new UI piece — OKR tree, activity feed, provenance graph, brief authoring, etc.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write a correct Drizzle schema change plus migration and Row-Level Security policy for MemOS. Use when adding or altering any table, index, or RLS policy.
Generate realistic, screenshot-ready seed data for MemOS — a believable org with teams, projects, agents, OKRs, briefs, and a rich graph of facts/learnings/artifacts. Use before demos, screenshots, or recording the README Loom.
Run an HLD + LLD design review on a proposed plan BEFORE coding a non-trivial MemOS feature. Use at the start of any feature that touches more than one module, the data model, or a core invariant.
Audit that the MemOS core write-gating invariants (evidence gate, non-obvious gate, provenance thread, tenant isolation) are actually enforced and tested. Run before merging any change to the fact/learning/artifact/workflow write path.
Add a new MemOS API intent end-to-end (Zod schema, handler, route registration, test, and API docs) in the consistent project pattern. Use whenever adding or modifying an intent like fact.record, workflow.create, brief.fetch.
Capture an Architecture Decision Record for a real design choice in MemOS. Use whenever a non-trivial decision is made (tech choice, schema modeling, isolation strategy, a tradeoff with alternatives).
| name | frontend-component |
| description | Build a polished MemOS dashboard component to the project design system (Next.js App Router, Tailwind, shadcn/ui, Framer Motion). Use for any new UI piece — OKR tree, activity feed, provenance graph, brief authoring, etc. |
The dashboard is the showpiece — it must look extraordinary, not just functional. Every component is accessible, responsive, dark-mode-aware, and animated with restraint. Build to the design system; do not invent one-off styles.
What does it render? Which intent(s) or API route feeds it? Define the TS type (import from packages/shared — never redefine).
packages/web/components/<area>/<Name>.tsxbd_id and target_objective_id links. Clicking a learning expands its full chain. This is the single most impressive screenshot — make it beautiful and interactive.Use Supabase Realtime channels or an SSE endpoint on the gateway. Debounce/batch updates so the feed doesn't thrash.
Hover states, transitions, responsive breakpoints (mobile → wide). Screenshot it in dark mode for the README.
Component renders all states (loading/empty/error/data), matches the design system, animates with restraint, is accessible, and looks good enough to put in the README. Commit as feat(web): <component>.