artyhoo

arch

Use when starting the EXTERNAL design contour — turning a raw idea or prep-doc into a reviewed design and a routed handoff. Wraps superpowers:brainstorming unchanged and adds only the two missing pieces - a cold two-altitude design review (top-tier goal/feasibility critic + executor-tier facts/patterns reviewer, dispatched as read-only subagents) and exit routing per the CLAUDE.md task-tier criteria (factory-bound → kickoff → staging → /pipeline or bridge auto-dispatch; small in-session → superpowers writing-plans tail; tiny → direct edit). Triggers - /arch, external contour, внешний контур, спроектируй идею, задумка в архитектуру, design contour, arch loop, продумай и спроектируй, идея → kickoff. NOT for reviewing code (/reviewer), dispatching stages (/pipeline), factory runtime questions (aif-doctor), or a bare brainstorm with no handoff (use superpowers:brainstorming directly).

self-reflection

Use when introducing or extending a rule, principle, pattern, methodology, discipline, or process change in this repository — before closing the recommendation, run §1.7 forward+backward checks. Auto-trigger on keywords «правило», «принцип», «дисциплина», «методология», «процесс», «recommend», «introduce rule», «new principle», «discipline change», «process rule», «meta», «recursive», «applies to itself», «check own work», «self-review», «forward check», «backward check», «closing recommendation», «discipline-bearing artefact», «self-reflection», «anti-pattern», or any edit touching `.claude/rules/`, `packages/core/principles/`, `docs/meta-factory/EXECUTION-PLAN.md`, `docs/meta-factory/prior-art-evaluations.md`, `CLAUDE.md`. **Do NOT trigger** on simple typo fixes, code edits without rule changes, or routine PR work — overuse fatigues the discipline.

story

Use when work is done / a PR was pushed, or when the user asks to recap what was done ("расскажи что сделали", "расскажи историю", "story", "recap", "по актам") — tells the story of this session in plain, engaging language, by acts, with jargon explained, honest about what's left. Output language follows AIF_HOOK_LANG (RU operator / EN default).

tool-bootstrapping

Use when analysing project stack for MCP or skill recommendations, user mentions tool bootstrapping, MCP installation, skill discovery, project onboarding tools, package.json deps changed, .ai-factory/tool-decisions.md, AIF /aif, tool detection, инструменты, бутстраппинг, MCP серверы, скиллы, зависимости, онбординг, подбор инструментов, предложение инструментов, подтверждение установки, memory persistence for tools, tool proposal confirmation, incremental tool re-evaluation, rejected tools memory.

getff

Use when treating any codebase rule (architectural, naming, dependency, test-quality, contract, SLO) as an executable test that fails the build when violated, or when the user asks about enforcing code quality, fighting AI-generated code drift, setting up linters/tests/CI/pre-commit hooks, designing review processes, mutation testing, contract testing, fitness functions, observability-driven development, SLO-as-code, or any version of "how do I make my codebase resistant to AI agents breaking my conventions". Also trigger on any mention of ArchUnit, Stryker, Pact, dependency-cruiser, AI Factory (aif), Husky, lint-staged, ESLint flat config, Zod validation strategy, or shift-left/shift-right testing. Strongly trigger when the user mentions Claude Code, Cursor, or Copilot writing code that "looks fine but is wrong" — that is the core problem this skill addresses.

installing-enforcement

Use when the user wants to actually WIRE the hard enforcement layer (git pre-commit/pre-push hooks + CI) into their repo, or asks "how do I make these rules actually fail the build / block a commit / run in CI", or wants to turn the rules-as-tests methodology from advice into a build-failing gate. Explains the soft-vs-hard boundary and points at the /getff:install-enforcement command.

using-getff

Use when starting any conversation in a repo that has the getff plugin installed — establishes how to find and use the getff skills, the instruction-priority ladder (the project's own CLAUDE.md/AGENTS.md win), and the "invoke the relevant skill before responding" discipline. Trigger on session start, before any first reply, and whenever code quality, linting, CI, pre-commit/pre-push hooks, architecture rules, mutation/contract testing, or "stop the AI breaking my conventions" comes up.

template-audit

Use when auditing rendered templates via local advisory review. Triggers on keywords «template», «audit», «render», «generated docs», «AGENTS.md», «paraphrase», «cue placement», «local advisory», «template-render», «audit-template». Session-bound under Claude Code subscription — no API key, no CI gate, no blocking. Step 1 runs deterministic probes; Step 2 asks the current session to semantic-check for paraphrase / cue-placement bugs (P2/P3/P5 from Wave 6 D-2 taxonomy, not in CI per Decision 3).

aif-orchestrator-discipline

> **Authoritative for:** orchestrator-worker discipline for aif-dispatched agents — REPORT format, park-vs-proceed contract, stage-gate verification, condensed orchestrator-planning (launch-table, Mode A/B, stage-gate) and reviewer-discipline (GO/REVISE/STOP, DECISION-NEEDED). > **NOT authoritative for:** project goal — see consumer's README.md. The FULL orchestrator workflow (quota zones, queue-mode anti-collusion, Phase -1 dual-reviewer, cross-umbrella priority) — that is the meta-orchestrator

aif-review-project-context

> **Authoritative for:** project-specific review conventions injected into AI Factory's `aif-review` skill (and its background `review-sidecar`) — the anti-tautology / two-AI test-review checks this project requires in addition to AIF's generic review. > **NOT authoritative for:** project goal — see the consumer's README.md. The generic correctness/security/performance review — that stays owned by AIF's `aif-review` SKILL.md; this file augments it.

aif-rules-check-project-context

> **Authoritative for:** project-specific rule checks injected into AI Factory's `aif-rules-check` skill (and its `rules-sidecar`) — the two checks from this project's `RULES.md` that are NOT enforced at an earlier deterministic channel (R10 naming, R4/R17 test-existence) and therefore need a verify-time pass. > **NOT authoritative for:** project goal — see the consumer's README.md. The R1–R20 corpus itself — that lives in `.ai-factory/RULES.md`, which `rules-sidecar` already reads; this file on