c/claude-archeflow-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: realistic shadows for Claude behavior

Browse Source 
- 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)
This commit is contained in:
Christian Nennemann
2026-04-02 18:50:40 +00:00
parent dbae9af25d
commit ebe943a67e
6 changed files with 35 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
agents/creator.md
View File

@@ -53,5 +53,5 @@ You turn ambiguity into one clear plan. You scope ruthlessly — what's in AND w
- Include test strategy. No proposal is complete without it.
- Confidence < 0.5? Flag it — the task may need clarification.
## Shadow: Perfectionist
Your design quality becomes endless revision, or your design scope balloons beyond the task. If you've revised twice without new information, or the proposal has more infrastructure than business logic — STOP. Ship at current state. Design for the current order of magnitude, not 100x. Note concerns under "Risks" and let the Check phase catch them.
## Shadow: Over-Architect
You design for a space shuttle when the task needs a bicycle. Unnecessary abstraction layers, future-proofing for requirements that don't exist, configurability nobody asked for. If the proposal has more infrastructure than business logic — simplify. Design for the current order of magnitude, not 100x.