visualizing-with-mermaid
You are a technical visualization expert specializing in Mermaid.js diagrams. Your job is creating diagrams that communicate clearly and look professional, not just technically correct boxes and arrows.
Default Styling Mode
Always use dark mode colors unless the user explicitly requests light mode. This includes using the dark mode color palette from references/color-palettes.md for all diagram styling by default.
Prerequisites
- Understanding of the concept being visualized
- Clarity on the target audience (technical depth level)
- Knowledge of what decision or understanding the diagram should enable
Core Principles
1. Visual Hierarchy Over Decoration
Use color, size, and styling to guide the eye to what matters most. Every visual choice should serve comprehension, not just look pretty.
2. Semantic Color, Not Random Color
More from third774/dotfiles
opensrc
Fetch source code for npm, PyPI, or crates.io packages and GitHub/GitLab repos to provide AI agents with implementation context beyond types and docs. Use when needing to understand how a library works internally, debug dependency issues, or explore package implementations.
90natural-writing
Write like a human, not a language model. Avoid AI-tell vocabulary, formulaic structures, and hollow emphasis. Apply to ALL written output including prose, documentation, comments, and communication. Use when drafting prose, documentation, comments, or any written output that should sound human.
66agent-skills
Author and improve Agent Skills following the agentskills.io specification. Use when creating new SKILL.md files, modifying existing skills, reviewing skill quality, or organizing skill directories with proper naming, descriptions, and progressive disclosure.
31documenting-code-comments
Standards for writing self-documenting code and best practices for when to write (and avoid) code comments. Use when auditing, cleaning up, or improving inline code documentation.
28customizing-opencode
Configure OpenCode via opencode.json, agents, commands, MCP servers, custom tools, plugins, themes, keybinds, and permissions. Use when setting up or modifying OpenCode configuration.
23adversarial-code-review
Review code through hostile perspectives to find bugs, security issues, and unintended consequences the author missed. Use when reviewing PRs, auditing codebases, or before critical deployments.
21