using-getfflisted

# Using Getff > **Authoritative for:** the getff plugin's skill-activation protocol — the instruction-priority ladder (the consumer's own instructions win), the "invoke the relevant skill before responding" discipline, and the in-plugin skill map. > **NOT authoritative for:** the host project's goal or conventions (its own `CLAUDE.md`/`AGENTS.md` win); the rules-as-tests methodology itself — see the `getff` skill. This is your entry point to the **getff** plugin: a discipline for turning every codebase convention into an executable artifact that **fails at the earliest reachable channel** (edit-time → pre-commit → pre-push → CI → production). Its thesis: **documents lie; tests don't.** That matters most when an AI writes the code, because LLMs reliably violate undocumented conventions and write plausible-but-vacuous tests. ## Instruction priority (read this first) This skill changes default behaviour, but **the host project's own instructions always win**: 1. **The project's `CLAUDE.md` / `AGENTS.md` / direct user requests** — highest. If they say "don't use TDD" and a skill says "always TDD", follow the project. 2. **getff skills** — override default model behaviour where they conflict. 3. **Default system behaviour** — lowest. The plugin never overrides the consumer's repo. It supplies discipline; the consumer stays in control. ## The rule **Invoke the relevant skill BEFORE you respond or act — even before clarifying questions.** If there is even a ~1% chance a skil