What is sdd-claude-kit CLAUDE.md?

Repository instructions for a framework that uses Spec-Driven Development, meaning written requirements guide implementation before code is changed. It tells Claude Code which project documents and active feature specification to read.

Use it when working on this repository to check the relevant specification, confirm dependencies and acceptance criteria, implement one task at a time, add tests, and update task status.

It reduces invented requirements and inconsistent changes by making the product rules, architecture, coding standards, and acceptance criteria the basis for implementation.

How idosreisjunior/sdd-claude-kit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to idosreisjunior/sdd-claude-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/idosreisjunior/sdd-claude-kit/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/idosreisjunior/sdd-claude-kit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/idosreisjunior/sdd-claude-kit/claude-md/github.svg)](https://agentmods.dev/instructions/idosreisjunior/sdd-claude-kit/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/idosreisjunior/sdd-claude-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/idosreisjunior/sdd-claude-kit/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/idosreisjunior/sdd-claude-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/idosreisjunior/sdd-claude-kit/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 842 This file is loaded in full into every session.

When invoked 842 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00842	$0.00842
Opus 5	$0.00421	$0.00421
Sonnet 5	$0.00168	$0.00168
Haiku 4.5	$0.00084	$0.00084

Measured 9d ago against content hash 5941a7b2610c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

sdd-claude-kit CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — SDD Claude Kit

Este repositório desenvolve o SDD Claude Kit, um framework de Spec-Driven Development para Claude Code. O projeto é construído usando o próprio método que ele propõe: a especificação vem antes do código.

Contexto obrigatório

Antes de qualquer mudança estrutural, leia:

PRD.md — fonte da verdade do produto.
.specs/project/constitution.md — regras invioláveis do projeto.
.specs/project/architecture.md — arquitetura e limites de módulos.
.specs/project/standards.md — convenções de código e documentação.
A especificação ativa em .specs/features/<id>/.

Carregue apenas o necessário para a tarefa atual (princípio 7.6 do PRD). Não leia todas as specs de uma vez.

Regras obrigatórias

Não implemente funcionalidades que não estejam no PRD ou na spec ativa.
Não invente requisitos. Se faltar informação, registre uma hipótese explícita (> HIPÓTESE:) ou uma questão pendente na spec.
Trabalhe em uma tarefa por vez.
Antes de implementar, verifique requisitos, dependências e critérios de aceite da tarefa.
Crie ou atualize testes para toda regra implementada.
Atualize o status da tarefa em tasks.md e status.yaml.
Atualize traceability.yaml (requisito → cenário → tarefa → arquivo → teste).
Execute lint, testes e build antes de concluir.
Não altere arquivos fora do escopo da tarefa sem justificar.
Ao encontrar uma decisão arquitetural não prevista, interrompa e proponha um ADR.
Não marque uma tarefa como concluída enquanto existirem falhas de validação.

Fluxo de trabalho

/sdd-kit:new → spec → clarify → design → tasks → approve → implement → verify → archive

O estado de cada mudança vive em .specs/<tipo>/<id>/status.yaml. Transições válidas estão em .specs/project/architecture.md.

Estrutura

Caminho	Conteúdo
`plugins/sdd-kit/`	O plugin Claude Code (skills, agents, hooks, scripts, templates, schemas)
`packages/cli/`	CLI opcional (Fase 5 — ainda não implementada)
`.specs/`	Especificações deste repositório
`docs/pt-BR/`, `docs/en/`	Documentação de usuário
`examples/`	Projetos de exemplo
`tests/`	Testes automatizados do framework

Read the full file on GitHub · 70 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 70 lines · 842 tokens per session scan A 5941a7b2610c

Subscribe to this mod's changes

sdd-claude-kit CLAUDE.md is an instructions file published in the GitHub repository idosreisjunior/sdd-claude-kit (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 842 tokens to every session, about $0.0042 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

sdd-claude-kit: Instructions file for Claude Code