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
- kensaurus/skillsword for word, first seen Oct 1, 2026
- Andyt2666/agent-skillstheir own version, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 1
- kensaurus/skills★ 9100% same
Edited · 0
None found.
Wrote their own version · 1
- Andyt2666/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository165 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/approved-plan-execution.mdcCursor rule
- .cursor/rules/skill-workflows.mdcCursor rule
- .cursor/rules/verification-before-completion.mdcCursor rule
- llms.txtllms.txt
- audit-accessibilitySkill
- audit-agent-speedSkill
- audit-analyticsSkill
- audit-auth-flowsSkill
- audit-backend-architectureSkill
- audit-bundle-sizeSkill
- audit-cicdSkill
- audit-codemod-safetySkill
- audit-code-qualitySkill
- audit-code-reviewSkill
- audit-db-schemaSkill
- audit-doctrineSkill
- audit-env-paritySkill
- audit-fe-apiSkill
- audit-gate-logicSkill
- audit-i18nSkill
- audit-infra-costSkill
- audit-langfuse-llmSkill
- audit-llm-securitySkill
- audit-monetization-iapSkill
- audit-payment-systemSkill
- audit-performanceSkill
- audit-realworldSkill
- audit-registry-listingSkill
- audit-resilienceSkill
- audit-responsiveSkill
- audit-securitySkill
- audit-skill-conflictsSkill
- audit-ui-statesSkill
- audit-uiux-design-systemSkill
- audit-ux-journeysSkill
- audit-uxSkill
- backend-db-performanceSkill
- backend-error-handlingSkill
- backend-observabilitySkill
- backend-patternsSkill
- backend-realtimeSkill
- burndown-fullSkill
- complete-everythingSkill
- data-pipelineSkill
- data-visualizationSkill
- debug-errorSkill
- debug-fe-be-integrationSkill
- debug-sentry-monitorSkill
- deploy-npmSkill
- deploy-verifySkill
- design-apiSkill
- design-emailSkill
- design-frontendSkill
- design-generative-artSkill
- design-mobile-firstSkill
- design-motionSkill
- design-prdSkill
- design-systemSkill
- design-themeSkill
- The first 60 shown.
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
- Very specific: line 15
Create design philosophies that are expressed visually.
- Distinctive: line 42
Create a VISUAL PHILOSOPHY that will be expressed through:
- Distinctive: line 59
Leave creative space for interpretation
- Distinctive: line 66
Create museum or magazine quality work
- Distinctive: line 67
Use repeating patterns and perfect shapes
- Distinctive: line 68
Treat abstract design as systematic observation
- Distinctive: line 69
Add sparse, clinical typography
- Distinctive: line 70
Use limited, intentional color palette
- Distinctive: line 71
Ensure nothing overlaps or falls off the canvas
- Distinctive: line 77
Use different fonts for variety
- Distinctive: line 78
All elements need breathing room and clear separation
- Distinctive: line 101
Every detail should look labored over with care
- Distinctive: line 108
Don't add more graphics; refine what exists
- Distinctive: line 109
Ask: "How can I make what's here more of a piece of art?"
- Distinctive: line 114
Create additional pages following the design philosophy
- Distinctive: line 148
After creating the artifact:
≈ “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.
Files
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
- Inventory — existing brand assets and visual language
- Name — 1–2 word movement
- Compose — form, space, color; text as accent only
- 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:
- Name the movement (1-2 words): "Brutalist Joy" / "Chromatic Silence"
- 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
- Design Philosophy (.md) - 4-6 paragraphs describing the aesthetic movement
- Visual Artifact (.pdf or .png) - Museum-quality visual design
Check existing first [LOW freedom — run exactly]
Before creating ANY visual design, verify:
- Check for existing brand assets:
ls -la public/ assets/ src/assets/ 2>/dev/null
ls -la *.svg *.png brand/ logos/ 2>/dev/null- 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- 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:
- Visual inspection → Check composition and balance
- Typography check → Fonts render correctly, readable hierarchy
- Color verification → Colors match specification
- Export quality → Resolution appropriate for intended use
- Accessibility → Sufficient contrast for any text elements
- File size → Optimized for intended distribution
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
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.

