Skills de Claude Code · página 45

|

|

|

|

|

|

|

|

別エージェントのinboxにメッセージを送信する。agent-to-agent通信の唯一の手段。

全エージェント（家老・足軽1-7・軍師）の稼働状態を一覧表示するスキル。tmux pane状態（稼働中/待機中/不在）とタスクYAML状態（task_id, status）と未読inbox数を統合表示。「稼働確認」「エージェント状態」「布陣確認」「agent status」で起動。

>

>

|

README.md（英語）とREADME_ja.md（日本語）の同期を確認・実行するスキル。README変更時に両言語版を必ず同時更新するために使用。「README更新」「README同期」「readme sync」で起動。

|

|

Find the ghost tokens. Audit Claude Code or Codex setup, see where context goes, fix it. Use when context feels tight.

Audit token waste across agent systems (Claude Code, Codex, OpenClaw, Hermes, OpenCode). Detect idle burns, model misrouting, and config bloat with dollar savings.

|

Open the Token Optimizer dashboard. Collects latest session data, regenerates the dashboard, and opens it in your browser.

多角色 YAML 工作流执行引擎——解析 workflow YAML，加载 agency-agents-zh 角色，按 DAG 顺序执行

The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行'). ALL task types. Not for first failures.

NoPUA Lite — core wisdom in ~1.5k tokens. Drives AI with trust and inner motivation instead of fear. Same Daoist philosophy, minimal footprint. For personal use and small-context models.

The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行'). ALL task types. Not for first failures.

>-

>-

>-

>-

>-

>-

>-

>-

>-

>-

>-

>-

>-

>-

Configure Spec Kitty agent profiles, host-specific paths, command installation, and model/tool routing.

Open or report the Spec Kitty dashboard. Use for dashboard URL, localhost daemon metadata in .kittify/.dashboard, --open, --kill, or status views.

Operate Spec Kitty git workflows, worktrees, safe commits, merge preflights, stale state checks, and recovery.

Install, verify, and repair Spec Kitty commands, skills, agent paths, runtime prerequisites, and common setup failures.

Upgrade Spec Kitty installations and repair generated commands, skills, migrations, and compatibility shims.

Recognize bulk-edit missions and apply occurrence classification guardrails before modifying many matching instances.

Run Spec Kitty charter interview, generation, context loading, and synchronization workflows.

Curate and apply Spec Kitty glossary terminology, canonical terms, aliases, conflicts, and semantic drift checks.

Load a Spec Kitty agent profile on demand for interactive sessions, including identity, governance scope, boundaries, and initialization.

Invoke Randy Reducer and semantic-compression doctrine for behavior-preserving code reduction.

Drive REASONS Canvas authoring and review for missions using Spec Kitty Structured-Prompt-Driven Development.

Run the Spec Kitty accept gate for a completed mission and verify final readiness before merge.

Merge an accepted Spec Kitty mission safely, preserving git invariants, mission state, and post-merge follow-through.

Run post-merge Spec Kitty mission review for spec-to-code fidelity, FR coverage, drift, risk, and final verdict.

Create or verify Spec Kitty mission retrospectives after merge and surface process learnings without blocking completed work.

Use Spec Kitty orchestrator-api from external systems, respecting host boundaries, state contracts, and workflow commands.

Author future Spec Kitty spk skills using the 3.2.0 naming convention, lifecycle families, and doctrine/command boundaries.

Discover the Spec Kitty 3.2.0 spk skill hierarchy, naming convention, legacy aliases, and the correct skill for a user intent.

Operate documentation-oriented Spec Kitty missions and ensure docs stay tied to shipped behavior and doctrine.

Operate the Spec Kitty plan phase: convert an approved spec into architecture, data flow, risks, and implementation strategy.

Operate pre-spec or in-mission research workflows while keeping findings tied to mission decisions.

Operate the Spec Kitty specify phase: turn user intent into a mission spec while preserving scope, ambiguity, and acceptance criteria.

Operate Spec Kitty task and work-package authoring, including tasks outline, package slicing, and finalization.

Explain Spec Kitty mission types, step contracts, action indices, and when to choose each mission workflow.

Recover from Spec Kitty blocked runtime states, missing artifacts, failed guards, stale worktrees, and decision-required loops.

Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.

Drive the canonical spec-kitty next control loop and route step, blocked, decision_required, and terminal results.

Orchestrate multi-repo, multi-mission Spec Kitty programs across dependencies, parallel agents, review gates, merge, and post-merge closeout.

Review a Spec Kitty work package through the runtime review surface and approve or reject with structured feedback.

Choose the correct Spec Kitty workflow for Codex CLI/desktop/cloud, Claude Code, and supported slash-command or command-skill harnesses.

Map Spec Kitty slash commands and CLI entry points to spk skills. Use when choosing /spec-kitty.* commands or explaining command-skill boundaries.

Guide a first Spec Kitty feature from setup through specify, plan, tasks, implementation, review, accept, merge, and retrospective.

Start here for Spec Kitty. Orient CLI users and supported agent-harness users; choose the right command, skill family, and recovery path.

Handle Spec Kitty team authentication, hosted credentials, account selection, and auth-related recovery.

Operate Spec Kitty connector integrations and route connector work across tracker, sync, SaaS, and external services.

Operate Spec Kitty team sync, hosted SaaS sync, offline queue, diagnostics, and recovery flows.

Operate Spec Kitty tracker workflows, tracker service discovery, binding, hosted routing, and tracker recovery.

Validate an approved mission before merge

Cross-artifact consistency and quality analysis

Interview and compile a project charter

Execute a work package implementation

Create an implementation plan

Generate research documents for the current mission

Review a work package implementation

Create a mission specification

Validate dependencies, finalize WP metadata, and commit all task artifacts.

Create a work package manifest

Materialize work package files

Translate implementation concerns into work packages

>-

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", or "organic growth". Also trigger when designing shareable features, crafting social media campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", or "LSM tree vs B-tree". Also trigger when choosing between SQL and NoSQL, designing data pipelines, or debugging distributed system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "fault tolerance", "mental model", "mapping", or "seven stages of action". Also trigger when diagnosing why users make mistakes, reducing product complexity, or improving error messages and feedback systems. Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.