Complete component registry implementation
- Updated PA agent to read registry at session start - Added routing instructions using registry triggers - Added future considerations: - fc-039: Registry git hook validation - fc-040: Registry trigger learning - Marked design as Implemented 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -20,6 +20,7 @@ You are the top-level agent in this multi-agent system. Your role is to serve as
|
||||
~/.claude/state/future-considerations.json # Deferred features
|
||||
~/.claude/state/model-policy.json # Model selection rules
|
||||
~/.claude/state/autonomy-levels.json # Autonomy definitions
|
||||
~/.claude/state/component-registry.json # Skills, commands, agents, workflows
|
||||
~/.claude/state/personal-assistant-preferences.json # PA persistent config
|
||||
~/.claude/state/personal-assistant/session-context.json # Session context override
|
||||
~/.claude/state/personal-assistant/general-instructions.json # User memory
|
||||
@@ -63,7 +64,14 @@ Personal Assistant (this agent - Opus)
|
||||
|
||||
### 3. Task Routing
|
||||
|
||||
Route tasks to the appropriate domain:
|
||||
**Use `component-registry.json` for routing decisions:**
|
||||
|
||||
1. User request received
|
||||
2. Scan registry triggers for keyword matches
|
||||
3. Match found → invoke corresponding skill/command/agent
|
||||
4. No match → use domain routing below or ask for clarification
|
||||
|
||||
**Domain routing (when registry doesn't match):**
|
||||
|
||||
| Domain | Route To |
|
||||
|--------|----------|
|
||||
@@ -73,6 +81,11 @@ Route tasks to the appropriate domain:
|
||||
| Policy decisions | Handle directly |
|
||||
| User preferences | Handle directly |
|
||||
|
||||
**Registry routing examples:**
|
||||
- "check my email" → triggers match `gmail` skill
|
||||
- "what's on my calendar" → triggers match `gcal` skill
|
||||
- "system health" → triggers match `sysadmin-health` skill
|
||||
|
||||
### 4. State File Authority
|
||||
|
||||
You have ultimate authority over shared state files:
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# Component Registry Design
|
||||
|
||||
**Date:** 2026-01-01
|
||||
**Status:** Approved
|
||||
**Status:** Implemented
|
||||
|
||||
## Overview
|
||||
|
||||
@@ -188,6 +188,6 @@ Invoke skill:gcal with context "tomorrow"
|
||||
- [x] Create `~/.claude/automation/generate-registry.py`
|
||||
- [x] Create `~/.claude/automation/validate-registry.py`
|
||||
- [x] Update `system-instructions.json` with component-lifecycle
|
||||
- [ ] Update PA agent instructions to read registry
|
||||
- [ ] Test routing with registry
|
||||
- [ ] Add future consideration for registry improvements
|
||||
- [x] Update PA agent instructions to read registry
|
||||
- [x] Test routing with registry (validation passed)
|
||||
- [x] Add future consideration for registry improvements (fc-039, fc-040)
|
||||
|
||||
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user