-
Notifications
You must be signed in to change notification settings - Fork 13
chore: update README.md #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
joshsny
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really nice - left a couple small things as take it or leave it comments :)
README.md
Outdated
|
|
||
| ## Analytics | ||
|
|
||
| Did you know you can capture PostHog analytics even for ancillary products like a command line tool? `src/utils/analytics.ts` is a great example of how to do it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ancillary is too complex a word for my brain to handle 😂
README.md
Outdated
|
|
||
| `src/lib/prompts.ts` demonstrates how to wrap a deterministic fence around a chaotic process. Every wizard session gets the same prompt, tailored to the specific files in the project. | ||
|
|
||
| These prompts are channeled using `src/utils/query.ts` to an LLM interface we host. This gives us more control: we can be certain of the model version and provider which interpret the prompts and modifies the files. This way, we can find the right tools for the job and again, apply them consistently. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The main goal of routing through the query endpoint is so that we pay on behalf of the user - it's very cheap and not needing them to paste in an api key is advantageous for creating a good flow. might be worth mentioning here!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
* Update README.md * tweak * Update README.md * Update README.md with blog link * Copy tweaks * Copy tweaks
Adding to our endless PR dependency chain, this one awaits our envoy blog post.
This pull adds some documentation to the readme to help developers get their bearings in the project. We now highlight the especially interesting code they'll want to understand to use it themselves.