architecture
The architecture skill provides import graph analysis and codebase structure documentation, including hub file identification and domain cluster mapping. Use it when understanding file dependencies, planning code changes that might have wide impact, or assessing how modifications in one file will propagate through the codebase.
git clone --depth 1 https://github.com/aspenkit/aspens /tmp/architecture && cp -r /tmp/architecture/.agents/skills/architecture ~/.claude/skills/architectureSKILL.md
# Architecture This skill provides codebase structure and import graph data. When you need to understand file relationships, hub files, or domain clusters, check `references/code-map.md` for the full import graph analysis. ## Key Rules - Check hub files (high fan-in) before modifying - changes propagate widely - Respect domain cluster boundaries - keep related files together - Check cross-domain dependencies before creating new imports
LLM-powered injection of project context into installed agent templates via `aspens customize agents`
Core conventions, tech stack, and project structure for aspens
Claude/Codex CLI execution layer — prompt loading, stream-json parsing, file output extraction, path sanitization, skill file writing, and skill rule generation
Top-level Commander wiring, welcome screen, missing-hook warning, CliError exit handling, and the public programmatic API surface
Multi-target output system — target abstraction, backend routing, content transforms for Codex CLI and future targets
Context health analysis — freshness, domain coverage, hub surfacing, drift detection, LLM-powered interpretation, and auto-repair for generated agent context
Incremental skill updater that maps git diffs to affected skills and optionally auto-syncs via a post-commit hook
Static import analysis that builds dependency graphs, domain clusters, hub files, git churn hotspots, and file priority rankings