Tesseract

View saved version →

---
name: tesseract-3d
description: Create and revise editable 3D scenes in Tesseract with cameras, lights, meshes, materials, imported Blender/glTF models and property animation inside a portable document. Use for Scene3D work with a 3D-enabled Tesseract CLI, including requests phrased in Blender terms; use tesseract-motion for 2D motion graphics.
---

# Design editable 3D scenes with Tesseract

Open the working `.tsrct` with `open_in_codex` (file target, absolute path) near the start of authoring, ideally just after creating it, so the user can follow changes live, inspect layers and the timeline, and attach a timestamp or layer selection to chat. Keep that same file open throughout revisions rather than waiting until the composition is ready for review. If the viewer cannot open, continue with rendered previews and provide the editable project file.

The CLI may send basic usage telemetry for some commands. You can provide optional attribution via `TESSERACT_SKILL=tesseract-3d` and the [other attribution variables](references/telemetry.md). Respect the CLI's telemetry opt-out setting; never enable telemetry on the user's behalf.

1. Resolve this skill's root from the directory containing this `SKILL.md`. Read [CLI installation](references/installation.md) and check the required Tesseract version once per session. Use the resolved executable path throughout the task. Scene3D requires a 3D-enabled CLI build: save `tsrct project schema` to a file and search it for `createFxScene3DLayer` (never print the whole schema). If it is absent, stop and tell the user that this CLI cannot author 3D scenes; do not substitute 2D layers or retry the actions. Read [local operation](references/local-operation.md) and [native authoring](references/native-authoring.md).
2. Read [Scene3D basics](references/scene3d-basics.md), including its [validator rules](references/scene3d-basics.md#rules-the-validator-enforces). Start from the matching [recipes](references/scene3d-recipes.md). When the user describes the work in Blender terms, use [Scene3D for Blender users](references/scene3d-blender.md) to pick the closest control and to name what has no equivalent. Establish the canvas, intended camera view, scale (`pixelsPerMeter`) and timing. For `--hdr`, an HDR delivery, `hdrGraphicsWhiteNits`, RGB above 1, or HDR stills, read [HDR](references/hdr.md); a Radiance `.hdr` environment map needs only Scene3D basics. Preserve existing identities, animation and packaged resources when revising a scene.
3. [Choose the renderer](references/scene3d-basics.md#choose-the-renderer): prefer the path tracer for realistic lighting, reflections and refraction; use raster for stylized graphics and fast layout or motion checks.
4. Build native editable items rather than a prerendered image. Look up each action's exact fields in `tsrct project schema` before writing it; do not invent property names, enum spellings or commands. Apply in small batches and stop at a rejected batch before rendering. For imported models, read the conversion diagnostics and list clips, morphs and node overrides in `poseStack` (see [imported models](references/scene3d-basics.md#imported-models)).
5. Use [filmstrip review](references/filmstrip-review.md) at feature-critical times. Animation is verified only when the sampled frames visibly differ; a stored keyframe or binding is not proof. Inspect saved JSON after structural edits and reload the document before delivery. Check representative frames with the final renderer and settings and estimate the cost before a long export. Before step 6, follow [review and delivery](references/review-and-delivery.md) and run the relevant `tsrct evaluate --checks` recipes in [Scene3D basics](references/scene3d-basics.md#run-placement-checks), fix actionable findings, and rerun them. Use `scene3d.items` only when you also need per-item measurements; it does not run checks by itself.
6. Read and follow the [critic review](references/critic-review.md): two indep

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 34 — file references are metadata, not package contents.

View saved version →

---
name: tesseract-design
description: Create and revise static visual designs as editable Tesseract compositions and rendered PNGs, including posters, social graphics, slide layouts, diagrams, and web/UI mockups. Use when the requested deliverable is a design image.
---

# Design with Tesseract

Open the working `.tsrct` with `open_in_codex` (file target, absolute path) near the start of authoring, ideally just after creating it, so the user can follow changes live, inspect layers and the timeline, and attach a timestamp or layer selection to chat. Keep that same file open throughout revisions rather than waiting until the composition is ready for review. If the viewer cannot open, continue with rendered previews and provide the editable project file.

For converting files to or from other editing tools, such as Premiere Pro or After Effects, read [conversion](references/conversion.md). When opening shared or older `.tsrct` files, updating tools, or investigating load/render differences, read [versions and compatibility](references/versions.md).

Turn the user's brief into static visual designs as editable compositions, rendered to PNG.
Render them with `tsrct preview`. Deliver the PNGs as the primary result and keep their editable `.tsrct` sources for revisions.
Match the format to the request: a poster, social graphic, slide, diagram, interface mockup, or another composition.

The CLI may send basic usage telemetry for some commands. Read [telemetry](references/telemetry.md) for collected data and opt-out; never enable telemetry on the user's behalf.

## Establish the design

Use the context already provided: the design’s purpose, audience, message or action, intended medium, copy, brand assets, visual references, and requested dimensions or variants. Inspect supplied references and assets. Ask only for missing information that materially changes the design; state reasonable assumptions for open choices and continue. For revisions, preserve the existing direction and scope.

Choose a visual direction tied to the brief and content: type hierarchy, spacing, grid, color, and imagery. Use realistic copy and supplied assets; identify placeholder content rather than inventing customer evidence or claims. Adapt composition and type to each requested format. For web/UI mockups with responsive variants, reflow content for each width instead of shrinking the desktop image.

## Author and preview

Resolve this skill's root from the directory containing this `SKILL.md`. Follow [installation](references/installation.md), check the required CLI version once per session, and use its resolved executable path throughout.

1. Follow [static authoring](references/static-authoring.md) to create or revise the design, import fonts/images, and save editable layers. Look up the fields needed in the installed schemas; never invent APIs or assume browser/CSS behavior.
2. Keep text, shapes, diagram elements, and layout geometry as native editable layers. Use images for photography, logos, and other supplied raster assets. Do not flatten the entire layout into one image. Use named groups where useful for related elements or components.
3. Render a PNG early, open it, and revise the saved composition. Review hierarchy, alignment, spacing, line breaks, clipping, image crops, contrast, and text legibility at the intended viewing size. Inspect large or detailed designs in close-up as well as at an overview scale. A successful render alone does not establish a good design.
4. Read and follow the [critic review](references/critic-review.md): two independent critics, an art director and a specialist for the design's purpose, such as a social media strategist for a social graphic, score each final PNG, and you revise between rounds until both rate every design at least 8.5/10, for at most three review rounds. Tell the user the review plan, each round's scores and feedback, and the final scores.

## Deliver designs

Render each final design or requested varia

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 11 — file references are metadata, not package contents.

View saved version →

---
name: tesseract-editor
description: Build or modify a custom browser editor for Tesseract .tsrct files. Use for editor controls, previews, and saving projects; use the motion or video skill for direct project authoring.
---

# Build a Tesseract editor

If the editor needs to import or export other tools’ project formats, such as Premiere Pro or After Effects, read [conversion](references/conversion.md). When opening shared or older `.tsrct` files, updating tools, or investigating load/render differences, read [versions and compatibility](references/versions.md).

The browser engine opens, previews, edits, and saves `.tsrct` projects locally. A static HTML application is sufficient; no backend or native CLI is required. The browser runtime does not export video.

The [browser API reference](references/browser-api.md) covers initialization, actions, playback, and saving. Examples: [general layer controls](examples/timeline-editor/README.md) and [controls for a bundled project](examples/bouncing-ball/README.md).

## Runtime and serving

Download the browser runtime from [the CDN](references/runtime.md) into a local `runtime/` directory beside `index.html`. Use both files from the specified version. No npm installation or native CLI is needed. `version()` returns the runtime release.

The editor needs HTTP serving and browser GPU/media support. Its HTML depends on the runtime files; attachment viewers may not execute WASM. CLI or skill updates do not require upgrading an existing editor’s runtime.

## Editing and saving

`actionSchema()` describes supported engine actions. UI controls, playback scheduling, and selection gestures belong to the application. Await rendering so frames do not overlap; edit groups combine continuous changes into one history entry.

`TesseractEngine.create(file)` accepts a File or Blob. `toBlob()` packages the current document with its original assets; it does not write to disk. Overwriting the source file can invalidate asset reads; the API reference describes reopening the saved Blob. Page refresh discards unsaved edits.

## Review before handoff

Read and follow the [critic review](references/critic-review.md): two independent critics, an art director and a creative-tool UX designer, score the running editor, and you revise between rounds until both rate it at least 8.5/10, for at most three review rounds. Tell the user the review plan, each round's scores and feedback, and the final score.

The art director judges the editor's own visual design (layout, hierarchy, typography, color, and control states) and whether the preview shows the document without visible defects; the opened `.tsrct` is the user's content and outside the review, so give the critics this scope. Test and capture on a copy of the project, never the user's file. Between rounds, revise the editor source, reload it, and recapture the screenshots. If a step cannot be captured, such as a permission prompt or a canvas left blank because the automated browser lacks WebGPU (confirm that `navigator.gpu` is missing or `requestAdapter()` returns null there), tell the critics so they list it under Not evaluated.

Referenced files: 20 — file references are metadata, not package contents.

View saved version →

---
name: tesseract-motion
description: Create editable motion graphics locally in Tesseract, including full-frame animated scenes, typography, diagrams, lower thirds, and overlays on supplied footage. Use for focused motion-design work; use tesseract-video for assembling or revising a complete footage edit.
---

# Design motion with Tesseract

Open the working `.tsrct` with `open_in_codex` (file target, absolute path) near the start of authoring, ideally just after creating it, so the user can follow changes live, inspect layers and the timeline, and attach a timestamp or layer selection to chat. Keep that same file open throughout revisions rather than waiting until the composition is ready for review. If the viewer cannot open, continue with rendered previews and provide the editable project file.

For converting files to or from other editing tools, such as Premiere Pro or After Effects, read [conversion](references/conversion.md). When opening shared or older `.tsrct` files, updating tools, or investigating load/render differences, read [versions and compatibility](references/versions.md).

The CLI may send basic usage telemetry for some commands. You can provide optional attribution via `TESSERACT_SKILL=tesseract-motion` and the [other attribution variables](references/telemetry.md). Respect the CLI's telemetry opt-out setting; never enable telemetry on the user's behalf.

Create a moving composition with a clear visual idea. Establish what the motion communicates, its rhythm, the destination canvas, and whether this is a full scene or an overlay that must leave footage visible.

When designing an ad opening, read [ad hooks](references/ad-hooks.md): develop a clear visual idea tied to the actual product/message, align its key arrival to confirmed opening music cues when available, and preview it together with the next scene. Sound and transitions strengthen the idea; they are not a required effects stack.

Resolve this skill's root from the directory containing this `SKILL.md`. Read [CLI installation](references/installation.md) and check the required Tesseract version once per session. Use the resolved executable path throughout the task.

1. Read [local operation](references/local-operation.md) and [native authoring](references/native-authoring.md).
2. Read [motion design](references/motion-design.md). Use the supplied brand/style references. For an overlay, inspect the actual footage at the intended placement and timing; design around the subject, text, and action.
3. Choose a useful mechanism—typography, paths, masks, precomps, a diagram, or a media treatment. Use native layers and a coordinated AnimationGraph. Existing footage and graphic assets are welcome; a single prerendered image of the design defeats editable motion.
4. Read the [capability map](references/capabilities.md) when choosing a feature or checking its limits. Look up the specific definitions needed in the action and document schemas.
   Retrieve them from `tsrct project schema` or `tsrct project schema --document`.
   [FX authoring](references/fx-authoring.md) and [motion](references/motion.md) show working wire shapes and local rendering, not mandatory designs. For subject occlusion use actual person mattes when supported, not an approximate hand-drawn silhouette. For `--hdr`, an HDR delivery, `hdrGraphicsWhiteNits`, RGB above 1 or HDR images, read [HDR](references/hdr.md).
5. When supplied or previously generated music sets the rhythm, read [waveform editing](references/waveform-editing.md): open a music waveform, listen to confirm accents and phrase changes, and map animation arrivals/reveals to the selected music events before authoring timing. Preserve the chosen track; do not mistake every peak for a beat or sync every movement mechanically. Read [sound design](references/sound-design.md) when the graphic is part of an audible video. Add a local accent or transition sound when it strengthens the movement; leave it quiet when speech or the exis

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 36 — file references are metadata, not package contents.

View saved version →

---
name: tesseract-video
description: Edit existing footage into finished videos locally with Tesseract. Make cuts, preserve dialogue, add purposeful sound design, mix audio, and decide where native motion-graphics scenes or overlays improve the story. Use for video editing and revising Tesseract projects, not avatar or video generation.
---

# Edit video with Tesseract

Open the working `.tsrct` with `open_in_codex` (file target, absolute path) near the start of authoring, ideally just after creating it, so the user can follow changes live, inspect layers and the timeline, and attach a timestamp or layer selection to chat. Keep that same file open throughout revisions rather than waiting until the composition is ready for review. If the viewer cannot open, continue with rendered previews and provide the editable project file.

For converting files to or from other editing tools, such as Premiere Pro or After Effects, read [conversion](references/conversion.md). When opening shared or older `.tsrct` files, updating tools, or investigating load/render differences, read [versions and compatibility](references/versions.md).

The CLI may send basic usage telemetry for some commands. You can provide optional attribution via `TESSERACT_SKILL=tesseract-video` and the [other attribution variables](references/telemetry.md). Respect the CLI's telemetry opt-out setting; never enable telemetry on the user's behalf.

Make a deliberate edit from the user's material. Tesseract is the local editing and rendering engine; the agent supplies editorial judgment. The output is both a playable video and its editable project.

## Start with the material

Resolve this skill's root from the directory containing this `SKILL.md`. Read [CLI installation](references/installation.md) and check the required Tesseract version once per session. Use the resolved executable path throughout the task. Scripts and references are relative to the installed skill, not a guessed home directory or development checkout.

1. Read [local operation](references/local-operation.md). Probe the supplied media, sample frames at meaningful points, and listen to its audio using the host's available media tools. Metadata does not tell you what a shot depicts. If audio cannot be auditioned, disclose that limit rather than claiming a complete review.
2. Establish the deliverable, audience, aspect ratio, duration, must-keep moments, and supplied brand assets from the request. Ask only for missing information that materially changes the edit. For a small correction, preserve the existing edit's style and scope.
3. Read [editorial decisions](references/editorial-decisions.md) before planning a new edit. For each beat decide **footage**, **footage with graphics**, or **full graphics** and why. This is not a quota: do not add motion graphics just to demonstrate the engine.

For a new ad or a revision to its opening, read [ad hooks](references/ad-hooks.md). Build a visual hook in the opening seconds from the actual footage, proposition, and evidence. Consider distinct concepts, select the strongest, and map its reveal/motion and purposeful SFX to confirmed opening music cues when music is provided. Render and inspect the hook plus its handoff into the ad before polishing the rest. Preserve the scope of unrelated revisions.

Read [waveform editing](references/waveform-editing.md) when music sets the pacing or when trimming talking footage. Generate and **open** the music waveform before planning picture timing; confirm beats, phrases, and major changes by listening and map visual arrivals to them. For speech, use overview and zoomed source waveforms to choose pause trims, protect quiet word boundaries, and retain natural breathing. Waveform markers are candidates, never automatic cut decisions.

For a substantial new video, share a concise edit plan with the source moments, their narrative purpose, graphic treatment, and audio intent. Routine authorized edits can proceed. Do not require a

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 37 — file references are metadata, not package contents.