model-design

Provide layout and notation guidelines for block diagrams and state charts.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/zeveck/zskills --skill model-design-zeveck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-design
Source: https://github.com/zeveck/zskills/tree/main/block-diagram/model-design
Command: npx skills add https://github.com/zeveck/zskills --skill model-design-zeveck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create clear, consistent guidelines for designing well-laid-out block diagrams and state charts to improve readability, verification, and collaboration across engineering teams.

Core Features & Use Cases

  • Layout rules for block diagrams (flow direction, spacing, alignment, port positioning).
  • State-chart guidelines (state sizing, transitions, labeling, and hierarchy).
  • Verification and anti-pattern avoidance to reduce crossings, overlaps, and ambiguity.

Quick Start

Apply these guidelines to produce readable, scalable block diagrams and state charts for your projects.

Frequently Asked Questions about model-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best layout guidelines for block diagrams in engineering documentation?

State-chart guidelines cover state sizing, transitions, labeling, and hierarchy to reduce crossings, overlaps, and ambiguity during modeling and architecture reviews.

How do I avoid overlaps and crossings when modeling complex systems?

Familiarity with layout practices, port alignment, overlap avoidance, and standardized notation such as MAAB-guided conventions is required to effectively apply these diagram design guidelines.

How do I design readable state charts for architecture reviews?

These guidelines apply to engineering teams who need to communicate complex systems clearly, especially for modeling tasks, architecture reviews, and engineering documentation.

Do I need MAAB-guided notation familiarity to use these block diagram rules?

Yes, prerequisites include familiarity with layout practices, port alignment, overlap avoidance, and standardized notation such as MAAB-guided conventions to properly apply the rules.