GlyphfieldDocs
Documentation/System reference

Skills overview

Install the five Glyphfield Agent Skills and pick the one that fits a task, from Design Lab composition and HTTP generation to export checks and brand setup.

Maintained with source

Glyphfield ships five Agent Skills in the repository's skills/ directory. An Agent Skill is a folder of instructions that a coding agent loads only when a matching task comes up. Each Glyphfield skill covers one part of the agent contract.

Glyphfield Design Lab with a live shader, authored layers, and output controls
Create and Studio skillsCompose · inspect · keep source
Glyphfield Animation workspace with timing and output controls
Export skillStills · motion · audio checks

Included skills

SkillUse it forScope
$glyphfield-createLayered Design Lab compositions, saved designs, shaders, text, effects, marks, images and stickersCreates or revises editable composition state
$glyphfield-apiCatalog discovery, SVG and JSON generation, batches and Design Lab sequence documentsUses the versioned HTTP contract without an open project
$glyphfield-studioLive browser projects, accessible controls, exact source edits, local files, Canvas, WebGL and LottieOperates window.glyphfield.studio and the browser renderer
$glyphfield-exportSVG, PNG, JPG, GIF, MP4, PDF, JSON and .lottie files, loop and audio checks, and export problemsChecks the actual file instead of the action result
$glyphfield-brandSetting up or improving a brand identity from its own sources, the health audit and the brand kitApplies validated identity source and files through the Brand identity Browser API

Install

Each folder is self-contained. SKILL.md is the entry point, agents/openai.yaml holds client metadata, and references/ holds detail that the skill loads when a task needs it.

For Codex, copy or link the packages you want into $CODEX_HOME/skills, or into ~/.codex/skills when CODEX_HOME is unset. Other clients that support Agent Skills install the same folders through their own local-skill mechanism.

Contributors working in the repository do not need a second copy, because the root AGENTS.md routes work to the checked-in packages. An installed copy makes automatic discovery and explicit $skill-name calls work outside this checkout.

skills/
├── glyphfield-create/
│   ├── SKILL.md
│   ├── agents/openai.yaml
│   └── references/design-lab.md
├── glyphfield-api/
├── glyphfield-studio/
├── glyphfield-export/
└── glyphfield-brand/

Skill selection

Use the skill whose description matches the immediate outcome:

  • “Build a poster with two text layers and Gem Smoke” → $glyphfield-create.
  • “Generate 40 slide SVGs from JSON” → $glyphfield-api.
  • “Update the open General Translation project without losing its layers” → $glyphfield-studio.
  • “Download a seamless GIF and confirm the text does not flash” → $glyphfield-export.
  • “Set up our brand from acme.com and this repository” → $glyphfield-brand.

Do not load every skill by default. Add another skill only when the workflow reaches its scope.

Skill combinations

The skills hand work to one another and keep separate responsibilities.

OutcomeSequence
SVG batch$glyphfield-api → check each returned SVG
Revision of an existing Design Lab design$glyphfield-create → $glyphfield-studio for inspection in the browser
Shader video from a generated document$glyphfield-api → $glyphfield-studio → $glyphfield-export
Export of an existing animation$glyphfield-studio → $glyphfield-export
New brand and its first social images$glyphfield-brand → $glyphfield-export
Read live contracts

Catalog IDs, enum values, accessible labels and tool counts come from the running Glyphfield instance.

Round-trip source

Agents keep unknown fields, stable IDs, assets, pages, layer order and the current schema versions.

Use the owning renderer

Canvas, WebGL, local files, fonts and codecs stay on the Studio's browser renderer.

Check the result

Agents read the source again, inspect the visuals, and check bytes, MIME type, dimensions, frames, loops and audio.

Continue with Choose an agent interface, Agent recipes or the Studio Browser API.

On this page