>- Applies Michael F. Bryan's visual design system — warm high-contrast palette, typography scale, spacing tokens, light/dark themes, and artefact theming — across websites, email signatures, Word/Google Doc templates, slides, rich HTML artefacts, and any branded surface. Use whenever the user mentions Michael F. Bryan brand colours, personal site theming, email signatures, document templates, rich artefact styling, or "make it look like Michael" — even without naming this skill.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
LicenseLICENSE
Default branchmain
Open issues0
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md4,443 B
docsREADME.md1,804 B
docsSUMMARY.md513 B
History
First seen on skills.sh
First recorded snapshot · 8 installs
SKILL.md
Michael Brand Pack
Michael F. Bryan visual design system. This skill owns look and visual judgement. It does not replace writing voice or rich-communication workflow. Do not use “Operator Notes” as the conceptual frame for all artefacts; treat it, if used at all, as one possible surface label rather than the governing abstraction.
Quick start
Read references/tokens.md for values.
Pick one channel below → read the matching reference.
Start from a template when useful: templates/rich-html-document.html, templates/dark-tool.html, templates/email-signature.html, or templates/style-calibration.md.
For web/rich HTML, apply assets/css/tokens.css plus assets/css/web-base.css.
Check that styling makes the work legible and the next move obvious.
Channel router
User task
Read
Assets
Personal site, app chrome, landing pages
references/websites.md
tokens.css, web-base.css
Email signature, HTML email
references/email.md
Token values inline
Word / Google Docs templates
references/documents.md
Token values as pt/hex mapping
Rich HTML artefact: decision brief, explainer, design review, report, deck
references/html.md
Pair with html-rich-communication; templates in templates/
Full visual language, mood, diagrams
references/visual-language.md
All CSS assets and templates/style-calibration.md
Core visual rules
Legibility is authority — important text must be readable at 100% zoom.
Structure before decoration — layout exposes the thinking.
Use warm light theme for documents, reports, explainers, and review artefacts; dark theme for tools, dashboards, demos, and long-running screen work.
Styling must not make the wrong artefact look finished. Fix the communication structure first.
Body text: 17–18px long-form; dense UI not below 15px.
Primary text targets AAA-like contrast; secondary text stays readable, not faint.
Borders visible when they carry structure — no rgba(0,0,0,0.05) dividers.
Colour signals meaning; every status also has a text label.
Direct annotation beats legends: labels, units, and caveats sit near the thing they explain.
Domain motifs are accents, not the governing system, unless the artefact is a demo/marketing surface.
If the user asks for a conflicting mood, run style-conflict calibration: preserve brand legibility, honour the requested feel where it serves the job, and show a quick proof before polish.
No SaaS gradient card grids, startup chrome, cyberpunk terminal cosplay, or decorative branding.
Accessible by default — focus states, semantic HTML, print-friendly where relevant.
Pairing
Rich artefact workflow and verification → html-rich-communication
