claude-code-plugin

Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.

Internal project-context placement and consistency reference used by context refactoring and verification workflows.

This skill should be used when the user asks to "audit project standards", "check standards compliance", "devkit audit", "find standards violations", "are we following devkit standards", "what's not following standards", "compliance report", "規約チェック", "スタンダード監査", or "規約違反を探して". It actively scans code and reports violations. Do NOT use for project scaffolding (use init-project), single-CLI-tool checks (use cli-compliance), or looking up what the standards are (use standards).

This skill should be used when the user asks to "set up a project", "choose a tech stack", "establish coding standards", "configure linting", "set up tests", "pick a framework", "review code quality", "set up logging", "configure observability", "choose an ORM", "set up auth", "set up Storybook", "write stories", "visual testing", "CSF", "coverage threshold", or discusses any technology choices for a TypeScript project. Also use when starting a new project, setting up CI/CD, choosing between tools (oxlint vs ESLint, pnpm vs npm), configuring environment variables, or when any other devkit skill needs to reference project conventions. This is the central reference for all devkit technology decisions and coding principles.

Review whether the current code satisfies a GitHub issue, then update the issue status to match. Use when the user asks to 'review an issue', 'check if an issue is done', 'is this issue resolved', 'update issue status', 'issueの対応状況を確認', 'issueが完了しているかレビュー', or 'issueのステータスを更新'.

This skill should be used when the user asks to 'create a skill', 'add a new skill', 'make a skill', 'scaffold a skill', 'new skill', 'スキル化して', 'スキルを作成', 'スキルを追加', or wants to create a new Claude Code skill for a plugin or project. Provides a guided workflow with automated scaffolding, validation, and dynamic context injection.

This skill should be used when the user asks to "review past work", "過去の作業を確認", "what was done", "TODO履歴", or wants past task and TODO history from previous sessions reviewed.

Manual persona state command replacement for direct skill invocation only. Switches planner / worker / idealist / orchestrator / sparring / pathfinder / foreman state, clears it, or displays current persona status.

This skill should be used when the user asks to "research this library", "ライブラリを徹底調査", "framework investigation", "knowledge base", or wants clone-first hands-on research persisted as reusable knowledge.

This skill should be used when the user asks to "run SDD on autopilot", "自動で進めて", "一気に実装", "autopilot", or wants the SDD workflow advanced with minimal human intervention.

This skill should be used when the user asks for "SDD help", "SDDの使い方", "SDDワークフローを説明", "what is the next SDD command", or wants an overview of the SDD workflow.

This skill should be used when the user asks "what should I do next", "次に何をすればいい", "SDD next", "次のSDDステップ", or wants the next action inferred from the current specs state.

This skill should be used when the user asks to "plan phases", "break down a phase", "implement an SDD phase", "Phase構成", "Phase詳細計画", or wants SDD phase planning, breakdown, implementation, or insertion.

This skill should be used when the user asks to "conduct SDD research", "調査を実施", "不明点を明確化", "research clarify", or wants technical investigation or clarification for an SDD spec.

This skill should be used when the user asks to "create an SDD spec", "仕様書を作成", "要件定義", "技術設計", "spec init", or wants SDD overview, requirements, or technical-details documents created.

This skill should be used when the user asks for "SDD status", "タスクのステータス", "進捗を見せて", "spec一覧", or wants all SDD task statuses displayed.

This skill should be used when the user asks to "define project steering", "プロジェクト方針を定義", "技術スタックを整理", "steering", or wants persistent SDD project context initialized or migrated.

This skill should be used when the user asks to "sync implementation status", "実装状況を仕様書に同期", "SDD sync", "進捗をドキュメントに反映", or wants current code progress reflected in SDD spec documents.

This skill should be used when the user asks to "validate a phase", "Phase検証", "SDD validate", "実装を検証", or wants docs, requirements, quality, and feasibility checks for an SDD phase.

SDDワークフロー全体のガイド。SDD コマンドを実行する時に、全てのコマンドで読み込む必要がある。

This skill should be used when the user asks to "implement Figma screens", "implement this design", "implement the whole flow", "batch implement from Figma", "implement all screens", or provides a Figma prototype URL and wants to build the UI. Traces the prototype graph, plans all screens, then implements one screen at a time with subagent-driven review.

This skill should be used when the user asks to "save a Figma screenshot", "export a Figma node as image", "capture Figma design", or needs to save Figma node screenshots to local files. Prefer this over Figma MCP's get_screenshot.

This skill should be used when the user asks to "create a workspace directory", "workspace-id", "作業ディレクトリを作成", "agent workspace", or wants canonical agent workspace naming and directory conventions.

This skill should be used when the user asks to "verify merge", "マージの確認", "コンフリクト解消を確認", "意図しない変更が入ってないか確認", "check merge resolution", or wants to detect unintended changes introduced during conflict resolution. This is a post-merge verification skill — it checks the result of an already-completed merge, not performs the merge itself.

Internal idealist persona behavior guide referenced by persona hooks and direct skill invocation.

This skill should be used when the user asks to '複数のPRを順番に処理して', 'PRキューを回して', 'PRをまとめてmergeまで面倒見て', 'PRをスタックして', 'process these PRs in order', 'orchestrate PR merges', 'PRパイプライン', 'pr-stack', or wants multiple pull requests analyzed for dependencies, chained via base branches, and processed sequentially by Opus sub-agents.

This skill should be used when the user asks to 'PR push後にmergeまで監視して', 'CI通るまで自動で見て', 'pushしたPRをmergeまで面倒見て', 'watch this PR until merge', or wants a pushed pull request updated from origin/main, monitored through CI, repaired on failures or conflicts, pushed again, and watched until merge completion.

This skill should be used when the user asks to "check PR", "PRの状態を確認", "review comments", "CI failures", or wants PR review comments, CI status, or check-pr actions inspected.

This skill should be used when the user asks to 'watch PRs', 'monitor PR status', 'PRを監視', 'PRの状態を見て', 'babysit this PR', 'PRが通るまで見て', or when the agent needs to monitor PR health after push, PR creation, or CI failure detection.

This skill should be used when the user asks to 'origin/mainをmergeしてpushして', 'mainを取り込んでCI確認して', 'merge main and push', 'update this branch from main', or wants a one-command style flow that fetches origin/main, merges it into the current branch, resolves conflicts, pushes, and checks CI.

GitHub Actions のワークフロー失敗をデバッグする。フルログを ZIP でダウンロードしてローカルで調査する。Use when the user says 'CIが落ちた', 'GitHub Actionsをデバッグ', 'ワークフローが失敗', 'debug CI', 'debug GitHub Actions', 'CI failure', 'GHAのログを見て', 'actionsのエラーを調べて', or wants to investigate a GitHub Actions workflow failure.

This skill should be used when the user asks about 'codex の使い方', 'codex exec のやり方', 'codex でレビュー', 'codex review', 'codex の設定', 'how to use codex', 'codex CLI guide', or wants to run OpenAI Codex CLI from within Claude Code. Covers exec patterns, sandbox modes, output separation, configuration, and integration guidelines.

Internal foreman persona behavior guide referenced by persona hooks and direct skill invocation.

Internal planner persona behavior guide referenced by persona hooks and direct skill invocation.

Internal pathfinder persona behavior guide referenced by persona hooks and direct skill invocation.

Internal sparring persona behavior guide referenced by persona hooks and direct skill invocation.

This skill should be used when the user wants to write a daily journal entry, record what happened today, or reflect on the day. Triggers on '日記を書く', '今日の記録', '日記', 'daily note', 'write diary', '今日あったこと', '1日の振り返り', '日報', 'journal'.

Vault の健全性チェックを実行する。リンク切れ検出・孤立ノート検出・統合候補提案を行う。

This skill should be used when the user explicitly asks to write a note, save a memo, or record something in the Zettelkasten vault. Triggers on 'これ書いて', 'メモして', 'ノートにして', 'Zettelkastenに保存', 'write this down', 'save this note', 'record this', 'これを記録して', 'ノートを作って'.

This skill should be used when the user wants to analyze a repository and extract reusable knowledge into Zettelkasten notes. Triggers on 'リポジトリを分析して', 'リポジトリを解剖', 'このリポジトリの知見をまとめて', 'コードベースを分析して Zettelkasten に', 'dissect this repo', 'analyze this codebase', 'extract knowledge from this repo'.