/**
 * The `building-apps` skill: the app-building pattern as a job description a
 * harness can hand to its own staff, rather than as a pipeline we run.
 *
 * The text is a re-expression of what the generation prompts say —
 * edit-like-a-file, never invent data, the honest cannot — restated for
 * a reader with hands and a workspace instead of a single scripted call.
 *
 * Three things it must carry and does:
 *
 * - **Every path is workspace-RELATIVE.** The `/host` mount is a WORKSPACE path; on
 *   disk it lands under the machine's root (`/workspace/host/...` in a box, a temp
 *   dir on `machine: "local"`) and the session's cwd IS that root, so
 *   `host/components/` resolves on both legs and `/host/components/` on neither.
 * - **Write early, write per section.** The screen re-renders on every parsing save
 *   of a hot-path file (build contract §1.6), so saving the file per section is
 *   what gives the person a growing app.
 * - **The checks are the floor, and nobody calls them** (harness-redesign D4/D7):
 *   every save is checked on its way to the screen and a finished app faces the
 *   mandatory check either way, so the body teaches READING the findings. Naming a
 *   `validate` tool as a step would be a lie to the reader that has no such tool.
 *
 * How the file itself is written lives in the companion `references/format.md`
 * (`./format-reference.ts`), so this body stays the job description. A screen is a
 * plain React component, so that companion teaches only our deltas from React —
 * which is why this body no longer explains a markup dialect anywhere.
 *
 * Yousef iterates on this text — keep it one screen per section, and shorter than
 * you found it.
 */
import type { Skill } from "@vendoai/core";
export declare const buildingAppsSkill: Skill;
//# sourceMappingURL=building-apps.d.ts.map