layout-framework

Enforce standardized grid and spacing layouts for PierceDesk frontend pages.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RockwallJMC/Threadbilt-v0 --skill layout-framework
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: layout-framework
Source: https://github.com/RockwallJMC/Threadbilt-v0/tree/main/.claude/skills/layout-framework
Command: npx skills add https://github.com/RockwallJMC/Threadbilt-v0 --skill layout-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standardizes frontend layout decisions to ensure consistent alignment, spacing, and component usage across PierceDesk screens, reducing layout drift and design-system gaps.

Core Features & Use Cases

  • Box/Container/Grid/Stack/Paper usage guidelines for responsive layouts.
  • Two-column forms, 8/4 splits, and address blocks as common patterns.
  • Spacing rules based on theme values to avoid hardcoded sizes.
  • Triggers for layout QA to fix misalignments and maintain consistency across pages.

Quick Start

Implement a two-column form using Grid with responsive size values and wrap sections in Paper surfaces per the layout rules.

Frequently Asked Questions about layout-framework

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

FAQPage Schema
How do I standardize responsive frontend layouts to prevent alignment drift?

To standardize responsive frontend layouts, enforce a grid and spacing framework using Grid with size props, Stack for rhythm, and Paper surfaces. This ensures consistent alignment across dashboard pages and form-heavy interfaces.

What is the best way to structure a two-column responsive form?

The best way to structure a two-column responsive form is using Grid with responsive size values, wrapping sections in Paper surfaces, and applying spacing rules based on theme values to avoid hardcoded sizes.

Why does my dashboard layout have misaligned components and inconsistent spacing?

Dashboard layouts have misaligned components and inconsistent spacing due to layout drift and design-system gaps. Running layout QA triggers and enforcing Container for page width fixes these misalignments across breakpoints.

Can I use hardcoded pixel values for spacing in a design system?

You should not use hardcoded pixel values for spacing in a design system. Spacing rules must be based on theme values to maintain consistent rhythm across breakpoints and prevent layout drift on responsive pages.

When do I need to use Grid versus Stack for frontend page organization?

You need to use Grid for two-column forms and 8/4 splits requiring dimensional control, while Stack manages vertical or horizontal rhythm. Grid uses size props for breakpoints, and Stack maintains consistent spacing flow.

Does this layout framework work for address blocks in dashboard pages?

Yes, the layout framework works for address blocks in dashboard pages by applying standardized Grid size props and Paper surfaces. It enforces consistent alignment and component usage across PierceDesk screens for these common patterns.