> Activate when creating new modules, refactoring class hierarchies, introducing design patterns, or making changes spanning 3+ files in the APM CLI codebase.
348 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3460
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
Performance-sensitive paths (parallel downloads, large manifests)
Key rules
Follow existing patterns (BaseIntegrator, CommandLogger, AuthResolver) before inventing new ones
Prefer composition over deep inheritance
Push shared logic into base classes, not duplicated across siblings
One canonical owner per decision: route through the existing authority (target_catalog, AuthResolver/host_providers, runtime registry, CommandLogger, CompiledOutputWriter, deployment_ledger, install-outcome, neutral hook IR, BaseIntegrator); extend it, never fork it. Full rule: .apm/instructions/architecture.instructions.md
Lock every centralization with a dual guardrail: a regression test plus a static check in scripts/lint-architecture-boundaries.sh
How to use it
Copy the folder
Take microsoft/python-architecture from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.