| name | flowguard-ui-flow-structure |
| description | Use for UI content admission, observed surface, behavior, structure/text, operability, evidence, or transitions. |
FlowGuard UI Flow Structure
Purpose
Admit content, model UI event x UI state behavior, and prove runnable visible surface evidence.
Entrypoint Scope
This standalone FlowGuard satellite skill owns ui_flow_structure (public_owner) admission/UI evidence, not styling or code structure.
Local Material Routing
Read references/ui_flow_structure_protocol.md for observed surface, interaction, journey, structure, text hierarchy, human, implementation, and geometry.
Entrypoint Acceptance Map
Accept admission, UI state/task/control coverage, and current evidence; block leaks, blindspots, or stale proof.
Use When
- Use for UI content/details, controls, surfaces, tasks/actions, runnable/layout evidence, typography hierarchy, or product-wide interaction language.
Do Not Use When
- Do not style first, invent roles, or treat observation as permission; return non-UI work to
model-first-function-flow.
Required Workflow
- Declare
greenfield, source_based, or mixed; observation never grants display permission.
- Classify only
user_visible, user_on_demand, or internal; require task/state/recovery/safety need. Exempt only an exact normal task-control label with no extra state/metadata. Build behavior, journeys, structure, text hierarchy, tasks, and operability.
- For complete-product claims compare canonical typography/component/navigation/interaction/feedback/recovery/transitions across surfaces. Business rows reuse existing intent/commitment/path ids; keep ids internal.
- Bind claims to plan, inventory, content rows, screenshot/DOM/event/result evidence, click chains, blindspots, and tests.
Hard Gates
- Model-purpose gate: before build/change, freeze this instance's task-specific failure(s) and boundary; then bind candidate plus native good/bad-per-failure/oracle/current evidence. Reusable types are not fixed-purpose; no mode/fallback; SkillGuard only supervises FlowGuard-declared checks.
- Use the real FlowGuard check engine and AGENTS.md managed record; never create a fake mini-framework.
- Unclassified/internal content cannot render; do not add audience/role/persona categories.
- On-demand stays hidden until an accessible task-owned reveal/return; hover has keyboard/focus parity.
- Every reachable enabled action needs control -> event -> owner -> function -> UI update -> evidence, pure-UI disposition, or blindspot.
- Repeated surfaces for one exact intent reuse one commitment, selected path, and canonical semantic grammar. Exceptions may change presentation for a typed platform/accessibility/native/safety reason, but never intent, path, visibility class, or external result.
- Design evidence cannot prove runnable UI; source, recovery, freshness, and harvest gaps stay explicit.
Output Requirements
Return evidence, failures, blockers, skipped_checks, residual_risk, claim_boundary, typed_next_actions, blindspots, and a UI state diagram; edges mean reachable interaction transitions.
SkillGuard Maintenance
Edit contract source, regenerate; SkillGuard is not UI runtime/human evidence.
