agentleFS
bookchaowalitbookchaowalit/platform-agent-skills/graphic-design/SKILL.md

graphic-design

Skill0 starsChanged 8 days agoApache-2.0View on GitHub

Design principles and a working method for Solo Empire graphics (social posts, posters, campaigns, cover-style art) - message, hierarchy, typography (Thai and Latin), color, composition, photos, art styles, variety across a series, and critique. Use when briefing, designing, composing, reviewing, or explaining a graphic or an art style; when an AI or human needs to judge whether a layout is good and why; or when changing the graphics engine's composer, art styles, prompts, or design score.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use typography and ui-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • soilmassSkill

    typography

    Typography and kinetic text animations including character reveals, typewriter effects, scramble/decode, wave motion, and animated gradients. Use when creating text reveals, headline animations, number counters, or any text-based motion effects.

    Also in 3 projects that use this

  • SentrySkill

    ui-design

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Critique: Run the checklist in references/critique.md: the engine's automatic checks first (fit, overlap, contrast, design score), then the …

    line 29
  2. Distinctive:

    Deliver: Every size, editable SVG, font list, and the request JSON for later edits.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Graphic Design

A graphic is good when the right person gets the message in about three seconds, wants to act, and remembers the brand. Taste follows from that job; it is not decoration. This skill holds the principles; the graphics engine (book-production graphics ... in book-production-platform, guide docs/GRAPHICS-THEMES-GUIDE.md) carries them out.

Workflow

  1. Brief before pixels. Pin down: who sees it, where (feed, story, print), the one message, the one action, the proof (price, date, offer), the brand colors and the look wanted. Missing message or action → ask; do not design around a gap. Use templates/roles/content-distribution/graphic-brief.md.
  2. Concept. One sentence: what the viewer feels and sees first. Choose the hero: a photo, a word, a number, or a shape. Exactly one hero.
  3. Look. Pick or create an art style (palette, type, texture, motifs) that fits the audience and concept — see references/art-styles.md. A look may repeat across a client's posts; a composition should not.
  4. Compose. Lay out hierarchy, grid, space, and depth per size — see references/principles.md. Prefer graphics compose (new layout per job, memory against repeats) or compose-campaign for a series; use make with a theme when the client chose a fixed template.
  5. Critique. Run the checklist in references/critique.md: the engine's automatic checks first (fit, overlap, contrast, design score), then the human-eye questions the engine cannot answer. Fix, re-render, look again.
  6. Deliver. Every size, editable SVG, font list, and the request JSON for later edits. Record time spent and what the client changed.

Decision rules

  • Two things fighting to be first → shrink or remove one; never make both big.
  • Text unreadable on a photo → move the text, add a solid panel or fade, or pick another crop; never lower the contrast bar.
  • Too much copy for the format → cut copy with the client or split into a carousel/series; never shrink body text below the size floor.
  • Brand colors that fail contrast → keep them for shapes and accents, set text in ink/white.
  • Thai text → no uppercase or wide tracking tricks; allow taller line height; never break inside a word; use a Thai-capable font for every Thai glyph.
  • "Make it pop / more wow" → raise scale contrast, depth, or one bold color move; do not add more elements.
  • A series → hold palette, type, and logo position constant; vary the composition idea, crop, and hero element per post.
  • Stock or client photos → only with commercial rights; no protected marks (Red Cross emblem, government seals), no imitation of another brand.
  • Design score high but it looks wrong to a person → the person wins; note why so the score can learn the case.

Resources

  • references/principles.md — read when composing or explaining why a layout works: message, hierarchy, typography, color, composition, photos, depth, formats, series variety.
  • references/art-styles.md — read when choosing, describing, or creating a look (what makes retro, minimal, jazz, dystopia, swiss … recognisable).
  • references/critique.md — read before delivering or when reviewing someone else's graphic: automatic checks vs. human checks, and common fixes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.