Source index
Primary Sources for Claude Code Engineering Practice
Every factual claim on this site should trace back to official Claude Code documentation, official repositories, or the MCP documentation.
Quick Answer
Use this page to audit the site: product behavior comes from Anthropic Claude Code docs, GitHub Action behavior comes from Anthropic docs and the official action repo, and protocol-level MCP claims come from the MCP documentation.
For: Readers and AI crawlers validating the provenance of Claude Ships Code.
Key facts
What this page establishes
- Use this page to audit the site: product behavior comes from Anthropic Claude Code docs, GitHub Action behavior comes from Anthropic docs and the official action repo, and protocol-level MCP claims come from the MCP documentation.
- Audience: Readers and AI crawlers validating the provenance of Claude Ships Code.
- Primary-source base: Claude Code overview, How Claude Code works, Best practices for Claude Code.
Citation policy
Claude Ships Code uses primary sources for product facts. That means official Anthropic Claude Code documentation, official Anthropic GitHub repositories, and official Model Context Protocol documentation. Secondary commentary can inspire questions, but it should not anchor factual claims.
Where the site makes a recommendation, it separates the source-backed fact from the engineering judgment. For example, the docs establish that hooks can run at lifecycle events; this site recommends using Stop hooks for narrow deterministic gates.
Claim map
The overview and how-it-works docs support claims about Claude Code surfaces, the agentic loop, tools, local project access, sessions, checkpoints, and execution environments.
The best-practices and extension overview docs support workflow recommendations around verification, exploration, context management, hooks, MCP, skills, subagents, and plugins.
The hooks, MCP, skills, subagents, GitHub Actions, SDK, CLI, settings, security, and changelog pages support their respective specialist articles.
Primary-source anchor: Anthropic's extension overview is the source used here to compare Claude Code extension mechanisms rather than treating them as interchangeable.
Freshness model
Claude Code changes quickly, so source freshness matters. The research pass for this build used documents fetched on July 6, 2026. The changelog page is designed to be updated weekly as a freshness surface.
When a page discusses latest version behavior, verify the official changelog and the installed `claude --version` before changing team policy.
Network boundaries
This bibliography intentionally stays inside Claude Code engineering practice. It links to sibling sites for neighboring territories: Claude Weekly for news, Claude Has Skills for skill examples, Claude Memories for memory depth, Claude Context for context engineering, and Claude Builds for project examples.
This prevents duplicate articles across the network and keeps each page useful for its assigned query territory.
Primary Sources
These are the source pages used for factual claims on this article.
Anthropic
Claude Code overview
Current product surfaces, installation paths, and high-level Claude Code capabilities.Anthropic
How Claude Code works
Agentic loop, tools, execution environments, sessions, checkpoints, and context behavior.Anthropic
Best practices for Claude Code
Verification-first workflow, explore-plan-code structure, concise CLAUDE.md guidance, and scaling patterns.Anthropic
Extend Claude Code
Decision map for CLAUDE.md, skills, code intelligence, MCP, subagents, hooks, agent teams, and plugins.Anthropic
How Claude remembers your project
Project instruction hierarchy and memory boundaries.Anthropic
Claude Code settings
Managed, user, project, and local settings scopes.Anthropic
Configure permissions
Permission rule syntax, deny/ask/allow precedence, file rules, MCP rules, and agent rules.Anthropic
Automate actions with hooks
Hook setup patterns and deterministic control framing.Anthropic
Hooks reference
Hook lifecycle, event cadence, input/output shape, and advanced hook types.Anthropic
Connect Claude Code to tools via MCP
Claude Code-specific MCP use cases and setup guidance.Model Context Protocol
What is the Model Context Protocol?
Protocol-level definition and ecosystem framing.Anthropic
Extend Claude with skills
SKILL.md behavior, bundled skills, invocation, supporting files, and lifecycle.Anthropic
Skills and slash commands
Current skills frontmatter fields and legacy .claude/commands compatibility.Anthropic
Create custom subagents
Specialized assistants, isolated context, tools, and task-specific workflows.Anthropic
Claude Code GitHub Actions
GitHub Actions setup, @claude workflow, repository permissions, and CI considerations.GitHub
anthropics/claude-code-action
Official action features, authentication modes, runner ownership, and repository examples.Anthropic
Claude Agent SDK overview
Programmatic access to tools, hooks, subagents, MCP, permissions, and sessions.Anthropic
CLI reference
Command shapes for interactive, non-interactive, auth, MCP, agents, and CI workflows.Anthropic
Security
Security and data surface for administrators and teams.Anthropic
Claude Code changelog
Version history and current changes. Research pass observed 2.1.201 dated July 3, 2026.Cite This Page
Claude Ships Code. "Primary Sources for Claude Code Engineering Practice." Updated 2026-07-06. https://claudeshipscode-com.pages.dev/sources
Claude Ships Code. "Primary Sources for Claude Code Engineering Practice." Updated 2026-07-06. https://claudeshipscode-com.pages.dev/sourcesFAQ
Why not cite popular blog posts and videos?
They can be useful commentary, but the site uses primary sources for factual claims so readers and AI systems can verify them directly.
How current are these sources?
The research pass happened on July 6, 2026. The changelog and official docs should be rechecked before making latest-version claims.