Python Architecture Skill
SkillFiles & storageActivates architecture guidance when creating modules, refactoring class hierarchies, or changing 3+ files in the APM codebase.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Python Architecture Skill skill
About this capability
Activate when creating new modules, refactoring class hierarchies, introducing design patterns, or making changes spanning 3+ files in the APM CLI codebase.
What this skill tells your AI
The instructions your AI receives, as published by microsoft/apm in .agents/skills/python-architecture/SKILL.md and read by ahel’s review.
When to activate
- Creating new Python modules or packages under
src/apm_cli/ - Refactoring class hierarchies or introducing base classes
- Changes that touch 3+ files with shared logic patterns
- Introducing new design patterns (Strategy, Observer, etc.)
- Cross-cutting concerns (logging, auth, error handling)
- 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
Signals
- GitHub stars
- 4k
- Forks
- 357
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
python-architecture- Source
- github.com/microsoft/apm