메뉴
Generate on-brand Alex — ACT Edition SVG banners for documents (READMEs, plans, notes, release artifacts)
Use when the user wants to humanize, de-AI, de-slop, or un-ChatGPT a piece of text — strip AI-isms and add real voice. Scans for 29 documented AI-writing patterns (Wikipedia's "Signs of AI writing") and produces a draft → self-audit → final rewrite. Optional voice-calibration from a user-provided writing sample. Adapted from Hermes Agent / blader/humanizer.
Use when the user wants a plan instead of execution, or before any non-trivial implementation (multi-file, architectural choice, > 15 min). Writes a concrete actionable markdown plan with bite-sized tasks (2-5 min each), exact file paths, complete code, and verification steps. Adapted from Hermes Agent / obra/superpowers.
Use when the user wants to feel out an idea before committing to a real build — "spike this out", "try it", "is this even possible?", "compare A vs B". Throwaway experiments that decompose into 2-5 feasibility questions, build minimal observable prototypes, and return VALIDATED / PARTIAL / INVALIDATED verdicts. Disposable by design. Adapted from Hermes Agent / GSD.
Use for any feature, bug fix, refactor, or behavior change — enforces RED-GREEN-REFACTOR. Write the failing test first, watch it fail, write minimal code to pass, refactor. Carve out only throwaway prototypes, generated code, configuration files. Adapted from Hermes Agent / obra/superpowers.
Create agents that pass agent-review's six gates by construction — role capture, distinct-from-skill check, tool allowlist minimization, draft against gates, dogfood self-review. Use when authoring a new agent, refactoring an existing one, or promoting a Mall agent into the heir's brain.
Audits a candidate agent (.agent.md) against five gates (spec compliance, content quality, scope fit, safety, currency & coherence) plus Gate 6 (tool allowlist minimality). Use when reviewing a new agent draft before commit, evaluating a Mall agent or store agent for adoption, or re-auditing existing agents on a periodic cadence.
| name | alex-banner-generation |
| description | Generate on-brand Alex — ACT Edition SVG banners for documents (READMEs, plans, notes, release artifacts) |
| lastReviewed | "2026-05-26T00: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/skills/alex-banner-generation/scripts/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.
Revisit this skill by 2026-08-26 (90 days) or sooner if any of the following fires: