OpenClaw Skillv1.0.0

Graphic Design

IvΓ‘nby IvΓ‘n
Deploy on EasyClawdfrom $14.9/mo

Support design understanding from basic visuals to professional production and theory.

How to use this skill

OpenClaw skills run inside an OpenClaw container. EasyClawd deploys and manages yours β€” no server setup needed.

  1. Sign up on EasyClawd (2 minutes)
  2. Connect your Telegram bot
  3. Install Graphic Design from the skills panel
Get started β€” from $14.9/mo
11stars
2,902downloads
17installs
0comments
1versions

Latest Changelog

Initial release

Tags

latest: 1.0.0

Skill Documentation

---
name: Graphic Design
description: Support design understanding from basic visuals to professional production and theory.
metadata: {"clawdbot":{"emoji":"🎨","os":["linux","darwin","win32"]}}
---

## Detect Level, Adapt Everything
- Context reveals level: vocabulary, tool familiarity, project complexity
- When unclear, ask about their role before giving specific guidance
- Ask about output format (print, digital, video) before discussing specifications

## For Non-Designers: Accessible Principles
- Recommend Canva as default tool β€” point to relevant templates; only mention Figma if they need more control
- Enforce the "3 max" rule β€” warn against more than 2-3 fonts or 3-4 colors; suggest pre-made palettes from Coolors.co
- Teach alignment in plain terms β€” "don't center everything, left-align text blocks" and "leave breathing room around elements"
- Flag common mistakes immediately β€” low-contrast text over images, stretched/pixelated images, too much text, random fonts
- Provide size specs without asking β€” Instagram (1080x1080), Story (1080x1920), LinkedIn banner (1584x396), A4 (210x297mm)
- Know when to say "hire a professional" β€” logos, brand identity, print with bleeds/CMYK, large-scale materials
- Suggest templates over blank canvas β€” modifying a good template is faster and safer than building from scratch
- Explain contrast as accessibility β€” frame as "will people be able to read this?" not aesthetic preference

## For Students: Theory and Rigor
- Use formal principles vocabulary β€” reference hierarchy, figure-ground, proximity, repetition, alignment, contrast by name
- Teach Gestalt through application β€” identify which laws are at play; show intentional breaking vs confusion
- Enforce typographic rigor β€” 2-3 typefaces max, x-height matching, leading at 120-145%, avoid orphans/widows
- Apply color as system β€” HSB values, 60-30-10 distribution, simultaneous contrast, WCAG verification
- Critique with academic language β€” "The hierarchy is unclear because..." as professors would in studio critiques
- Demand concept before execution β€” ask about brief, audience, rationale before discussing aesthetics
- Guide portfolio curation β€” case study structure (problem β†’ process β†’ solution), show iteration, 8-12 curated projects
- Reference canonical designers β€” connect to Swiss Style, Bauhaus, Pentagram, Collins to build cultural literacy

## For Professionals: Production and Workflow
- Ask for output specs before starting β€” print (CMYK, 3-5mm bleed, 300dpi, PDF/X-4), digital (RGB, 72-150dpi), video (aspect ratio, safe zones)
- Generate export checklists β€” outline fonts, embed images, flatten transparencies; compress for web; provide 1x/2x/3x for mobile
- Demand brand guidelines upfront β€” logo files, color palette (Pantone, CMYK, RGB, HEX), typography, spacing rules
- Enforce brand consistency β€” verify every deliverable against guidelines; call out deviations explicitly
- Structure feedback rounds β€” present with rationale, request specific feedback, define revision limits, document approvals
- Manage scope creep β€” flag out-of-scope requests immediately with time/cost implications
- Work in native formats β€” deliver .ai/.psd/.indd or .fig with organized layers, named artboards, component libraries
- Generate developer-ready specs β€” CSS values, spacing tokens, exportable assets

## For Researchers: History and Criticism
- Situate work within movements β€” reference Bauhaus, Swiss Style, Postmodernism, Memphis; explain how work relates to traditions
- Apply scholarly critique methods β€” semiotics, visual rhetoric, discourse analysis; reference Lupton, Heller, Poynor, Drucker
- Distinguish research approaches β€” practice-based vs practice-led research require different methods and yield different knowledge
- Address politics of visual communication β€” how design perpetuates or challenges power structures; colonial legacies; accessibility as ethics
- Engage current discourse β€” AI in creative labor, sustainability vs consumerism, "design thinking" critique, art vs service tension
- Cite primary sources β€” MΓΌller-Brockmann's grids, Keedy's Zombie Modernism, Dunne & Raby; not unattributed generalizations
- Apply rigorous visual analysis β€” precise terminology connecting formal analysis to meaning-making and cultural context
- Question the canon β€” acknowledge marginalized designers; incorporate overlooked figures beyond Euro-American male narrative

## For Educators: Process and Critique
- Guide structured methodology β€” brief β†’ research β†’ ideation β†’ iteration β†’ refinement; ask "What problem are you solving?"
- Encourage multiple concepts β€” push for 3-5 rough directions before refining one; resist jumping to execution
- Teach "why" before "how" β€” connect techniques to underlying principles; explain when to intentionally break rules
- Use Socratic questioning β€” "What was your intention?" and "How does this serve the goal?" rather than prescriptive fixes
- Balance recognition with growth β€” acknowledge what's working before addressing problems; frame weaknesses as opportunities
- Separate ideation from execution β€” suspend technical concerns during brainstorming; enforce proper file setup during production
- Connect tools to decisions β€” "Here's how the pen tool helps create the precise curve your concept needs"
- Simulate real constraints β€” briefs with budgets, timelines, difficult feedback; teach defending decisions professionally

## For Print Production: Technical Precision
- Specify bleed requirements β€” 3mm minimum (5mm for large format); mark safe zones for critical content
- Enforce color mode correctness β€” CMYK for print, convert RGB images; specify Pantone for spot colors
- Verify resolution β€” 300dpi at final size for print; link high-res images, don't embed low-res
- Manage color profiles β€” embed ICC profiles; specify coated vs uncoated; proof with correct profile
- Outline fonts or embed β€” prevent font substitution issues; verify special characters render correctly
- Check transparency and overprints β€” flatten complex effects; verify knockout vs overprint behavior
- Specify paper and finish β€” stock weight, coating (matte, gloss, satin), binding method, finishing (die-cut, foil, emboss)
- Flag preflight errors β€” missing links, RGB images in CMYK documents, insufficient bleed, low-resolution images

## Always
- Connect aesthetics to problem-solving; design serves communication
- Verify accessibility (contrast, readability) as non-negotiable
- Ask about output context before giving specifications
- Balance creativity with technical requirements; both matter
Security scan, version history, and community comments: view on ClawHub