Repository navigation
Conversation
After the routing question's Just build it, ask what it is, who it's for, how it should feel and for real details in one call, each skippable in the choice UI, then build. Supplied details are used verbatim and the rest is never invented. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Staging Workspace Sync SuccessfulSuccessfully synced changes to staging workspace Sync Details |
It only pointed back to index.md, which every session reads first. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lucaslyl
marked this pull request as ready for review
October 9, 2026 03:33
richardhjtan
reviewed
Oct 9, 2026
richardhjtan
left a comment
richardhjtan
left a comment
Contributor
There was a problem hiding this comment.
[Claude Code 🤖] One blocking finding, inline.
The rule read as covering every value in the build, which clashed with the design-playbook's realistic sample data. It now covers the user's own business name, address, staff names, rating, reviews, founding year, awards and prices, and says sample records still look real, as domain-interview does. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lucaslyl
added a commit
that referenced
this pull request
Oct 9, 2026
The section now carries #196's exact text: the one call of four questions and the never-invent rule scoped to the user's own business, with sample records still realistic. This branch keeps its extras around it: the page-colour hint, the Look check and Never invent proof links, and the research and page-or-app steps after the call. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
richardhjtan
approved these changes
Oct 9, 2026
lucaslyl
added a commit
that referenced
this pull request
Oct 12, 2026
…s final wording Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Linear: ECO-599
Why
On main, picking Just build it at the routing question goes straight to the build, so a vague prompt ("build me a landing page") is built on a guess about what it is, who it's for and how it should feel. A test build on main skills confirmed it asks nothing after the routing question.
What changes
index.md: after Just build it, one call of up to four questions, then build. What are you making (up to three readings, most likely first), who's it for, how should it feel, and real details. Every one is skippable in the choice UI, and a question the prompt already answers is skipped. Supplied details are used verbatim; nothing is invented.Split out of #151, where this already runs. Its research step and its page-or-app step stay there: they depend on files not on main yet.
Tested
Not yet on this branch. In #151 sessions (clothes shop, crypto tracker), Just build it was followed by this call and then the build.
🤖 Generated with Claude Code