From intent-layer
Use when maintaining an existing Intent Layer, during quarterly reviews, after significant code changes, when something confused you, or when user asks to audit/update CLAUDE.md or AGENTS.md files.
npx claudepluginhub orban/intent-layer --plugin intent-layerThis skill uses the workspace's default tool permissions.
Run the maintenance flywheel for projects with an existing Intent Layer.
Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.
Generates Angular code and provides architectural guidance for projects, components, services, reactivity with signals, forms, dependency injection, routing, SSR, ARIA accessibility, animations, Tailwind styling, testing, and CLI tooling.
Executes ctx7 CLI to fetch up-to-date library documentation, manage AI coding skills (install/search/generate/remove/suggest), and configure Context7 MCP. Useful for current API refs, skill handling, or agent setup.
Run the maintenance flywheel for projects with an existing Intent Layer.
completeintent-layer skill first if state is none or partialdigraph maintenance {
rankdir=TB;
"Start" [shape=ellipse];
"Verify state=complete" [shape=box];
"State complete?" [shape=diamond];
"Run intent-layer skill" [shape=box];
"Measure token growth" [shape=box];
"Any >20k threshold?" [shape=diamond];
"Flag child node candidates" [shape=box];
"Ask pain point questions" [shape=box];
"Map findings to sections" [shape=box];
"Present update proposal" [shape=box];
"User approves?" [shape=diamond];
"Apply updates" [shape=box];
"Done" [shape=ellipse];
"Start" -> "Verify state=complete";
"Verify state=complete" -> "State complete?" ;
"State complete?" -> "Run intent-layer skill" [label="no"];
"State complete?" -> "Measure token growth" [label="yes"];
"Run intent-layer skill" -> "Done";
"Measure token growth" -> "Any >20k threshold?";
"Any >20k threshold?" -> "Flag child node candidates" [label="yes"];
"Any >20k threshold?" -> "Ask pain point questions" [label="no"];
"Flag child node candidates" -> "Ask pain point questions";
"Ask pain point questions" -> "Map findings to sections";
"Map findings to sections" -> "Present update proposal";
"Present update proposal" -> "User approves?";
"User approves?" -> "Apply updates" [label="yes"];
"User approves?" -> "Done" [label="no"];
"Apply updates" -> "Done";
}
# From intent-layer skill
scripts/detect_state.sh /path/to/project
If state is not complete, redirect to intent-layer skill for initial setup.
Use the consolidated measurement script to analyze all candidates at once:
# Recommended: Auto-discover and measure all candidates
scripts/estimate_all_candidates.sh /path/to/project
# Or measure individual directories manually:
scripts/estimate_tokens.sh /path/to/project/src
scripts/estimate_tokens.sh /path/to/project/lib
Thresholds:
Generate a structured template to capture findings:
scripts/capture_pain_points.sh pain_points.md
# Then fill in the generated template
These questions surface tribal knowledge that should be documented:
| Finding Type | Target Section |
|---|---|
| Surprising behavior | Pitfalls |
| "Never do X" rule | Anti-patterns |
| Must-be-true constraint | Contracts & Invariants |
| Technical decision rationale | Architecture Decisions |
| New common task | Entry Points |
| New subsystem | Subsystem Boundaries |
| Relationship to external | Related Context |
| New/moved child node | Downlinks |
| Changed parent/sibling | Navigation |
Show user exactly what will change:
## Proposed Updates to CLAUDE.md
### Pitfalls (adding 2)
+ `config/legacy.json` looks unused but controls feature flags for enterprise clients
+ Running `make clean` deletes cached auth tokens - must re-authenticate
### Contracts (adding 1)
+ API v2 endpoints require `X-Request-ID` header (enforced by gateway, not code)
### No changes needed
- Anti-patterns
- Architecture Decisions
- Entry Points
Edit the CLAUDE.md file to add new items to appropriate sections.
Validation after update:
| Audit Type | Focus |
|---|---|
| Quarterly review | Full: tokens + all question categories |
| Post-incident | Pitfalls + Contracts that were violated |
| After refactor | Entry Points + Subsystem Boundaries |
| After new feature | Architecture Decisions + Patterns |
| Mistake | Fix |
|---|---|
| Conflating Pitfalls with Anti-patterns | Pitfalls = surprising truth. Anti-patterns = things to avoid. |
| Adding every small finding | Only add if it would confuse future agents/engineers |
| Not measuring before asking | Always measure first - growth data informs questions |
| Updating without proposal | Show changes, get approval, then apply |
When code changes (e.g., after merge), identify which Intent Nodes need review:
scripts/detect_changes.sh main HEAD
This outputs affected nodes in leaf-first order. Check each for behavior changes.
For Intent Layers with 4+ nodes, use parallel subagents to speed up audits.
| Node Count | Approach |
|---|---|
| 1-3 nodes | Sequential (standard workflow) |
| 4-8 nodes | Parallel validation + gap detection |
| 9+ nodes | Full parallel mode |
Validate all nodes simultaneously with multiple Task calls in a single message:
Task 1 (Explore): "Validate CLAUDE.md against the codebase. Check:
- Are Entry Points still accurate?
- Are Contracts still enforced?
- Are Pitfalls still relevant?
- Any new patterns not documented?
Return: list of stale items + missing items"
Task 2 (Explore): "Validate src/api/AGENTS.md against src/api/. Check:
- Are Entry Points still accurate?
- Are Contracts still enforced?
- Are Pitfalls still relevant?
Return: list of stale items + missing items"
Task 3 (Explore): "Validate src/core/AGENTS.md against src/core/. Check:
[same questions]"
Find undocumented areas across the codebase:
Task 1 (Explore): "Search for error handling patterns in src/. Find:
- try/catch patterns that aren't documented
- Silent failures that should be Pitfalls
- Error contracts not in any AGENTS.md"
Task 2 (Explore): "Search for API contracts in src/. Find:
- Input validation rules not documented
- Response shapes not in Contracts
- Auth/permissions not documented"
Task 3 (Explore): "Search for integration points in src/. Find:
- External service calls
- Database access patterns
- Message queue usage
Check if documented in nearest AGENTS.md"
After an incident, audit relevant nodes in parallel:
Task 1 (Explore): "Review [incident area] for Pitfalls. Find:
- What assumption was violated?
- What would have prevented this?
- What should be added to Pitfalls?"
Task 2 (Explore): "Review [incident area] for Contract gaps. Find:
- What invariant was broken?
- What constraint should be documented?
- What boundary was crossed?"
After parallel agents complete:
| Metric | Sequential | Parallel |
|---|---|---|
| 5-node audit | ~20 min | ~7 min |
| 10-node audit | ~40 min | ~10 min |
| Coverage consistency | Variable | Uniform |
For complex areas where template-based capture (capture_pain_points.sh) feels insufficient, use agent-driven capture:
See references/capture-workflow-agent.md for the full three-phase process.
Use scripts/capture_state.sh to generate a tracking template for open questions during capture.
This skill uses scripts from the intent-layer skill:
| Script | Purpose |
|---|---|
detect_state.sh | Check state (none/partial/complete) |
estimate_tokens.sh | Measure single directory |
estimate_all_candidates.sh | Measure all candidates at once |
capture_pain_points.sh | Generate pain points template |
capture_state.sh | Track open questions during capture |
detect_changes.sh | Find affected nodes on merge/PR |
analyze_structure.sh | Find semantic boundaries |
validate_node.sh | Check node quality after updates |
References:
references/templates.md - Templates (S/M/L), three-tier boundariesreferences/compression-techniques.md - Compression techniques, LCA placement, parent node compressionreferences/capture-workflow-agent.md - Agent-driven capture workflowreferences/agent-feedback-protocol.md - How agents surface missing contextAll paths: ${CLAUDE_PLUGIN_ROOT}/