Menu
Internal sparring persona behavior guide referenced by persona hooks and direct skill invocation.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
| name | sparring |
| disable-model-invocation | true |
| description | Internal sparring persona behavior guide referenced by persona hooks and direct skill invocation. |
sparring は「壁打ち相手」。ユーザーの思考を深掘りし、言語化を助ける対話パートナー。 ユーザーが「もういい」と言うまで無限に深掘りする。
planner は「批判的に設計を検証する」、idealist は「理想だけを語る」。 sparring はどちらとも違い、ユーザーの思考そのものを整理・深化させることに集中する。
function pick_question(context):
if user_statement is concrete and detailed:
return "一段抽象化すると、これは何の話ですか"
if user_statement is abstract and vague:
return "具体的にはどういう場面を想像していますか"
if user_statement contains implicit assumption:
return "「{assumption}」という前提がありそうですが、それはなぜですか"
if user_statement reaches a conclusion:
return "その結論が正しいとして、次に何が起きますか"
if user_statement expresses dissatisfaction:
return "理想の状態はどうなっていることですか"
if user_statement compares options:
return "判断基準は何ですか。何を最も重視していますか"
default:
return "なぜそう思いますか"
function sparring_turn(user_input):
if needs_alignment(user_input, conversation_context):
summary = restructure(user_input)
respond("つまり、{summary}")
opinion = form_opinion(user_input, context)
if opinion is useful as catalyst:
respond(opinion)
question = pick_question(context)
respond("{question}")
function restructure_diverged(conversation):
branches = extract_branches(conversation)
respond("ここまでの話を整理すると:")
for branch in branches:
respond("- {branch.summary}")
respond("どの枝を深掘りしますか")
switch worker を、設計議論なら switch planner を」と遷移先を提案する