agentleFS
Sign inStart free
t1mericksont1merickson/skills/kit/SKILL.md

kit

Skill1 starsChanged 2 months agoMITView on GitHub

Operate Kit, the font-project toolkit (`kit` CLI) that holds all of a type-design workspace's tooling: audits and rule plugins, measuring, parts, coverage and fill, curve repair, plans applied safely to Glyphs packages, kerning and spacing, sheets and specimens, tracing, Bench views. Use for any measuring, checking, editing or reporting on fonts in a workspace that has Kit, before writing a new script.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read-only sources (archives, font libraries, installed fonts, Downloads) are never written to.

    line 45
  2. Very specific:

    Use the library in a few lines of Python (from kit import font, geom, report.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Kit

Kit is one CLI and Python library for a type-design workspace (Developer/Fonts): every font project reads fonts, measures, checks, edits and reports through it. The projects hold data, sources and pages; the tools live in Kit. Its docs live with it: Kit/README.md, Kit/docs/cookbook.md (which command answers which question), Kit/docs/commands.md, Kit/docs/library.md, and Kit/DESIGN.md (the contract). Read the cookbook first; read DESIGN.md before changing Kit.

Run it

From inside a project (Kit finds the nearest kit.toml): .venv/bin/kit <command>. The project's kit.toml supplies the font, the reference, the output folder and the rules, so most commands need no arguments.

NeedCommand
check drawing against the project's rules (plus rule plugins: health, components, kinks, joints, wobble...)kit audit (prints new / fixed / same)
numbers: levels, stems, weight, curves, terminals, serifs, spacing, sides, body, nib...kit measure FONT TOPIC (--list shows topics)
stroke weight and contrast at chosen spotskit weigh
shared drawings, components, ligature parts, markskit parts
what's built, waiting, left to draw; language supportkit coverage, kit languages
fill a glyph set from a reference out of your own partskit fill --plan, then --apply --glyphs-closed
curve repair: fair, fillets, rounds, snap, smooth, refitkit curves ... (a plan + Bench overlays)
apply any plan to a package safely; preview itkit apply PLAN --glyphs-closed, kit preview PLAN
a bold from the regular; serif corners as components; stems on a reference's hintskit embolden, kit corners, kit align
kerning and spacingkit kern ..., kit space ...
pictures and pageskit sheet, kit overlay, kit specimen, kit proof
pictures to outlines; pen centerlineskit trace, kit skeleton
what changed between two versionskit diff BEFORE AFTER
one glyph's points, a font's tableskit inspect FONT GLYPH, kit info FONT
fonts by namekit fonts
Bench views, measurement marks, review listskit view, kit marks, kit review, kit retire

Each report writes report.html for the user and report.json for you, side by side in <out>/<command>/. Read the JSON; send the user the HTML. --json prints the result instead of the summary.

Rules Kit enforces, and you keep

  • Glyphs packages: close the font in Glyphs first (through the Glyphs MCP, refusing if it has unsaved edits; ask the user to save), kit snapshot --reason R, write, then kit diff against the snapshot. Never delete glyphs. Never discard the user's unsaved edits.
  • Read-only sources (archives, font libraries, installed fonts, Downloads) are never written to.
  • A reference font is a witness, not a target: report a difference as a question, lead with the glyph's own family.

When Kit can't answer it yet

Use the library in a few lines of Python (from kit import font, geom, report; see Kit/docs/library.md) rather than a standalone script in a project. If the question comes back, add a command: module plus kit/commands/<group>.py with register(subparsers), a golden test against any script it replaces, a line in docs/commands.md and the cookbook. Ideas already harvested from retired scripts, by module: the workspace's .toolkit-survey/harvest/ideas-by-module.md.

Verify

PYTHONPATH=Kit .venv/bin/python -m unittest discover -s Kit/tests from the workspace root. Tests read a frozen fixture (tests/make_fixtures.py), never the live package.

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.

Check your setup, free