docs: improve English mykey template guidance#284
Open
GGzili wants to merge 1 commit into
Open
Conversation
Keep the template compact while adding the missing setup guidance from the Chinese version: session type selection, native tool protocol recommendation, apibase auto-append rules, common fields, and minimal optional integration examples. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
This is a focused follow-up to the previous PR feedback: keep the English mykey template improvement standalone and much tighter.
Changes are limited to mykey_template_en.py:
This intentionally avoids the prior broad 77→400 line expansion and does not include class renames or exception cleanup.