Menu
Generate on-brand Alex — ACT Edition SVG banners for documents (READMEs, plans, notes, release artifacts)
End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.
Detect, create, and manage the AI-Memory fleet communication channel. Fires on bootstrap, session start (announcements), and feedback writes.
Patterns for fiction, narrative structure, character development, dialogue, and storytelling craft.
Convert Word documents (.docx) to clean Markdown with image extraction and pandoc cleanup
Greeting-triggered self-check — recognise greetings, check Edition version against the upstream tag, scan AI-Memory announcements, and report inside the greeting reply
Write markdown that passes markdownlint on first attempt — encode the most common rules as muscle memory
| type | skill |
| lifecycle | stable |
| name | alex-banner-generation |
| description | Generate on-brand Alex — ACT Edition SVG banners for documents (READMEs, plans, notes, release artifacts) |
| tier | standard |
| inheritance | inheritable |
| applyTo | **/*banner*,**/assets/**,**/README*,**/PLAN*,**/CHANGELOG* |
| muscle | .github/muscles/generate-banner.cjs |
| currency | "2026-04-30T00:00:00.000Z" |
| lastReviewed | "2026-04-30T00:00:00.000Z" |
Generate visually consistent SVG banners for any document in this heir using the Alex — ACT Edition brand template.
Looking for a lighter, hand-authored variant? The Mall ships
document-banner-pastel-- pastel 1200x240 banners with content-specific iconography (tracks / hub-and-spokes / mockup / badge / symbol). Use that pattern for branding, education, or audience-facing docs; use this muscle for technical artifacts that need brand-stamped consistency.
| Element | Value |
|---|---|
| Dimensions | 1200 × 300 px |
| Background | #0f172a (Slate 900) |
| Accent bar | 4px wide, #6366f1 (Indigo 500) |
| Series label | ALEX · ACT EDITION |
| Title | 56px / weight 700 / #f1f5f9 |
| Subtitle | 18px / weight 600 / #94a3b8 |
| Watermark | ~100px / weight 800 / #f1f5f9 / 10% opacity |
Pick the one that matches the document's role:
| Watermark | Use For |
|---|---|
ACT | Critical-thinking content, ACT framework artifacts, manifestos |
EDITION | Top-level repo identity (root README, ABOUT) |
DOCS | User guides, tutorials, reference material |
RELEASE | CHANGELOGs, release notes, version stamps |
PLAN | Planning docs, roadmaps, milestone trackers |
NOTE | Session notes, ad-hoc memos |
If no category fits, ask the user before inventing one — the muscle rejects unknown watermarks.
Ask the user only for what's missing. Defaults:
assets/banner-<title-slug>.svg. Override with --out if the user wants a specific path.node .github/muscles/generate-banner.cjs \
--title "Document Title" \
--subtitle "One-line purpose statement." \
--watermark PLAN
Add --force to overwrite an existing file. Add --out path/to/banner.svg for a non-default location.
The muscle exits 0 on success, 1 on validation errors (length, watermark whitelist), 2 on filesystem errors (file exists without --force).
Add this line just under the document's H1:
The muscle prints the exact embed line; copy it verbatim.
The muscle takes whatever subtitle you pass — quality is your job. Good subtitles:
"Critical thinking made operational." not "This document explains ACT.")If you're not sure the subtitle is right, show two options to the user before generating.
Before declaring done:
assets/GitHub renders SVG banners natively in README.md and most surfaces, so SVG is preferred. If a downstream tool needs PNG:
# Via mermaid-cli's bundled chrome (already a dependency):
npx svgexport assets/banner-foo.svg assets/banner-foo.png 1200:300
Don't ship PNGs unless required — they double the asset weight and can drift from the SVG source.