feat: add mindtwo-branding skill for on-brand artifact and document creation

[blumewas]

Summary

Distributes the mindtwo corporate identity skill to the team via agent-tooling. The skill auto-activates whenever Claude styles a client- or team-facing deliverable (Artifacts, HTML reports, one-pagers, slide decks, PDF templates, email templates) and applies the mindtwo CI:

• The three brand colours with the binding 60/30/10 rule (white/black/red) and the established Tailwind grey ramp
• Roobert typography rules, including the licensing caveat for publicly shared pages
• Document patterns from the canonical PDF template (eyebrow, headings, tables, callouts, page chrome)
• Form language (flat, geometric, restrained shadows) and explicit anti-patterns

What's included

• skills/mindtwo-branding/SKILL.md — the skill itself; the mindtwo repo remains the source of truth
• references/tokens.css — ready-to-paste :root token block with light and dark themes
• references/inline-assets.py — inlines the Roobert font and logo as data URIs for Artifact publishing (the Artifact CSP blocks external hosts)

Portability

The inlining script previously hardcoded one developer's checkout path. It now resolves the mindtwo repo via the MINDTWO_REPO env var or common project directories (~/Development/Projects, ~/code, ~/Projects), so it works on any teammate's machine. Brand assets (fonts, logos) are not committed here — they stay in the mindtwo repo, so the Roobert commercial licence is unaffected.

No install.sh changes needed; it picks up every directory under skills/ automatically.

Test plan

• python3 -m py_compile on the inlining script
• Env-var override and auto-detection of the brand repo both resolve correctly
• End-to-end run: substituted RoobertVF (89 KB) and the horizontal logo into a test page
• bash -n install.sh