agentleFS
ratacatratacat/ratacats-skills/skills/ansi-art/SKILL.md

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.

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
  1. Distinctive:

    Every row has a fixed cell width and preserves intentional leading/trailing spaces.

    line 21
  2. Distinctive:

    Stop when the art is display-ready for the requested environment or when the remaining uncertainty is a named terminal/font limitation.

    line 25
  3. Distinctive:

    Ask one blocking question only when width, subject, or output format is genuinely unknown.

    line 33
  4. Distinctive:

    Use a cell grid for app and CLI assets: each cell has a glyph, foreground, background, and optional attributes.

    line 36
  5. Distinctive:

    Use UTF-8 Unicode glyphs that correspond to CP437 for modern terminal output.

    line 37
  6. Very specific:

    Use CP437 bytes plus ANSI SGR only when producing a real .ANS artifact.

    line 38
  7. Distinctive:

    Use BIN/XBIN only when the user needs authentic textmode files, custom fonts/palettes, or archival compatibility.

    line 39
  8. Very specific:

    Read references/formats-and-rendering.md before designing storage or renderer code.

    line 40
  9. Very specific:

    Add shade transitions with ░, ▒, and ▓.

    line 46
  10. Distinctive:

    Use line drawing for UI frames and architectural structure.

    line 47
  11. Very specific:

    Read references/creation-playbook.md when the task is artistic rather than mechanical.

    line 48
  12. Distinctive:

    Use a constrained glyph vocabulary.

    line 50
  13. Very specific:

    Start with the core block set and box drawing set in references/glyphs-and-palette.md.

    line 51
  14. Distinctive:

    Treat letters, punctuation, bullets, and math symbols as texture accents after the big forms work.

    line 52
  15. Distinctive:

    Keep ambiguous-width Unicode outside the art unless the target renderer has explicit width tests.

    line 53
  16. Distinctive:

    Check that each non-ASCII glyph is in the allowed CP437 map.

    line 64
  17. Distinctive:

    Test narrow-terminal behavior: center, skip, or use a smaller mark instead of letting the terminal wrap.

    line 66
  18. Very specific:

    Read references/research-notes.md for the source-backed synthesis behind this skill.

    line 87
  19. Very specific:

    Read references/glyphs-and-palette.md for CP437 glyph families, color ramps, and style vocabulary.

    line 88
  20. Very specific:

    Read references/formats-and-rendering.md for .ANS, SAUCE, BIN/XBIN, UTF-8 terminal rendering, and code storage choices.

    line 89
  21. Very specific:

    Read references/creation-playbook.md for composition, shading, lettering, and polish steps.

    line 90

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Frame the target.
    • Identify the surface: CLI banner, splash screen, NFO, .ANS file, 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.
  2. 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 .ANS artifact.
    • Use BIN/XBIN only when the user needs authentic textmode files, custom fonts/palettes, or archival compatibility.
    • Read references/formats-and-rendering.md before designing storage or renderer code.
  3. 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.md when the task is artistic rather than mechanical.
  4. 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.
  5. 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.
  6. 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.md for the source-backed synthesis behind this skill.
  • Read references/glyphs-and-palette.md for CP437 glyph families, color ramps, and style vocabulary.
  • Read references/formats-and-rendering.md for .ANS, SAUCE, BIN/XBIN, UTF-8 terminal rendering, and code storage choices.
  • Read references/creation-playbook.md for composition, shading, lettering, and polish steps.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.