konraddzbik

Build interactive, click-through architecture diagrams for software systems — a self-contained single HTML file with animated step-by-step flows, mode toggles (dev/prod, offline/online, v1/v2), dark/light theme, and a side panel with payload details, plus a companion markdown description. Use when the user wants to visualize or design a system: architecture diagram, service map, data flow, RAG/agentic flow, microservices topology, integration diagram, CI/CD or data/ETL pipeline, multi-agent system, or onboarding diagram — or to design a new service's flows before building. Natural-language triggers: 'I'm building X, what should the flow look like', 'pokaż jak działa system', 'diagram architektury', 'wizualizacja systemu', 'klikany diagram'. Do NOT use for static diagrams that belong inline (Mermaid/PlantUML), slide decks, or printable/PDF handouts — this produces interactive HTML for browser consumption.

Direct, artifact-focused code review and architecture critique. Opens with the most important issue first, states findings as artifact-focused critique, never sugarcoats. Professional but uncompromising — critiques the code, not the person. Works in English and Polish. Invoke when user says 'critical review', 'review this', 'critique this', 'be direct', 'check this idea', 'verify this solution', 'validate this approach', 'is this correct', 'does this make sense', 'sanity check', 'second opinion', 'what am I missing', 'bez ściemy', 'powiedz wprost', 'straight talk', 'rip it apart', 'what's wrong with this', 'be honest', 'don't sugarcoat', 'co jest nie tak', 'szczera ocena', 'oceń to', 'przejrzyj to', 'daj prawdę', 'sprawdź to', 'zweryfikuj to', 'czy to ma sens', or any request for direct technical feedback, idea validation, or solution verification. Also invoke for code reviews, architecture critiques, plan reviews, and PRD feedback.