anthropics/claude-cookbooks
Logical Components
An overview of source code logical components.

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 19 components.

claude_agent_sdk10050 LOC (19%) 32 files
managed_agents9594 LOC (18%) 43 files
tool_use8490 LOC (16%) 23 files
misc7506 LOC (14%) 13 files
capabilities3822 LOC (7%) 33 files
patterns3141 LOC (6%) 6 files
skills1780 LOC (3%) 8 files
ROOT1212 LOC (2%) 5 files
coding1175 LOC (2%) 1 file
evals926 LOC (1%) 3 files
extended_thinking862 LOC (1%) 1 file
scripts748 LOC (1%) 4 files
fable_5_fallback_billing563 LOC (1%) 1 file
multimodal508 LOC (<1%) 1 file
.github414 LOC (<1%) 5 files
.claude346 LOC (<1%) 1 file
finetuning258 LOC (<1%) 1 file
tool_evaluation34 LOC (<1%) 1 file
anthropic_cookbook1 LOC (<1%) 1 file

scope details...
  • 183 files, 51,430 LOC (100.0% vs. main code).
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
ROOT97 commits (15%)
misc66 commits (10%)
tool_use53 commits (8%)
managed_agents37 commits (5%)
capabilities31 commits (4%)
scripts22 commits (3%)
claude_agent_sdk19 commits (2%)
patterns18 commits (2%)
skills14 commits (2%)
multimodal13 commits (2%)
finetuning11 commits (1%)
extended_thinking9 commits (1%)
.claude7 commits (1%)
coding6 commits (<1%)
.github5 commits (<1%)
tool_evaluation3 commits (<1%)
fable_5_fallback_billing3 commits (<1%)
anthropic_cookbook2 commits (<1%)
evals1 commits (<1%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026 2025 2024
ROOT
70
27
tool_use
6
40
7
managed_agents
37
misc
18
19
29
capabilities
19
12
scripts
2
20
claude_agent_sdk
14
5
patterns
4
11
3
skills
1
13
extended_thinking
1
8
finetuning
1
8
2
.claude
3
4
multimodal
1
5
7
coding
1
5
.github
5
tool_evaluation
3
fable_5_fallback_billing
3
anthropic_cookbook
2
evals
1


Dependencies between components in same commits (past 180 days)
The number on the lines shows the number of shared commits.
See detailed temporal dependencies report... 

flowchart TB
    n0["ROOT"]
    n1["managed_agents"]
    n2["claude_agent_sdk"]
    n3["capabilities"]
    n4["patterns"]
    n5["fable_5_fallback_billing"]
    n6[".claude"]
    n7["misc"]
    n8["finetuning"]
    n9["scripts"]
    n10["tool_use"]
    n11["evals"]
    n0 ---|"20"| n0
    n0 ---|"18"| n1
    n1 ---|"12"| n1
    n2 ---|"5"| n2
    n2 ---|"5"| n0
    n3 ---|"3"| n3
    n4 ---|"3"| n0
    n0 ---|"2"| n5
    n3 ---|"2"| n0
    n6 ---|"2"| n1
    n6 ---|"2"| n0
    n7 ---|"1"| n0
    n8 ---|"1"| n3
    n7 ---|"1"| n3
    n7 ---|"1"| n8
    n7 ---|"1"| n7
    n9 ---|"1"| n3
    n9 ---|"1"| n8
    n9 ---|"1"| n7
    n10 ---|"1"| n3
    n10 ---|"1"| n8
    n10 ---|"1"| n7
    n10 ---|"1"| n9
    n11 ---|"1"| n0
    n11 ---|"1"| n11
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0FF,stroke-width:10px
    linkStyle 1 stroke:#00688bED,stroke-width:9px
    linkStyle 2 stroke:#a0a0a0B7,stroke-width:6px
    linkStyle 3 stroke:#a0a0a070,stroke-width:2px
    linkStyle 4 stroke:#00688b70,stroke-width:2px
    linkStyle 5 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 6 stroke:#00688b5E,stroke-width:1px
    linkStyle 7 stroke:#00688b5E,stroke-width:1px
    linkStyle 8 stroke:#00688b5E,stroke-width:1px
    linkStyle 9 stroke:#00688b5E,stroke-width:1px
    linkStyle 10 stroke:#00688b5E,stroke-width:1px
    linkStyle 11 stroke:#00688b4C,stroke-width:1px
    linkStyle 12 stroke:#00688b4C,stroke-width:1px
    linkStyle 13 stroke:#00688b4C,stroke-width:1px
    linkStyle 14 stroke:#00688b4C,stroke-width:1px
    linkStyle 15 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 16 stroke:#00688b4C,stroke-width:1px
    linkStyle 17 stroke:#00688b4C,stroke-width:1px
    linkStyle 18 stroke:#00688b4C,stroke-width:1px
    linkStyle 19 stroke:#00688b4C,stroke-width:1px
    linkStyle 20 stroke:#00688b4C,stroke-width:1px
    linkStyle 21 stroke:#00688b4C,stroke-width:1px
    linkStyle 22 stroke:#00688b4C,stroke-width:1px
    linkStyle 23 stroke:#00688b4C,stroke-width:1px
    linkStyle 24 stroke:#a0a0a04C,stroke-width:1px
About This Analysis

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-06 23:02