docs: improve getting started guides and CLI documentation#231
Merged
Conversation
- update installation commands to use latest npx syntax - clarify LogicStamp’s relationship to TypeScript contracts - improve MCP getting started descriptions and navigation links - add troubleshooting tips for npx vs global CLI installs - refine .gitignore entries and context generation details
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Description
This PR improves the Getting Started and CLI documentation to make onboarding clearer and reduce common setup confusion.
What’s changed
npxsyntax.npxvs global installs in the CLI docs..gitignorerecommendations and clarified context generation details.Type of Change
Preview
None.
Checklist
Additional Notes
These changes aim to reduce friction for first-time users and clarify how the CLI fits into the workflow, especially around installation and context generation.