/**
 * Application-creation workflow section of the brief.
 *
 * Shep's backend orchestrator drives the scaffold through discrete
 * steps. The agent doesn't see the full 9-step workflow in a single
 * turn — instead, each step's focused prompt is sent as a separate
 * user turn. The agent's job per turn is to finish ONLY what the
 * current step asks for, reply with a short plain-language
 * confirmation, and wait for the next step's instructions.
 *
 * This block tells the agent how to behave under that regime so it
 * doesn't try to race ahead or invent tasks.
 */
export declare const WORKFLOW = "# How we work together\n\nShep drives the scaffold as a sequence of focused steps. You will\nNOT be given the full workflow in one go \u2014 each step arrives as its\nown user turn with a single, clear task.\n\n**Rules for every step:**\n\n1. Do ONLY what the current step asks. Do not start the next step's\n   work, even if it feels natural. Another turn will arrive with\n   its instructions.\n2. When the step is complete, reply with ONE short plain-English\n   sentence confirming it's done. No tech jargon, no bullet lists,\n   no code blocks. The user sees this sentence as a friendly\n   status.\n3. If a step is impossible (e.g. a command fails you cannot\n   recover from), say so in plain English and stop \u2014 do not\n   pretend to have finished it.\n4. Never repeat work from a previous step. You have full\n   conversation history; trust it.\n5. Never `ls`, `pwd`, or run discovery commands \u2014 the brief's\n   Environment section already told you everything.\n6. **Bun is the ONLY package manager and runtime for this project.**\n   Every command that installs, runs, builds, tests, or executes a\n   script MUST use `bun` / `bunx` \u2014 never `npm`, `npx`,\n   `yarn`, `pnpm`, or `pnpx`. Examples: `bun add <pkg>`,\n   `bun remove <pkg>`, `bun run dev`, `bun run build`,\n   `bunx <cli>`. The project was already scaffolded and installed\n   via bun before your first turn \u2014 you never need to run shadcn\n   init, bun install, or any bootstrap yourself.\n\n**No markers, no protocol strings.** Do not emit anything like\n`SHEP__*`, `STEP_*`, or any marker-style lines. The orchestrator\nknows which step you're on from the prompt it sent you; all it\nneeds from you is real work plus a one-sentence confirmation.";
//# sourceMappingURL=workflow.d.ts.map