ui-architecture-preflight

Identify UI architecture boundary violations and backend contract gaps before feature planning.

20|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Accelerated-Innovation/governed-ai-delivery --skill ui-architecture-preflight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-architecture-preflight
Source: https://github.com/Accelerated-Innovation/governed-ai-delivery/tree/main/agents/codex/skills/ui/architecture-preflight
Command: npx skills add https://github.com/Accelerated-Innovation/governed-ai-delivery --skill ui-architecture-preflight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate UI architecture boundaries, backend contracts, and ADR needs before committing to feature planning.

Core Features & Use Cases

  • Produce a comprehensive architecture_preflight.md that documents MVVM layer impact, backend contracts, repository scope, and accessibility considerations.
  • Validate repository scope completeness and identify external dependencies or required contracts before UI implementation.
  • Align state management decisions and ADR requirements to ensure a smooth handoff between design, frontend, and backend teams.

Quick Start

Provide an architecture preflight plan for a UI feature by referencing docs/ui/architecture guidelines and ADR needs.

Frequently Asked Questions about ui-architecture-preflight

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

FAQPage Schema
How do I validate MVVM layer boundaries before starting UI feature planning?

You can identify UI architecture boundary violations by generating an architecture_preflight.md that documents MVVM impacts, repository scope, backend contracts, and accessibility considerations before committing to feature planning.

What is UI architecture preflight and when do I need it?

UI architecture preflight is a validation step that identifies boundary violations and backend contract gaps before feature planning. You need it when aligning state management decisions across design, frontend, and backend teams.

How do I document backend contract gaps and repository scope for a new UI feature?

Document backend contract gaps and repository scope by producing an architecture_preflight.md that validates repository scope completeness and identifies external dependencies or required contracts before UI implementation.

Does UI architecture preflight support ADR planning and state management alignment?

Yes, UI architecture preflight aligns state management decisions and ADR requirements by producing a formal architecture_preflight.md that includes ADR considerations and evaluation readiness to ensure a smooth handoff.

Can I use architecture preflight to check accessibility considerations before UI implementation?

Yes, architecture preflight ensures accessibility considerations are documented in the architecture_preflight.md alongside MVVM impacts and shared components, validating evaluation readiness before UI implementation begins.

What is the best way to align frontend and backend teams on backend contracts before spec planning?

The best way to align teams is to run an architecture preflight that validates backend contracts, repository scope, and ADR needs, producing a formal architecture_preflight.md for a smooth cross-team handoff.