Repository navigation
docs(site): replace pre-1.0 copy with the shipped CLI surface - #56
Merged
Merged
Conversation
"How Architect Builds Context" still described the skill-installer product, ending on "a clear blueprint your agent can follow" - the 1.0 output is a violation report with an exit code. That section is now the real command surface: check, init and verify, each with the flags the published build actually accepts, verified against `--help`. verify was missing from the page entirely even though half the demo video is a regression failing it. It now has a card, and the /architect-refactor card names the gate it really runs after every phase, `architect verify . --phase N --strict`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015e3bqn8QmG1H2fgHL15RoH
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Levironexe
added a commit
that referenced
this pull request
Oct 23, 2026
docs(site): replace pre-1.0 copy with the shipped CLI surface
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
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.
What was outdated
"How Architect Builds Context" was written for the pre-1.0 skill-installer product. Its payoff box read "A clear blueprint your agent can follow", but what 1.0 hands you is a violation report and an exit code.
verifydid not appear anywhere on the page, even though the second half of the demo video is a regression failing it.What it says now
That section is now Three commands, one card each for
check,initandverify, with the flags the published build actually accepts. Every claim was checked againstarchitect <cmd> --helpon the built CLI:architect check .--json--list-rules--ignore <rules>--baselinearchitect init .--skill <id>--updatearchitect verify . --strict--phase <n>--jsonThe
/architect-refactorcard now names the gate the shipped template really runs after every phase,architect verify . --phase N --strict, and says it stops on a failure.Also verified, left alone
The capability table and the three slash-command descriptions were checked against the shipped templates and the CLI and are accurate:
initrenders 14 template tokens into the installed skills, the blueprint carriespatternsand 10fix:strings, and.gitignoreis respected by the file walker.🤖 Generated with Claude Code
https://claude.ai/code/session_015e3bqn8QmG1H2fgHL15RoH