Work with fonts in the Shift font editor. Use for questions about the font, glyph, source, selection, or view open in the running Shift app (through its local MCP server), for reading, authoring, or compiling saved .shift documents and other font files with shift-cli, and for font concepts such as contours, components, masters, and variable fonts.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Shift is a desktop font editor. An agent can reach it in two ways; pick by where the font is.
| The font is… | Use | Read |
|---|---|---|
| Open in the running Shift app, or the user means "what I'm looking at" | The local MCP server (shift.describe, shift.execute, shift.capture) | references/mcp.md |
A saved file (.shift, UFO, Designspace, Glyphs, TTF, OTF), a batch job, or CI | shift-cli | references/cli.md |
For vocabulary and conventions shared by both, read references/fonts.md; for axes, masters, instances, and interpolation, read references/variable-fonts.md.
To change how Shift itself looks (its colors, a theme, or the user's rice), edit the theme files in its config folder; read references/themes.md.
shift-cli, or describe the change for the user to make. Never claim an edit happened through MCP.shift.describe; for the CLI, run shift-cli --help and shift-cli <command> --help. This skill describes workflows and interpretation, not every parameter.windowId from shift.sessions.list(). If a window or session disappears, list sessions again and say so; never silently switch to another font.shift.layers.render) or capture the editor (shift.capture) and inspect the image. Do not claim a shape looks right from coordinates alone.Shift serves MCP only while Settings → Agents → Allow agent connections is on, and only while the app is running. Each build (Shift, Nightly, Dev) has its own server name and port; the Agents panel shows the exact setup command. Ask the user to turn it on rather than guessing ports.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Canonical rules for writing git commits in the Shift codebase. Use whenever the user asks to commit, stage and commit, create a pull request that requires commits, or draft a commit message. Enforces Conventional Commits, release-note quality, concise subjects, and logical commit boundaries.
The English summary is being prepared. Showing the original description.
Find and remove dead code (unused files, exports, class members) using Knip as a candidate generator, then verify each candidate through AST-level analysis and interface tracing before removing anything. Use when the user asks to clean up unused code, find dead code, or reduce the codebase.
The English summary is being prepared. Showing the original description.
Update or create DOCS.md files for Shift subsystems. Use this skill whenever the user asks to update docs, refresh documentation, create a DOCS.md, write module documentation, or says "update docs for X". Also trigger after completing a large feature when Claude.md says to update docs — check if any DOCS.md in the affected subsystem needs refreshing.
The English summary is being prepared. Showing the original description.
Adversarially fact-check DOCS.md files against the actual source code, verifying every concrete claim rather than trusting structure checks. Use when the user asks to audit docs, verify documentation accuracy, check whether docs are still true, or on a scheduled documentation review. This is the semantic layer the mechanical checkers cannot cover.
The English summary is being prepared. Showing the original description.
Canonical rules for finding, creating, and updating Shift GitHub issues. Use whenever the user asks to file, create, open, update, triage, or search for an issue, or when substantial work needs an issue before a pull request. Prevents duplicates and defines acceptance criteria and pull-request closure semantics.
The English summary is being prepared. Showing the original description.
Add or revise source-level JSDoc for Shift APIs. Use this skill before writing or editing documentation comments for exported classes, methods, constructors, domain data structures, render frames, reactive state, or any API where caller intent, side effects, lifetime, ownership, or nullability are easy to misunderstand.
The English summary is being prepared. Showing the original description.