Devil Gate

Effect

Systematizes the Devil’s Advocate “what to look for” into 10 distinct perspectives. You don’t run all of them every time — select based on the nature of the change.

When to Use

• CR (Code Quality) applies to every change (baseline)
• The other 9 perspectives are selected based on what changed

How It Works

1. Select Applicable Perspectives

ID	Perspective	When to Apply
SR	Security	API / auth / input handling changes
CR	Code Quality	All changes (always applied)
UX	UI/UX	Component / style changes
ARCH	Architecture	Changes spanning multiple modules
DDD	DDD Boundaries	Domain layer changes
PERF	Performance	Rendering / bulk data processing
A11Y	Accessibility	UI component additions
MEM	Memory Leaks	Async / WebSocket / Observer code
COMPAT	Compatibility	Browser / runtime API usage
FLOW	Data Flow	Service-to-service communication path changes

2. Execute the Checklist for Each Selected Perspective

3. Concerns Found → Fix → Re-check → Converge to Zero

Combinations

Card	Synergy
Devil Chain	Slot checklist items into each chain step (structured review)
Devil Starswarm	Assign an Agent per perspective (parallel review)

Growth

The checklists are not static. They evolve through battle.

Devil execution → new pattern discovered → append to checklist
→ Referenced 3+ times → promote to Skill

---

The gate through which all Devil cards pass. — Eris

Want to use this card permanently? Convert it directly into a SKILL.md — Effect → Overview, When to Use → Trigger, How It Works → Steps.