Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions directory/skills/raea/3d/blender.md
Original file line number Diff line number Diff line change
Expand Up @@ -202,8 +202,7 @@ import { BlenderShot } from "raea/blender/shot";
server's env. It can otherwise send prompts, code and screenshots to its author.
- `generate_3d` can cost the person a credit, and makes one object only; `raea gen` is the generation route. Ask first.

In the raea app, a workspace gives it to the feed's agents with a controller's servers field holding
`uvx mcp-for-blender` (`raea controller set PATH VALUE`).
`raea skills install --agent NAME` adds it to that agent as an MCP server (`--no-mcp` leaves it out).

## Licences

Expand Down
12 changes: 6 additions & 6 deletions directory/skills/raea/3d/prompts.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Where these texts come from: the published Blender + Claude workflows.

## What to do

1. Write the brief from the template (section 1). Write a `plan.ts` for every hero object.
1. Write the brief from the template (section 1). Write a `NAME.parts.ts` for every hero object.
2. Start the builder with the builder prompt (section 2), filled from the brief.
3. After every stage and every fix, run step R: the review sheets, then the judge prompt (section 3) in a new context
and `raea judge` on the same sheets.
Expand All @@ -29,7 +29,7 @@ Where these texts come from: the published Blender + Claude workflows.

The brief is data, in three files:
- `brief.ts` for the scene, made with `brief()` from `raea/brief`.
- A `plan.ts` for each hero object, made with `plan()`.
- A `NAME.parts.ts` for each hero object, made with `parts()`.
- For an interior, the room plan that `checkLayout` reads (`raea/room`).

Fields that have no schema yet go in `sections` as text.
Expand Down Expand Up @@ -72,12 +72,12 @@ Each generated object needs a reference picture made from this template:
> light, plain pale grey seamless background, the whole object in frame with margin, three-quarter view from slightly
> above, sharp focus, no people, no text, no brand names, no logos.

Each hero object gets a plan. Its fields are the frozen contract that `raea solid info --expect` and the judge check
Each hero object gets its parts (NAME.parts.ts). Its fields are the frozen contract that `raea solid info --expect` and the judge check
against:

```ts
import { plan } from "raea/brief";
export default plan({
import { parts } from "raea/brief";
export default parts({
concept: { what: "coin-op tumble dryer, stacked pair", style: "worn 1990s commercial", size: 1.9, seenFrom: 1.2,
material: "enamelled steel" },
parts: {
Expand All @@ -104,7 +104,7 @@ finished scene must read as the same place, the same objects and the same light.
invent in the same world. brief.ts notDoing is a hard list: add nothing on it, and nothing the brief doesn't name.

ORDER OF WORK (one stage at a time; a stage that fails its check is fixed before the next one starts)
0. Plan. Every object row in brief.ts has a route, a real size and, for each hero, a plan.ts with its part tree and
0. Plan. Every object row in brief.ts has a route, a real size and, for each hero, a NAME.parts.ts with its part tree and
connection map. If any is missing, write it first, from how the real thing is built: look up the real product.
1. Space. Block the room as boxes at real size. Place furniture with place() from raea/3d (on, against, beside,
near, apart, facing, align, clear), never typed coordinates; its `found` must be empty. Check: `raea run checks.ts`
Expand Down
4 changes: 2 additions & 2 deletions directory/skills/raea/3d/scenes.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ The brief template, the builder prompt and the judge prompt to paste are in `bev
- Printed matter.
- Motion.
- Budget: generation cents and judge rounds.
- Each hero object gets a `plan.ts` (`plan()`) with its concept (what, style, size, seenFrom, material) and parts, each
- Each hero object gets a `NAME.parts.ts` (`parts()`) with its concept (what, style, size, seenFrom, material) and parts, each
with a role, a level (primary, secondary, tertiary), a parent, a count and `near` detail. Below it, add a connection
map with one line per joint: `door <-> cabinet hinge side touches`.
- Write the plan from how the real thing is built: look up the product, the catalogue or a drawing.
Expand Down Expand Up @@ -65,7 +65,7 @@ check names a script (`bevy/blender`). It never places, lights, frames, material

### 3. Build, one stage at a time; a stage that fails its check is fixed first

0. **Plan.** Every object row has a route and a real size, and every hero has a `plan.ts`.
0. **Plan.** Every object row has a route and a real size, and every hero has a `NAME.parts.ts`.
1. **Space.** Block the room as boxes at real size. Place furniture by relations, not typed coordinates:
`place({ room, objects, rules })` from raea/3d. Rules are `on`, `against` a wall, `beside`, `near`, `apart`,
`facing`, `align` and `clear` (floor kept free in front). It returns each object's `center`, `base` and `yaw`,
Expand Down
59 changes: 32 additions & 27 deletions directory/skills/raea/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: raea
description: Make video, motion graphics, games and 3D scenes with raea, the Render Anything Engine, by writing React/TypeScript compositions with raea and rendering them on the GPU with the raea CLI (or playing games live). Use when the user names raea, or wants 3D scenes (Bevy materials, lights, physics, Gaussian splats), 3D placed into footage (matchmove), a playable game, footage cut by its words, cuts timed to a song's beat map, or foley and instruments made locally on the Mac. Also for writing or fixing 3D TSX (Camera3d, Mesh3d, lights, materials, glTF models, post effects, an ECS world), a 3D render or play that looks wrong, extending raea's Bevy SDK, rendered video, captions and motion graphics from code, and frames rendered headlessly.
metadata:
raea-tested-against: 0.1.0-rc1
raea-verbs: render play run check init cut song guide skill skills app controller workspace project spec doctor next library setup gen context brand scene splat blender
raea-verbs: render play run check init cut song guide skill skills app workspace project spec doctor next library setup gen context brand scene splat blender
---

# raea
Expand Down Expand Up @@ -72,7 +72,7 @@ Generated from the code by `tools/skills.sh gen`, so they're current. Read the o
- [reference/cli.md](reference/cli.md): every `raea` verb, its flags and where it runs (`raea help` prints the same).
- [reference/feed.md](reference/feed.md): the raea app's tools for an agent it launches, and which need its page.
- [reference/files.md](reference/files.md): a workspace's and a project's files, what lives in `~/.raea`, and each
spec's fields (brief.ts, NAME.script.ts, taste.ts, plan.ts, controllers/ID.ts).
spec's fields (brief.ts, NAME.script.ts, taste.ts, NAME.parts.ts).
- [reference/sdk.md](reference/sdk.md): what each `raea` import gives a composition.
- [reference/app.md](reference/app.md): driving the raea app's window over MCP, as a person would (HOST).
- [reference/platforms.md](reference/platforms.md): each network the app publishes to: shapes, lengths, file and
Expand All @@ -95,7 +95,7 @@ task needs.
| an app's interface (web or native) | [apps.md](apps.md) |
| generated images, video, sound or meshes | [gen.md](gen.md) |
| the export, the share copy, platform specs, posting a deliverable | [delivery.md](delivery.md) |
| working with the person in the raea app: the feed, controllers, the editor, boards | [collaborate.md](collaborate.md) |
| working with the person in the raea app: the feed, rules, the editor, boards | [collaborate.md](collaborate.md) |
| planning the work and keeping its tasks: the project's plan.org, the person's to-do list | [plan.md](plan.md) |
| checking a cut against the person's taste and rules, reading their notes on a sound, or teaching their fingerprint | [fingerprint.md](fingerprint.md) |

Expand All @@ -109,12 +109,12 @@ an explain, a story, a game or a tool has to do; `craft/verbs/` has one file per

Work lives in a workspace: a git repo under raea.root (`git config --global raea.root`; unset, `~/Studio` where
workspaces already are, else `~/Documents/raea`, or `~/raea` when iCloud keeps Documents), one per studio or client,
holding projects and controllers. In the raea app a project shows as a channel.
holding projects and the workspace's taste.ts. In the raea app a project shows as a channel.
- `raea workspace init NAME` makes one; `raea workspace adopt DIR` makes an existing folder one. `raea workspace`
shows it (`--json` for the projects and their paths).
- `raea project new NAME` adds a project: its folder with `brief.ts`, `AGENTS.md`, `compositions/`, `components/`,
`controllers/`, `assets/`, `artifacts/` and `out/`. The workspace's `shared/` has the same five folders, which any
project imports from as `@shared/components/NAME`. A project can live inline or as its own repo
`assets/`, `artifacts/` and `out/`. The workspace's `shared/` has the same folders but `out/`, which any project
imports from as `@shared/components/NAME`. A project can live inline or as its own repo
(`raea project split NAME`, `raea project join NAME`); both keep its history.
- Work in the project's folder. Footage and other media go in `assets/` (`media/` in a project made before the
layout), renders in `out/`.
Expand All @@ -124,34 +124,29 @@ holding projects and controllers. In the raea app a project shows as a channel.

- `raea context .` in the project prints everything to read first, in order: the person's taste
(`~/.raea/taste/taste.ts`; a line there beats any guide's default), the workspace's taste, the brief, the look, the
workspace's controllers, the craft floor and each of the brief's modes' guides. Read all of it. In the raea app,
craft floor and each of the brief's modes' guides. Read all of it. In the raea app,
`rules_read` lists every rule the work follows, the project's own `taste.ts` first ([collaborate.md](collaborate.md)).
- Run it once a session. If it refuses, say so in one line ("raea context failed: its message; reading the brief and
controllers directly") and read `brief.ts`, any `*.script.ts`, `~/.raea/taste/taste.ts` and `raea controller ls`
yourself. A `CONTEXT_STALE` line means `raea doctor` finds files from another version: run `raea doctor --fix`.
taste directly") and read `brief.ts`, any `*.script.ts`, `~/.raea/taste/taste.ts` and the workspace's and the
project's `taste.ts` yourself. A `CONTEXT_STALE` line means `raea doctor` finds files from another version: run `raea doctor --fix`.
- With no request in hand, `raea next` lists the two or three useful next steps from the brief, the compositions,
the renders and their checks. Offer them; never run one unasked.
- The controllers (`raea controller ls`, `raea controller get PATH`) are the workspace's settings and workflows:
delivery specs, who reviews what, the tools every agent gets. Work to them. Change one only when the person asks:
`raea controller set PATH VALUE` (each change is a commit).
- A controller is not a feed item. A feed item is one piece of work (a render, a still, a question): the person
reviews it once and a note on it is answered by its next version. A controller is a standing decision every agent
reads before it starts, so changing it changes all the work after. If the person would say it again on the next
piece ("always 9:16", "Grade checks every cut"), it belongs in a controller; if it's about this piece only, it's a
note. When the work needs such a decision from the person, put the controller in front of them with the feed's
`controller_post` (its id, the fields as group.field, a line on what you need decided) rather than asking in prose;
a controller you make with `controller_write` reaches their feed on its own. Fields are typed (toggle, choice,
number, text, list, agents, channels, workflow, servers, skills, rule; reference/files.md), so put what they'll
adjust in fields, one controller per concern. A style preference with no fields to set ("words never cover the
action") is a rule instead: `rule_add` in the app, or a line in the project's `taste.ts`.
- A `rule` field is a line every piece is held to and the check that holds it: one of raea's by name with its values,
or a `.ts` check written with `raea/check` (craft/ROUTER.md, step 7). `raea check PROJECT` runs every rule that
applies, with raea's floor and the person's taste, and says what waits for a render.
- Standing decisions are taste lines: the person's taste, the workspace's `taste.ts` and the project's `taste.ts` hold
what holds for every piece (the delivery spec, the loudness, "always 9:16", "words never cover the action"). A line
says it in words and, when something can hold it, names its check: one of raea's forms or checks by name with its
values, or a `.ts` check written with `raea/check` (craft/ROUTER.md, step 7). Work to them. Add or change one only
when the person says so: `rule_add` in the app, or a line in the project's (or workspace's) `taste.ts`.
`raea check PROJECT` runs every line that applies, with raea's floor, and says what waits for a render.
- A taste line is not a note. A feed item is one piece of work (a render, a still, a question): the person reviews it
once and a note on it is answered by its next version. If the person would say it again on the next piece, it's a
taste line; if it's about this piece only, it's a note. When the work needs a decision from the person, ask it in
the chat with your best guess (or `feed_propose` what you'd make), rather than burying it in a long reply.
- If the brief isn't shaped (no `believe`, no `mode`), shape it before making anything: ask who it's for and the one
thing they should believe, or write your best guess and add its field to the brief's `assumed` list.
- For a pitch, an explain or a story, plan first: write the deliverable's storyboard as `NAME.script.ts` beside the
brief (`export default script({...})` from "raea/brief": scenes of beats, what's on screen and what each scene must
land; its fields are in reference/files.md), name it on the deliverable, and add a task "storyboard approved" tagged `gate`. `raea spec NAME.script.ts`
land; its fields are in reference/files.md), name it on the deliverable, and add its task to plan.org with the
storyboard's feed item on it once posted ([plan.md](plan.md)): their approval closes it. `raea spec NAME.script.ts`
checks it. Render nothing until the person approves it (PERSON).
- Show a plan as what it will be, in this order: previz (a rough, fast raea render of the blocking, timing and
camera: grey shapes, placeholder type, no polish; it is the plan, not the piece, so the gate allows it), else a
Expand Down Expand Up @@ -270,6 +265,16 @@ least sure of. Once they've answered, `--tally` makes the answers evidence.
next tool call and keeps your turn from ending until you have it (where there is no hook, follow the file with
`tail -n0 -F FILE` or your harness's monitor). Answer each: it may change what you're doing. Without the app,
`raea show` opens the file in the Mac's own viewer and says so; take the person's notes as text then.
- When one picture holds several things (a contact sheet, a side by side, a before and after, a grid of props or
characters), label each instead of naming them by position in the title or your message. A label is a tag of a few
words that stands beside the picture, never on it, and points at its place when the person's pointer is on it; give
it a paragraph only where a tag isn't enough. In the app, `feed_post` takes `labels`: each `{ text, detail?, box:
[x0, y0, x1, y1] }` or `point: [x, y]` in the picture's own 0-1, with `frame` for a storyboard's still, `t` (and
`to`) for a film's seconds, or `part` for a scene's part. Outside it: `raea show sheet.png --label "0,0,.5,1 v1, hook
first" --label ".5,0,1,1 v2, product first" --detail "Opens on the product for two seconds, then the hook."` (each
`--label` is the place, then its tag; a `--detail` is the paragraph of the `--label` before it). A sheet `raea media
sheet` made comes labelled with each cell's time or file; to say more, edit the tags and paragraphs in its
`OUT.labels.json` before you show it.
- When you need the person to choose or fill something in (pick an opening, rank cuts, set a price), post an artifact:
a React `.tsx` of your own, `feed_post` with `type: "artifact"`, the file, and an `ask` line. The app builds it and
runs it sandboxed in the feed. Its default export is the component. It imports `react`, `@raea/app` and its own
Expand Down Expand Up @@ -333,7 +338,7 @@ least sure of. Once they've answered, `--tally` makes the answers evidence.
- A render is a standard MP4 but large: H.264 High and AAC on a Mac (VideoToolbox), H.264 Constrained Baseline and
Opus on Windows and Linux (openh264), yuv420p on all. Hand over a share copy too, which any player takes:
`ffmpeg -i film.mp4 -c:v libx264 -preset slow -crf 23 -maxrate 2600k -bufsize 5200k -pix_fmt yuv420p -c:a aac -b:a 128k -movflags +faststart film-share.mp4`.
- Deliver to the controllers' specs (sizes, platforms, loudness) when the workspace sets them; each network's shapes,
- Deliver to the taste's specs (sizes, platforms, loudness) when the workspace or project sets them; each network's shapes,
lengths and UI zones are in [reference/platforms.md](reference/platforms.md), and [delivery.md](delivery.md) routes
the rest (one composition per shape, cutdowns, tags, handing over).

Expand Down
Loading