getfflisted

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.
artyhoo/getff · ★ 0 · Code & Development · score 58

Install: claude install-skill artyhoo/getff

# Rules as Tests A unified framework for treating **every codebase rule as an executable test**. Documents lie; tests don't. This becomes critical when AI agents write the code, because LLMs reliably violate undocumented conventions and generate plausible-but-vacuous tests. > **Authoritative for:** skill activation conditions (frontmatter `description`); 5-layer framework summary; reference index (when to read which `references/*.md`); enforcement-extension surfaces (shift-left to AIF, shift-right to production, sideways via Pact). > **NOT authoritative for:** project-host goal — see consumer's own `README.md` (this skill is shipped to consumer projects via [`install.sh`](../../install.sh)). For the framework's authoring repo: see [README.md#why-this-exists](../../README.md#why-this-exists). Per-layer technical detail is in [references/overview.md](references/overview.md). ## When this skill is relevant Use this skill when the user is working on (or asking about): - Setting up linting / testing / CI / pre-commit / pre-push hooks for a JS/TS project - Architecture enforcement (layer rules, dependency direction, no-cycles, banned imports) - Mutation testing (Stryker, PIT, mutmut) - Contract testing between microservices (Pact, can-i-deploy) - Fighting AI agents introducing drift / `as any` / tautological tests - AI Factory (aif) integration with Claude Code - Production fitness functions: SLO-as-code, error budgets, observability - Feature flags, canary releases, chaos eng