1. Resolve the project root (the current working directory) and run: ```bash .claude/mysql-disable.sh ``` If `.claude/mysql-disable.sh` does not exist, use `.claude/switch-mcp.sh none` as fallback. 2. Inform the user that MySQL MCP will be disabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

Only if ALL true: 1. Changes are PURELY backend (no views, routes, controllers) 2. No migrations affecting displayed data 3. No asset changes (JS/CSS) 4. No navigation/menu changes If in doubt → ask for frontend validation.

[What you actually verified — syntax, tests, build] FRONTEND VALIDATION REQUIRED I can ONLY verify backend/build. Frontend consequences are INVISIBLE to me. YOU MUST TEST: - [Affected Page](https://reportmaker.magitek.no/path) — Test [specific thing] CHECKLIST: - [ ] Pages load without errors - [ ] No JavaScript console errors - [ ] Data displays correctly - [ ] Visual appearance correct Current Status: Waiting for your validation ```

```

Never say: "Fixed!", "BUG CRUSHED", "Everything is working", "Ready to merge", "All done!" These are lies — you cannot verify frontend.

- Frontend display (you cannot see how pages render) - JavaScript runtime behavior - CSS/Layout visual regressions - User experience issues

1. Resolve the project root (the current working directory) and run: ```bash .claude/switch-mcp.sh serena ``` If `.claude/switch-mcp.sh` does not exist in the current project, check `/var/www/reportmaker/.claude/switch-mcp.sh` as fallback. 2. Inform the user that Serena will be enabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

```bash chmod 644 path/to/file.php ```

PHP, Blade, JavaScript, TypeScript, CSS, JSON, YAML, Markdown — everything in app/, resources/, config/, routes/, coordination/, .claude/.

| Situation | Action | |-----------|--------| | After Write tool creates file | fix-permissions.sh | | Before git commit | fix-permissions.sh --check | | "Permission denied" in logs | fix-permissions.sh | | "Kunne ikke laste detaljer" | fix-permissions.sh |

```bash ./coordination/scripts/fix-permissions.sh ```

600 (rw-------) → must be 644 (rw-r--r--) `www-data` is in group/others and MUST read PHP, Blade, JS, JSON files.

Claude Code Write tool creates files with **600 permissions** (owner-only). `www-data` cannot read 600 files → "Permission denied", "Kunne ikke laste detaljer", Blade rendering errors.

1. Resolve the project root (the current working directory) and run: ```bash .claude/switch-mcp.sh lighthouse ``` If `.claude/switch-mcp.sh` does not exist in the current project, check `/var/www/reportmaker/.claude/switch-mcp.sh` as fallback. 2. Inform the user that Lighthouse will be enabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

``` BEFORE modifying ANY file: 1. git diff --name-only 2. If file listed → read the diff 3. PRESERVE existing uncommitted changes 4. Only ADD your changes on top NEVER overwrite uncommitted changes NEVER assume you have the latest version ```

If spawner says "DO NOT TOUCH X" or marks sections as PROTECTED: - Identify those sections in the file - Preserve them exactly - Only modify the OTHER parts

```bash git diff <file_path> | head -50 ``` Then: 1. PRESERVE existing changes in your modifications 2. ADD your changes on top — never overwrite 3. Report: "File has uncommitted changes from another session — merged"

| File in diff output? | Action | |---------------------|--------| | NO | Safe to modify | | YES | Read the diff first, preserve changes |

```bash git diff --name-only ```

Parallel sessions modify files without committing. Spawned agents overwrite those changes, destroying work-in-progress.

1. Note in response 2. Proceed with manual exploration 3. Consider creating handoff: `coordination/experts/handoffs/HANDOFF-{domain}-{date}-{agent}.md`

Each expert file contains: - Quick reference (key files, classes, methods) - Database schema - Known gotchas and bugs - Integration points - Data flow diagrams

All in: `coordination/experts/{domain}/` Current domains: - `security-audit-system` — security scanning, audit rules - `findings-templates` — template system, findings management - `findings-blocks-seo-migration` — block-based findings, SEO - `web-discovery-verification` — website discovery, verification - `page-crawler-system` — Puppeteer, web scraping - `analysis-execution-infrastructure` — analysis runners, queues - `backend-refactoring-patterns` — service patterns, DI -...

```bash # List all available expert domains ./coordination/scripts/discover-experts.sh --list # Match by agent type ./coordination/scripts/discover-experts.sh --agent {your-agent-type} ```

```bash ./coordination/scripts/discover-experts.sh --for-task "your task description" ``` Read ALL matched expert files BEFORE starting work. Token savings: 80-90% vs manual exploration.

```bash # Free-text search (ALL workspaces with Laravel): php artisan kb:query "TOPIC" --limit=5 # Structured lookup (specific file/domain/masterplan): php artisan kb:context domain:customer-management --limit=5 php artisan kb:context file:app/Services/Example.php --limit=5 # Non-Laravel workspaces (magitek-ops, dam): vendor/bin/kb query "TOPIC" --limit=5 --project-root=$(pwd) ``` KB returns relevant excerpts AND points to which expert files are most relevant. **If KB returns useful results...

1. Resolve the project root (the current working directory) and run: ```bash .claude/context7-disable.sh ``` If `.claude/context7-disable.sh` does not exist, use `.claude/switch-mcp.sh none` as fallback. 2. Inform the user that Context7 will be disabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

- KB gives **direction**, not complete solutions - Always read the actual files for full context - If KB returns 0 results → proceed without it (do not block on this) - Max 5 results — more wastes tokens without benefit - Skip KB if task is purely administrative (git commits, file moves, etc.)

Extract 1-3 keywords from the task that represent the domain: - "Fix the analysis queue job" → topic: `analysis queue` - "Update Proxmox backup policy" → topic: `proxmox backup` - "Add CSV export for customers" → topic: `customers export` - "Debug NPM proxy issue" → topic: `npm proxy` **Keep topics short and specific** — 2-3 words max.

| Workspace | Command | |-----------|---------| | `/var/www/reportmaker` | `php artisan kb:query "$TOPIC" --limit=5` | | `/var/www/skymirror` | `php artisan kb:query "$TOPIC" --limit=5` | | `/var/www/magitek-ops` | `vendor/bin/kb query "$TOPIC" --limit=5 --project-root=$(pwd)` | | Any other | Check for `artisan`, fall back to `vendor/bin/kb` |

Read the KB output before starting work. This gives you: - Known gotchas and bugs for this domain - Relevant expert files to read - Patterns and lessons from previous work

```bash # Non-Laravel workspaces (magitek-ops, or any without artisan): $PROJECT_ROOT/vendor/bin/kb query "$TOPIC" --limit=5 --project-root="$PROJECT_ROOT" # Laravel workspaces (reportmaker, skymirror) — free-text search: php $PROJECT_ROOT/artisan kb:query "$TOPIC" --limit=5 # Laravel workspaces — structured lookup (specific file/domain/masterplan): # php $PROJECT_ROOT/artisan kb:context domain:$DOMAIN --limit=5 # php $PROJECT_ROOT/artisan kb:context file:$FILE_PATH --limit=5 ``` **Workspace...

```bash # Use the current working directory as project root PROJECT_ROOT=$(pwd) ```

Before starting work, extract the main topic/domain from the task and run a KB search.

1. Resolve the project root (the current working directory) and run: ```bash .claude/switch-mcp.sh css ``` If `.claude/switch-mcp.sh` does not exist in the current project, check `/var/www/reportmaker/.claude/switch-mcp.sh` as fallback. 2. Inform the user that CSS MCP will be enabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

1. Resolve the project root (the current working directory) and run: ```bash .claude/accessibility-disable.sh ``` If `.claude/accessibility-disable.sh` does not exist, use `.claude/switch-mcp.sh none` as fallback. 2. Inform the user that Accessibility Scanner will be disabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

| Symptom | Fix | |---------|-----| | "My fix isn't working" | queue:restart | | Changes not visible in browser | npm run build | | Route/View not found (but exists) | optimize:clear | | "Class not found" in queue job | queue:restart |

- queue workers hold PHP code in memory — optimize:clear alone is NOT enough - Wait 5+ seconds after queue:restart before testing - Files with 600 permissions cause all clearing to fail — run fix-permissions.sh FIRST

| Change Type | queue:restart | optimize:clear | npm run build | |-------------|---------------|----------------|---------------| | PHP Service/Controller | YES | YES | No | | PHP Model/Repository | YES | YES | No | | Blade template | No | YES | No | | JavaScript/TypeScript | No | No | YES | | CSS/Tailwind | No | No | YES | | Config file (config/) | No | YES | No | | Route file | No | YES | No | | Queue Job class | YES | YES | No | | Livewire component | YES | YES | No | **Rule of thumb:** -...

Hooks handle execution automatically. This skill identifies WHAT to clear based on change type.

1. Resolve the project root (the current working directory) and run: ```bash .claude/lighthouse-disable.sh ``` If `.claude/lighthouse-disable.sh` does not exist, use `.claude/switch-mcp.sh none` as fallback. 2. Inform the user that Lighthouse will be disabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

1. Resolve the project root (the current working directory) and run: ```bash .claude/switch-mcp.sh accessibility ``` If `.claude/switch-mcp.sh` does not exist in the current project, check `/var/www/reportmaker/.claude/switch-mcp.sh` as fallback. 2. Inform the user that Accessibility Scanner will be enabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

1. Resolve the project root (the current working directory) and run: ```bash .claude/switch-mcp.sh mysql ``` If `.claude/switch-mcp.sh` does not exist in the current project, check `/var/www/reportmaker/.claude/switch-mcp.sh` as fallback. 2. Inform the user that MySQL MCP will be enabled on next restart. Note: uses a read-only database user (reportmaker_ro) — SELECT and SHOW VIEW only. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

5+ verified discoveries → orchestrator prompts for expert update. User approval required before update.

FORBIDDEN: code examples, bash examples, "Here's how to..." explanations, verbose descriptions. REQUIRED: file:line references, 1-line function signatures, 3-line gotcha descriptions.

```json { "id": "disc-{NNN}-{short-slug}", "timestamp": "ISO-8601", "agent": "{agent-name}", "type": "fix|gotcha|new_feature|refactor|integration", "severity": "low|medium|high|critical", "category": "{category-slug}", "title": "Short title (max 10 words)", "content": "File:line ref. Problem → Cause → Fix (3 lines max)", "files_affected": ["path/to/file.php:123"], "verified": true, "user_confirmed": false } ```

``` coordination/experts/{domain}/pending-updates.json ``` Domain mapping: - Analysis details templates → `analysis-details-system` - UI/UX issues → `ui-ux-system` - Security rules → `security-audit-system` - Analysis system → `analysis-system` - Other/general → `generic-development`

Log BEFORE marking task complete when you: - Fix a bug (any severity) - Find a gotcha (non-obvious behavior) - Discover architecture insight - Find data structure mismatch - Encounter silent failure pattern - Learn integration point Never log: trivial typos, things already in expert file, temporary workarounds.

1. Resolve the project root (the current working directory) and run: ```bash .claude/serena-disable.sh ``` If `.claude/serena-disable.sh` does not exist, use `.claude/switch-mcp.sh none` as fallback. 2. Inform the user that Serena will be disabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.

1. Resolve the project root (the current working directory) and run: ```bash .claude/switch-mcp.sh context7 ``` If `.claude/switch-mcp.sh` does not exist in the current project, check `/var/www/reportmaker/.claude/switch-mcp.sh` as fallback. 2. Inform the user that Context7 will be enabled on next restart. 3. Ask the user if they want to restart now with `/restart` or `/exit`.