Feature Comparison
| Artifact | Where to store it | Update trigger |
|---|---|---|
| CLAUDE.md or AGENTS.md | Repo root or package root | Commands, architecture, or workflow rules change |
| Hooks settings JSON | .claude/settings.json or team setup docs | Lifecycle automation or permissions change |
| Custom commands | .claude/commands/*.md | Repeated prompt workflow changes |
| Subagent briefs | docs/ai/subagents.md or issue templates | Roles, handoff format, or review process changes |
| MCP config | mcp.json, setup docs, or local config notes | Server command, token scope, or tool ownership changes |
Artifact Register Template
A lightweight register keeps reusable Claude Code outputs discoverable. Add one row whenever a generated file becomes part of the team workflow.
| Artifact | Path | Owner | Validation | Review cadence | | --- | --- | --- | --- | --- | | hooks settings | .claude/settings.json | DevEx | npm run lint | monthly | | code-review command | .claude/commands/code-review.md | Platform | manual dry run | quarterly |
What Counts As An Artifact
An artifact is any output that should outlive one Claude Code session. That includes configuration, markdown commands, generated docs, migration plans, review reports, MCP setup notes, and subagent task briefs.
Promotion Workflow
Do not commit every generated output. Promote an artifact only when it saves repeated work, has an owner, and can be validated.
- Draft in chat or a temporary file.
- Move stable instructions into CLAUDE.md, AGENTS.md, commands, hooks, or docs.
- Add validation notes and the reason the artifact exists.
- Review stale artifacts when commands or dependencies change.
Related Generators
Use generators for repeatable artifact formats, then review the output before sharing it with a team.
FAQ
Are Claude Code artifacts only files?
No. They can be generated files, review reports, reusable prompts, setup notes, or structured outputs that a team wants to keep.
Should every artifact be committed?
No. Commit shared, non-secret artifacts. Keep private notes, credentials, and local-only config out of the repo.
How do artifacts relate to hooks and subagents?
Hooks, command files, and subagent briefs are artifacts when they become reusable project assets.
What is the easiest first artifact?
Start with CLAUDE.md or AGENTS.md, then add hooks and custom commands only when the workflow repeats.