greyboxing

Build responsive greybox layouts from DESIGN.md and PAGES.md inputs.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/Firzus/agent-skills --skill greyboxing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: greyboxing
Source: https://github.com/Firzus/agent-skills/tree/main/skills/web/greyboxing
Command: npx skills add https://github.com/Firzus/agent-skills --skill greyboxing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you build the structural, visual, and motion shell of a website before final content exists, so the product can be reviewed, iterated, and validated earlier.

Core Features & Use Cases

  • Page-by-page greyboxing: Builds responsive layouts for each page from an existing DESIGN.md and page plan.
  • Shared chrome and consistency: Ensures header, footer, and navigation stay centralized and consistent across the site.
  • State and motion planning: Defines signature elements, motion theses, and reachable loading, empty, and error states for review.
  • Use Case: A frontend team can use this Skill to turn a design system into a complete set of placeholder pages that are ready for stakeholder review and implementation.

Quick Start

Use the greyboxing skill to build the page structure and motion for the next page in PAGES.md from DESIGN.md.

Frequently Asked Questions about greyboxing

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

FAQPage Schema
How do I build responsive page layouts before final content is ready?

Responsive page layouts can be built using greyboxing to create structural and visual placeholder shells from your design system. This allows your team to review and validate the product earlier by separating layout planning from content creation.

What is greyboxing in UI prototyping and frontend workflows?

Greyboxing in UI prototyping is the process of constructing placeholder page shells from an existing design system. It establishes shared chrome, responsive structures, and motion planning before real content is added to the site.

Do I need a design system document to start greyboxing site pages?

Yes, greyboxing requires DESIGN.md and PAGES.md inputs to generate responsive layouts. These documents provide the existing design system and page plan needed to build consistent header, footer, and navigation structures across the site.

How do I plan motion design and loading states for a responsive layout?

Motion design and state coverage are planned during the greyboxing phase by defining signature elements and motion theses. The process outlines reachable loading, empty, and error states for stakeholder review before final implementation.

Can I validate placeholder layouts and shared chrome with browser support?

Yes, placeholder layouts and shared chrome can be validated using optional prototype and browser support. This validation ensures centralized consistency and state coverage across all generated pages before real content is added.

What's the best way to turn a design system into working page shells for review?

The best way to turn a design system into working page shells is applying page-level review discipline through greyboxing. It transforms your design system inputs into a complete set of responsive placeholder pages ready for stakeholder iteration.