考试的五个领域
代理、工具/MCP、Claude Code、提示词、上下文及其分值权重。
考试的五个领域 是 CoddyKit 上的免费 Claude Architect 课时。 这是第 2 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Claude Architect 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Claude Architect 课程共包含 4 节课。
本课时的部分内容尚未翻译,以英文显示。
Why Domains Matter
The exam splits into five weighted domains. Knowing the weights tells you where to invest your study time. This lesson maps all five and what each one tests.
The Five Domains at a Glance
Memorize the five and their weights (they total 100%): D1 27%, D2 18%, D3 20%, D4 20%, D5 15%. D1 is the heaviest; D3 and D4 tie for second. Study accordingly.
domains = {
"D1 Agent Architecture & Orchestration": 27,
"D2 Tool Design & MCP": 18,
"D3 Claude Code Config & Workflows": 20,
"D4 Prompt Engineering & Structured Output": 20,
"D5 Context Management & Reliability": 15,
}
assert sum(domains.values()) == 100D1 — Agent Architecture (27%)
D1 — Agent Architecture (27%) tests the agentic loop: check stop_reason, run tools on tool_use, resend the full history, and repeat until end_turn. Never stop by parsing for 'done'.
resp = client.messages.create(
model="claude-sonnet-4-5",
max_tokens=1024,
tools=tools,
messages=messages, # full history every turn
)
if resp.stop_reason == "tool_use":
results = run_tools(resp.content)
messages.append({"role": "user", "content": results})
# loop again until stop_reason == "end_turn"D1 — Multi-Agent & Hooks
D1 also covers multi-agent orchestration: subagents don't inherit the coordinator's history, so pass context explicitly. Plus hooks — deterministic enforcement for financial, legal, or safety stakes.
AgentDefinition(
name="refund_specialist",
description="Handles verified refund requests",
system_prompt="...full context, since history is NOT inherited...",
allowed_tools=["get_customer", "process_refund"], # least privilege
)
# Coordinator's allowedTools MUST include "Task" to delegateD2 — Tool Design & MCP (18%)
D2 — Tool Design and MCP (18%): tool descriptions drive selection, not names. Keep 4-5 tools per agent, and use tool_choice to allow, require, or force a tool call.
{
"name": "lookup_order",
"description": "Fetch an order by ID. Input: order_id like 'ORD-1234'. "
"Returns status, items, total. Returns isError if the ID "
"is unknown. Use only after the customer is verified.",
"input_schema": {"type": "object",
"properties": {"order_id": {"type": "string"}},
"required": ["order_id"]}
}D2 — MCP Primitives & Errors
D2 covers MCP's three primitives — Tools, Resources, and Prompts — plus injecting secrets via env vars (never commit tokens) and preferring structured errors that enable recovery.
{
"mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": { "GITHUB_TOKEN": "${GITHUB_TOKEN}" }
}
}
}D3 — Claude Code Config (20%)
D3 — Claude Code Config (20%): the CLAUDE.md hierarchy — user-level is personal (not shared via VCS), project-level is shared. Use @path imports and scoped .claude/rules/ to save context.
---
paths:
- "src/payments/**"
---
# Payment module rules
- Never log full card numbers.
- All refunds over $500 require a hook-enforced approval.
# (Loads only when editing files under src/payments/)D3 — Workflows & CI/CD
D3 also covers workflows: use plan mode for big or architectural changes, direct execution for quick fixes. For CI/CD, run with -p and --output-format json, and review in an isolated session.
claude -p "Review the diff for correctness bugs only" \
--output-format json \
--append-system-prompt "Report only NEW or UNFIXED issues"D4 — Prompting & Structured Output (20%)
D4 — Prompting (20%): explicit criteria beat vague guidance, and few-shot examples aid consistency. For structured output, pair tool_use with JSON Schema, marking a field required only if always set.
schema = {
"type": "object",
"properties": {
"category": {"enum": ["bug", "feature", "other"]},
"detail": {"type": "string"}, # free text for 'other'
"severity": {"type": "integer"}, # optional, may be absent
},
"required": ["category"], # only the always-present field
}D4 — Validation & Retry
D4 also tests recovery: retry-with-feedback fixes format and arithmetic errors, but not missing info. And remember — a fresh-instance review beats same-session self-review.
def retry_with_feedback(doc, bad_output, error):
return client.messages.create(
model="claude-sonnet-4-5",
max_tokens=1024,
messages=[{"role": "user", "content":
f"Document:\n{doc}\n\nYour previous output:\n{bad_output}\n"
f"\nValidation error:\n{error}\nReturn corrected JSON."}],
)D5 — Context & Reliability (15%)
D5 — Context and Reliability (15%) is small but trap-filled: progressive summarization makes numbers vague, so keep case facts verbatim. Watch lost-in-the-middle, and escalate on real triggers.
case_facts = { # kept VERBATIM, never summarized
"order_id": "ORD-1234",
"refund_amount": 540.00,
"order_date": "2026-05-02",
}
summary = summarize(long_history) # vague over time
prompt = f"CASE FACTS (authoritative):\n{case_facts}\n\nSummary:\n{summary}"Quick Check
Test your grasp of the domain weights and where one key decision lives.
Recap — The Five Domains
You've got the exam map: D1 27%, D2 18%, D3 20%, D4 20%, D5 15% (total 100%), pass at 720. Study D1 hardest, and never guess at identity or completion.
用 AI 导师学习 Python — 免费
在浏览器中编写并运行真实代码,获得全天候 AI 导师的即时帮助,并在网页或应用中继续学习。
- 课程
- 26
- 课程
- 104
常见问题解答
「考试的五个领域」课时是免费的吗?
是的 — 「考试的五个领域」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Claude Architect 课程的其余内容,请升级到 CoddyKit PRO。 Claude Architect 课程共包含 4 节课。
「考试的五个领域」这节课中我会学到什么?
代理、工具/MCP、Claude Code、提示词、上下文及其分值权重。 你通过在浏览器中直接运行的动手代码来练习 Claude Architect,全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Claude Architect 需要有经验吗?
无需任何先前经验。CoddyKit 上的 Claude Architect 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 2 节课,共 4 节。
「考试的五个领域」课时需要多长时间?
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。
我能在这节 Claude Architect 课中编写并运行代码吗?
能。每节 Claude Architect 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。
此课程中的所有课时
- 认证概览
- 考试的五个领域
- 基于场景的考试形式与评分
- 谁适合参加这项考试