frontend-design

Guides design decisions for Astro pages, CSS, and ECharts components in the factory dashboard.

11|9|Updated May 25, 2026
One-click install
npx skills add https://github.com/projectbluefin/lab --skill frontend-design-projectbluefin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-design
Source: https://github.com/projectbluefin/lab/tree/main/docs/skills/frontend-design
Command: npx skills add https://github.com/projectbluefin/lab --skill frontend-design-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing pages for the Project Bluefin factory dashboard often drifts into generic admin-panel patterns that fail to communicate OS QA evidence. This Skill enforces deliberate, subject-grounded design choices when modifying Astro pages, styles, charts, or visual components under src/. ## Core Features & Use Cases - Design Brief Discipline: Requires stating each page's subject, audience, and single job before making visual changes, keeping every page an evidence surface. - Semantic Design Rules: Enforces rules for colour as status, typography, structural markers, and purposeful motion grounded in the Bluefin/bootc domain. - Build-Time Verification: Mandates ESM imports for ECharts, local assets instead of CDN scripts, and validation via npm run build and page smoke tests. - Use Case: When adding a new test-results page, use this Skill to choose a status-driven hero, assign semantic colours, bundle ECharts locally, and verify the built HTML renders the intended structure. ## Quick Start Use the frontend-design skill to redesign the Tests page hero so it answers the page's primary question with a live chart instead of a generic KPI number.

Frequently Asked Questions about frontend-design

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

FAQPage Schema
How do I design a new page for an Astro dashboard site?▼

Start by stating the page's subject, audience, and single job before touching layout. Ground typography, colour, and structure in the site's domain, then verify with npm run build and page smoke tests against the built HTML.

How do I add ECharts to an Astro page without a CDN?▼

Import ECharts as an ESM module with `import * as echarts from 'echarts'` and load page scripts from src/scripts/. This keeps the site buildable offline and prevents Cloudflare Rocket Loader from rewriting boot paths.

When should I not use this frontend design guidance?▼

Skip it for backend collector changes in .github/workflows/ or scripts/, Argo WorkflowTemplate or Kubernetes manifest edits, and pure content fixes like typos that do not alter visual design.

Why should dashboard colours have semantic roles?▼

Colour should encode status, not decorate. The palette assigns green to healthy, amber to warning, rose to failure, and purple to cluster fabric, so any new hue must document a semantic role to stay meaningful.

What are common dashboard design mistakes to avoid?▼

Avoid numbered markers on non-sequential content, scattered decorative animations, CDN-loaded scripts, hiding missing data instead of showing an unavailable state, and hero KPIs that do not answer the page's primary question.