Sdk
The hard rules for editing `@kortix/sdk` (packages/sdk), a PUBLISHED npm package with...
Install
npx skills add kortix-ai/suna --skill sdk -g -a claude-code -y- Repository
- kortix-ai/suna20.3k
- Category
- Testing
- Updated
- 3d ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
The hard rules for editing `@kortix/sdk` (packages/sdk), a PUBLISHED npm package with constraints no other package in this repo has: TDD is mandatory for the public surface and the stream/transport behavior (failing test first, gates run and pasted every turn, explicit shippable YES/NO/NOT YET); exported names INCLUDING types are a public API contract and renaming one is a breaking change; the `version` field is inert and must never be hand-bumped; adding an export requires three synchronized edits; and a static import-graph tripwire enforces the framework-free core. Load WHENEVER you add, edit, rename, move, export, test, or delete anything under packages/sdk, or touch its streaming/transport layer.
@kortix/sdk
Read the repo-root AGENTS.md first, it covers the monorepo (worktrees, the local
stack, verification standard, release topology). This file covers only what is
specific to this package, and the traps that have no analogue elsewhere in
the repo.
Three rules before you touch anything
- Write the failing test first for every change to an exported name, a public behavior, or the stream/transport layer. RED → GREEN → REFACTOR. A test you have never seen fail is not a test. An internal refactor with no behavior change adds no test: typecheck plus the existing tests prove it. A test that pins an internal detail and goes red on such a refactor is deleted (the repo testing philosophy, 2026-10-16). The full loop is in Test-driven, always below.
- Never hand back a red suite. Loop, run, read, fix, re-run, until every test passes. Loop on the code, never on the test. Deleting, skipping, weakening, or filtering a test to reach green is forbidden. If the test itself is wrong, or it caught a pre-existing bug, stop the loop and say so.
- Run the gates and paste the output before you answer.
typecheck+test+smoke:install. Then state plainly: is this shippable to production, YES, NO, or NOT YET? Never "should work". Never "looks correct".This package is on npm. A mistake here lands in a stranger's build, not in your PR. See Test-driven, always below.
The mental model: what this SDK actually is
Learn this once and most questions answer themselves.
This SDK talks to two completely different upstreams and hides the seam.
