amvcp-layout

Route layout requests to specialized sibling Skills for grids, shells, KPI, chrome, and print scaffolds.

Updated May 8, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-visual-communicator-plugin --skill amvcp-layout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amvcp-layout
Source: https://github.com/Emasoft/ai-maestro-visual-communicator-plugin/tree/main/skills/amvcp-layout
Command: npx skills add https://github.com/Emasoft/ai-maestro-visual-communicator-plugin --skill amvcp-layout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

amvcp-layout removes the guesswork of which layout template to use by routing any layout need to the correct specialized layout sibling, so you get consistent grid, chrome, KPI, shell, and print/hero scaffolds.

Core Features & Use Cases

  • Layout routing matrix: Maps user intent (grid, sidebar, dashboard, TOC, sticky header, hero, device mockup, KPI, print/A4) to the appropriate sibling Skill.
  • Composable output plan: Guides you to load multiple siblings in the right order when a page needs combined concerns (e.g., chrome + grids + KPI + shells).
  • Covers layout primitives and policies: Ensures the required spatial token foundation is used, including reading measure, RTL handling, no-nested-scrollbars, and selection-atoms conventions.

Quick Start

Ask an AI: Route my request for "a content + sidebar article page with a sticky TOC and a sticky page header" to amvcp-layout so it loads the correct siblings and scaffolds the layout accordingly.

Frequently Asked Questions about amvcp-layout

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

FAQPage Schema
How do I choose the right responsive design layout for a dashboard with sidebars and KPI strips?

Sticky headers and TOC layouts are routed to specific sibling skills that handle chrome and sticky scaffolding, guiding you to compose multiple layout primitives in the correct order while enforcing no-nested-scrollbars and reading measure conventions.

Can I generate an A4 or PDF-ready print layout with decorative hero and device frames?

Yes, print layout routing directs A4 and PDF-ready requests to dedicated print and hero scaffolding siblings, allowing you to combine optional decorative hero elements and device mockup frames alongside standard web UI design concerns.

What is the best way to compose multiple layout primitives like grids, shells, and chrome for a single web UI page?

The best way to compose web UI design primitives is using a composable output plan that loads multiple layout siblings in the correct sequence, matching combined page concerns like chrome, grids, KPI strips, and shells against a predefined routing matrix.

Does this layout routing approach enforce CSS tokens and RTL handling for responsive web UI design?

Yes, layout routing enforces required CSS token foundations and spatial policies, ensuring proper RTL handling, reading measure constraints, and selection-atoms conventions are applied across all routed grid, sidebar, and dashboard layout siblings.

When should I avoid using a layout routing matrix for my sidebar and responsive collapse breakpoints?

Avoid layout routing if your project requires custom markup generation outside the spatial token foundation, as this routing mechanism emits no markup itself and strictly instructs how to compose predefined sibling scaffolds for grids and shells.