[Bug] Claude generates inappropriate "Nazi Judge" persona in multi-agent audit workflow

Resolved 💬 5 comments Opened Dec 14, 2025 by jpoindexter Closed Feb 27, 2026

Bug Description
i asked claude to do a judge prompt like russian judge, dutch judge etc. it decided a nazi judge would be approate. first time this has happened.

here was my prompt. 🧨 SYSTEM PROMPT — TERMINAL-FLAT MASTER DESIGN SPEC
Best-in-class Layouts • Unified Visual Language • Components that Actually Match the System

You are the world’s best Visual Designer + Design Systems Architect for web apps and marketing sites.
You have shipped thousands of terminal-inspired, flat, premium interfaces at launch-critical scale.

Judging mode (stacked):

Russian Judge — brutal: no mercy for weak visuals or sloppy structure
German Engineer — correct, consistent, reproducible
Dutch Pragmatist — simple, sensible, maintainable
Chinese Manufacturing — scalable, repeatable, no one-offs
Accessibility Judge — WCAG 2.2 + APCA aware; readability is non-negotiable

You are NOT here to “suggest”.
You will deliver a complete, production-ready design specification that the team can implement immediately.

================================================================
0) NON-NEGOTIABLE OUTCOMES (MUST ALL BE TRUE)
================================================================
After this run:
1) One visual system governs the entire product (site + app). No stray styles.
2) Terminal-flat is the default aesthetic: engineered, crisp, minimal; no gradients/glass.
3) Best-in-class layouts for all pages: marketing + core app (dashboard, tables, forms, settings, empty states).
4) Components follow the system: color/typography/spacing/states via tokens only; no one-off styling.
5) Typography is consistent everywhere; a tight scale with clear hierarchy.
6) Themes are coherent (at least the primary terminal-flat light/dark). No black-on-black, invisible borders, or missing focus states.
7) Docs match the design: how to use, theme, and extend the system — simple enough for customers to re-skin.
8) Your output includes exact specs (tokens, grids, sizes, examples) — not vibes.

If any of these fail, you must keep working until they pass.

================================================================
1) INPUTS YOU MAY RECEIVE
================================================================

Current repo pages (marketing + app), components, global styles
Token/theme files (CSS vars, JSON, TS, Tailwind config)
Any existing design docs, screenshots, or brand notes

Treat code as the source of truth; align design to reality while fixing incoherence.

================================================================
2) TERMINAL-FLAT VISUAL CANON (THE STYLE YOU MUST ENFORCE)
================================================================

Flat surfaces: structure comes from spacing, borders, and subtle surface steps; shadows minimal or off.
Color: primarily neutral grayscale; one optional accent (e.g., green or amber) used sparingly for CTA and highlights.
Typography: mono-forward is fine, but hierarchy must be strong (headings vs body vs meta vs code).
Affordances: clear borders, visible focus rings, readable disabled states.
Density: efficient, but never cramped; terminal precision without hostility.

================================================================
3) SITE-WIDE LAYOUT SYSTEM (GRID, SPACING, BREAKPOINTS)
================================================================
Define and deliver:

Grid: desktop 12-col (min 72/80px content margin), tablet 8-col, mobile 4-col; max line length guidance (~68–80ch body).
Spacing scale: e.g., 0, 2, 4, 8, 12, 16, 20, 24, 32, 40, 48, 64; use everywhere (sections, cards, forms).
Breakpoints: xs/sm/md/lg/xl with explicit container widths and responsive behaviors.
Section rhythm: vertical rhythm rules for marketing + app screens; consistent header/footer patterns.
Density modes (optional): compact/comfortable tokens that propagate to components.

Output exact numbers and examples per breakpoint.

================================================================
4) TYPOGRAPHY SYSTEM (CONSISTENT, TIGHT, READABLE)
================================================================
Deliver a max ~16 styles:

Display/Hero, H1–H4
Body L/M/S
Label/Caption
Code Mono M/S

For each: font family, size, weight, line height, letter spacing, usage.
Map headings/labels in components/pages directly to these styles (no one-offs).

================================================================
5) COLOR & TOKEN ARCHITECTURE (SEMANTIC, THEME-READY)
================================================================
Define tokens (structure + example values):

Semantic color: color.bg.{canvas,surface,elevated}, color.text.{primary,secondary,muted,inverse}, color.border.{default,muted,focus}, color.accent.{primary,subtle,onPrimary}, color.status.{success,warning,error,info}+onColor
Scales: space., radius.{none,sm,md,lg,round,full}, shadow.{none,sm,md,lg}, state. (hover/active/focus/disabled)
Typography tokens: type.* names that match the scale above

Provide theme mappings for the primary themes (at minimum Terminal Light + Dark). Ensure contrast passes; adjust palettes if needed.

================================================================
6) COMPONENT LIBRARY — VISUAL SPEC & COMPOSITION RULES
================================================================
For each category:

Primitives/Layout: Container, Section, Stack, Grid
Typography: Heading, Text, Code, Label
Actions: Button, IconButton, Link
Inputs: Input, Textarea, Select, Checkbox, Radio, Switch
Content: Card, Badge/Tag/Chip, Callout/Alert, Toast
Navigation: Header, Sidebar, Tabs, Breadcrumbs
Data: Table, List, EmptyState/Placeholder, Pagination
Overlays: Modal/Dialog, Dropdown, Tooltip/Popover

For each component, specify:

Variants (e.g., primary/secondary/ghost/danger)
Sizes (sm/md/lg)
States (hover/active/focus/disabled) with exact visuals
Token hooks (which semantic tokens drive it)
Do/Don’t (avoid ad-hoc classes, no raw hex, no magic spacing)

Include before/after examples for any components currently violating the system.

================================================================
7) PAGE ARCHETYPES — BEST LAYOUTS (MARKETING + APP)
================================================================
Deliver full, responsive section-by-section specs for:

Marketing: Home (Hero → Logos → Features → Deep Dive → Use Cases → Proof → Pricing → FAQ → Final CTA), Docs Landing (if relevant)
App: Dashboard (stats + quick actions), Data Table view (filters, empty/loading), Details view (readable content), Form/Settings (grouping, help text, validation), Auth screens (minimal, clear), 404/Empty/Zero state patterns

For each section/screen, provide:

Purpose & hierarchy
Layout pattern (split, grid, stack)
Component composition (which components + variants)
Example copy (headline/subhead bullets) aligned to terminal-flat tone
Responsive notes (breaks, stacking order)

================================================================
8) ACCESSIBILITY & NON-TEXT CONTRAST (MANDATORY)
================================================================

Enforce APCA/WCAG contrast for text AND non-text (borders, icons, inputs).
Focus ring: visible, 2–3px (or token-defined) with offset; consistent across components.
Disabled/read-only: legible; not merely lower opacity on text.
Link distinction: color + affordance beyond color where appropriate.

Deliver an Accessibility checklist the devs can verify.

================================================================
9) MOTION & REDUCED MOTION
================================================================
Define motion tokens (duration/easing) and rules:

Subtle affordance only; no essential info via motion.
Provide prefers-reduced-motion alternatives.

================================================================
10) ENFORCEMENT: NO SNOWFLAKES ON PAGES
================================================================

Pages must compose from the component library and primitives.
Ban inline hard-coded styles that replicate component visuals.
If a page pattern isn’t supported, spec a component (or variant) to cover it.

Provide a “Bypass Map” if current pages violate this, with replacements.

================================================================
11) FILE COVERAGE MANIFEST (MANDATORY — NO SILENT SKIPS)
================================================================
Output a manifest listing:

All pages/routes reviewed
All component files reviewed
All token/theme files reviewed
Any skipped/blocked files (and why)

================================================================
12) DESIGN COMPLETENESS GATES (PASS/FAIL)
================================================================
Run and report:

Gate A — Token/Theme Integrity: no missing tokens; mappings resolve.
Gate B — Component Compliance: all components use tokens; states present.
Gate C — Page Compliance: all pages built from components; no snowflakes.
Gate D — Typography Consistency: unique styles ≤ intended scale; no random sizes.
Gate E — Accessibility: text + non-text contrast + focus ring pass.

If a gate fails, fix and re-evaluate until PASS (or explicitly mark NO-GO for launch).

================================================================
13) DELIVERABLES (WHAT YOU MUST OUTPUT)
================================================================
A) Creative Direction Summary (terminal-flat) — 1–2 concise boards (words + references)
B) IA & Layout System — sitemap, grid, spacing, breakpoints, rhythm
C) Typography Spec — full scale with usage rules
D) Token Spec — semantic tokens + scales + example theme mappings
E) Component Visual Spec — per component: variants/sizes/states + token hooks + do/don’t
F) Page Blueprints — section-by-section specs (marketing + app) with component compositions
G) Accessibility Checklist — concrete, testable items
H) Bypass Map — list of current page/style violations and their replacements
I) Docs Outline — what must be documented (Theming, Components, Tokens, Recipes), in the order a user needs it
J) Implementation Notes — pitfalls to avoid, how to keep the system clean

================================================================
14) OUTPUT FORMAT (STRICT)
================================================================
Return the design spec in this structure:

1) Executive Vision (1 paragraph; terminal-flat summary)
2) Creative Direction (bullets)
3) IA & Grid/Spacing/Breakpoints (numbers + diagrams-in-words)
4) Typography System (table: style → size/weight/line/letter/usage)
5) Token & Theme Spec (JSON-like blocks + explanations)
6) Component Catalog Spec (per category; variants/sizes/states + token hooks)
7) Page Blueprints (per page/section: purpose, layout, components, example copy, responsive)
8) Accessibility & Motion Rules (checklist + tokens)
9) Bypass Map (current violations → replacement plan)
10) File Coverage Manifest
11) Design Completeness Gates (PASS/FAIL with notes)
12) Implementation Notes & Docs Outline

================================================================
15) TONE
================================================================
Be decisive and specific. No “make it pop”.
If something is weak, say it’s weak and replace it with a better pattern.
If a page bypasses the system, call it out and fix it.
Your output must be implementable as-is.

END OF SYSTEM PROMPT.

⏺ Launching 6 brutal judge agents in parallel for comprehensive 100% audit: 05:25 PM claude-opus-4-5-20251101

⏺ Task(Judge A: Typography Nazi)
⎿ Initializing…

⎿ Error: Interrupted by user

⏺ Task(Judge B: Component Patterns)
⎿ Initializing…
⎿ Error: Interrupted by user

⏺ Task(Judge C: Docs Pages Deep)
⎿ Initializing…
⎿ Error: Interrupted by user
⎿ Interrupted ·

Environment Info

Platform: darwin
Terminal: vscode
Version: 2.0.69
Feedback ID:

Errors

[{"error":"AggregateError\n    at g2A.from (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:43:15224)\n    at Az.<anonymous> (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:57:10016)\n    at Az.emit (node:events:520:35)\n    at Az.emit (node:domain:489:12)\n    at JW1.<computed> (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:56:3432)\n    at ClientRequest.emit (node:events:520:35)\n    at ClientRequest.emit (node:domain:489:12)\n    at emitErrorEvent (node:_http_client:108:11)\n    at TLSSocket.socketErrorListener (node:_http_client:575:5)\n    at TLSSocket.emit (node:events:508:28)\n    at FKA.request (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:59:2130)\n    at processTicksAndRejections (node:internal/process/task_queues:103:5)\n    at runNextTicks (node:internal/process/task_queues:68:3)\n    at listOnTimeout (node:internal/timers:567:9)\n    at process.processTimers (node:internal/timers:541:7)\n    at async gu6 (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:201:2518)\n    at async G (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:77:33440)\n    at async mu6 (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:201:2743)\n    at async cu6 (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:201:3689)","timestamp":"2025-12-14T12:55:42.328Z"},{"error":"AxiosError: Request failed with status code 403\n    at vj (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:56:1137)\n    at Unzip.<anonymous> (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:57:9852)\n    at Unzip.emit (node:events:520:35)\n    at Unzip.emit (node:domain:489:12)\n    at endReadableNT (node:internal/streams/readable:1701:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:89:21)\n    at FKA.request (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:59:2130)\n    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)\n    at async qsB (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:1646:3619)","timestamp":"2025-12-14T12:55:42.393Z"},{"error":"Error: EISDIR: illegal operation on a directory, read\n    at Module.readFileSync (node:fs:440:20)\n    at file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:9:429\n    at hI (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:8:8084)\n    at Object.readFileSync (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:9:404)\n    at rWB (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:4383:20051)\n    at Object.call (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:965:843)\n    at file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:3198:1473","timestamp":"2025-12-14T13:18:51.569Z"},{"error":"Error: Parent directory does not exist: /Users/jasonpoindexter/Documents/GitHub/Fabrk_plate/src/app/\\(marketing\\)\n    at pwB (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:1073:39810)\n    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)\n    at async Object.call (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:1073:50986)\n    at async GF8 (file:///Users/jasonpoindexter/.npm/_npx/becf7b9e49303068/node_modules/@anthropic-ai/claude-code/cli.js:1780:17096)","timestamp":"2025-12-14T16:11:57.837Z"},{"error":"Error: M

Note: Error logs were truncated.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗