Onboarding a Client
Everything else in Syntaxis assumes a project already exists. These two skills cover the step before that: a prospective client asks “can you show me?” and then “how much?”.
/mock-up show the client their system ↓client demo you present it ↓/quote price the real build ↓signed? /scaffold or /onboard, then the build loop| Command | Writes | Job |
|---|---|---|
/mock-up |
mock-up/ |
A clickable, branded demo of the client’s app on desktop, iPhone, and iPad, full of believable mock data |
/quote |
quotes/<date>-<client>/ |
An internal costing and a client-facing quote for building the real system |
Where to run them
Section titled “Where to run them”Anywhere Syntaxis is installed. For a prospect with no project yet, the simplest setup is one folder per client:
mkdir acme-pitch && cd acme-pitchnpx create-syntaxis@latestThen open the folder in your AI tool and run /mock-up. If the client signs,
the same folder can become the real project: /scaffold
merges a stack in alongside mock-up/ and quotes/ without touching them.
Both skills also work inside an existing project, for example to pitch a new module to a current client.
From signed quote to build loop
Section titled “From signed quote to build loop”The quote describes what was sold. Carry it into the project so the build plan matches it:
- Start the real project with
/scaffoldin an empty directory, or/onboardafter your own scaffold. - Put the agreed scope into
syntaxis/project-plan.mdandsyntaxis/build-plan.md— directly, or through/discovery. The quote’s phases make a good first cut of the build plan. - Point the plan’s UI/UX section at the mock-up as the visual reference.
- Run
/overview, then the normal build loop.
The mock-up is not application source. The real app is built in its own stack through the build loop; the mock-up only shows what it should look and behave like.
/mock-up or /prototype?
Section titled “/mock-up or /prototype?”They sound alike and do different jobs.
/mock-up |
/prototype |
|
|---|---|---|
| Audience | The client, before a deal | You, before building the UI |
| Output | A working demo app with flows, data, roles, and device preview | Static screens plus a theme.css of design tokens |
| Deployable | Yes, to Vercel as-is | No |
| Lifetime | Kept as a sales asset | Discarded at the first UI feature’s /complete |
| Part of the build loop | No | Yes, a pre-build step |
What to commit
Section titled “What to commit”mock-up/is your call. It is a self-contained static site; committing it keeps the demo safe and deployable from the repository. If the folder later sits inside a real app, exclude it from that app’s linter and build.quotes/holds your rates and margins./quoterecommends adding it to.gitignorebefore writing anything, because a repository is often handed to the client at the end of a project.
- Building a Mock-up — the full walkthrough.
- Pricing a Mock-up — how the numbers are built.