amw-text-visual-state

Generates validated ASCII state machines and user-journey storyboards for documentation.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-webdesign --skill amw-text-visual-state-emasoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amw-text-visual-state
Source: https://github.com/Emasoft/ai-maestro-webdesign/tree/main/skills/amw-text-visual-state
Command: npx skills add https://github.com/Emasoft/ai-maestro-webdesign --skill amw-text-visual-state-emasoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Modeling stateful processes like user lifecycles, issue triage, or retention loops in plain text is error-prone: states get orphaned, transitions lack labels, and diagrams break terminal width limits. This Skill produces rigorous, completeness-checked ASCII state machines that paste cleanly into PRs, ADRs, and growth docs. ## Core Features & Use Cases - Bracket-notation state machines: Renders [STATE] boxes with labeled --> transitions, guard conditions ([guard: x]), side-effect actions (/{action}), and terminal ((STATE)) markers. - Completeness verification: Checks every state has ingress and egress edges, every arrow has a trigger label, and recovery states have paths back to healthy states before delivery. - Metric annotation: Links each transition to a dashboard or query (e.g. metric: retention_rate_7d (grafana://dash/retention)) so the diagram stays falsifiable. - Mandatory validation gate: Every diagram passes bin/amw-validate-ascii.py and respects 78-column terminal / 100-column GitHub width ceilings. - Use Case: Ask for an ASCII state machine of your onboarding funnel, and receive a validated diagram of New → Activated → Retained → Churned with guards, metrics, and recovery edges ready to paste into a pull request. ## Quick Start Ask the AI to draw an ASCII state machine for your user lifecycle with states New, Activated, Retained, and Churned, including the trigger for each transition.

Frequently Asked Questions about amw-text-visual-state

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

FAQPage Schema
How do I create an ASCII state machine for a user lifecycle?▼

Provide the full state list, the trigger for each transition, any guard conditions or actions, and the start and end states. The Skill drafts a bracket-notation diagram, runs a completeness check, and validates it with an ASCII linting script before presenting it in a fenced block.

What notation does a text state diagram use for guards and actions?▼

Guards use a bracket prefix like [guard: has_verified_email] and actions use a slash suffix like /{ send_welcome_email }, placed on the transition label between the trigger and the target state. Terminal states use double brackets like ((CHURNED)) and optional transitions use dotted ..> arrows.

Can I add metrics or dashboard links to state transitions?▼

Yes, each transition can carry a metric annotation line such as metric: retention_rate_7d (grafana://dash/retention) below the arrow. Uninstrumented transitions should be tagged with a TODO marker so reviewers know they are not yet measured.

When should I use Mermaid instead of an ASCII state machine?▼

Use Mermaid or SVG output when you need clickable, rendered diagrams rather than paste-able monospace text. This Skill emits ASCII only and routes Mermaid requests to the diagram-architecture skill in mermaid-passthrough mode.

What are the limitations of ASCII state machine diagrams?▼

Diagrams are capped at 78 columns for terminal use and 100 columns for GitHub, and machines with more than 15 states should be split or collapsed into super-states. The Skill does not emit HTML or SVG and refuses to fabricate states or triggers the user has not specified.