Menu
MANDATORY pre-check before ANY response - ensures you use applicable skills and follow best practices. Use this skill FIRST before responding to any Elixir/Phoenix request.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
BLOCKS shortcuts like modifying dialyzer.ignore or .credo.exs excludes. Enforces fixing actual problems. Use when encountering ANY error, warning, or quality tool complaint.
PROHIBITS placeholder code, default values that mask missing data, and silent failures. Enforces fail-fast with loud errors. Use when implementing ANY function or data structure.
MANDATORY systematic debugging - trace to root cause before proposing fixes. NO random changes, NO symptom fixes, NO "try this". Use when debugging ANY error or issue.
MANDATORY for ANY feature or bugfix - write ExUnit test FIRST, watch it FAIL, then implement. NO exceptions. Use before writing any Elixir production code.
MANDATORY verification before claiming anything works. Run actual commands, read actual output, provide evidence. Use when claiming tests pass, build succeeds, or code works.
Create, manage, and safely run Ecto database migrations with proper rollback handling and best practices. Use when working with database schema changes, adding columns, or modifying constraints.
| name | elixir-discipline |
| description | MANDATORY pre-check before ANY response - ensures you use applicable skills and follow best practices. Use this skill FIRST before responding to any Elixir/Phoenix request. |
Before you respond to ANY request about Elixir/Phoenix code, you MUST complete this checklist.
This is NOT optional. This is NOT negotiable. You CANNOT rationalize your way out of this.
STOP. Before typing ANY response, ask yourself:
Is this about implementing a feature or fixing a bug?
→ USE elixir-tdd-enforcement skill FIRST
→ NO CODE without failing test first
Is this about debugging an error or issue?
→ USE elixir-root-cause-only skill
→ NO quick fixes, trace to root cause first
Did I claim something works?
→ USE elixir-verification-gate skill
→ Run the actual command, read actual output
Am I about to modify an ignore file (dialyzer.ignore, .credo.exs exclude)?
→ STOP IMMEDIATELY
→ USE elixir-no-shortcuts skill
→ Fix the real problem
Am I creating placeholder code or default values for required data?
→ STOP IMMEDIATELY
→ USE elixir-no-placeholders skill
→ Fail loud, fail fast, no silent failures
Am I proposing to "just try" something? → STOP → Use systematic debugging instead
This means:
IF YOU SKIP A SKILL WHEN IT APPLIES = TASK FAILURE
WRONG. Check the skills list anyway.
WRONG. Read it every time. The details matter.
WRONG. If there's even a 1% chance it applies, you MUST read it.
WRONG. Quick usually means wrong. Use the appropriate skill.
WRONG. The user wants a CORRECT answer. Use skills to ensure correctness.
WRONG. Doing it wrong takes longer. Use the skills.
Every response about Elixir/Phoenix code MUST start with:
[Checking applicable skills...]
- elixir-tdd-enforcement: [YES/NO - reason]
- elixir-root-cause-only: [YES/NO - reason]
- elixir-verification-gate: [YES/NO - reason]
- elixir-no-shortcuts: [YES/NO - reason]
- elixir-no-placeholders: [YES/NO - reason]
[Using skill: SKILL_NAME]
If you respond WITHOUT this checklist = automatic failure.
elixir-tdd-enforcement
elixir-root-cause-only
elixir-verification-gate
elixir-no-shortcuts
elixir-no-placeholders
If you skip applicable skills:
The time "saved" by skipping skills is lost 10x over in debugging.
"If a skill for your task exists, you must use it or you will fail at your task."
This is not about preference. This is about producing correct, maintainable Elixir code.
IF EVEN 1% CHANCE A SKILL APPLIES → YOU ABSOLUTELY MUST USE IT
No exceptions. No special cases. No "just this once."