- **General workflow:** [docs/llm/README.md](docs/llm/README.md) - **Git workflow:** [docs/llm/07-GITHUB-WORKFLOW.md](docs/llm/07-GITHUB-WORKFLOW.md) - **All bugs/gotchas:** [docs/llm/04-BUGS-OG-FIXES.md](docs/llm/04-BUGS-OG-FIXES.md) - **Architecture:** [docs/llm/01-ARKITEKTUR.md](docs/llm/01-ARKITEKTUR.md) skills: [_gap-posting] ---

**For translation work (Role 1 or 4):** | Resource | Location | |----------|----------| | EXPERT File | `coordination/experts/06-infrastructure/i18n/language-i18n-system/CURRENT.md` | | Lang Files | `resources/lang/{en,nb}/*.php` (23+ files per locale) | | Database Translations | `App\Models\Translation` (polymorphic) | **Key points:** - ~2100 translation keys across 23+ lang files - Keys must exist in BOTH en/ and nb/ - Use `__('file.key')` for static, `$model->translate('field')` for...

**For Role 3 (UI/UX Designer) - Key resources:** | Resource | Location | |----------|----------| | Scoring Dashboard | `/settings/ui-ux-scoring` | | EXPERT File | `coordination/experts/07-ui-frontend/ux-patterns/ui-ux-system/CURRENT.md` | | Route Scores | Use discover-experts.sh (dirs reorganized 2026-02-02) | | Discoveries | Log to pending-updates.json in domain directory | **Workflow:** 1. Score URLs in dashboard (1-10) 2. For fixes: "Fiks layout på /URL" 3. Inspector looks up score + finds...

``` app/ ├── Http/Controllers/ # Route handlers ├── Models/ # Eloquent models └── Services/ # Business logic resources/views/ # Blade templates + partials database/migrations/ # Schema changes (ASK USER FIRST!) docs/llm/ # LLM documentation coordination/ # Orchestrator coordination files ``` skills: [_gap-posting] ---

- **Backend:** Laravel 12, PHP 8.3, MariaDB - **Frontend:** Blade templates, Vanilla JS, Tailwind CSS - **Services:** Puppeteer (Node.js, port 3001), Wappalyzer (Python) - **Environment:** Single production server (no dev/staging separation) skills: [_gap-posting] ---

**NEVER conclude work is "done" without user validation!** You can verify: - ✅ Backend code, database, syntax, tests You CANNOT verify: - ❌ Frontend display, JavaScript errors, UX issues **Always say:** ``` ✅ Backend changes applied ⚠️ FRONTEND VALIDATION REQUIRED Please test these pages: - [List affected pages with links] Status: Waiting for your validation ``` **Reference:** `.claude/agents/includes/frontend-validation-protocol.md` skills: [_gap-posting] ---

**FORBIDDEN (system blocks these):** ```bash php artisan migrate:fresh # ❌ CATASTROPHIC php artisan migrate:reset # ❌ CATASTROPHIC php artisan db:wipe # ❌ CATASTROPHIC ``` **Safe approach:** ```bash # For complex migrations: # 1. Use staging-specialist agent to test in staging DB # 2. Get user approval # 3. Run in production with backup # For simple migrations: php artisan migrate # After user approval ``` skills: [_gap-posting] ---

1. **This IS production** - All changes take immediate effect (except cache) 2. **Multiple LLM sessions** - Use selective git staging always 3. **No test database** - Migration errors affect live database 4. **Cache is mandatory** - Run `optimize:clear` after code changes 5. **Frontend validation required** - Backend fixes ≠ frontend works 6. **File locks matter** - Check before editing (orchestrator coordination) skills: [_gap-posting] ---

```bash # Debug php artisan logs:browser --errors-only tail -f storage/logs/laravel.log # Git (selective staging!) git status git add file1 file2 # Only YOUR files git commit -m "description" git push origin main # ⚠️ CACHE CLEAR (etter PHP-endringer) # HUSK: Navbar-knappen håndterer queue restart automatisk! # Manuell fallback kun hvis knappen ikke fungerer: php artisan optimize:clear # Frontend only (no queue restart needed) npm run build # Tests php artisan test # Database (ask...

| Endret fil | Trenger restart? | Knappen viser | |------------|------------------|---------------| | `app/Jobs/*.php` | ✅ JA | 🔴 Rød | | `app/Services/*.php` | ✅ JA | 🔴 Rød | | `config/*.php` | ✅ JA | 🔴 Rød | | `resources/views/*.blade.php` | ❌ Nei | Grå | | `resources/js/*.js` | ❌ Nei | Grå | **EXPERT fil:** `coordination/experts/05-operations/operations/operations-system/CURRENT.md` skills: [_gap-posting] ---

```bash php artisan queue:restart && php artisan optimize:clear ```

**ETTER at du har endret Jobs/Services/Config-filer:** ``` ✅ Kodeendringer fullført. ⚠️ QUEUE RESTART PÅKREVD! Queue-knappen i navbar bør nå vise RØD pulserende status. Klikk på "Q ↻" knappen i øvre høyre hjørne for å restarte workers. (Eller så oppdateres den automatisk om 30 sekunder) ```

**Det finnes en Queue Restart-knapp i navbar på alle sider!** ``` ┌─────────────────────────────────────────────────────────┐ │ ReportMaker [Customers] [Reports] ... [Q ↻] │ │ ↑ │ │ Queue Restart-knapp │ └─────────────────────────────────────────────────────────┘ ``` **Knappen:** - **Grå** = Alt OK, ingen restart nødvendig - **Rød pulserende** = Kode er endret, TRENGER restart! - **Blå...

**⚠️ #1 CAUSE OF "BUG DOESN'T FIX" FRUSTRATION - NÅ LØST MED UI-KNAPP!**

**IMPORTANT:** When you commit to main, orchestrator worktrees may become out of sync! **How it works:** 1. Orchestrator creates worktree from `main@A` 2. You (solo) commit to main → `main@B` 3. Worktree is still based on `main@A` 4. When orchestrator merges → potential conflicts! **Best practice when worktrees exist:** ```bash # Check for active worktrees WORKTREES=$(git worktree list | grep -v "\[main\]" | wc -l) if [ "$WORKTREES" -gt 0 ]; then echo "⚠️ $WORKTREES active worktree(s)...

**CRITICAL:** Stashing without coordination creates nightmares! **BEFORE stashing:** ```bash # 1. Check what would be stashed git status --porcelain # 2. Ask yourself: "Are ALL these changes MINE?" # - Files I created/edited: ✅ Mine # - Files I don't recognize: ❌ Someone else's work! # - Untracked Event classes, Services: ❌ Probably orchestrator's WIP # 3. If >3 stashes already exist, STOP! git stash list # More than 3? → Clean up first, don't add to the mess ``` **If you find...

**CRITICAL:** Multiple LLM instances work simultaneously! **BEFORE editing files:** ```bash # Check if file is locked by orchestrator ./scripts/solo-check-locks.sh path/to/file.php ``` **BEFORE pushing to main:** ```bash # Check if orchestrator is merging cat coordination/merge_queue.json | jq '.queue[] | select(.status == "merging")' # Check for active worktrees (orchestrator may be working) git worktree list | grep -v "^\S*\s\+\[main\]" ``` **Why:** Prevents git conflicts between parallel...

```bash git add coordination/handoffs/HANDOFF-{NNN}-*.md git commit -m "handoff: {kort beskrivelse}" git push origin main ``` skills: [_gap-posting] ---

[Hva neste sesjon bør gjøre] ```

| File | Change | |------|--------| | path/to/file.php | Beskrivelse |

- [Bugs, mangler, TODO]

- [Konkrete endringer med fil:linje-referanser]

```markdown # HANDOFF-{NNN}: {Kort tittel} **Status:** In Progress / Complete / Blocked **Date:** YYYY-MM-DD **Session:** {solo-mode} on {branch}

``` coordination/handoffs/HANDOFF-{NNN}-{YYMMDD}-{description}.md ```

```bash ls coordination/handoffs/HANDOFF-*.md 2>/dev/null | sort -t- -k2 -n | tail -1 ```

**Når du avslutter en sesjon, SKRIV ALLTID en handoff-fil:**

**coordination/ root must stay clean - only README.md allowed!** ``` ✅ ALWAYS use correct subdirectory: coordination/ ├── handoffs/ ← HANDOFF-{NNN}-{YYMMDD}-{desc}.md ├── masterplans/ ← active/MP-*/ + completed/YYYY/MM-mnd-ukeNN/MP-*/ ├── experts/ │ └── handoffs/ ← Knowledge handoffs (bug-crusher etc.) ├── tasks/ ← TASK-*.md ├── audits/ ← AUDIT-*, ANALYSE-*, GAP-ANALYSIS-*.md ├── task-completion/ ← COMPLETION-*.md ├──...

1. **`sudo` kommandoer** ← ❌ FUNGERER ALDRI! Sløser tokens! - ⚠️ Du har IKKE sudo-tilgang i dette miljøet - ⚠️ Hver sudo-feil = bortkastet API-kall + token-sløsing - ✅ Be brukeren kjøre privilegerte kommandoer manuelt - ✅ Finn alternative løsninger som ikke krever root 2. **`git add .`** ← ❌ NEVER! Stages other LLM's work - ✅ Use: `git add file1 file2` (specific files only) 3. **`git stash`** ← ❌ NEVER without checking! Stashes OTHER agents' work too! - ✅ First: `git status`...

``` DENNE SERVEREN (172.20.0.94): ├─ Apache 2.4 + PHP-FPM 8.3 (IKKE nginx!) ├─ :80 → Apache HTTP ├─ :8081 → Laravel Reverb (WebSocket) ├─ :3001 → Puppeteer (Node.js) └─ Vhost: /etc/apache2/sites-enabled/reportmaker.magitek.no.conf EKSTERN REVERSE PROXY (172.20.0.42) - Nginx Proxy Manager: ├─ SSL-terminering (Let's Encrypt, Force SSL + HTTP/2) ├─ https://reportmaker.magitek.no → http://172.20.0.94:80 └─ /app (WebSocket) → http://172.20.0.94:8081 ❌ ALDRI: nginx-kommandoer (finnes ikke...

``` Handoff Status = "Complete"? ├─ YES + uklar instruksjon → SPØR BRUKER │ "Handoff sier Complete. Hva er neste oppgave?" ├─ YES + klar instruksjon → UTFØR (kun expert hvis trengs) └─ NO (In Progress) → Les expert, evt. plan for kontekst ``` skills: [_gap-posting] ---

| Anti-Pattern | Token Cost | Riktig Tilnærming | |--------------|------------|-------------------| | Lese plan-fil når handoff = "Complete" | ~25k waste | Spør bruker om oppgave | | Lese expert-fil + plan-fil + kildekode | ~50k+ | Les kun det nødvendige | | "Plan Reference:" i expert → les alt | ~25k waste | IGNORER plan-referanser |

``` 1. Handoff-fil FØRST (~1k tokens) → Sjekk "Status:" feltet → Les "Next LLM Instruction" 2. Expert-fil KUN hvis nødvendig (~5k tokens) → Dokumenterer CURRENT state → Gotchas og patterns 3. ALDRI les plan-filer automatisk! (~25k+ tokens) → Plan = historisk "hvordan vi bygde dette" → Kun relevant hvis du skal ENDRE arkitekturen ```

**Kontekst-lasting koster tokens. Les RIKTIG rekkefølge:**

1. **[docs/llm/00-ONBOARDING.md](docs/llm/00-ONBOARDING.md)** ← **READ THIS FIRST!** - 14 CRITICAL RULES (production environment, git workflow, migrations, etc.) - Architecture quick reference - Parallel LLM sessions awareness 2. **[docs/llm/04A-CRITICAL-GOTCHAS.md](docs/llm/04A-CRITICAL-GOTCHAS.md)** - Top 4 silent failure patterns 3. **[docs/llm/02-KODEBASE-KART.md](docs/llm/02-KODEBASE-KART.md)** - File locations and structure skills: [_gap-posting] ---

**If user chooses Role 1 (Local Developer):** → Read [docs/llm/07A-LOCAL-DEVELOPMENT.md](docs/llm/07A-LOCAL-DEVELOPMENT.md) **If user chooses Role 2 (Branch Reviewer):** → Read [docs/llm/07C-BRANCH-REVIEW.md](docs/llm/07C-BRANCH-REVIEW.md) **If user chooses Role 3 (UI/UX Designer):** → Read [docs/llm/07D-UI-UX-DESIGNER.md](docs/llm/07D-UI-UX-DESIGNER.md) → **NEW!** Use Scoring Dashboard: `/settings/ui-ux-scoring` → **NEW!** Read EXPERT:...

- **Context7** — Oppdatert dokumentasjon for Laravel, PHP, JS-biblioteker - **Playwright** — Nettleserautomatisering, skjermbilder, UI-testing - **MySQL** — Direkte DB-spørringer (3-lags sikkerhet, safety hooks aktive) - **Lighthouse** — Ytelse/SEO/tilgjengelighetsrevisjoner - **Accessibility** — WCAG-testing (axe-core) - **CSS** — Stilark-analyse, MDN-dokumentasjon skills: [_gap-posting] ---

**Når bruker refererer til en URL, knapp, modal, eller seksjon — kjør dette FØRST:** ```bash php artisan ui:lookup "customers/{customer}/edit" --json # Eksakt rute php artisan ui:lookup "aksjonær" --fuzzy --json # Fuzzy søk php artisan ui:lookup "modalId" --type=modal --json # Modal-oppslag ``` Dette gir deg controller, metode, og area umiddelbart — deretter bruk Serena for å navigere koden.

**Når du utforsker kode, BRUK SERENA FØR Grep/Read:** ``` 1. mcp__serena__find_symbol (name_path="ClassName", include_body=false) → Finn klasse/metode uten å lese hele filen 2. mcp__serena__get_symbols_overview (relative_path="app/Services/Foo.php") → Se alle metoder/properties i en fil uten å lese den 3. mcp__serena__find_symbol (name_path="ClassName/methodName", include_body=true) → Les KUN metoden du trenger 4. mcp__serena__find_referencing_symbols (symbol_name="methodName") →...

Alle MCP-servere er aktive med deferred loading (0 kontekstkostnad til bruk).

| Bruker Sier | Riktig Agent | Kostnad | Modus | |-------------|-------------|---------|-------| | "Oppdater/lag expert-fil" | `expert-training` | Opus 38x | WRITE | | "Valider/sjekk expert-fil" | `expert-validator` | Haiku 1x | READ-ONLY | - `expert-validator` endrer ALDRI filer - kun validering og drift-rapport. - `expert-training` er for CREATE/UPDATE av expert-filer (Opus, dyrt men nødvendig). skills: [_gap-posting] ---

Ask user immediately: ``` Jeg er på laravelserver-v11. Hvilken rolle har jeg? 1. Local Developer (skriv kode, utvikle features, commit/push) - 35% 2. Branch Reviewer (test Claude Web sin branch, staging-specialist) - 5% 3. UI/UX Designer (test design, accessibility, responsiveness) - 5% 4. Troubleshooter (finn og fiks feil i eksisterende kode) - 50% 5. Rådgiver & Planlegger (strategi, prioritering, roadmap) - 5% Velg 1, 2, 3, 4 eller 5. ``` **Role → Agent mapping:** - Role 1 (Developer) →...

**Available agents with performance/cost metrics:** - `generic-light-perf3-cost1x` - Simple CRUD, repetitive (fastest, cheapest) - `generic-fast-thinking-perf5-cost4x` - Moderate complexity, reasoning ⭐ **BEST VALUE** - `generic-development-perf6-cost8x` - Standard development (balanced) - `generic-balanced-thinking-perf8-cost33x` - Complex cross-domain (deep reasoning) - `generic-quality-perf8-cost38x` - Quality synthesis without reasoning - `generic-heavy-perf10-cost163x` - Architecture,...

**📢 ALLTID VERBOSE (BLOCKING) OUTPUT!** Agenter skal ALDRI kjøres med `run_in_background: true`. Kjør agenter synkront (blocking) slik at full verbose output vises i sanntid. **MANDATORY: Auto-select optimal agent based on task complexity → 30-87% cost savings!**

- Bruker sier "bare fiks", "enkel fix", "quick fix" → Åpenbart triviell - Fixen er synlig (typo, manglende import, syntaksfeil, manglende komma) - Bruker eksplisitt ber om å fortsette i dev-mode - Bruker allerede har identifisert årsak og løsning skills: [_gap-posting] ---

``` 🐛 Dette høres ut som debugging/feilsøking. Dev-agenter er optimalisert for å BYGGE, ikke DIAGNOSTISERE. Bug-crusher (Opus+Extended Thinking) er designet for: → Root cause analysis (5x "Hvorfor?") → Data flow tracing gjennom hele stacken → Systematisk hypotese-eliminering Alternativer: 1. /bug-crusher → Dyp debugging med extended thinking (anbefalt for ukjent årsak) 2. /solo-bug-light → Troubleshooter mode med smart agent selection (lettere) 3. Fortsett her → Hvis det er en...

| Kategori | Nøkkelord | |----------|-----------| | **Direkte** | bug, feil, error, exception, crash, broken, ødelagt, virker ikke, fungerer ikke, feiler | | **Symptomer** | blank side, 500, 404, null, undefined, timeout, spinner, feil data, viser feil, tom, mangler | | **Debugging** | hvorfor, undersøk, finn ut, debug, trace, reproduser, merkelig, rart, uventet |

**Når bruker-prompt inneholder bug/feil-signaler, STOPP og foreslå delegering FØR du starter!**

**Symptom:** Feil som nevner disse mappene: - `/home/heine/.claude/projects/-tmp/` - `/home/heine/.claude/todos/` - `/home/heine/.claude/projects/` **Rotårsak:** `www-data` (webserver-brukeren) mangler skrivetilgang til Claude CLI-mapper. **Løsning - be brukeren kjøre:** ```bash setfacl -R -m u:www-data:rwx /home/heine/.claude/projects/-tmp/ setfacl -d -m u:www-data:rwx /home/heine/.claude/projects/-tmp/ setfacl -R -m u:www-data:rwx /home/heine/.claude/todos/ setfacl -d -m u:www-data:rwx...

**⚠️ CRITICAL: Du har IKKE sudo-tilgang. ALDRI prøv sudo-kommandoer!** ``` ❌ FORBUDT (kaster vekk tokens - fungerer ALDRI): - sudo anything (unntatt: sudo systemctl restart puppeteer-server) - chown - chmod (systemfiler) - apt-get / apt install - systemctl / service (unntatt: puppeteer-server) - mkdir /var/... (utenfor prosjektmappen) - Any command requiring root privileges 🔧 SPESIALTILFELLE - Puppeteer restart (DU KAN): ✅ sudo systemctl restart puppeteer-server (fungerer!) ✅ POST...

**Welcome!** You are now in **SOLO mode** for ReportMaker development. > 💡 **For enklere sesjoner:** Bruk `/solo-light` (548 tokens vs 3800+) > - Ingen orchestrator-kompleksitet > - Parallelle solo-sesjoner på main > - Samme kritiske regler, kompakt format skills: [_gap-posting] ---