agent-instructions
Use when writing project instructions for a coding agent (CLAUDE.md, AGENTS.md, or equivalent). Covers what belongs in them, what does not, structure, and…
Use when creating posters, covers, social graphics, or other static visual designs. Covers composition, typographic hierarchy, colour, and producing original work rather than pastiche.
$ npx -y skills add nimadorostkar/Claude-Skills-collection --skill visual-design --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/visual-designContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when creating posters, covers, social graphics, or other static visual designs. Covers composition, typographic hierarchy, colour, and producing original work rather than pastiche.
name: visual-design description: Use when creating posters, covers, social graphics, or other static visual designs. Covers composition, typographic hierarchy, colour, and producing original work rather than pastiche. metadata: category: design version: 1.0.0 tags: [design, layout, typography, composition, poster]
Produce static visual designs — posters, covers, graphics — that are composed deliberately rather than assembled. Most weak design is not a failure of taste; it is a failure to establish a hierarchy.
1. **Establish the hierarchy first** — What is read first, second, third? If everything is emphasized, nothing is. This decision precedes every other one. 2. **Build on a grid** — Even a loose one. A grid is what makes an intentional composition distinguishable from an accidental one, and it is what makes breaking it read as deliberate. 3. **Use negative space as a material** — Space is not emptiness to be filled. It is what gives the focal point its force. 4. **Restrict the palette** — Two or three colours plus neutrals. Every additional colour dilutes the hierarchy you just built. 5. **Restrict the type** — Two typefaces at most. Hierarchy comes from size, weight, and space — not from more fonts. 6. **Test at the actual viewing distance** — A poster is read from three metres. Shrink it to thumbnail size: the focal point should still be unmistakable.
**Establishing hierarchy through contrast, not decoration:**
A conference poster. Three pieces of information:
1. The conference name <- must be read first, from across a room
2. The dates and the city <- second
3. The URL and the sponsors <- third, only if they are already interested
Weak: all three set at similar sizes, centred, in three colours. The eye lands
nowhere. From three metres it is a grey rectangle.
Composed:
- Name : 240pt, one colour, occupying the upper-left third, ranged left,
with the counters tight. It is the only thing visible at
thumbnail size — which is the test.
- Dates/city : 48pt, the accent colour, sitting directly beneath the name's
baseline, aligned to the same left edge.
- URL/sponsors: 18pt, neutral grey, at the foot, with generous space above so
they read as a footer rather than as content.
- The lower-right 40% of the poster is empty. That emptiness is what gives the
name its force. Filling it with a stock image would halve the poster's impact.
Palette: one dark neutral, one accent, white. Nothing else.
Type: one display face, one text face.**Output specification, which is where designs get ruined:**
Print (A2 poster):
- 300 DPI at final size. A 150 DPI file will look acceptable on screen and
visibly soft in print.
- CMYK, with the accent colour checked for gamut. A vivid RGB blue frequently
prints as a dull purple, and this is discovered at the printer.
- 3mm bleed on every edge, with nothing important within 5mm of the trim.
- Fonts outlined or embedded.
Screen (social, 1080x1350):
- RGB, sRGB colour profile.
- Text no smaller than 24px at 1080 width, or it is unreadable on a phone.
- Check the composition at 150px wide — that is the size of a feed thumbnail,
and it is where most people will see it.A curated library of 137 production-grade skills for Claude and other AI coding agents. Every skill follows one structure, speaks with one voice, and earns its place by changing what the agent does.
Repo: nimadorostkar/Claude-Skills-collection
Use when writing project instructions for a coding agent (CLAUDE.md, AGENTS.md, or equivalent). Covers what belongs in them, what does not, structure, and…
Use when an agent needs state that survives a session or a context compaction. Covers what to persist, file-based memory, structuring notes for retrieval, and…
Use when automating agent behavior with lifecycle hooks. Covers hook events, deterministic enforcement of rules the model should not be trusted to remember,…
Use when packaging skills, commands, hooks, and MCP servers into a distributable plugin. Covers manifest structure, bundling, versioning, testing, and…
Use when writing a new skill for an AI agent. Covers scoping, description writing for reliable triggering, progressive disclosure, and the difference between a…
Use when reviewing or improving an existing agent skill. Covers triggering accuracy, content quality, redundancy with the base model, and measuring whether the…