formae-author

name

formae-author

description

Use when the user wants to start authoring formae infrastructure or deploy something NEW with formae — e.g. 'I want to deploy X with formae', 'build a k8s app with formae', 'set up infrastructure for Y', 'create a new forma file for my service', 'write formae IaC for Z'. The front door that triages where the work happens, sets up plugin schema deps, and dispatches to focused authoring skills. NOT for applying an existing forma file (use formae-apply) or operating existing infra.

formae-author — Authoring Front Door

This skill is a thin dispatcher. It triages the user's authoring intent, locates (or creates) the code workspace, infers the right schema plugins, and hands off to the focused skills that carry the deep procedures. Do not duplicate those procedures here.

Step 1 — Locate the code

Determine where the authoring will happen. Three branches:

(a) Already in a formae project — if the current working directory or any ancestor contains a PklProject that declares a @formae/ dependency, OR a .pkl file that starts with extends "@formae/forma.pkl" (or the legacy amends "@formae/forma.pkl"), work in place. Confirm the project root to the user and continue to Step 2.

(b) User knows a path — if there is no formae project here, ask: "Do you have an existing formae project elsewhere?" If the user provides a path, verify it is a real formae project (same checks as above). If it is, cd there and continue to Step 2. If it is not a formae project, say so and ask whether to create a new project there instead (offer Step 1c).

If the user is unsure whether a project exists, offer to scan ~/dev for PklProject files that declare a formae dependency. Present only verified hits from that scan — never invent or guess paths.

(c) No project exists — hand off to the skill. That skill handles directory selection, collision safety, running , and scaffolding. Return here after init completes.