Skip to content

aosoficial/agent-infographic-skill

editorial-infographics

Verified

Create original, evidence-led editorial infographics and social graphics that avoid generic AI aesthetics. Use for infographics, news cards, data stories, Pinterest pins, social carousels, visual explainers, diagrams, or when a graphic must explain, prove, compare, map, or humanize an idea.

references/design-language.md

View on GitHub
# Editorial design language

## Goal

Make the piece feel composed around a specific idea. The viewer should notice the relationship being explained before noticing the visual effect.

## Core grammar

### Canvas

- Prefer quiet paper-like or cool neutral backgrounds.
- Use negative space as part of the hierarchy, not as empty leftover area.
- Keep one visual center of gravity; asymmetry is welcome when balanced.

### Typography

- Use one sans-serif family with no more than two weights, plus an optional mono label style.
- Let scale create hierarchy; avoid five competing text styles.
- Titles should state the insight, not name the topic.
- Body copy is supporting evidence, not a miniature article.

### Geometry

- One dominant spatial metaphor per image.
- Hairline connectors, direct labels, and small indices are preferred to floating cards.
- Shapes should encode containment, convergence, hierarchy, sequence, magnitude, or overlap.
- Soft blur or gradient may indicate depth, influence, or a boundary. It must not exist only to look futuristic.

### Color

- Start with ink + paper + one accent.
- Add a second accent only when it encodes a distinct category.
- Keep saturation localized to the insight.
- Do not use the default purple-blue AI gradient.

### Texture and humanity

- Use real screenshots, photographed objects, a small human silhouette, handwriting, or source artifacts when they add scale or credibility.
- Avoid decorative robots, glowing brains, circuit heads, holograms, and stock “AI” symbolism.

## Anti-patterns

- headline plus three rounded cards;
- dark dashboard background for every topic;
- glassmorphism without an interface reason;
- icon per bullet as decoration;
- fake product UI;
- data with no source or denominator;
- the same grid repeated with different copy;
- every element centered;
- excessive glow, pill badges, all caps, and tiny footer text;
- a visual that becomes meaningless when the headline is removed.

## Reference use

When the user supplies design references:

1. Identify hierarchy, rhythm, topology, density, contrast, and material treatment.
2. Write those traits as a design brief.
3. Do not copy exact copy, distinctive artwork, or the original composition point-for-point.
4. Create a new layout that serves the user's content and brand.

slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall