Point agent instructions at the SDK development specification - #98
Open
brionmario wants to merge 1 commit into
Open
Point agent instructions at the SDK development specification#98brionmario wants to merge 1 commit into
brionmario wants to merge 1 commit into
Conversation
Signed-off-by: Brion <info@brionmario.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Sep 11, 2026
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.
Purpose
The ThunderID SDK development specification defines the contract every SDK implements: layering, operational modes, configuration keys, client surface, error model, security floor, platform packaging, testing, and the cross-SDK parity rules. It lives in the product repository, along with the threat model behind its security floor and an agent skill that loads both and drives the work.
Nothing in this repository points at it, so a contributor or an agent working here has no way to find the contract this SDK is meant to implement. This adds that pointer to
AGENTS.md, whichCLAUDE.mdalready includes.Approach
A link, not a copy. The specification governs all four SDK repositories, so duplicating it here would give it four places to drift. The section names the three documents and says when to read them:
sdk-developmentskill, which loads both and drives the work from locating the SDK checkouts through validation to raising the linked pull requests.It closes with the rule that matters most day to day: a capability landing here usually needs to land in the sibling SDKs too, and the pull request answers that question either way.
The same section, worded identically, goes into all four SDK repositories. The links resolve once thunder-id/thunderid#5367 merges, so that PR should land first.
Related Issues
Related PRs
SDK parity
The same change is raised in every SDK repository:
Checklist
breaking changelabel added.Security checks