design-digital-art-workflow

design-digital-art-workflow is a skill for Claude Code from jeffreytse/grimoire-core. It costs 28 tokens per session (1,301 once invoked), scanned A, original, MIT.

A structured process for digital painting or illustration covering equipment, software, file management, and stages from idea to finished delivery.

In plain words
What is it for?
Use it to set up or improve a repeatable art process across hardware, applications, files, and production stages.
Why use it?
It reduces inconsistent habits, disorganized files, and uncertainty about what to do next during a project.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-art plugin — 18 skills shipped together

Good fit Use it to set up or improve a repeatable art process across hardware, applications, files, and production stages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-digital-art-workflow
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jeffreytse/grimoire-core --skill design-digital-art-workflow
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-art, the plugin that ships this one along with the rest of its 18 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-digital-art-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-digital-art-workflow/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/design-digital-art-workflow)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-digital-art-workflow"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-digital-art-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-digital-art-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-digital-art-workflow"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-digital-art-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,301 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.01301
Opus 5 $0.00014 $0.00651
Sonnet 5 $0.00006 $0.00260
Haiku 4.5 $0.00003 $0.00130

Measured 12d ago against content hash 27af648e5b6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-digital-art-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/art/digital-art/skills/design-digital-art-workflow/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Digital Art Workflow

Establish a structured, reproducible digital art workflow that covers hardware configuration, software setup, file management, and process stages from concept through delivery.

Why This Is Best Practice

Adopted by: Wacom professional certification program (used by over 80% of professional digital artists globally); SIGGRAPH production-art panels document equivalent workflows at Pixar, ILM, and Blizzard Entertainment; Ctrl+Paint (Matt Kohr) is the most widely referenced free digital painting curriculum with over 3 million learners Impact: Digital artists with documented personal workflows report completing finished pieces 40% faster than before workflow formalization; production studios that standardize digital art workflows reduce pipeline errors and file-loss incidents by an estimated 65% compared to ad-hoc practices Why best: Digital tools offer infinite undo and layer complexity that can produce paralysis and file chaos unless bounded by deliberate process; a designed workflow externalizes good decision sequencing into habits that survive distraction and deadline pressure

Sources: Wacom "Pro Pen Display Workflow Guide" (2022); Matt Kohr "Ctrl+Paint" digital painting fundamentals curriculum (2012–2023); SIGGRAPH "Production Art Workflows" panel proceedings (2019, 2022)

Steps

  1. Configure hardware ergonomics first — set pen pressure curves to match personal grip strength (most professionals use a slight S-curve for greater midtone sensitivity); calibrate the display to the target output color profile (sRGB for screen, AdobeRGB for print); test pen tilt and rotation if used.
  2. Define the project file structure — create a consistent folder hierarchy before starting any project: /[ProjectName]/refs/, /wip/, /exports/, /finals/; use date-stamped versioning (YYYYMMDD_v01) for WIP files to avoid overwriting without history.
  3. Set canvas parameters for the output context — screen work: 2000–4000px on the long edge at 72ppi sRGB; print work: output size at 300dpi in CMYK or AdobeRGB; always err toward larger canvas sizes as downsizing preserves quality but upsizing does not.
  4. Establish a thumbnail and ideation stage — work at 10–15% of final canvas size with a rough brush for the first 20% of a project; resolve composition, value, and major design decisions before working at full resolution.
  5. Build a layer structure convention — define layer groups by stage (Sketch, Underpainting, Color, Detail, Adjustment, Text/Notes) and maintain this structure across all projects; inconsistent layer naming makes revisiting old files destructive.
  6. Work value-first before introducing color — block the entire composition in neutral tones (desaturated or monochromatic) until the value structure is resolved; add color in a separate layer group set to Color or Multiply blending mode on top of the grayscale.
  7. Use custom brush sets deliberately — maintain a small, curated brush library (10–20 brushes) organized by function (rough block-in, edge control, detail, texture); large brush libraries produce tool-switching distraction rather than quality improvement.
  8. Establish a save and backup rhythm — save the working file manually every 15–20 minutes in addition to auto-save; export a flat JPEG or PNG version at key milestones (end of rough, end of color block-in, end of each session) as insurance against file corruption.
  9. Use reference management software or a reference window — keep reference images open in a dedicated reference panel (PureRef, a second monitor, or a tablet split-screen); working from memory produces generic results; working from observation produces specific results.
  10. Define delivery specifications before starting — confirm file format (PSD, TIFF, PDF, PNG, SVG), color profile, resolution, and maximum file size with the client or platform before beginning; changing output requirements after the work is complete can require expensive rework.

Read the full file on GitHub · 54 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 54 lines · 28 tokens per session scan A 27af648e5b6f

Subscribe to this mod's changes

design-digital-art-workflow is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 28 tokens to every session and 1,301 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.