brief
Skill473 starsChanged 44 days agoMITView on GitHub
Turn a vague pixel-art request into a written brief — size, palette, view, light, outline style — and confirm it with the user before any pixel is drawn. Use when the request is open-ended ("make me a knight") rather than a specific edit.
78 other projects use a version of this.
Adopted by
Most recently taken up by
- serhiileniv/skillstheir own version, first seen Nov 8, 2026
- serhiileniv/ccstheir own version, first seen Nov 8, 2026
- fjwood69/moritheir own version, first seen Nov 8, 2026
- cathyzhang0905/agent-cockpittheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- grainulation/grainulatortheir own version, first seen Nov 3, 2026
Used with
Projects with it also use capture, strategy and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
toneron2Skillcapture
Capture thoughts to inbox with automatic classification
Also in 6 projects that use this
EpistatesSkillstrategy
Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.
Also in 4 projects that use this
aleksander-dytkoSkilldecision
Make a product decision with full context from the vault and available sources
Also in 3 projects that use this
dirienSkilldecide
Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.
Also in 5 projects that use this
JaimeGBASkillingest
Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base
Also in 7 projects that use this
howellsSkillreconcile
Audit a project against current plugin conventions and offer to update structure.
Also in 3 projects that use this
Other versions78 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 78
- anthropics/knowledge-work-plugins★ 35ksame name
- suboss87/FDEOps★ 940same name
- educlopez/ui-craft★ 441same name
- github/lever★ 279same name
- dylanroscover/Embody★ 213same name
- yofine/skills★ 154same name
- grainulation/grainulator★ 86same name
- g2i-ai/agents★ 52same name
- gregmos/memoforge★ 38same name
- manusco/resonance★ 38same name
68 more not listed
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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 71 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
preflight: If not ready, stop and tell the user — nothing below works without a live Aseprite. - Very specific: line 29
Read what already exists: If a sprite is open, sprite_info it.
- Very specific: line 46
When the request is something new — a character, a prop, an animation — aseprite:concept follows, and its offer goes in this same message: …
- Distinctive: line 52
Ask only what genuinely blocks you: If the sprite is for a specific game and you do not know its tile size, that one is worth asking.
“Common” is measured: kept by at least 6 in 10 of the 71 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plan a sprite before drawing it
A request like "draw me a knight sprite" contains none of the decisions that determine whether the result is usable. Guessing them and drawing anyway wastes the user's time and yours. Five questions, one answer, then draw.
What you need to know
| Decision | Why it cannot be deferred | Reasonable default |
| Canvas size | Determines how much can be shown at all | 32×32 for a character |
| Palette | Choosing it later means repainting | PICO-8 (16 colours) |
| View | Side-on, top-down and 3⁄4 are different drawings | 3⁄4 |
| Light direction | Must be fixed before any shading | Upper-left |
| Outline | Changes every edge in the sprite | Selective, dark-coloured |
| Destination | A game engine wants tags and a sheet | Ask |
Procedure
preflight. If not ready, stop and tell the user — nothing below works without a live Aseprite.- Read what already exists. If a sprite is open,
sprite_infoit. The user's existing canvas size and palette usually answer half the questions, and matching an existing project's style is almost always what they want. - Draft the brief. Fill the table above from what the user said plus the defaults. Do not ask about things you can reasonably infer — "a Game Boy style knight" has already told you the palette and the size range.
Put it to the user in one message, as decisions rather than questions:
32×32, PICO-8 palette, 3⁄4 view, light from upper-left, selective dark outline. Knight in plate with a sword, facing camera. Say if any of that is wrong — otherwise I'll start.
One round trip, not five. If they said nothing about a detail, they probably do not care about it.
When the request is something new — a character, a prop, an animation —
aseprite:conceptfollows, and its offer goes in this same message: the decisions above, then the image-model prompt in one code block, then the choice between sending references and continuing without. The user answers once. If they correct a decision, fix the prompt to match before they copy it.- Ask only what genuinely blocks you. If the sprite is for a specific game and you do not know its tile size, that one is worth asking. Light direction is not.
- Record the brief in your working notes and hold to it. Every later decision either follows from the brief or is a mistake.
Then
aseprite:concept for anything drawn from scratch — its offer is already in
the message above. Then aseprite:new to create the document, or
aseprite:draw if a suitable sprite is already open.
Related
rules://00-core-principles for what the sizes buy you.
rules://03-silhouette-and-form for view and proportion.
rules://30-proportions-by-size and rules://14-readability-and-scale for what
each canvas size can hold; rules://90-platform-styles when the user names a
console or era.
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.