stevesolun

Design or revise concise skills with clear triggers, proportional constraints, progressive disclosure, and realistic validation.

日本語の概要は準備中です。原文の説明を表示しています。

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

日本語の概要は準備中です。原文の説明を表示しています。

Apply test-driven development with small, behavior-focused feedback loops. Use when the user asks to build or fix something test-first, mentions red-green-refactor, or wants integration tests.

日本語の概要は準備中です。原文の説明を表示しています。

Teach a skill or concept at the user's current level, optionally preserving a lightweight multi-session learning record.

日本語の概要は準備中です。原文の説明を表示しています。

Map a large, unclear, multi-session effort as linked decisions, then advance the map until the route to the destination is clear.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate questions using high-trust primary sources and traceable citations. Use when the user asks for research, current documentation or API facts, source verification, or evidence-backed comparison.

日本語の概要は準備中です。原文の説明を表示しています。

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

日本語の概要は準備中です。原文の説明を表示しています。

Resolve an in-progress Git merge or rebase conflict while preserving the relevant intent of both sides. Use when conflict markers or an interrupted merge/rebase need investigation and resolution.

日本語の概要は準備中です。原文の説明を表示しています。

Configure repository-local tracker, triage, and domain-document conventions needed by the Matt Pocock engineering skills.

日本語の概要は準備中です。原文の説明を表示しています。

Classify and advance issues or external pull requests through the configured triage workflow. Use explicitly to inspect queues, evaluate an item, recommend a state, or apply an authorized transition.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze a codebase for high-leverage architectural improvements and explain evidence, tradeoffs, and next steps. Use explicitly for architecture audits or deep-module refactoring opportunities.

日本語の概要は準備中です。原文の説明を表示しています。

Implement work from a spec, ticket, or agreed conversation. Use explicitly when the user wants an existing plan carried through to working code.

日本語の概要は準備中です。原文の説明を表示しています。

A relentless interview to sharpen a plan or design.

日本語の概要は準備中です。原文の説明を表示しています。

Synthesize an implementation-ready spec from the current conversation and relevant repository context. Use explicitly when the user wants agreed work captured as a spec or PRD.

日本語の概要は準備中です。原文の説明を表示しています。

Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker.

日本語の概要は準備中です。原文の説明を表示しています。

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

日本語の概要は準備中です。原文の説明を表示しています。

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

日本語の概要は準備中です。原文の説明を表示しています。

Compact the current conversation into a handoff document for another agent to pick up.

日本語の概要は準備中です。原文の説明を表示しています。

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

日本語の概要は準備中です。原文の説明を表示しています。

Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

日本語の概要は準備中です。原文の説明を表示しています。

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

日本語の概要は準備中です。原文の説明を表示しています。

Alive skill router — reads the current project's stack and loads/unloads skills dynamically. Invoke at session start or when project context changes.

日本語の概要は準備中です。原文の説明を表示しています。

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

日本語の概要は準備中です。原文の説明を表示しています。

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

日本語の概要は準備中です。原文の説明を表示しています。