ansi-art
Skill9 starsChanged 5 months agoMITView on GitHub
Create, review, convert, or embed terminal text art: ASCII/ANSI art, CP437, block ASCII, BBS logos, CLI banners, NFOs, SAUCE/XBIN/BIN/ANS output.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agentic-scaffoldingSkill
- annas-archive-ebooksSkill
- clarifySkill
- conjecture-cascadeSkill
- crystallizeSkill
- dianalokadaSkill
- duris-game-knowledgeSkill
- duris-group-combatSkill
- ebook-extractorSkill
- failure-modesSkill
- gpt-pro-loopSkill
- graph-researcherSkill
- improve-codebaseSkill
- jevSkill
- julian-writingSkill
- kalshi-prediction-marketSkill
- lemmaSkill
- medium-paywall-bypassSkill
- ml-learning-methodsSkill
- name-reviewSkill
- no-process-pornSkill
- pm-deep-analysisSkill
- pm-market-analysisSkill
- pm-research-methodologiesSkill
- pm-situation-framingSkill
- prediction-drillSkill
- probe-driven-designSkill
- refine-testsSkill
- remove-ai-sinsSkill
- show-usageSkill
- writing-claude-skillsSkill
- x-undocumented-apiSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. About 0 are common, 12 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Every row has a fixed cell width and preserves intentional leading/trailing spaces.
- Distinctive: line 25
Stop when the art is display-ready for the requested environment or when the remaining uncertainty is a named terminal/font limitation.
- Distinctive: line 33
Ask one blocking question only when width, subject, or output format is genuinely unknown.
- Distinctive: line 36
Use a cell grid for app and CLI assets: each cell has a glyph, foreground, background, and optional attributes.
- Distinctive: line 37
Use UTF-8 Unicode glyphs that correspond to CP437 for modern terminal output.
- Very specific: line 38
Use CP437 bytes plus ANSI SGR only when producing a real .ANS artifact.
- Distinctive: line 39
Use BIN/XBIN only when the user needs authentic textmode files, custom fonts/palettes, or archival compatibility.
- Very specific: line 40
Read references/formats-and-rendering.md before designing storage or renderer code.
- Very specific: line 46
Add shade transitions with ░, ▒, and ▓.
- Distinctive: line 47
Use line drawing for UI frames and architectural structure.
- Very specific: line 48
Read references/creation-playbook.md when the task is artistic rather than mechanical.
- Distinctive: line 50
Use a constrained glyph vocabulary.
- Very specific: line 51
Start with the core block set and box drawing set in references/glyphs-and-palette.md.
- Distinctive: line 52
Treat letters, punctuation, bullets, and math symbols as texture accents after the big forms work.
- Distinctive: line 53
Keep ambiguous-width Unicode outside the art unless the target renderer has explicit width tests.
- Distinctive: line 64
Check that each non-ASCII glyph is in the allowed CP437 map.
- Distinctive: line 66
Test narrow-terminal behavior: center, skip, or use a smaller mark instead of letting the terminal wrap.
- Very specific: line 87
Read references/research-notes.md for the source-backed synthesis behind this skill.
- Very specific: line 88
Read references/glyphs-and-palette.md for CP437 glyph families, color ramps, and style vocabulary.
- Very specific: line 89
Read references/formats-and-rendering.md for .ANS, SAUCE, BIN/XBIN, UTF-8 terminal rendering, and code storage choices.
- Very specific: line 90
Read references/creation-playbook.md for composition, shading, lettering, and polish steps.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
ANSI Art
Goal: Create original CP437/ANSI/textmode art that renders cleanly in modern fixed-width terminals while carrying the visual richness of oldschool BBS art.
Success means:
- The target terminal, width, height, color policy, and output format are explicit.
- Every row has a fixed cell width and preserves intentional leading/trailing spaces.
- The glyph vocabulary comes from CP437-safe single-cell characters.
- The final output includes validation notes for width, colors, wrapping, and fallback behavior.
Stop when the art is display-ready for the requested environment or when the remaining uncertainty is a named terminal/font limitation.
Workflow
- Frame the target.
- Identify the surface: CLI banner, splash screen, NFO,
.ANSfile, README preview, game UI, or code-embedded asset. - Set hard dimensions in character cells. For CLI banners, prefer 40-64 columns and 6-14 rows unless the user asks for larger art.
- Select color mode: monochrome, 8-color ANSI, 16-color ANSI/iCE-style, 256-color, truecolor, or no-color fallback.
- Ask one blocking question only when width, subject, or output format is genuinely unknown.
- Identify the surface: CLI banner, splash screen, NFO,
- Choose the representation.
- Use a cell grid for app and CLI assets: each cell has a glyph, foreground, background, and optional attributes.
- Use UTF-8 Unicode glyphs that correspond to CP437 for modern terminal output.
- Use CP437 bytes plus ANSI SGR only when producing a real
.ANSartifact. - Use BIN/XBIN only when the user needs authentic textmode files, custom fonts/palettes, or archival compatibility.
- Read
references/formats-and-rendering.mdbefore designing storage or renderer code.
- Compose like pixel art.
- Block in the silhouette at thumbnail scale.
- Pick a light source before adding texture.
- Build large masses with
█,▀,▄,▌, and▐. - Add shade transitions with
░,▒, and▓. - Use line drawing for UI frames and architectural structure. For organic outlines, use line drawing only when the style calls for a hard-edged look.
- Read
references/creation-playbook.mdwhen the task is artistic rather than mechanical.
- Use a constrained glyph vocabulary.
- Start with the core block set and box drawing set in
references/glyphs-and-palette.md. - Treat letters, punctuation, bullets, and math symbols as texture accents after the big forms work.
- Keep ambiguous-width Unicode outside the art unless the target renderer has explicit width tests.
- Start with the core block set and box drawing set in
- Render for terminals.
- Emit explicit line breaks at the chosen width.
- Preserve leading and trailing spaces in source storage and output tests.
- Batch adjacent cells with the same style into one ANSI SGR span.
- Reset SGR before each newline and after the last row.
- Provide a no-color version when the art is used in a CLI that honors
NO_COLOR,TERM=dumb, or--color never.
- Validate.
- Count cell width for every row.
- Check that each non-ASCII glyph is in the allowed CP437 map.
- Preview in at least one monospaced terminal font with box/block glyph support.
- Test narrow-terminal behavior: center, skip, or use a smaller mark instead of letting the terminal wrap.
- For code assets, add a focused test that rejects tabs, wide glyphs, inconsistent row widths, and unterminated ANSI styling.
Output Patterns
For design work, return:
Target:
Dimensions:
Palette:
Glyph set:
Art:
Validation:
Implementation notes:For implementation work, include the renderer/storage choice and the tests that guard spacing.
Research References
- Read
references/research-notes.mdfor the source-backed synthesis behind this skill. - Read
references/glyphs-and-palette.mdfor CP437 glyph families, color ramps, and style vocabulary. - Read
references/formats-and-rendering.mdfor.ANS, SAUCE, BIN/XBIN, UTF-8 terminal rendering, and code storage choices. - Read
references/creation-playbook.mdfor composition, shading, lettering, and polish steps.
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.

