Forge design systems and source formats

Brand grounding and source support

Your brand kit supplies logos, palette and typography; the brand book supplies creative context. Those inputs do not add support for a source application, install a missing font, or make an unsupported feature editable. Inspect the exact template contract before mapping values. Upload → parse → edit → preview → render → export are separate capabilities. Library acceptance, a thumbnail, a schema enum or a successful parse establishes only that stage. A preview may be a sidecar or a preflight rather than final pixels. No new customer rendering or fidelity qualification was performed for this map (checked 2026-11-09).

Source families

Source	Upload	Parse	Edit	Preview	Render	Export	Evidence boundary
After Effects	Project or collected package	Inspect parseState; missing dependencies can block	Exposed fields; supported revision layer/slot edits	Contract/revision preview and render preflight	Published template → render set	Files declared by the template outputs	Customer template rendering is documented; this mapping run starts no renders.
Photoshop / Illustrator	Accepted source files; EPS is Library intake	Source-specific import; inspect the actual result	Only the fields/layers the imported revision exposes	Library preview or supported template preview	Only after a usable template is published	Declared output files; no promise of PSD/AI round-trip	Upload is documented. Arbitrary-file fidelity and end-to-end rendering are not established by this map.
Presentations	Library intake	Inspect the source parse result	No presentation-specific action in the captured Forge surface	Companion preview when available	No general deck-render action documented here	Original download; do not infer PPTX/PDF generation	Library support does not establish an agent authoring/export workflow.
Premiere Pro	Library project storage	Not a template family in the captured source contract	No Forge project-edit action verified	Sidecar video, when supplied	No Forge project-render action verified	Original project download	A project file and a rendered movie are different resources.
HTML / HyperFrames	HTML or classified bundle	Native source; inspect family and parseState	Only the native contract’s exposed fields	Source/Library preview does not certify rendered frames	Use only the execution path exposed for that source	Only artifacts returned by that path	Does not enter `template_forge`. Browser/native rendering fidelity is not qualified by this documentation run.
Web components	ZIP with a recognized component manifest	Bundle contents decide the family	Declared component contract only	Inspect the source’s supported preview	Only an exposed template/output contract	Returned artifacts, not arbitrary source conversion	Does not enter `template_forge`. A generic ZIP is not automatically a component.
Blender / scenes	Library source; accessible scenes come from scenes	Inspect native source/scene readiness	`scene_fill` values, not unrestricted scene editing	Review filled values; this is not a pixel preview	`scene_fill` → `scene_render` for listed outputs	Scene results in Library; use scene history	Does not enter `template_forge`. No arbitrary customer-scene fidelity claim.
Figma	`forge_manage` `source_figma` with a frame or file link (up to 5 frames)	Each frame becomes a web-component template; read `forge_query` sources until parsed	The text columns `forge_query` template exposes	`render_preview` preflight for its render set	Renders as its templateKey (web: plus the asset id) with no build	Returned render outputs; no Figma round-trip	Needs a Figma connection on the brand; ask support to set one up. A file link only lists frames.
Canva	Not a local-file extension promise	Connected import is separate from file intake	No dedicated action in the captured Forge pair	Do not infer from connection availability	No general execution recipe verified here	No round-trip promise	A connection or source-family enum alone is not an executable function.
CAD / 3D model files	Library model intake; CAD has separate tools	Use the CAD capability guide for CAD resources	Not `forge_manage` template edits	Model viewer does not establish CAD rendering	Separate `cad_query` / `cad_manage` contract	Separate CAD artifacts; no manufacturing qualification implied	Adjacent interface, not a Forge render-set family. Inspect `help_describe` before use.
Fonts	Licensed font intake	Font metadata and dependency checks	A dependency, not an image/template	No standalone font preview promise	Required faces can block template rendering	Do not assume fonts can be downloaded or redistributed	Brand typography names do not prove the required font bytes are available.
Other design files	Library intake	No blanket Forge parser guarantee	No blanket template-edit guarantee	Raster/embedded/companion strategy varies by format	Only if an executable template is separately discovered	Original download; no conversion promise	Library preview strategies are not Forge renderer qualification.
Media, documents and other files	Library or mixed-file handoff	Document/media classification is not template parsing	Use the relevant Library/Canvas/video tool	Depends on media format and proxy availability	No template engine implied by storage	Original or explicitly returned artifacts	Store source identity and version IDs; refresh short-lived signed URLs as needed.

Route by returned identity

Published render template: discover templateKey, bindingId where needed, variable keys and outputs. Use sets and the render-preview/confirm sequence.
Revision source: keep assetId, variantId and revisionId distinct. Inspect its layers; save immutable revisions rather than replacing the Original. Publication requires an eligible source and appropriate role.
Native HTML, component or Blender source: follow its own exposed contract. Never send it into template_forge just because it parsed.
Scene: use the assetId, exact versionId and output IDs returned by scenes, then scene_fill and scene_render.
CAD or another adjacent tool: load that tool’s current guide. Forge identifiers, editing rules and status readers do not transfer automatically.

A ZIP’s contents decide its family. A stored original is not proof that an editable export or another application’s native project can be generated. Ask for only the outputs the discovered contract declares.

Before a render

Check fonts, field kinds, required values, text budgets, media/version references, output IDs and the saved delivery settings. Preserve any refusal. Brand-book grounding cannot override a missing dependency or renderer limitation.

Try it

“Upload our After Effects package, and tell me when it’s ready to edit.”
“Import this Figma frame as a design template.” (paste a frame link)
“Which of our templates are published and ready to render?”

What’s next

Agent quickstart

Choose a function and execute safely.

Function reference

Inspect the selected action.

Get started

AI assistant (MCP)

For developers and agents

Creative+

Organic+

Performance+

Brand and account

Resources