CLAUDE'S ARCHITECT WORKSHOP
Early AI Dopters — community study notes

1. PUT CHECKS BEFORE ACTIONS
Enforce mandatory requirements before a tool runs. A prompt reminder alone is not a guarantee.
For Claude Code tool calls, a PreToolUse hook can block a disallowed action.

2. GIVE GUIDANCE A HOME
Put team conventions in the project's CLAUDE.md. Keep personal preferences separate.
Use path-scoped rules for instructions that apply only to particular files.

3. CHECK MORE THAN THE SHAPE
Schema compliance does not establish factual accuracy.
Verify calculations and source support. Preserve unknown values rather than inventing them.
In the demonstration: 20 + 30 + 40 = 90; the unsupported date remains unknown.

FURTHER STUDY
https://code.claude.com/docs/en/hooks
https://code.claude.com/docs/en/memory
https://platform.claude.com/docs/en/build-with-claude/structured-outputs
https://anthropic-partners.skilljar.com/claude-certified-architect-foundations-certification

Independent community study companion. These three principles do not cover the full certification curriculum.