aurora-layout

Standardize Aurora UI form layouts with a 12-column grid and semantic sections.

1|Updated Jun 20, 2022
One-click install
npx skills add https://github.com/avvale/aurora-front --skill aurora-layout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aurora-layout
Source: https://github.com/avvale/aurora-front/tree/main/.claude/skills/aurora-layout
Command: npx skills add https://github.com/avvale/aurora-front --skill aurora-layout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and enforces consistent UI form layouts across Aurora apps, addressing the fragmentation of form patterns and visual inconsistencies that slow down development and degrade user experience.

Core Features & Use Cases

  • 12-column grid with col-X classes to control field widths and alignment across detail forms, editors, and dashboards.
  • Semantic grouping of fields into logical sections (Identification, Data, Contact, etc.) with optional toolbars to improve scanning and usability.
  • Responsive layout guidance that adapts to mobile and desktop, enabling predictable behavior across devices and screen sizes.

Quick Start

Apply the grid-based layout and sectioning rules to a target form by:

  • Defining 12-column grid usage with col-*, aligning fields by data type.
  • Grouping related fields into semantic sections and inserting a toolbar separator when 6+ fields exist.
  • Applying responsive classes to ensure full-width on mobile and compact columns on larger screens.

Frequently Asked Questions about aurora-layout

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

FAQPage Schema
How do I standardize responsive form layouts across different screen sizes?

Standardize responsive form layouts by applying a 12-column grid with col-* classes to control field widths and alignment, ensuring forms adapt predictably across mobile and desktop devices without external tooling.

What is the best way to group form fields semantically in a detail editor?

Group form fields semantically by organizing them into logical sections like Identification, Data, or Contact, inserting a mat-toolbar separator when a section contains six or more fields to improve scanning.

How do I use a 12-column layout grid to align form fields by data type?

Use a 12-column layout grid by assigning col-X classes to fields based on their data type, controlling widths and alignment to enforce consistent visual structure across detail forms and dashboards.

Do I need external dependencies to enforce consistent UI form patterns?

You do not need external dependencies to enforce UI form patterns. The layout framework applies responsive grid behavior and sectioning rules natively, standardizing form structure without requiring external tooling.

Can I use mat-toolbar section dividers for multi-section form screens?

You can use optional mat-toolbar section dividers to separate semantic field groupings in multi-section screens, improving usability and visual scanning when dealing with complex detail forms or editors.

When should I not use a 12-column grid for frontend forms?

A 12-column grid may not suit frontend forms requiring highly custom, free-form layouts outside standard detail forms or dashboards, as it enforces strict column alignment and semantic sectioning rules.