beautify-github-readmelisted

Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets. Use when a user asks to beautify, redesign, rebrand, visually upgrade, simplify, or audit a GitHub README; create only a hero, section headers, diagrams, badges, motion graphics, showcase modules, or other README assets; or turn a repository homepage into a cohesive visual story. If whole-README work versus asset-only work is unclear, ask which scope the user wants. For hero-like assets where pure SVG and generated raster material are both viable, explain the tradeoffs and confirm the implementation before creating the asset.
risukisu/marketing-skills · ★ 3 · AI & Automation · score 76

Install: claude install-skill risukisu/marketing-skills

# Beautify GitHub README Turn a repository homepage or requested visual asset into a concise, theme-specific visual story. Treat Markdown as the content layer, deterministic SVG as the layout system, and generated raster material as an optional visual ingredient. ## Workflow ### 1. Confirm the mode before editing Use exactly one execution mode: - **README mode** — improve the whole README: information order, copy hierarchy, proof, Markdown, and visual system. - **Asset-only mode** — create only the requested static SVG or visual asset set. Static SVG is the default. Only after the user explicitly opts into meaningful motion, optionally deliver a GitHub-safe GIF while keeping the SVG as the editable fallback. Do not rewrite, reorder, or embed anything in the README unless the user explicitly adds that scope. If the mode is not explicit, ask one compact question before making changes: > Would you like me to improve the whole README or only create visual assets? If asset-only, tell me whether you need a hero, section headers, workflow, badge, motion graphic, or a coordinated set. When a hero, badge, workflow, or diagram has meaningful motion and the user has not specified static or animated output, ask one compact follow-up: > Should this stay as a static SVG, or would you like a GitHub-safe GIF animation with the SVG kept as the editable fallback? GIF is opt-in and never the default. If the user declines, does not answer, or has no meaningful moti