From 7ccfa329af3b22015ca66a5b836e51d4bd7c3fcd Mon Sep 17 00:00:00 2001 From: Wayner Barrios Date: Tue, 28 Jul 2026 14:09:20 -0400 Subject: [PATCH] Separate frontend planning scopes --- skills/frontend-design/SKILL.md | 18 +++++++++++++++--- tests/frontend-design.test.mjs | 30 ++++++++++++++++++++++++++++++ 2 files changed, 45 insertions(+), 3 deletions(-) diff --git a/skills/frontend-design/SKILL.md b/skills/frontend-design/SKILL.md index f65a72e..d5c15e7 100644 --- a/skills/frontend-design/SKILL.md +++ b/skills/frontend-design/SKILL.md @@ -8,6 +8,18 @@ This skill guides creation of distinctive, production-grade frontend interfaces The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. +## Scope and requirements + +Before design thinking, classify the request and plan the appropriate ownership boundary. Ask only about missing information that materially changes structure, behavior, integration, or accessibility; when requirements are sufficient, proceed without a round trip. + +- **Page or application**: Plan the user journey, information architecture, content hierarchy, navigation and route context, page-level states, full-viewport responsive composition, and one coherent visual concept. +- **Isolated or reusable component**: Plan its responsibility, public inputs and content, events, variants, loading/empty/error/disabled/selected states where applicable, host context, intrinsic sizing, keyboard and focus semantics, tokens, and composition boundaries. +- **Hybrid work**: Plan both layers and keep page-owned requirements out of reusable component internals. + +A component must not invent an unrelated page shell, global landmarks, document-level `

`, global typography or background, or viewport metadata. A page must not collapse planning into individual components without first establishing page hierarchy, navigation, content flow, and responsive behavior. + +All three tracks converge into the design thinking, implementation, anti-generic guidance, self-critique, and optional validation below; do not duplicate those stages per track. + ## Design Thinking Before coding, understand the context and commit to a BOLD aesthetic direction: @@ -62,11 +74,11 @@ Models tend to confidently praise their own mediocre output, so do not ask yours Accessibility: - Body-text contrast is at least 4.5:1; large text (24px+, or 18.66px+ bold) and the borders of UI controls and meaningful icons are at least 3:1. Meaning is never carried by color alone. -- Semantics are native: `