valorisa

setup-matt-pocock-skills

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

skill-factory

Advanced meta-skill for creating, reviewing, validating, and improving Claude skills following Anthropic's official patterns. Use when the user asks to build a production-ready skill, audit skill quality, generate complete skill packages with tests and validation, review skill architecture, or optimize skill triggering. Handles all 3 categories (document creation, workflow automation, MCP enhancement).

create-github-issues

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into GitHub issues.

diagnose

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

improve-codebase-architecture

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.

llm-council

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

promptor

Generate optimized, domain-agnostic prompts via a 5-circle validation pipeline fused with 18 optimization hacks. Produces auditable, copy-paste-ready prompts for any AI tool. TRIGGERS: 'create a prompt', 'optimize this prompt', 'promptor', '/promptor', 'generate a system prompt', 'prompt engineering', 'build me a prompt for'. Also triggers on: 'reverse prompt engineer this', 'improve this prompt', 'prompt audit'.

rescue-tokens

Use when user hits rate limits, quota exceeded errors, context exceeds 40%, or exhibits token waste symptoms (long conversations, wrong model, verbose output, MCP bloat, cache invalidation, expensive files, too many requests)

spec-driven

Activate spec-driven development mode with enforced pipeline (SPEC→PLAN→IMPL→VERIF→SYNTHESE), 3-way triage (FULL/LIGHT/SHIP), token budgets, and explicit gates. Use when starting a feature, refactoring, or complex task that benefits from structured spec-first workflow. TRIGGERS: 'spec-driven', '/spec-driven', 'mode spec', 'spec first', 'pipeline complet', 'workflow structure'. Do NOT trigger on simple questions, quick fixes, or when user explicitly wants fast/informal mode.

standardize-github-repo

Automatic GitHub repo standardization at publication checkpoints with bilingual READMEs (EN/FR), CI linting, badges, and About configuration

tdd-hybrid

Test-driven development combining strict discipline (Iron Law, mandatory verification) with intelligent workflow (planning, vertical slicing, domain awareness). Use when implementing features or fixing bugs with TDD.