メニュー
Use this skill when asked to review, check, or validate code in a Cratis-based project. Produces a structured review report with blocking issues and suggestions, checked against all project architecture and style standards.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Step-by-step guidance for building a React page in a Cratis Arc application — listing data with DataPage, toolbar actions with CommandDialog, row selection, detail panels, observable queries, and MVVM. Use whenever building or modifying a React page that lists or displays data, adding a table or grid, wiring up Add/Edit/Delete actions, using DataPage, DataTableForQuery, CommandDialog, or any @cratis/components. Also trigger when connecting a React component to a proxy-generated query or observable query.
Use this skill when asked to add a Chronicle reactor (automation or translation) to a Cratis-based project. Reactors observe events and produce side effects.
Diátaxis Documentation Expert for Cratis projects. Writes high-quality DocFX documentation guided by the Diátaxis framework — classifying every page as a Tutorial, How-to Guide, Reference, or Explanation.
Use this skill when changing, fixing, or improving Cratis documentation whose source file is under `Documentation/**` in a product or contributing repo. The content is split across repos (each product owns its docs in its own `Documentation/` folder; the `Documentation` repo aggregates them), so this skill finds the real source file, edits it, syncs, and verifies. Trigger whenever someone asks to edit/update/fix/reword a docs page, fix a broken link, correct a code example, update a guide or tutorial or reference page, or says a docs page is wrong/outdated — for Chronicle, Arc, Components, CLI, Fundamentals, or the contributing docs.
Use this skill to visually QA rendered docs site pages after changes to source files under `Documentation/**` — screenshot pages headless in light AND dark, evaluate how they look against the aspire.dev bar, check diagrams/tables/code blocks render, and diagnose layout-shift ("flicker"/"twitch"/"pop") bugs. Trigger when someone asks to screenshot the docs, check how a docs page looks, review the docs visually, verify a diagram or table renders, compare the docs to aspire.dev, or investigate a flicker/jump/layout-shift on the docs site.
Use this skill when creating a NEW Cratis documentation page under `Documentation/**` in a product or contributing repo — a new tutorial chapter, how-to/guide, explanation/concept page, reference page, or scenario/recipe. Handles where the file goes (which product repo), wiring it into the sidebar nav (toc.yml + Diátaxis bucket), and verifying it renders. Trigger when someone asks to add/create/write a new docs page, document a new feature, add a guide/tutorial/recipe/concept to the docs, or add a new section to a product's documentation.
| name | review-code |
| description | Use this skill when asked to review, check, or validate code in a Cratis-based project. Produces a structured review report with blocking issues and suggestions, checked against all project architecture and style standards. |
Review changed code against all Cratis project standards and produce a structured report.
Features/<Feature>/<Slice>.cs with all backend artifactsrecord type with Handle() directly on them — no separate handler classesrecord type, no mutable properties.AutoMap() only needed after .NoAutoMap()IServiceProvider not injected)<NamespaceRoot>.<Feature>.<Slice>using directives alphabetically sortedusing directivesis null / is not null — never == null / != nullvar preferred over explicit typesAsync, Impl, Service on class names<summary> tags always multiline — never /// <summary>Text</summary> on one line<param name="..."> for each<returns>InvalidOperationException, ArgumentException, etc.Guid/string in domain models)const over let over vare, idx, prev, dir, posany type — unknown with type guards(x as any) — use value as unknown as TargetTypeCommandDialog from @cratis/components/CommandDialog for command dialogsDialog from @cratis/components/Dialogs for data-only dialogsDialog from primereact/dialog directlyStart with: Review result: ✅ Approved / ⚠️ Approved with comments / ❌ Changes requested
Then list issues:
### <file path>
**[BLOCKING]** Line N: `problematic code`
Because: explanation
Fix:
```corrected code```
End with a concise summary of what passed and what must change.
For the full expanded checklists across all categories, see references/CHECKLISTS.md.