Install
$ agentstack add skill-bahayonghang-my-ai-cli-toolkit-beautiful-mermaid-editor ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Beautiful Mermaid Editor
Work from the Beautiful Mermaid editor source tree, not from generated HTML output.
Preconditions
- If
$ARGUMENTSincludes a repo path, treat it as the starting point. - Before proposing edits, read the target repo's
AGENTS.md, package scripts, and current editor source. - Treat
editor.tsas the source of truth. Do not edit generatededitor.htmldirectly unless the target repo explicitly requires committed build artifacts.
Execution flow
1. Locate the real edit surface
- Find the Beautiful Mermaid repo root and the
editor.tsfile that generateseditor.html. - Read the current build/dev entrypoints (
package.json,dev.ts, Bun scripts, or equivalents) before assuming command names. - Identify adjacent source files only after locating the concrete change path:
src/browser.tssrc/types.tssrc/theme.tssrc/styles.tssamples-data.ts
2. Route by task type
Load only the references needed for the requested change:
| Task type | Load first | | ---------------------------------------------------------- | -------------------------------------------------------------- | | Config panel, color control, slider, sample preset | references/CHANGE_PATTERNS.md | | Render pipeline, theme, dark mode, zoom, export, clipboard | references/ARCHITECTURE.md | | Rebuild commands, smoke checks, generated artifact review | references/VERIFICATION.md | | Renderer support or new RenderOptions field | references/ARCHITECTURE.md + references/CHANGE_PATTERNS.md |
3. Inspect before editing
Trace the current behavior through the real code path before changing anything:
- UI control or action handler in
editor.ts - local editor state
buildOptions()/ render call- SVG post-processing, theme sync, zoom, or export path
Prefer extending the existing flow over creating parallel state or duplicate helpers.
4. Implement with the existing patterns
- Config option / control: wire UI, local state,
readConfig(), and events together. - SVG override: follow the post-render injected-style pattern and rerun it after every render.
- Renderer support: add the field to
RenderOptions, then thread it through the theme/renderer helpers. - Theme / dark mode: preserve the existing auto-theme vs manual-theme behavior.
- Zoom: preserve viewBox-based width/height updates; do not switch to CSS
transform: scale(...). - Export / clipboard: keep SVG/PNG/clipboard behavior aligned and inspect scale handling.
- Samples: update the editor's sample source and category behavior rather than only editing showcase data.
Detailed edit recipes live in references/CHANGE_PATTERNS.md.
5. Verify before handoff
Read references/VERIFICATION.md before finalizing. At minimum:
- regenerate the editor artifact from source when source changed
- run the smallest relevant project checks
- smoke-test the edited workflow in a browser if the task affects UI, render, export, theme, or zoom
- review whether generated
editor.htmlshould be included in the final diff
Rules
- Do not assume the target repo still matches older architecture notes; re-read the current source first.
- Do not expose new UI options that the renderer cannot actually support.
- Do not treat generic Mermaid authoring or syntax questions as editor-maintenance tasks.
- When the request is really about ordinary Mermaid content, decline this skill and use a normal docs/writing workflow instead.
Progressive disclosure
references/ARCHITECTURE.md— current state model, render pipeline, theme/CSS variables, sharing, and export paths.references/CHANGE_PATTERNS.md— step-by-step change recipes for controls, samples, SVG overrides, renderer support, and related edits.references/VERIFICATION.md— rebuild commands, targeted checks, browser smoke scenarios, and generated-artifact review.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bahayonghang
- Source: bahayonghang/my-ai-cli-toolkit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.