brawler-design
Use before ANY Brawler UI work — writing/changing JSX, drawing a mockup, styleguide or visual-language work, choosing colors/typography/labels, designing a panel or empty state. Binds the generic design skills to Brawler's normative design language (ADR 0104) and authoring contract.
- License 许可
- MPL-2.0
- 最近更新
- 2026-11-01
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- brawler-design
- description
- Use before ANY Brawler UI work — writing/changing JSX, drawing a mockup, styleguide or visual-language work, choosing colors/typography/labels, designing a panel or empty state. Binds the generic design skills to Brawler's normative design language (ADR 0104) and authoring contract.
03 SKILL.md 正文
Brawler design ritual
Thin by design: rules live in the canonical docs; this skill is the load order, the precedence, and the pre-write ritual. Never restate rule content here — link it (single source of truth).
Load order (before the first line of JSX or mockup HTML)
- ADR 0104 — the design language (accent discipline + form rule, typography, verb dictionary, patterns, provenance thread).
- docs/ui-authoring.md — the authoring contract (primitive-first, mockup-first, density contracts, i18n, its v2 checklist section).
- Visual reference:
docs/mockups/frontend-v2-styleguide/(approved canvas; gitignored). - For charts/tiles: the
datavizskill. For aesthetic judgment: thefrontend-designskill. For owner mockup rounds: thedesignskill (canvas) — the approved result is saved back todocs/mockups/(owner rule 2026-08-18).
Precedence (on any conflict)
Repo beats generic skill: src/ui primitives and ADR 0076 tokens/scales beat whatever a generic
design skill would invent; ADR 0104's dictionary beats any label instinct; product language
(no dev vocabulary) beats cleverness. A generic skill's advice is welcome exactly where the repo
is silent.
Pre-write ritual (every time)
- Verb check: does every action label start with a dictionary verb (ADR 0104 dec. 3) and predict its effect? Run the swap test.
- Color check: is every non-neutral color a MEANING (interaction-filled / provenance-quiet / status)? Count filled elements at rest: max one.
- Copy check: user vocabulary only; empty states carry three beats (what → where from → action).
- Structure check: ui-authoring pre-write self-check (primitives, scaffold-from-sibling, no inline
styles,
text()both languages, density contract for the pane). - Figures in mono; human title before filename; provenance thread only under theses.
Mockup workflow (new panel/screen or redesign)
Mockup BEFORE code (binding): draw on the design canvas → owner round(s) → approved artboards
copied to docs/mockups/<feature>/ → then experience contract/storyboard if the work touches a
journey (ADR 0081 posture per plan) → only then components.
04 同仓库更多 Skills
ship-pr
Use when a change is implemented and needs to land as a PR — branching, evidence, commits, PR creation, CI watching, or when CI jobs fail and you must decide rerun-vs-fix. Also use when a "green" claim is about to be made.
repoctx
Use repoctx for fast, indexed code navigation in this repo. Beats grep/find/cat on structural questions about symbols, definitions, the call graph (who-calls / callees / callgraph), and surrounding source.
packaging
Build and smoke-test Brawler release artifacts — portable Windows .exe from Linux/WSL via cargo-xwin, Linux .deb/.rpm/AppImage, native Windows fallback. Use for packaging, cross-build verification, or Windows hands-on testing paths.
investing-domain
Domain lens for designing/building Brawler — how an equity investor actually reads companies (fundamental analysis, quality assessment, GPW specifics). Load when designing UI hierarchies, panels, journeys, or analytics for company data.
guardrail-harvest
Convert a flagged defect's class into a durable guardrail — a precise automated gate or a documented rule + checklist line — in the same change. Use whenever the user, a review, or a failing gate flags a defect.
brawler-mcp
Use when you (an AI agent) are connected to Brawler over its MCP server and need to read the user's investment research or write back into it — including acquiring KPIs from an issuer report ("process all pending KPI ingests", staging observations, resuming a pending run, a lease that expired, a validation that failed). Covers tool discovery, the read/act tiers, mandatory-source (provenance) rules, the KPI-ingest run workflow, internal-id conventions, the permanent denylist, and safe read→analyze→write sequences. Load it before your first tools/call against Brawler.