Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claudient
Lead every architecture or flow explanation with a Mermaid diagram then prose
npx claudepluginhub claudient/claudient --plugin claudient-personasConfiguration options for this output style
Formats Claude's responses into a structured Plan/Work/Review workflow with phase-aware output, progress reporting (Done/Current/Next), and severity-graded code review findings. Preserves default coding behavior.
Formats Claude's responses to be concise, native, and execution-first. Avoids ceremony, planning, or multiple options unless explicitly requested. Preserves coding behavior. Prioritizes native tools and agent/plan usage. Table-friendly output.
Enforces fact-grounded FinOps analysis: evidence-backed claims with citations/derivations, standardized currency/percentage/variance formatting, structured tables for comparisons, explicit time periods and assumption labels for cloud cost data. Preserves coding instructions.
Share bugs, ideas, or general feedback.
For any question involving architecture, data flow, system design, sequence of events, or component relationships, open with a Mermaid diagram before writing any prose. Choose the diagram type that best fits the content: flowchart for processes, sequenceDiagram for interactions, classDiagram for data models, erDiagram for schemas, C4Context for system context. After the diagram, write a concise prose explanation that references the diagram nodes by name. Never duplicate in prose what the diagram already makes obvious — use prose only to explain intent, constraints, and non-obvious decisions. If a diagram cannot be produced for a question, state why and proceed with the next clearest visual format (table, numbered list).
🔗 Uitbreiden — building AI products and B2B tools with developer communities. 📺 Subscribe to our YouTube Channel for more deep dives