engineering-diagrams
Create or revise software flowcharts, API sequence diagrams, state machines, and entity-relationship diagrams using Mermaid by default, with notation-specific checks and editable source.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- engineering-diagrams
- description
- Create or revise software flowcharts, API sequence diagrams, state machines, and entity-relationship diagrams using Mermaid by default, with notation-specific checks and editable source.
02 资源文件 5
- 资产文件assets/decision.mmd286 B
- 资产文件assets/lifecycle.mmd300 B
- 资产文件assets/request.mmd456 B
- 资产文件assets/schema.mmd296 B
- 参考文档references/practices.md2.5 KB
03 SKILL.md 正文
Engineering diagrams
Read shared standards and the relevant notation in diagram practices before authoring. For architecture or dependency analysis, use that specialist even when the requested output is Mermaid.
Choose the representation from the question: flowchart for decisions and branching, sequence for
ordered interactions, state diagram for lifecycle transitions, ER for entities and cardinality.
Use repository terminology and trace important edges to evidence. Include meaningful failure paths
when they affect the explanation. Save maintained Mermaid source as .mmd without Markdown fences.
Render with the shared helper using the local Mermaid CLI and inspect the result at its intended size. Match the destination's supported syntax; prefer established diagram types over experimental features. Complete the shared evidence checks before describing the result as validated.
04 同仓库更多 Skills
toolkit-smoke-test
Verify a toolkit update across installed agent hosts using skill discovery, installed versions, MCP startup, and harmless tool calls. Use after installation or for cross-host release checks.
security-check
Assess security implications of a software change using project scanners, dependency and secret checks, and changed trust boundaries. Use for requested security checks or changes affecting authentication, permissions, untrusted input, or sensitive data.
research-and-recommend
Research an open question or unfamiliar implementation, compare viable approaches against the user's constraints, and recommend the best fit using primary sources and applicable standards. Use when the user wants evidence-backed options and a recommendation; a single documentation lookup belongs to find-docs.
release-acceptance
Verify a deployed release against public behavior and persistence requirements, recording inspectable evidence and cleaning up owned test data.
project-check
Discover and run a project's verification commands, recording commit-specific results and missing checks. Use to validate a change or establish the repository's verification gate.
pr-closeout
Finish an authorized GitHub PR through review remediation, CI, metadata, merge, and post-merge verification. Use for PR closeout; keep assessment-only requests read-only.