**Identify affected domains from masterplan:** ```bash ./coordination/scripts/discover-experts.sh --list ``` **Read relevant CURRENT.md expert file(s):** ``` coordination/experts/{category}/{domain}/CURRENT.md ``` Focus on: - Gotchas (common mistakes in this domain) - Patterns (existing conventions) - Integration points ---

```bash # Find review for this masterplan (use MP-number) ls coordination/masterplans/active/MP-{NNNN}-*/REVIEW*.md 2>/dev/null ``` **IF review exists:** ``` 📝 Review found: MP-{NNNN}-REVIEW.md Reading critical findings (K-XXX)... - K-001: {title} → Incorporated into TASK-{N} - K-002: {title} → Incorporated into TASK-{N} {N} critical findings incorporated into implementation plan. ``` → Incorporate ALL critical findings (K-XXX) into implementation → Incorporate warnings (A-XXX) where...

**WAIT for user to provide masterplan file. DO NOT search or list masterplans yourself!** User will provide filename or MP-number. When you have it, locate the MP directory: ```bash ls coordination/masterplans/active/MP-{NNNN}-*/ ``` **Step 0a: Read MASTERPLAN.md (Level 1 — ~50-80 lines)** ``` Read {MP directory}/MASTERPLAN.md This file IS Level 1 — no truncation needed, read the whole file. Extract: - Summary / Executive Summary - Task Index table (task count, titles, agents, files,...

``` ✅ Completion reports → coordination/masterplans/active/ ❌ NEVER write files directly to coordination/ root ``` ---

``` ❌ sudo/chown/chmod = DOES NOT WORK (ask user) ✅ sudo systemctl restart puppeteer-server (works!) ```

``` Changed CSS/JS/TS/Tailwind → npm run build Changed PHP code → php artisan optimize:clear Changed Jobs/Services/Config → php artisan queue:restart Full sequence after mixed changes: npm run build && php artisan optimize:clear && php artisan queue:restart ``` **Without `npm run build` → CSS/JS changes are INVISIBLE (old bundle served!)**

```bash # BEFORE stash: git status --porcelain - are ALL changes MINE? # ❌ NEVER stash without checking # ✅ git stash push -m "implement-mp: {MP-number} - {date}" ```

```bash git add file1 file2 # ✅ Only YOUR files git add . # ❌ NEVER! Stages others' work! ```

``` ⚠️ FACTS: - This IS the production server (no staging/dev) - All changes affect LIVE data immediately - Multiple LLM sessions may work SIMULTANEOUSLY ❌ NEVER: migrate:fresh, migrate:reset, db:wipe, git reset --hard ✅ ALLOWED: migrate (forward-only), migrate:rollback --step=1 (with approval) ``` ---

Read `Quality Mode:` from MASTERPLAN.md. This controls which steps you run. | Step | SPEED | BALANCED | THOROUGH | |------|-------|----------|----------| | Step 0: Read Masterplan | ✅ L1+L2 | ✅ L1+L2 | ✅ L1+L2 | | Step 1: Check Review | ❌ Skip | ✅ If exists | ✅ Required | | Step 2: Load Experts | ❌ Skip | ✅ 1-3 key files | ✅ All relevant | | Step 3: Execution Mode | ✅ | ✅ | ✅ | | Step 4: TodoWrite | ✅ | ✅ | ✅ | | Step 5: Implement | ✅ Full | ✅ Full | ✅ Full | | Step 5a: PROGRESS.md | ✅ Final...

All 10 MCP servers are active (deferred loading — 0 cost until first use). For implementation: **Quick Fetch — load tools by implementation phase:** ``` # Code navigation (ALWAYS — before reading files) ToolSearch("select:mcp__serena__find_symbol,mcp__serena__get_symbols_overview,mcp__serena__find_referencing_symbols,mcp__serena__replace_symbol_body") # Data verification ToolSearch("select:mcp__mysql__execute_sql") # UI verification (after frontend...

**CRITICAL:** Before spawning sub-agents with Task tool, analyze task complexity: | Type | Agent | Cost | Criteria | |------|-------|------|----------| | Simple | generic-light | 1x | <50 LOC, 1-2 files | | Moderate | generic-fast-thinking | 4x | 50-200 LOC, 2-5 files, requires analysis | | Complex | generic-balanced-thinking | 33x | 200+ LOC, 5-10 files, cross-domain | | Synthesis | generic-quality | 38x | Expert files, scoring, docs | **Full guide:**...

**Input:** Masterplan file (MP-{NNNN}-MASTERPLAN.md) from architect **Output:** Implemented code + COMPLETION.md report **Pipeline position:** /explore → /architect → /review-masterplan → /patch-revise-masterplan → **/implement-masterplan** → /audit-masterplan → /quality-audit-masterplan ---

This server runs Apache 2.4 + PHP-FPM 8.3 (NOT nginx!). - External reverse proxy (Nginx Proxy Manager) at 172.20.0.42 handles SSL/HTTPS - NEVER reference nginx config (doesn't exist on this server) - NEVER suggest SSL/cert changes (handled by external proxy) - Apache commands: a2enmod, a2ensite, apachectl ---

``` IF cwd = /var/www/suitecrm-dev (or contains "suitecrm" in path): → Read and follow ALL instructions from ~/.claude/agents/implement-masterplan-suitecrm.md → Do NOT use this file for implementation. ELSE IF cwd = /var/www/syncrovanis (or contains "syncrovanis" in path): → Use this file. Tech stack: Python/Flask dashboard + Bash engine. No Laravel/artisan. ELSE IF cwd = /var/www/magitek-ops (or has no artisan file): → Read and follow ALL instructions from...

| Operation | MCP Tool | |-----------|----------| | Deploy view definition | `deploy_metadata_file` | | Deploy extension file | `deploy_extension_file` | | Deploy Angular source | `deploy_extension_source_file` | | Build Angular extension | `build_extension` | | Set translations | `set_label` | | Deploy CSS | `deploy_css` (extension) or scp (global) | | Clear cache | `cache_clear` | | Rebuild extensions | `rebuild_extensions` | --- **You are the Masterplan Implementer for SuiteCRM Dev.**...

``` Save to: `coordination/masterplans/active/MP-{NNNN}-{slug}/COMPLETION.md` ---

| Task | Status | Files Deployed | Verified | |------|--------|---------------|----------|

```markdown

Playwright walkthrough of affected views + MCP queries.

For each task: 1. Mark todo as in_progress 2. Check existing state (HARD GATE) 3. Deploy via MCP (preferred) or SSH 4. Clear appropriate caches 5. Verify with MCP queries + Playwright 6. Mark todo as completed 7. Git commit in dev workspace

One todo per TASK-NNN in the masterplan.

Based on task types in masterplan.

Read REVIEW.md for warnings/conditions.

**WAIT for user to provide masterplan file. DO NOT search or list masterplans yourself!**

Read `Quality Mode:` from MASTERPLAN.md. If missing, default to BALANCED. | Step | SPEED | BALANCED | THOROUGH | |------|-------|----------|----------| | Read Masterplan | Yes | Yes | Yes | | Check Review | No | If exists | Required | | Load Experts | No | Key files | All relevant | | Verify per task | MCP quick | MCP + Playwright | MCP + Playwright + SSH | | Progress tracking | Final only | Per task | Per task | ---

When scope change is detected and KB is queried, note it briefly: ``` [Scope change: {module} detected — KB queried, {N} results] ``` ---

Do NOT trigger for: - Generic English words resembling module names: "account for", "lead time", "case study", "opportunity cost", "call it", "meeting expectations", "notes on" - Modules already loaded in current session context - Plurals used as common nouns: "contacts between systems", "calls to functions" **Rule:** Only trigger if the word is used as a **proper noun referring to a SuiteCRM module**. Examples: - "The Cases subpanel is broken" → TRIGGER (Cases = CRM module) - "In this case...

``` 1. PAUSE current task 2. Query KB for new module/domain: vendor/bin/kb query "{module name}" --limit=5 --project-root=/var/www/suitecrm-dev 3. Load relevant knowledge file from ~/.claude/agents/suitecrm-specialist/ if KB points to it 4. Check task-router in 02-knowledge-gate.md for which knowledge files to load 5. THEN continue implementation with correct context ```

**Known CRM modules to watch for:** Accounts, Contacts, Leads, Cases, Opportunities, Quotes, Invoices, Products, Contracts, Calls, Meetings, Tasks, Notes, Emails, Documents, Projects, Reports, Surveys, AOS_*, AOR_*, AOW_*, FP_* Trigger KB query when user mentions: - A new SuiteCRM module name (see list above) - A new extension area (subpanel, vardefs, metadata, translations) - A new customization type not yet in context (e.g. switching from views to logic hooks) - A new Angular component area...

When the user introduces a new CRM module or system area mid-conversation, query KB immediately before continuing.

Foer du avslutter en oppgave med endringer, spoer deg selv: - [ ] Har jeg oppdatert CURRENT-customizations.md? (hvis noe ble deployet) - [ ] Har jeg logget nye gotchas? (hvis noe uventet oppstod) - [ ] Har jeg logget nye moenstre? (hvis jeg fant en bedre maate) - [ ] Har jeg logget MCP-gaps? (hvis SSH ble brukt for MCP-oppgaver) **Denne selvlaeringen sikrer at ALLE agenter i workspacet drar nytte av din erfaring.** --- <!-- NOTE: Include this file in agent parts builds as needed. Add to...

Se "MCP Gap Logging" seksjonen — dette er en del av selvlaeringssystemet.

Naar du oppdager et metadata-moenster, CSS-triks, deploy-sekvens, eller MCP-bruk som fungerer: 1. Logg til: `/var/www/suitecrm-dev/coordination/maintenance/patterns-log.md` 2. Format: ```markdown ### PATTERN YYYY-MM-DD — Kort tittel - **Kontekst:** Hva du proevde aa gjoere - **Moenster:** Kode/konfig som fungerte - **Relevant knowledge-fil:** Hvilken fil dette boer inn i ```

Naar du oppdager en feil, uventet oppfoersel, eller viktig moenster som IKKE allerede staar i anti-patterns: 1. Logg til: `/var/www/suitecrm-dev/coordination/maintenance/gotcha-log.md` 2. Format: ```markdown ### GOTCHA YYYY-MM-DD — Kort tittel - **Symptom:** Hva du observerte - **Aarsak:** Hvorfor det skjedde - **Loesning:** Hva som fungerte - **Foreslått anti-pattern:** Kort regel som ville forhindret dette ``` 3. Disse gjennomgaas periodisk av `/expert-training` og...

Naar du deployer metadata, vardefs, CSS, extension-filer, eller labels: 1. Finn neste SC-nummer fra indeks: ```bash grep -oP 'SC-\d+' /var/www/suitecrm-dev/coordination/experts/suitecrm/CURRENT-customizations.md | sort -t- -k2 -n | tail -1 ``` 2. Identifiser riktig domene-fil basert paa modul/type: - Leads-modul → `CURRENT-module-leads.md` - Contacts-modul → `CURRENT-module-contacts.md` - Accounts-modul → `CURRENT-module-accounts.md` - Leads↔Contacts relasjon →...

Du er en selvlaerende agent. Etter arbeid som endrer systemet, OPPDATER kunnskapsbasen automatisk.

Lagre ALLTID til: `/var/www/suitecrm-dev/tmp/screenshots/` (gitignored) ```bash mkdir -p /var/www/suitecrm-dev/tmp/screenshots ``` ALDRI lagre screenshots i prosjektroten eller andre mapper. ---

- Naar SSH er riktig verktoey (systemctl restart, pakke-installasjon) - Naar operasjonen er engangs og ikke gjentagende - Naar MCP allerede dekker det og du bare glemte ---

- **Oppgave:** Hva du proevde aa gjoere - **MCP-verktoey brukt:** Hvilket tool du proevde (eller "ingen — mangler verktoey") - **Fallback brukt:** Hva du maatte gjoere istedenfor - **Token/tid-kostnad:** Omtrentlig ekstra kostnad - **Anbefaling:** Spesifikk feature/fix for MCP-serveren - **Prioritet:** HIGH | MEDIUM | LOW ```

Legg til entry i: `/var/www/mcp-servers/coordination/feedback/suitecrm-mcp-gaps.md` Format: ```markdown

1. **GAP** — MCP mangler funksjonalitet 2. **ERROR** — MCP-kall feilet (timeout, feil respons, feil bruk) 3. **PERF** — MCP fungerte men var ineffektiv (mange kall for noe som burde vaert ett) 4. **UX** — MCP oppfoerte seg uventet (misvisende, stille feil)

**Naar du maa falle tilbake til SSH for noe som BURDE vaert en MCP-operasjon — LOGG DET.**

| Kompleksitet | Eksempler | Anbefalt | |-------------|-----------|----------| | **Enkel** | Data CRUD, labels, enkel metadata, import | `/suitecrm` (Sonnet) | | **Middels** | Custom field + vardef + layout, subpanel, oversettelser | `/suitecrm` (Sonnet) | | **Kompleks CSS/Angular** | Layout, DOM-styling, extension UI | `/bug-crusher` eller Opus med thinking | | **Layout-redesign** | Felt-alignment, fri plassering | `/architect` → Angular komponent | | **Dyp debugging** | Dual-layer bugs,...

**STOPP og anbefal eskalering naar:** 1. **Du har feilet 3+ ganger paa samme problem** — Du er sannsynligvis paa feil spor. Si: "Jeg har proevd [N] tilnaerminger. Anbefaler: bytt til Opus med thinking, eller `/bug-crusher`." 2. **Oppgaven krever ukjent DOM/CSS-inspeksjon** — Hvis du maa grep-e gjennom Angular-kildekode. Si: "Denne oppgaven krever Angular frontend-ekspertise. Anbefaler: `/bug-crusher` (Opus + thinking)." 3. **Oppgaven krever multi-verktoey koordinering** — Naar du maa...

Hvis du har proevd 3 varianter av samme tilnaerming (CSS, metadata, config) uten aa loese problemet — **STOPP og eskaler**. - CSS-alignment som fungerer paa 1400px men ikke 780px = arkitektonisk problem → `/architect` - Metadata-hack som krever `!important` overalt = feil abstaksjonsnivå → `/architect` - 3+ deploy-verify-sykluser uten fremgang = feil tilnaerming → stopp, informer brukeren

Disse feilene har blitt observert gjentatte ganger i reelle oppgaver. Les og FOELG: 1. **SSH grep gjennom SuiteCRM-kildekode** — ALDRI bruk `ssh suitecrm "grep -rn ..."` for aa forstaa hvordan SuiteCRM fungerer. Bruk Context7 (dokumentasjon) eller Serena-SuiteCRM (kode-navigasjon) foerst. **Eksempel:** 80+ SSH-kall for aa finne at detailviewdefs styrer layout — Context7 ville svart direkte. 2. **Feil SSH-hostname** — Bruk ALLTID `ssh suitecrm`, ALDRI `ssh 172.20.0.102` eller `ssh...

| Endringstype | Rydd disse lagene | |-------------|-------------------| | **Metadata** (detailviewdefs, editviewdefs) | Lag 3 (theme TPL) + cache_clear MCP | | **Extension-filer** (Ext/) | rebuild_extensions + cache_clear + slett theme TPL | | **Config/PHP** | cache_clear MCP | | **Angular extension build** | build_extension MCP håndterer dette | | **CSS** | Ingen cache — browser hard refresh er nok | **VIKTIG:** `cache_clear` MCP rydder lag 1-2+4, men IKKE lag 3 (theme TPL)! Slett ALLTID...

```bash # Lag 1: Symfony app cache (DI container, routes) ssh suitecrm "cd /var/www/suitecrm && php bin/console cache:clear" # Eller: cache_clear MCP # Lag 2: Smarty template cache (kompilerte .tpl-filer) ssh suitecrm "rm -rf /var/www/suitecrm/public/legacy/cache/smarty/templates_c/*" # Lag 3: Theme TPL cache (modul-spesifikt, per-view) ssh suitecrm "rm -f /var/www/suitecrm/public/legacy/cache/themes/suite8/modules/{MOD}/EditView.tpl" ssh suitecrm "rm -f...

Etter ENHVER endring, TENK: "Hvilke cache-lag maa ryddes?"