# Source and review register

Review date: 7 September 2026
Edition: 2.0

## Scope and meaning

Official means published by the product's own organisation. Community means an independent source. Pow practice identifies an editorial workflow or original reusable prompt. These labels do not assert that software is safe, that a product is available on every account, or that an integration was tested end to end.

The review checked the new playbook, selected command behaviour, and design/Figma distinctions against primary sources. The broad command list retains the original page's coverage with source links and corrected summaries. It has not been executed against every CLI version. The directory lists integration ideas; prices, uptime and full tool chains are not certified.

## Source map

| Area | Source | Use in this guide |
| --- | --- | --- |
| Community practices | [Shan Raisshan's repository](https://github.com/shanraisshan/claude-code-best-practice) | Examples and editorial inspiration, not a product specification |
| Review snapshot | [Pinned repository revision](https://github.com/shanraisshan/claude-code-best-practice/tree/f7b4ce4de47fadeb00e59e8967e48af2b72d5684) | Stable record of the material reviewed |
| Working process | [Official best practices](https://code.claude.com/docs/en/best-practices) | Planning tradeoffs, concrete context, verification and review |
| Command behaviour | [Commands](https://code.claude.com/docs/en/commands) | Names, aliases, version gates and bundled skills |
| Startup flags | [CLI reference](https://code.claude.com/docs/en/cli-reference) | Flag scope, especially non-interactive budget limits |
| Memory | [Memory](https://code.claude.com/docs/en/memory) | Project guidance, auto memory and limits of instructions |
| Skills | [Skills](https://code.claude.com/docs/en/skills) | Reusable procedures and legacy custom commands |
| Subagents | [Subagents](https://code.claude.com/docs/en/sub-agents) | Independent contexts, task boundaries and isolation |
| Hooks | [Hooks guide](https://code.claude.com/docs/en/hooks-guide) | Configured lifecycle actions and read-only hook browser |
| Connections | [MCP](https://code.claude.com/docs/en/mcp) | External tools, configuration and trust |
| Access | [Permissions](https://code.claude.com/docs/en/permissions) | Enforced rules versus prompt guidance |
| Recovery | [Checkpointing](https://code.claude.com/docs/en/checkpointing) | Limits of restoring edits and external state |
| Usage | [Cost guide](https://code.claude.com/docs/en/costs) | Account billing, context, model choice and parallel usage |
| Design plugin | [Official marketplace listing](https://claude.com/plugins/design) | Listed tasks and installation surface |
| Frontend Design | [Official marketplace listing](https://claude.com/plugins/frontend-design) | Design guidance for frontend work |
| Figma plugin | [Official listing](https://claude.com/plugins/figma) | Publisher and integration entry point |
| Figma server | [Figma's guide](https://help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Figma-MCP-server) | Setup, capabilities and account conditions |

## Changes from the supplied page

- Added a five-step playbook, extension decision guide, troubleshooting and repository reading guide.
- Added original task-brief, reviewer and project-guide downloads.
- Restored the six missing thinking-framework downloads.
- Replaced unsupported numerical performance scores with an original evaluation worksheet.
- Removed ungrounded traffic counts, precise token-saving claims, blanket pricing badges and speculative release stories.
- Distinguished the Design marketplace plugin from the separate bundled /design command.
- Corrected /fork, /agents, /hooks, /doctor and several permission/usage descriptions.
- Replaced broad model-retirement claims with documented compatibility notes.
- Updated all learning notes, removed public-domain assumptions from prompts and bundled search locally.

## Maintenance procedure

When updating a claim, open the linked primary source and record the date, applicable product/version and exact behaviour. Distinguish an announcement from availability. Update the page, data and relevant learning notes together. Run the local source validation and production build. A source label alone is not evidence.

Do not mark the guide freshly reviewed just because styling changes. Do not restore a score, price or adoption claim without a dated method and supporting source.