Guide Integrator

Load development references and integrate into architecture documents. Three sources: plugin methodology refs, online dev-guides, and user's custom guides.

Built-in References (Methodology)

Online Dev-Guides (Drupal Domain)

Decision guides at https://camoa.github.io/dev-guides/. WebFetch the topic index, then fetch the specific atomic guide needed.

Activation

Activate when:

• •Designing features that match reference topics
• •User mentions specific patterns (TDD, SOLID, DRY)
• •Architecture drafting for any feature
• •Auto-triggered by architecture-drafter agent

Auto-Load Rules

Plugin References (Methodology)

Loaded from plugin's references/ folder:

User's Custom Guides (Optional)

If user has configured a guides_path in project_state.md, search the configured path for relevant files based on keywords in filenames.

Workflow

1. Load Plugin References (Methodology)

Based on detected keywords in the task:

1. •Identify which methodology references apply (see Auto-Load Rules)
2. •Read each applicable reference file
3. •Extract patterns relevant to current task

2. Fetch Online Dev-Guides (Drupal Domain)

For Drupal-specific architecture decisions:

1. •Match task keywords to the Online Dev-Guides table
2. •WebFetch https://camoa.github.io/dev-guides/{topic_url} for the topic index
3. •Identify the specific atomic guide from the index
4. •WebFetch that atomic guide for the decision pattern

Only fetch topics relevant to the current task — not all topics.

3. Check for Custom Guides (Optional)

Read {project_path}/project_state.md and look for **Guides Path:** {path}.

If configured: Glob {guides_path}/*.md, match filenames to task keywords, load matches. If not configured: continue with plugin refs and dev-guides only.

4. Extract Applicable Patterns

From all loaded sources, identify:

• •Patterns that apply to current feature
• •Checklists to follow
• •Warnings or anti-patterns
• •Recommended approaches

5. Add to Architecture

Use Edit to add references section to architecture file:

## Development References

### Plugin References (Methodology)
| Reference | Key Patterns |
|-----------|--------------|
| solid-drupal.md | Single responsibility, DI |
| library-first.md | Service → Form → Route |
| tdd-workflow.md | Red-Green-Refactor |

### Dev-Guides Applied (Drupal Domain)
| Topic | Key Decisions |
|-------|--------------|
| drupal/forms/ | ConfigFormBase vs FormBase |
| drupal/entities/ | Content entity vs config entity |

### Custom Guides Applied (if any)
| Guide | Relevant Sections |
|-------|-------------------|
| {user_guide}.md | {sections} |

### Enforcement Points
| Phase | Principle | Source |
|-------|-----------|--------|
| Design | Library-First | references/library-first.md |
| Design | SOLID | references/solid-drupal.md |
| Design | Drupal patterns | dev-guides (online) |
| Implement | TDD | references/tdd-workflow.md |
| Implement | DRY | references/dry-patterns.md |
| Complete | Quality Gates | references/quality-gates.md |
| Complete | Security | dev-guides drupal/security/ |

6. Summarize

Tell user what was integrated from each source: plugin methodology, dev-guides topics, and custom guides.

Reference Locations

Stop Points

STOP and ask user:

• •If multiple custom guides could apply (ask which to prioritize)
• •If custom guide path is configured but no files found
• •Before adding patterns that conflict with existing architecture