Add a Claude Skill to reference the Gateway API specification. #125
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
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.
I cloned down the GitHub repo containing the Gateway API spec and documentation, and then I build the spec from the CRD definitions, then I concatenated all of the markdown file and reformatted them. They all reside in the
reference.mdfile within this new Claude Skill.This should give Claude a knowledge base to reference when asked about the Gateway API specification. It will be able to pull these documents into its context window when it needs to, kind of like RAG but without vectorization, and directly into Context (i.e. this is Context Engineering 😉 )