← Back to archive

Repo of the Day

mankidev/antialgorithm

Published: Nov 16, 2026

Open repository ↗

Claude Code skill that steers the model away from its first, most average pick in creative work: names, copy, ideas, posters, UI

Summary

antialgorithm is a Claude Code skill for creative work, including names, copy, stories, game ideas, posters, and UI. It asks Claude to identify its first, average response, then deliberately move away from that choice using a reason drawn from the project rather than relying on arbitrary variation.

What it is useful for

Use it when a creative brief risks producing a familiar default. The README demonstrates this with a prompt asking for a 400×600 music-festival poster saved as final.svg: runs without the skill repeatedly chose similar-looking designs, while the skill was designed to encourage more varied outcomes.

The repository provides three Python scripts for specific parts of that process:

  • seed.py creates a starting point when the request is thin. It supports visual seeds covering making method, colors, layout, typography, scale, setting, and other elements; text seeds covering voice, entry point, and register; and idea seeds combining a verb, constraint, scale, and pressure. It uses system randomness, so identical prompts can start in different places.
  • rough.py alters an SVG’s straight lines, shapes, letters, and repeated spacing to give code-drawn artwork a handmade appearance. It is limited to hand-made methods such as print, paint, stamps, and ink; it should not be applied to screen, camera, or render-style work.
  • check.py renders SVG artwork at full and icon sizes and reports text that extends beyond an edge, sits beneath another shape, has low contrast, or is too small.

How engineers can use it

Install the skill from the README:

git clone https://github.com/mankidev/antialgorithm ~/.claude/skills/antialgorithm

The scripts require Python 3. check.py additionally requires NumPy, Pillow, and either rsvg-convert or the cairosvg package.

In a Claude Code session, use the skill for open-ended creative tasks where the first suggestion may be too predictable. For sparse briefs, seed.py can provide concrete dimensions before alternatives are developed. For SVG output, rough.py can adjust intentionally handmade artwork, while check.py can inspect legibility at both delivery size and icon size before handoff.

For example, a poster workflow can begin with the README’s 400×600 festival prompt, use the skill to move beyond an average festival concept, apply handmade texture only if the chosen style calls for it, and then inspect the resulting SVG for clipping, overlap, contrast, and small-text issues.

The README does not document exact command-line syntax for each script, so engineers should start with its script descriptions and inspect each script’s usage before integrating the tools into an automated workflow.