frontend-design

Structure site frontend design into phased workflows with DESIGN.md and PAGES.md artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design or redesign an entire site frontend without losing structure or consistency. It breaks the work into clear phases so the design can move from identity to page planning to final content with less rework.

Core Features & Use Cases

  • Design System Phase: Establish the visual identity, tokens, surfaces, and core design decisions in a dedicated artifact.
  • Greyboxing Phase: Map out the site’s pages, tiers, statuses, signature elements, and motion direction before detailed implementation.
  • Real Content Phase: Replace placeholders with final page content and complete the self-audit for each surface.
  • Use Case: A team redesigning a marketing site can use this Skill to define the system first, plan all pages next, and then finish each page with real copy in separate sessions.

Quick Start

Use the frontend-design skill to guide the current project phase and tell me which artifact to read or update next.

Frequently Asked Questions about frontend-design

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

FAQPage Schema
How do I structure a multi-page website redesign without losing consistency?

To structure a website redesign without losing consistency, break the frontend design into phased workflows for design system creation, greyboxing, and real-content implementation to enforce phase gates and reduce rework.

What is greyboxing in UX workflow and when should I use it?

Greyboxing in a UX workflow is the process of mapping out a site's pages, tiers, statuses, signature elements, and motion direction before detailed implementation. You use it to plan site architecture prior to applying final content.

How do I manage context across separate frontend design sessions?

To manage context across separate frontend design sessions, use artifact-driven handoff through DESIGN.md and PAGES.md files. These artifacts preserve context and enforce phase gates between the design system, greyboxing, and real content phases.

Can I use this phased approach for a new site build instead of a redesign?

Yes, you can use this phased approach for a new site build instead of a redesign. The workflow applies to both new site builds and multi-page website redesigns, moving from visual identity to page planning and final content delivery.

What is the best way to transition from design system creation to real content implementation?

The best way to transition from design system creation to real content implementation is to pass through a greyboxing phase. Map out all pages, tiers, and signature elements first, then replace placeholders with final copy and complete a self-audit.

Do I need specific design tools to implement a phased frontend delivery?

No specific design tools are required to implement a phased frontend delivery, but you must use artifact-driven handoff through DESIGN.md and PAGES.md files to preserve context and enforce phase gates throughout the workflow.