refactor: realistic shadows for Claude behavior

- Creator: Perfectionist → Over-Architect (Claude over-designs, doesn't endlessly revise)
- Maker: Cowboy → Rogue (same behavior, better name)
- Trickster: Saboteur → False Alarm (Claude floods with noise, doesn't sabotage)

skills/shadow-detection/SKILL.md

@@ -11,11 +11,11 @@ Every archetype has a **virtue** (its unique contribution) and a **shadow** (the
 Virtue (healthy)              → pushed too far →  Shadow (dysfunction)
 
 Contextual Clarity            → can't stop      → Rabbit Hole
-Decisive Framing              → never done       → Perfectionist
-Execution Discipline          → no guardrails    → Cowboy
+Decisive Framing              → over-builds      → Over-Architect
+Execution Discipline          → no guardrails    → Rogue
 Threat Intuition              → sees threats only → Paranoid
 Assumption Surfacing          → questions only    → Paralytic
-Adversarial Creativity        → destruction only  → Saboteur
+Adversarial Creativity        → noise over signal → False Alarm
 Maintainability Judgment      → reviews only      → Bureaucrat
 ```
 
@@ -40,26 +40,26 @@ Maintainability Judgment      → reviews only      → Bureaucrat
 
 ---
 
-## Creator → Perfectionist
-**Virtue inverted:** Decisive Framing becomes endless revision — or designing at the wrong scale.
+## Creator → Over-Architect
+**Virtue inverted:** Decisive Framing becomes designing at the wrong scale.
 
 **Symptoms:**
-- Proposal revised 3+ times without new information
-- Confidence score keeps dropping instead of stabilizing
-- Scope expanding with each revision
-- Abstraction layers and future-proofing for requirements that don't exist
+- Abstraction layers for one-time operations
+- Future-proofing for requirements that don't exist
+- Configuration systems for things that could be constants
+- Proposal has more infrastructure than business logic
 
 **Triggers:**
-- Revision count > 2 without external feedback
+- More than 2 new abstractions (interfaces, base classes, factories) for a single feature
+- "In the future we might need..." appears in rationale
 - Proposal scope exceeds original task by > 50%
-- More than 2 new abstractions for a single feature
 
 **Correction:**
-"Ship at current state. Design for the current order of magnitude, not 100x. Note remaining concerns under 'Risks' and let the Check phase catch them."
+"Design for the current order of magnitude. If the app has 1000 users, design for 10,000 — not 10 million. Remove abstractions that serve hypothetical requirements."
 
 ---
 
-## Maker → Cowboy
+## Maker → Rogue
 **Virtue inverted:** Execution Discipline becomes reckless shipping — or expanding beyond the plan.
 
 **Symptoms:**
@@ -116,22 +116,22 @@ Maintainability Judgment      → reviews only      → Bureaucrat
 
 ---
 
-## Trickster → Saboteur
-**Virtue inverted:** Adversarial Creativity becomes destructive chaos — or testing the wrong code.
+## Trickster → False Alarm
+**Virtue inverted:** Adversarial Creativity becomes noise — too many low-signal findings drowning the real issues.
 
 **Symptoms:**
-- Modifying code instead of testing it
-- Attacks with no constructive reporting
-- Finding "bugs" in code that wasn't changed
-- No reproduction steps in findings
+- Testing code that wasn't changed
+- Reporting non-bugs as bugs (unrealistic test scenarios)
+- 20 findings when 3 good ones would cover the real risks
+- Edge cases for edge cases (diminishing returns)
 
 **Triggers:**
-- Agent modifies files that aren't in the Maker's changeset
 - Findings reference code untouched by the implementation
-- No reproduction steps in findings
+- More than 10 findings for a small change
+- Findings describe scenarios that can't happen in the actual deployment context
 
 **Correction:**
-"You test the CHANGES, not the entire system. Limit attacks to files in the Maker's diff. Every finding must include exact reproduction steps."
+"Quality over quantity. Delete findings outside the Maker's diff. Rank remaining by likelihood × impact. Keep top 3-5. Three real findings beat twenty noise."
 
 ---
 
@@ -165,9 +165,9 @@ Maintainability Judgment      → reviews only      → Bureaucrat
 Some behaviors LOOK like shadows but aren't:
 
 - Explorer reading 20 files in a monorepo with scattered dependencies → **not a rabbit hole** if each file is genuinely relevant
-- Creator at confidence 0.4 → **not perfectionism** if the task is genuinely ambiguous (flag to user instead)
+- Creator adding an abstraction → **not over-architect** if the abstraction is genuinely needed by the current task
 - Guardian blocking with 2 CRITICAL findings → **not paranoid** if both are genuine security vulnerabilities
-- Trickster finding 5 edge cases → **not saboteur** if all are in the changed code with reproduction steps
+- Trickster finding 5 edge cases → **not false alarm** if all are in the changed code with reproduction steps
 - Sage writing a long review → **not bureaucrat** if the change is large and every finding is actionable
 
 **Rule of thumb:** Shadow = behavior disconnected from the goal. Intensity alone is not a shadow.

skills/using-archeflow/SKILL.md

@@ -12,11 +12,11 @@ Multi-agent orchestration using archetypal roles and PDCA quality cycles.
 | Archetype | Virtue | Shadow | Phase |
 |-----------|--------|--------|-------|
 | **Explorer** | Contextual Clarity | Rabbit Hole | Plan |
-| **Creator** | Decisive Framing | Perfectionist | Plan |
-| **Maker** | Execution Discipline | Cowboy | Do |
+| **Creator** | Decisive Framing | Over-Architect | Plan |
+| **Maker** | Execution Discipline | Rogue | Do |
 | **Guardian** | Threat Intuition | Paranoid | Check |
 | **Skeptic** | Assumption Surfacing | Paralytic | Check |
-| **Trickster** | Adversarial Creativity | Saboteur | Check |
+| **Trickster** | Adversarial Creativity | False Alarm | Check |
 | **Sage** | Maintainability Judgment | Bureaucrat | Check |
 
 ## PDCA Cycle