evo.snippets

An ongoing collection of code snippets — each one does exactly one thing, installs nothing, and then stops talking. Snip one out and take it home.

Repository (MIT license): github.com/evomedia-net/evo.snippets

Each snippet is a folder you can copy into a project, or run in place against any codebase — no install step, no framework, no shared runtime between them.

Every snippet uses only its language's standard library. There is nothing to pip install or npm install, no lockfile to drift, and no build step. Clone the repo, or copy the one folder you need.

Guides

Guide	What it covers
find-oversized-input-limits	Finding user-input character limits above a threshold, in any stack
confetti-burst	A confetti renderer that falls like paper — drag, tumble and flutter, with a tuning panel

---

Layout

Snippets are grouped by what they do, then by the language each implementation is written in:

<what-it-does>/<language>/

A snippet that exists in more than one language keeps its implementations side by side under the one folder, so you find the tool first and pick a runtime second.

The language folder describes a runtime, not a reach. The Python scanner reads TypeScript, PHP, Go, and Java codebases perfectly well — it just needs Python to run.

Shared conventions

Knowing one snippet means knowing all of them. Every folder follows the same shape:

• README.md plus a plain-text README.txt twin, kept in sync.
• COMMAND.md at the snippet root — every option the snippet takes, what it does, and a sample of its use, with a COMMAND.txt twin.
• run.ps1 and run.sh launchers that pass every argument straight through, so the same command line works on Windows and Linux.
• Standard library only.
• Exit code 0 when clean, 1 when the tool found something, and 2 for a usage or environment error. That 0/1 split is what lets any snippet drop into CI as a gate without a wrapper.
• -help works, alongside --help, --h, -h, and -?.

Twins

Where the same snippet exists in two languages, the two are kept behaviorally identical, not merely similar: same rules, same flags, same exit codes, and byte-identical output, verified by diffing both tools across every mode.

Pick by what your machine already has installed, not by what the snippet can do.

That guarantee shapes the code. The TypeScript twin of the scanner sorts with a codepoint comparator rather than localeCompare — because localeCompare folds case, which would sort Model.cs next to models.py instead of before every lowercase name, and break parity with Python's sorted().

Contact

Kelly Michels · kelly@evomedia.net

Issues and pull requests are welcome. If a snippet misses a pattern in a stack you use, that is worth reporting — coverage breadth is the whole point.