From the blog
Open Specification · Apache 2.0
SCS gives Claude Code the context it needs to work with your system instead of against it. Structured, versioned, git-native. Set up in 15 minutes.
See it in action
Point it at a PRD or existing project. SCS Vibe scans what's there, asks a few questions, and generates structured context Claude uses every session.
Install scs-vibe →Transform your existing PRDs, architecture docs, and compliance checklists into structured context so Claude gets the full picture before writing a line of code.
Install scs-team →The problem
Every session starts fresh. Claude improvises from training data — not your patterns, your constraints, or your team's decisions. The result:
SCS treats context as a first-class artifact — structured, versioned, and git-native, the same way your code is.
Why it works with Claude Code
SCS outputs exactly what Claude Code reads: CLAUDE.md and .claude/rules/. No middleware, no new toolchain.
| Without SCS | With SCS |
|---|---|
| Context lives in ad-hoc prompts and scattered notes | Context is a versioned YAML artifact in your repo |
| Each session starts from scratch | Claude loads structured context from CLAUDE.md every session |
| Team members give Claude different instructions | Context is shared, reviewable, and consistent across the team |
| No audit trail for what Claude was told | Git history shows every context change and who made it |
For regulated industries
Governance frameworks like CHAI, HIPAA, and SOC2 are written for human readers. AI systems run on structured data and explicit constraints. Nothing connects the two — until now. SCS includes a dedicated standards bundle type so that governance requirements travel directly from the standards body to the AI agent, intact and versioned.
CHAI T&E Framework
15 requirements across fairness, accuracy, scope, and transparency — transposed into a machine-readable reference bundle.
Read the article →Prior authorization AI
What changes when your coding agent has the compliance framework in its context before writing a line of criteria-matching logic.
Read the article →HIPAA · NIST · SOC2
Standards bundles are composable. A prior auth agent can load CHAI, HIPAA, NIST cybersecurity controls, and internal policy as a single unified governance stack.
See the spec →Reference implementation
The CHAI standards bundle is open source in the SCS repository — a working example of what a governance standard looks like when an AI agent can actually use it.
View on GitHub →If you represent a standards organization interested in publishing your framework in SCS format, get in touch.
From the blog
Documentation
If SCS is solving a real problem for you, star the repo — it helps other developers find it.
