最高评分
社区最喜爱的高星技能，质量有保障。
decision-log
taika-izumi
"重要な意思決定をADR（Architecture Decision Record）として記録・管理する。設計判断、プロセス決定、スコープ決定、方針決定を構造化して記録する。意思決定を検出した瞬間に呼ぶこと。実行中の他スキルの完了を待ってはならない。"
worklog-extract
taika-izumi
"中央ストアに蓄積された作業ログをオンデマンドで走査し、スキル化・ルール化する価値のある候補をクラスタリング・評価してランク付き候補リストとして人間に提示する。処理済み台帳で既処理を除外し、人間の採否を Issue 草案と台帳へ反映する。ユーザーが明示的に実行するスキル。"
worklog-record
taika-izumi
"作業の節目（スキル完了・plan タスク完了・重要な分岐通過）とセッション切り替え直前で、AI のデフォルト挙動と実際に必要だったことの差分（delta）を中央ストアへ1件記録する。start-work の節目の確認およびセッション終了処理から発火。記録ゲート（既存スキルで実施済みでない かつ AI 自律で毎回再現できない）を満たす場合のみ追記する。"
worklog-skillify
taika-izumi
"worklog-extract で採用された候補から、writing-skills 委譲で新規スキル作成または既存スキル拡張を行う。スコープ（汎用/プロジェクト固有/固有ルール）で成果物の配置先を振り分け、汎用パスをガイドライン配信元リポジトリ以外で実行しようとした場合は警告する。ユーザーまたは worklog-extract から起動。"
retrospective
taika-izumi
"サブプロジェクト1サイクル完了直後（feature ブランチを master へマージ後、handoff finalize 前）に実施する、サイクル末尾の課題抽出記録スキル。AI が plan / git log / handoff から課題候補（事象/原因/影響、system/flow 分類つき）を一括提示し、ユーザーが修正と起票判断を行う。フロー課題は delta 型（worklog で捕捉可能）か構造観察型かを振り分け、delta 型で急がないものは worklog パイプラインへ委ねる（ADR-0056）。抽出課題は docs/working/issues/system flow/ へ起票し（ADR-0028）、対策の採否・設計・ADR化は次サイクルへ委ねる（ADR-0021）。rubber-duck 独立レビューはユーザー要求時のみのオプション。"
flutter-testing
DonArtkins
"Flutter widget + integration tests for the Griot mobile app: widget tests for key screens, integration_test for device flows, Docker-pinned runner in CI."
jest-rtl
DonArtkins
"Jest + React Testing Library for the Griot web app: component tests for TaskCard/BoardView/modals, mocked Apollo/React Query hooks, MSW for the copilot stub."
k6-perf
DonArtkins
"k6 load/performance testing for Griot: dashboard query, login, board read. Baseline (Week 6) vs regression (Week 7). p95 < 500ms target."
newman-api
DonArtkins
"Newman CLI runs of the Postman collection in CI: API contract + regression suite, JSON schema assertions, chained tokens."
owasp-review
DonArtkins
"OWASP Top-10 basics review for the Griot estate: injection (parameterized SQL), broken auth (refresh rotation), sensitive data (no localStorage tokens), CORS allow-list, AI principal scope."
xunit-dotnet
DonArtkins
"xUnit unit + integration testing for the Griot backend: WebApplicationFactory against the real SQL Server container, refresh-rotation replay, bulk-atomicity, coverage collection."
apollo-graphql
DonArtkins
"Apollo Client integration for Griot's GraphQL reads: single client, InMemoryCache typePolicies, colocated fragments, refetch discipline."
auth-and-zustand
DonArtkins
"Web auth + client-state split: JWT access token in memory (Zustand), refresh token in an httpOnly cookie, silent refresh on boot, and the Zustand=client-only-state rule."
material-ui-theme
DonArtkins
"Build the MUI v6 theme from the Figma tokens: palette, typography, shape, transitions. The theme file is the single source of visual style."
impeccable
scs0209
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
impeccable
scs0209
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
organize-inbox
taika-izumi
"docs/inbox/ に置かれた未分類の情報を、フォルダ構成定義（docs/overview/folder-structure.md）の分類基準に照らして1件ずつ整理するスキル。移動だけでなく、複数分類への分割、既存ドキュメントへの追記統合も行う。ユーザーの明示実行、または start-work の inbox 検知からの提案で起動する。"
organize-inbox
taika-izumi
"docs/inbox/ に置かれた未分類の情報を、フォルダ構成定義（docs/overview/folder-structure.md）の分類基準に照らして1件ずつ整理するスキル。移動だけでなく、複数分類への分割、既存ドキュメントへの追記統合も行う。ユーザーの明示実行、または start-work の inbox 検知からの提案で起動する。"
ecosystem-upgrade
AtomiCloud
Drive a whole CyanPrint template-chain (ketone) through an ecosystem upgrade — baseline bump (e.g. nixos-26.05 + nix-registry/v3), modern nix-based generated CI, and republish — safely, in dependency order, and to a fixed point. Use when running /ecosystem-upgrade, performing a chain-wide baseline/registry bump across the ketone templates, upgrading the template ecosystem, or re-running the chain upgrade.
pre-action-review
taika-izumi
"不可逆操作や重要な変更の前に、実行内容のサマリーとリスク評価をユーザーに提示する。リスクレベルに応じてログのみ・サマリー表示・承認必須を切り替える。"
testing-template
AtomiCloud
Test this CyanPrint template. Use when the user asks to write tests, add test cases, update snapshots, or debug template test failures. Covers test.cyan.yaml format with answer_state, deterministic_state, validate commands, and expected output.
writing-template-typescript
AtomiCloud
Write or modify CyanPrint template code in TypeScript. Use when the user asks to add prompts, change template logic, modify the entry point, add processors/plugins/resolvers, or change generated output for a TypeScript template. Covers IInquirer question types (text, select, checkbox, confirm, password, dateSelect), processor configuration, and IDeterminism for non-deterministic values.
documenting-template
AtomiCloud
Document this CyanPrint template into README.MD. Use when the user asks to document the template, write a README, explain how to use the template, or add usage documentation. Reads cyan.yaml and entry point code to generate accurate, artifact-specific docs.
testing-plugin
AtomiCloud
Test this CyanPrint plugin. Use when the user asks to write plugin tests, add test cases, update snapshots, or debug plugin test failures. Covers test.cyan.yaml format with input directories, config, validate commands, and expected output.