Repository navigation
docs: add llms.txt and Markdown agent guide - #9
Merged
Merged
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.
Summary
llms.txtlinking to the developer guide, examples, exact YAML contracts, and CCE docsindex.mddescribedbydiscovery links,robots.txt, and a sitemapexamples/public-repo.ymland a worked AWS Samples result with verified JSON, field explanations, and IAM/runtime boundariesWhy
Agents can navigate through a concise index and inspect authoritative YAML without parsing HTML. Developers can try a pinned public repository and understand what the resulting evidence means before adding CCE to their own code.
Validation
npx --yes html-validate docs/index.htmlgit diff --checkNew Pages and example-file URLs will be verified after deployment.