BlueFenixProductions

Check a UI design against the Design-for-Developers DO/DON'T rulebook — use when asked to review, critique, lint, or sanity-check a design, component, CSS/tokens, or screenshot for concrete rule violations (contrast below 4.5:1, line-height too loose, button text under 14px, arbitrary spacing off the baseline, ALL-CAPS body, underlined links, same font for headers and body, oversized/wrapping headers, misused badges/toasts, weak hierarchy). Complements impeccable and design:design-critique by contributing this specific numeric rubric, not replacing their judgment.

Concrete design numbers and formulas for building UI — use when you need exact values for type scale / font sizes, line-height, letter-spacing, spacing and grid systems, color weight ladders (50–950), color harmony (triadic/analogous/complementary), OKLCH palette generation, contrast/WCAG ratios, shadow depth values, button/badge/card/input padding and sizing, or visual-hierarchy levers. Pulls precise tokens so designs use intentional, consistent values instead of guessed ones. Pairs with impeccable and frontend-design when implementing interfaces.

Use for the poop deck and the live agent war room. Two modes. LOG a decision — `/muster <topic>`, "muster this", "log a muster", "record this to the deck" — synthesizes the session's discussion into a dated entry on the poop deck (git → topo) and publishes it. JOIN the live war room — `/muster ahoy [topic]`, "come aboard", "join the muster" — opens this session's seat in the self-hosted Campfire war room (BFP fork on madara): post a hail, bridge the live conversation, LOG the verdict. Reach for this whenever a cross-session decision lands OR agents need to confer live, even if the Operator doesn't say "poop deck" explicitly.

Use when the Operator wants to capture the current session as a dated engineering/work journal entry written in their own voice — triggers include "/journal-this", "journal this", "summarize this session", "write a journal entry", "wrap this up as a journal entry", or winding-down cues like "good stopping point" / "let's call it here" at the end of substantive work. Also use on first run to configure the journal (name, voice source, destination). Saves the entry to a configured folder or GitHub repo.