agentleFS
kensauruskensaurus/cursor-kenji/skills/design-canvas/SKILL.md

design-canvas

Skill9 starsChanged 43 days agoMITView on GitHub

Create museum-quality visual art as .png or .pdf: posters, infographics, certificates, badges, banners, social graphics, print. Use when "create artwork", "design graphic", "visual identity", or "print material".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 15 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈15

    Distinctive · estimate

    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:

    Create design philosophies that are expressed visually.

    line 15
  2. Distinctive:

    Create a VISUAL PHILOSOPHY that will be expressed through:

    line 42
  3. Distinctive:

    Leave creative space for interpretation

    line 59
  4. Distinctive:

    Create museum or magazine quality work

    line 66
  5. Distinctive:

    Use repeating patterns and perfect shapes

    line 67
  6. Distinctive:

    Treat abstract design as systematic observation

    line 68
  7. Distinctive:

    Add sparse, clinical typography

    line 69
  8. Distinctive:

    Use limited, intentional color palette

    line 70
  9. Distinctive:

    Ensure nothing overlaps or falls off the canvas

    line 71
  10. Distinctive:

    Use different fonts for variety

    line 77
  11. Distinctive:

    All elements need breathing room and clear separation

    line 78
  12. Distinctive:

    Every detail should look labored over with care

    line 101
  13. Distinctive:

    Don't add more graphics; refine what exists

    line 108
  14. Distinctive:

    Ask: "How can I make what's here more of a piece of art?"

    line 109
  15. Distinctive:

    Create additional pages following the design philosophy

    line 114
  16. Distinctive:

    After creating the artifact:

    line 148

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Canvas Design Skill

Degree of freedom: MIXED. Movement name and composition [HIGH freedom]; brand-asset inventory [LOW freedom — run exactly].

Create design philosophies that are expressed visually. Output .md files (philosophy) and .pdf/.png files (visual art).

How to reason

  1. Inventory — existing brand assets and visual language
  2. Name — 1–2 word movement
  3. Compose — form, space, color; text as accent only
  4. Refine — second pass; nothing overlaps; museum craft

Worked example

Inventory: wordmark in public/brand/; no poster system; palette is charcoal + one red. Name: "Chromatic Silence". Compose: one red field, monumental type as shape, 12pt label only; no paragraph copy. Refine: crop so the wordmark does not collide; export PNG at print dpi.

Self-critique before reporting

  • Brand-first — new art complements existing assets; it does not invent a second identity
  • Text is accent — no paragraph dump on the canvas
  • Craft pass — second refine happened; nothing overlaps or clips
  • Right owner — UI chrome → design-frontend; data charts → data-visualization; token SSOT → design-system

Process

Step 1: Design Philosophy Creation [HIGH freedom]

Create a VISUAL PHILOSOPHY that will be expressed through:

  • Form, space, color, composition
  • Images, graphics, shapes, patterns
  • Minimal text as visual accent

Philosophy Structure:

  1. Name the movement (1-2 words): "Brutalist Joy" / "Chromatic Silence"
  2. Articulate the philosophy (4-6 paragraphs):
  • Space and form
  • Color and material
  • Scale and rhythm
  • Composition and balance
  • Visual hierarchy

Guidelines:

  • Avoid redundancy
  • Emphasize craftsmanship once, concretely — say what makes this piece look labored over, not as a refrain
  • Leave creative space for interpretation

Step 2: Canvas Creation [HIGH freedom]

With the philosophy established, express it visually.

Principles:

  • Create museum or magazine quality work
  • Use repeating patterns and perfect shapes
  • Treat abstract design as systematic observation
  • Add sparse, clinical typography
  • Use limited, intentional color palette
  • Ensure nothing overlaps or falls off the canvas

Text Rules:

  • Text is always minimal and visual-first
  • Context guides scale (punk poster vs. minimalist identity)
  • Fonts should be design-forward
  • Use different fonts for variety
  • All elements need breathing room and clear separation

Example Philosophies

"Concrete Poetry" Communication through monumental form and bold geometry. Massive color blocks, sculptural typography, Brutalist spatial divisions. Ideas expressed through visual weight and spatial tension. Text as rare, gesture - never paragraphs.

"Chromatic Language" Color as the primary information system. Geometric precision where color zones create meaning. Typography minimal - small sans-serif labels letting chromatic fields communicate. Information encoded spatially and chromatically.

"Analog Meditation" Quiet visual contemplation through texture and breathing room. Paper grain, ink bleeds, vast negative space. Photography and illustration dominate. Typography whispered. Japanese photobook aesthetic.

"Organic Systems" Natural clustering and modular growth patterns. Rounded forms, organic arrangements, color from nature. Information shown through visual diagrams, spatial relationships, iconography. Text only for key labels.

"Geometric Silence" Pure order and restraint. Grid-based precision, bold photography, dramatic negative space. Typography precise but minimal. Swiss formalism meets Brutalist honesty. Structure communicates.

Quality Standards

Quality bar:

  • Work must appear meticulously crafted
  • Every detail should look labored over with care
  • Composition, spacing, color choices must show expert-level craftsmanship
  • Nothing overlaps, formatting is flawless
  • Could be displayed in a museum

Refinement Process:

  • Take a second pass to refine/polish
  • Don't add more graphics; refine what exists
  • Ask: "How can I make what's here more of a piece of art?"

Multi-Page Option

When requested:

  • Create additional pages following the design philosophy
  • Each page should be a unique twist on the original
  • Almost tell a story in a tasteful way
  • Bundle in same .pdf or multiple .pngs

Output

  1. Design Philosophy (.md) - 4-6 paragraphs describing the aesthetic movement
  2. Visual Artifact (.pdf or .png) - Museum-quality visual design

Check existing first [LOW freedom — run exactly]

Before creating ANY visual design, verify:

  1. Check for existing brand assets:
ls -la public/ assets/ src/assets/ 2>/dev/null
ls -la *.svg *.png brand/ logos/ 2>/dev/null
  1. Check for existing design system:
cat tailwind.config.* 2>/dev/null | grep -A20 "colors\|fontFamily"
cat docs/THEME_GUIDE.md .cursor/rules/*.md 2>/dev/null
  1. Understand context:
  • Is there an existing brand identity?
  • What are the target use cases?

Why: Visual designs should complement, not conflict with, existing brand identity.

Validation [LOW freedom — do not skip]

After creating the artifact:

  1. Visual inspection → Check composition and balance
  2. Typography check → Fonts render correctly, readable hierarchy
  3. Color verification → Colors match specification
  4. Export quality → Resolution appropriate for intended use
  5. Accessibility → Sufficient contrast for any text elements
  6. File size → Optimized for intended distribution

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.