broomva-designlisted

Materialize and apply Broomva's platform-neutral calm blue-axis design system across digital products. Includes a portable DESIGN.md contract, semantic styling foundations, general React/web primitives, product-pattern and platform-adaptation guidance, and an optional agentic-work extension. Use for Broomva-branded web, native mobile, desktop, commerce, content, analytics, SaaS, internal tools, communication products, design reviews, or when a request mentions Broomva design, the blackhole mark, blue-axis styling, Undertow, receipts, DESIGN.md, or the Broomva component library.
broomva/skills · ★ 3 · Web & Frontend · score 69

Install: claude install-skill broomva/skills

# Broomva Design Apply one Broomva identity to the product's actual domain. The foundation is calm, matte, blue-axis, and product-neutral. Web components and agentic work patterns are adapters layered above it, never requirements of the brand. ## Start here 1. Read this skill's `DESIGN.md` before changing UI. 2. Inspect the target's platform, existing styles, primitives, accessibility baseline, and incumbent `DESIGN.md`. 3. Read `references/product-patterns.md` and `references/platform-adaptation.md` for the relevant product and platform. 4. Ask the materializer to recommend the smallest profile, then confirm it against the target's real domain. Do not overwrite an incumbent system without an explicit migration request. 5. Implement through semantic roles and reusable components, then validate behavior, accessibility, themes, and representative viewports or device classes. Set `SKILL_DIR` to the directory containing this file, then materialize the neutral foundation: ```bash python3 "$SKILL_DIR/scripts/materialize.py" materialize . --profile foundation python3 "$SKILL_DIR/scripts/materialize.py" verify . --profile foundation ``` For an unfamiliar target, get a recommendation before materializing: ```bash python3 "$SKILL_DIR/scripts/materialize.py" recommend . ``` Use `--agentic-work` only for products that actually model autonomous work, or `--maintainer` when evolving the design system itself. Explicit intent wins over an installed profile and framework detection. `-