Conversation
Alternative shape for the section, on its own branch for comparison. Instead of seven click-through steps, the main path is: get a project, hand Kai the whole pipeline in one prompt, then take the result apart. Verified live in project 264 (2026-09-02): the single prompt produced the HTTP source with four rows and a skip-lines processor, a Snowflake join, a two-phase flow scheduled 06:00 UTC, and a working map app — 14 minutes, 11 approvals, octopus_atlas at exactly 10,000 rows with display_name / depth_zone / basin. Kai wrote real app code (package.json, frontend, npm install, typecheck, commit to the app branch) rather than filling a template. - New: /getting-started/one-prompt/ — the prompt, the approval flow, and the one thing Kai cannot do (the Google consent screen). - New: /getting-started/what-kai-built/ — every artifact opened, the number that proves each worked, and the four concepts behind them. - Overview reframed: one prompt first, mechanics second; the existing step-by-step pages stay as "or build it by hand". The seven-step arc is untouched — this branch only adds the fast path in front of it, so both can be compared on preview. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Before you start no longer references step 4 / step 5 or the Kai tabs, neither of which exist on this path; SQL is now listed as not required, since Kai writes it. - The one-prompt page pointed at the Google Sheets *source* instead of the destination. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The build-note blocks rendered as visible body text — {/* */} is MDX
syntax and these pages are plain .md.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The live run used an [ONEPROMPT] prefix to avoid colliding with the arc's objects, so the flow screenshot disagreed with the prompt the page tells you to paste. Renamed the run's objects to plain names (Octopus sightings / Octopus atlas / Octopus pipeline), reshot the flow, and dropped the [TUTORIAL] prefix from the prompt and prose so all three agree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Collaborator
Author
|
Superseded by #1116, which rebuilds Getting Started on the Boolabean sample and puts every task page on the Prompt / UI / CLI tabs. It rewrites or deletes all 19 files this branch added under Closing to keep the queue honest rather than because the work was wrong — the arc, the side-trip filing and the one-prompt experiment all fed the rebuild. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft, for comparison only — an alternative shape for the section, stacked on #1071 so the diff shows only the change in approach.
The idea
Instead of seven click-through steps, the main path becomes: get a project → hand Kai the whole pipeline in one prompt → take the result apart. The point is to show that Kai handles a large, multi-part task, not just a single step.
It actually works — verified live
One prompt in demo project 264 on 2026-09-02, transcript kept:
skip-linesprocessor (Kai read the CSV headers first)octopus_atlasat exactly 10,000 rows, columnsscientific_name,display_name,depth_zone,basin[ONEPROMPT] Octopus pipeline, two phases, scheduled At 06:00 AM, every day (UTC) — and Kai named the phases after what they do[ONEPROMPT] Octopus map— real code, not a template: it editedpackage.json, wrote the frontend, rannpm install, type-checked, committed to the app's git branch, waited for the container, then showed the previewThe row count is the proof the joins were right: 10,000 in, 10,000 out.
Pages
/getting-started/one-prompt/— the prompt, what Kai does with it in order, what it asks you to approve, and the one thing it cannot do (the Google consent screen is in your own account)./getting-started/what-kai-built/— opens every artifact, gives the number that proves each one worked, and names the four concepts (data source connector, transformation, flow, data app). This is where the learning happens./getting-started/— one prompt first, mechanics second. The seven-step pages stay, demoted to "or build it by hand".What is deliberately unresolved
Compare the two shapes on preview and tell me which front door the section should have.
🤖 Generated with Claude Code