fix(docs): add Claude Code section back to GitBook navigation#137
Closed
mHaines9219 wants to merge 6 commits intomainfrom
Closed
fix(docs): add Claude Code section back to GitBook navigation#137mHaines9219 wants to merge 6 commits intomainfrom
mHaines9219 wants to merge 6 commits intomainfrom
Conversation
- Fix wrong file path in Ch 1: packages/contracts/ClownBeatdown.sol → packages/contracts/src/ClownBeatdown.sol - Add note explaining unused _clownStamina constructor param in Ch 1 - Fix stale "shakes" comment in Ch 3 final contract (no shake mechanic) - Fix CLI .env: add both CHAIN_ID (broadcast path) and VITE_CHAIN_ID (chain selection) to match actual seismic-starter - Add example ABI JSON structure in frontend Ch 2 showing address/chainId fields and where to find the deployed address
sforge does not have a --no-commit flag (it doesn't commit by default). The command should be just `sforge init`. Verified by running the tutorial end-to-end.
Walked through the Clown Beatdown tutorial start to finish and fixed all errors that would block a developer: - Add --force flag to sforge init (directory already exists in monorepo) - Replace mv -t with mv src/ (macOS doesn't support GNU -t flag) - Add missing bun add -d @vitejs/plugin-react-swc install step - Fix Config import to use type keyword (breaks Vite production build) - Fix ShieldedPublicClient/ShieldedWalletClient to type imports - Add missing supporting files: store, theme, pages, ExplorerToast, useToastNotifications, stylesheets
Additional fixes found during end-to-end testing: - Bump seismic-viem from 1.0.9 to 1.1.1 in CLI package.json (1.0.9 doesn't export sanvil/seismicTestnet chain configs) - Split deploy script: constructor-only deploy via sforge script, then add secrets via scast send (sforge script --broadcast crashes when broadcasting shielded writes like addSecret) - Add hexToString decoding to CLI rob() method so secrets display as readable strings instead of raw hex
sforge init works fine in an empty directory created by mkdir -p. The --force was only needed due to a testing mistake (running git init before sforge init). The tutorial flow doesn't require it.
The claude-code/ pages existed but were missing from SUMMARY.md, so they didn't appear on the documentation website.
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.
Summary
claude-code/directory (overview, workflow skills, 5 CLAUDE.md templates) already existed in GitBook but was missing fromSUMMARY.md, so the pages didn't appear on the docs website## Claude Codesection toSUMMARY.mdbetween Clients and NetworksTest plan