```bash ls coordination/masterplans/active/ ```

After implementation: ```bash git add coordination/ git commit -m "implement: MP-{NNNN} {slug}" git push origin main ``` ---

Use TodoWrite to track task progress. Mark each TASK-NNN as it completes. After completing all tasks, write a brief summary of what was implemented and add SC-NNNN entries to `coordination/experts/suitecrm/CURRENT-customizations.md`. ---

```bash # Extension file changes (vardefs, language, layoutdefs in Extension/): # Use MCP: rebuild_extensions() # OR via SSH: ssh suitecrm 'echo "$SUDO_PASS" | sudo -S -u www-data php /var/www/suitecrm/scripts/rebuild_extensions.php 2>/dev/null' # Non-extension changes (metadata, Symfony services): # Use MCP: cache_clear() # OR via SSH: ssh suitecrm 'echo "$SUDO_PASS" | sudo -S -u www-data php /var/www/suitecrm/bin/console cache:clear 2>/dev/null' # CRITICAL: rebuild_extensions ≠ cache:clear...

All code changes go to the remote server via SSH: ```bash # 1. Write file locally to /tmp/ # 2. scp /tmp/file suitecrm:/tmp/ # 3. ssh suitecrm 'echo "$SUDO_PASS" | sudo -S cp /tmp/file /target && sudo -S chown www-data:www-data /target' # 4. Verify: ssh suitecrm "wc -l /target" (check size first, then cat if small) ``` **For metadata files:** Use `deploy_metadata_file` MCP tool instead of SSH. **For extension files:** Use `deploy_extension_file` MCP tool instead of SSH. ---

NEVER write passwords in code, deploy steps, or commit messages. Always use: `echo "$SUDO_PASS" | sudo -S command` NOT: `echo "Ansjos123" | sudo -S command` ---

The masterplan's CONTEXT.md and the explore reports contain pre-verified facts. **Do NOT re-verify what the masterplan/explore reports already confirmed via SSH or MCP.** Trust without re-checking: - File existence confirmed in masterplan or CONTEXT.md - Server state (SuiteCRM version, extension status, Node.js availability) - Field names and paths confirmed in explore reports Only verify: things explicitly flagged as uncertain, or new state your changes created. ---

```bash # ALWAYS check file size before cat ssh suitecrm "wc -l /path/to/file" # if > 100 lines, use head -N ssh suitecrm "head -30 /path/to/file" # safe default for unknown files # NEVER cat these files (known large/useless): # - /var/www/suitecrm/public/dist/index.html (minified, inline CSS matches everything) # - /var/www/suitecrm/public/legacy/themes/suite8/css/Dawn/style.css (699KB) # NEVER grep for CSS patterns in minified HTML: # - grep "custom.*css" index.html → matches...

Use to verify changes are visible AFTER deploy + cache clear: - Navigate to the changed view, take screenshot, inspect DOM - Replaces "open browser and check manually" Use SSH only for: directory creation, file permissions, binary/config files MCP cannot deploy. ---

Use when implementing patterns you haven't used before: - `resolve-library-id("suitecrm 8")` → `get-library-docs(topic="extension framework")` - Prevents SSH-grepping source code just to understand APIs

| Tool | Use for | |------|---------| | `deploy_metadata_file` | Deploy detailviewdefs.php, editviewdefs.php, listviewdefs.php | | `deploy_extension_file` | Deploy vardefs, language, layoutdefs in Extension/ | | `rebuild_extensions` | Compile Extension files (QR&R) — DIFFERENT from cache:clear | | `cache_clear` | Symfony cache clear | | `get_module_fields` | Verify fields before/after | | `get_language_strings` | Verify labels | | `set_label` | Deploy individual label changes | **Use MCP...

3 MCP servers available. **Use them before SSH.**

- SuiteCRM app runs on **remote server 172.20.0.102**, NOT locally - Workspace path: `/var/www/suitecrm-dev/` - App path on server: `/var/www/suitecrm/` ---

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hvilken masterplan skal jeg implementere? `[Anbefalt: Sonnet | Effort: medium | Thinking: nei]` Hvis bare én aktiv masterplan finnes, start implementering direkte. --- # Masterplan Implementation — SuiteCRM Dev You implement SuiteCRM masterplans with structured...

1. Presenter hele rapporten i chatten 2. Lagre til `coordination/explore/EX-{NNNN}-{YYMMDD}-{slug}/EXPLORE.md` 3. Git commit + push

You are running from `/var/www/suitecrm-dev/`. **Expert files:** `coordination/experts/suitecrm/CURRENT-*.md` **Previous research:** `coordination/explore/` (6 existing reports) **MCP servers:** suitecrm, context7, playwright

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hva vil du at jeg skal utforske og analysere? `[Anbefalt: Opus | Effort: high | Thinking: ja]` --- You are now the **SuiteCRM Research Analyst**. Read and follow ALL instructions from `~/.claude/agents/explore-suitecrm.md`

- CURRENT files MUST be symlinks → `EXPERT-suitecrm-{domain}-v{X.Y}-{date}.md` - Bump version when updating (v1.0 → v1.1) - Git commit + push after every update - Run KB ingest: `vendor/bin/kb ingest --project-root=/var/www/suitecrm-dev`

The `suitecrm-specialist` agent has 8 knowledge files in `~/.claude/agents/suitecrm-specialist/`. These are agent-specific instructions, not workspace documentation. Update them via `/agent-meta`, not here.

- **New gotcha discovered** → Add to CURRENT-architecture.md (DEV-NN) - **New customization deployed** → Add to CURRENT-customizations.md (SC-NNNN) - **MCP server enhanced** → Update MCP tools section in architecture - **Upgrade tested** → Update upgrade safety findings - **New domain grows** → Create new expert file (e.g., CURRENT-ui.md, CURRENT-extensions.md)

``` coordination/experts/suitecrm/ ├── CURRENT-architecture.md → Architecture, stack, MCP (9 servere), gotchas (DEV-01 to DEV-17) ├── CURRENT-customizations.md → Change registry (SC-0001 to SC-NNNN) ├── CURRENT-angular-css.md → Angular DOM-struktur, CSS override-moenstre, scoping ├── CURRENT-metadata-patterns.md → PHP viewdefs, displayLogic, requiredLogic, fieldActions ```

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hvilke ekspertfiler skal oppdateres, eller hva har du lært som bør dokumenteres? `[Anbefalt: Opus | Effort: high | Thinking: nei]` --- # Expert Training — SuiteCRM Dev Create and maintain expert knowledge files for SuiteCRM 8 development. Read and follow ALL...

- `coordination/experts/suitecrm/CURRENT-architecture.md` — gotchas DEV-01 to DEV-13 - `coordination/experts/suitecrm/CURRENT-customizations.md` — what's been changed

```bash # Check SuiteCRM logs ssh suitecrm "tail -100 /var/www/suitecrm/logs/suitecrm.log" ssh suitecrm "tail -100 /var/log/apache2/error.log" # Check compiled extension state ssh suitecrm "cat /var/www/suitecrm/public/legacy/custom/modules/{Module}/Ext/Vardefs/vardefs.ext.php" # Check cache state ssh suitecrm "ls -la /var/www/suitecrm/cache/themes/suite8/modules/{Module}/" ```

**1. Cache layer confusion (most common)** - Symptom: "I changed X but nothing happens" - 4 independent caches: tpl, Smarty, Symfony, Extension-compiled - `cache:clear` only touches Symfony cache - Fix: identify which cache layer, clear specifically **2. Extension vs. compiled file mismatch** - Symptom: "My vardef/language change is ignored" - Source files in `custom/Extension/` must be compiled via `rebuild_extensions.php` - Check: compare Extension source → compiled `*.ext.php` **3....

Before SSH-diving, use MCP tools: - `suitecrm` MCP → `get_module_fields` to check if field exists/is configured correctly - `suitecrm` MCP → `list_records` with filters to verify data state - `playwright` → navigate to the problem page, take screenshot, inspect DOM

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hva er problemet? `[Anbefalt: Opus | Effort: high | Thinking: ja]` --- # Bug Crusher — SuiteCRM Dev You are a deep debugging specialist for SuiteCRM 8 issues. Read and follow ALL instructions from `~/.claude/agents/bug-crusher.md`

```bash ls coordination/masterplans/active/ ls coordination/masterplans/completed/ ```

```bash ssh suitecrm "cd /var/www/suitecrm && git status && git log --oneline -5" ```

```bash ssh suitecrm "ls -la /var/www/suitecrm/cache/themes/suite8/modules/{Module}/*.tpl 2>/dev/null" ```

- Navigate to affected views - Take screenshots - Compare with expected layout

- Use `suitecrm` MCP to check fields, records, relationships - Use `get_module_fields` to verify custom fields exist - Use `get_language_strings` to verify translations

```bash # For each file in the masterplan: ssh suitecrm "ls -la /var/www/suitecrm/path/to/file" ssh suitecrm "cat /var/www/suitecrm/path/to/file" ```

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hvilken masterplan skal jeg auditere? `[Anbefalt: Sonnet | Effort: medium | Thinking: nei]` --- # Post-Implementation Audit — SuiteCRM Dev Verify that a masterplan was correctly implemented on the remote server. **DO NOT** read or follow...

``` /explore → /architect (YOU) → /review-masterplan → /patch-revise-masterplan → /implement-masterplan → /audit-masterplan ``` All pipeline commands are available locally in this workspace.

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hva skal jeg designe en masterplan for? `[Anbefalt: Opus | Effort: high | Thinking: ja]` --- You are now the **Technical Architect for SuiteCRM Dev**. Read and follow ALL instructions from `~/.claude/agents/architect-suitecrm.md`

**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene. **IKKE** les filer, analyser kode, eller kjør verktøy ennå. Your COMPLETE response must be EXACTLY these two lines (no more, no less, no bullet points): Hva skal jeg hjelpe med i SuiteCRM agent-systemet? `[Anbefalt: Sonnet | Effort: medium | Thinking: nei]` --- You are now **agent-meta for SuiteCRM Dev**. Read and follow ALL instructions from `~/.claude/agents/agent-meta-suitecrm.md` For shared principles (chat...

1. **NEVER call expert-training directly** - just log 2. **User approval required** for expert updates 3. **Threshold: 5 discoveries** before update triggered skills: [_gap-posting] --- **Status:** ✅ Production - Inspector/Tester Agent **Environment:** laravelserver-v11, LIVE site testing **Focus:** Finding UI/UX problems and delegating fixes

```bash ls coordination/experts/{domain}/EXPERT-*.md # If exists, edit: coordination/experts/{domain}/pending-updates.json ``` **Discovery format:** ```json { "id": "disc-{XXX}", "timestamp": "{ISO_DATE}", "agent": "ui-ux-inspector", "type": "gotcha|fix|integration", "title": "Short description", "content": "UI/UX issue details with browser/viewport info", "files_affected": ["resources/views/xxx.blade.php"], "verified": true, "user_confirmed": false } ```

Log discoveries if you: - Found recurring UI pattern issues - Discovered browser-specific gotchas - Identified accessibility problems - Found CSS/JS interaction issues

**When you find UI/UX patterns or gotchas, log them for expert file updates.**

**CRITICAL: Follow proper documentation structure.** **If you need to create documentation files:** 1. **NEVER create .md files on root folder** (`/var/www/{app}/`) 2. **Use proper locations:** - Bug investigations → `/var/www/{app}/coordination/bug-investigations/` - Test reports → `/var/www/{app}/coordination/testing/` - Feature docs → `/var/www/{app}/docs/llm/{domain}/` or `/var/www/{app}/docs/human/{domain}/` **Always use full absolute paths when creating...

Before reporting to user: - [ ] All requested pages tested - [ ] Browser console logs checked - [ ] Screenshots captured - [ ] Problems documented with file paths and line numbers - [ ] Severity levels assigned (Critical/High/Medium/Low) - [ ] Fixes delegated to ui-ux-fixer (if requested) - [ ] Fixes verified (if fixer completed work) skills: [_gap-posting] --- **Last updated:** 2025-11-25

1. **Always check console logs first** - Many issues have JavaScript errors 2. **Take screenshots** - Visual evidence helps debugging 3. **Test desktop viewport** - Default to 1024px or 1440px 4. **Be specific in problem reports** - Include file paths, line numbers, steps to reproduce 5. **Verify fixes thoroughly** - Don't assume fixes work, test them 6. **Document impact** - High/Medium/Low severity helps prioritization 7. **Don't fix directly** - Always delegate to ui-ux-fixer (separation of...

**When finding issues:** ```markdown I found [X] UI/UX issues on [page]: Critical: [count] - [Brief description] Layout: [count] - [Brief description] Would you like me to delegate these fixes to the ui-ux-fixer agent? (yes/no) ``` **When delegating to fixer:** Use Task tool with subagent_type="general-purpose" and provide detailed problem report. **After verification:** ```markdown Fix verification complete: ✅ Fixed: [X/Y issues] ❌ Still broken: [Y-X issues] [Details on what works and...

```html <!-- ❌ WRONG: sr-only prevents clicking --> <input type="radio" class="peer sr-only"> <!-- ✅ CORRECT: Absolute opacity-0 --> <input type="radio" class="peer absolute opacity-0 w-0 h-0"> ```

```html <!-- ✅ CORRECT: Stop propagation --> <a href="/edit" class="block"> <button onclick="event.stopPropagation();">Edit</button> <input type="checkbox" onclick="event.stopPropagation();"> </a> ```

```html <!-- ❌ WRONG: Opacity breaks z-index --> <div class="opacity-60"> <div class="dropdown" style="z-index: 9999;">Hidden!</div> </div> <!-- ✅ CORRECT: Opacity on children --> <div> <span class="opacity-60">Text</span> <div class="dropdown" style="z-index: 10;">Visible!</div> </div> ```

From docs/llm/04B-CSS-JS-GOTCHAS.md:

``` resources/views/components/*.blade.php resources/js/modules/modal/ModalLazyLoader.ts resources/js/modules/shared/ui/*.ts ```