docs: add effective-practices supplemental documentation #7324
Conversation
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
aBurmeseDev
approved these changes
Sep 8, 2025
trivikr
reviewed
Sep 8, 2025
trivikr
reviewed
Sep 8, 2025
Co-authored-by: Trivikram Kamat <[email protected]>
Co-authored-by: Trivikram Kamat <[email protected]>
Co-authored-by: Trivikram Kamat <[email protected]>
Co-authored-by: Trivikram Kamat <[email protected]>
Co-authored-by: Trivikram Kamat <[email protected]>
trivikr
approved these changes
Sep 8, 2025
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
Issue
Internal JS-6099
Description
Adds a documentation page in supplemental docs that presents a set of effective practices.
Although written directly for SDK users by SDK maintainers, the contents can also be loaded into an LLM context to use for evaluating code.