thierryc/glyphs-mcp/glyphs-mcp-kerning

Glyphs Kerning

Use exact typed kerning edits for setting or removing supplied glyph/group pair values. Use language proofing for bounded pairs to inspect. Keep discovery, assignments and collision repair separate; one does not authorize another.

For unknown group assignments or stored pairs, use kerning discovery. Require the matching private capability; reuse connection/document context and request only needed fields. Discovery needs no job.

Reuse the verified $glyphs connection, capabilities and intended document_id already in context; do not repeat setup for this skill. If missing, use connection setup and document targeting. Reuse the ID for reads of the same font; rediscover after document_not_found or target change, not a missing glyph. Never silently substitute another open font. Each read is fresh; check source/dirty state when preparing edits.

For stored-value inspection, follow the kerning read reference. Read exact glyph-name or established group-key pairs on dirty or unsaved fonts; no Save, job or external script is needed. Pure inspection stops after reporting the stored evidence. It does not imply a collision-repair request.

Only when collision repair is requested, verify kerning_collision in this connection’s jobKinds. If unavailable, the installation needs updating: update the bridge, sidecar and skills together; do not use an earlier private fallback. Prepare supported work with start_job, inspect get_job until ready, and review its report before apply_job. Application is a reversible live change; it does not save. Use accept_job only when the user's task authorizes saving the reviewed whole document; it closes the rollback window. Use discard_job for whole-job restoration or cancellation. For collision jobs, native Undo/Redo belongs to the left glyph's Edit-view history; it is not whole-job restoration. See the focused reference for the tested scope and sampling limits. Never save merely to satisfy preparation, and never save, export, close, or overwrite a font unless the user's task authorizes it. Do not retry an uncertain write or save as a new job; reconcile the existing job identity first.

Apply supplied pair maps through kerning_edit in bounded batches. For a numeric transformation with broader computed scope or a coordinated group reassignment, use direct native scripting under the shared route and recovery guide. Use one whole script with exact master IDs, direction and pair/group keys in params; preserve untargeted exceptions and check for collisions when renaming groups. Saved-version recovery reloads the whole font's pre-run kerning along with its other persisted contents. Read back representative and boundary pairs and review proofs. Keep kerning_collision for its analysis and suggestions; a scripted value change is not optical repair.

Prepare kind="kerning_collision" with explicit pairs and master scope. Inspect pair clearance, existing kerning and the suggested corrections in the report. Preserve existing classes and exceptions unless explicitly targeted. Review proof strings before acceptance; collision avoidance is not optical kerning. See lean kerning.

Documentation.