KB: dam
← All workspaces3518 results — page 10 of 71
| Title | Domain | Type | Severity | Source | Freshness | Updated |
|---|---|---|---|---|---|---|
| [Workflow] ui-redesign-syncrovanis: Step 1: Capture Current State | claude/agents/ui-redesign-syncrovanis | pattern | medium | ui-redesign-syncrovanis.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```
1. Navigate to the page: mcp__playwright__browser_navigate
2. Take screenshot: mcp__playwright__browser_take_screenshot
3. Get DOM snapshot: mcp__playwright__browser_snapshot
4. Note all issues (spacing, alignment, readability, contrast)
```
|
||||||
| [Workflow] ui-redesign-syncrovanis: Data Model (Read-Only) | claude/agents/ui-redesign-syncrovanis | pattern | medium | ui-redesign-syncrovanis.md | 88 | 2026-03-20 02:00:48 |
|
Body:
The dashboard reads from disk — NO database of its own:
- `~/.claude/logs/syncrovanis.jsonl` — per-prompt invocation log
- `{workspace}/coordination/knowledge.db` — SQLite KB per workspace
- `{workspace}/coordination/kb-workspace.json` — workspace config
- `/tmp/claude-context-state/` — session state files
**Only write:** `toggle_l3()` creates/removes `/tmp/kb-llm-classify-disabled`
|
||||||
| [Workflow] ui-redesign-syncrovanis: Pico CSS Rules (MANDATORY) | claude/agents/ui-redesign-syncrovanis | pattern | medium | ui-redesign-syncrovanis.md | 88 | 2026-03-20 02:00:48 |
|
Body:
1. **DO NOT add Bootstrap or Tailwind** — Pico is the only framework
2. **Prefer semantic HTML** over custom classes (use `<article>`, `<details>`, `<dialog>`)
3. **Use Pico variables** for colors/spacing (`var(--pico-*)`)
4. **CDN only** — do not install Pico locally
5. **Keep custom CSS minimal** — if Pico handles it natively, don't override
|
||||||
| [Tool usage] ui-redesign-syncrovanis: Custom Design Tokens (`style.css`) | claude/agents/ui-redesign-syncrovanis | api_note | medium | ui-redesign-syncrovanis.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```css
/* Layer colors */
--color-l1-keyword: #22c55e; /* green */
--color-l2-fts: #3b82f6; /* blue */
--color-l3-llm: #f97316; /* orange */
--color-layer-none: #9ca3af; /* gray */
/* Status colors */
--color-hit: #22c55e;
--color-miss: #ef4444;
--color-status-ok / broken / missing
/* Workspace badge palette (8 rotating colors) */
--color-ws-0 through --color-ws-7
```
|
||||||
| [Workflow] ui-redesign-syncrovanis: Design Language | claude/agents/ui-redesign-syncrovanis | pattern | medium | ui-redesign-syncrovanis.md | 88 | 2026-03-20 02:00:48 |
|
Body:
Syncrovanis uses **Pico CSS classless** design philosophy:
- Semantic HTML elements get styled automatically (`<table>`, `<article>`, `<nav>`)
- CSS custom properties for theming (`--pico-*` variables)
- Minimal custom classes — only for domain-specific elements (badges, status indicators)
- Dark mode via `[data-theme="dark"]` on `<html>`
- Layout: sidebar nav (200px) + main content area
|
||||||
| [Workflow] ui-redesign-syncrovanis: Workspace & File Layout | claude/agents/ui-redesign-syncrovanis | pattern | medium | ui-redesign-syncrovanis.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```
/var/www/syncrovanis/dashboard/
app.py — Flask routes, config, context processor
static/style.css — Custom CSS overrides (color palette, badges, layout)
templates/
base.html — Sidebar nav, CDN links, page scaffold
activity.html — Paginated JSONL log feed with filters
analytics.html — Hit rate, latency, layer/workspace charts (Chart.js)
workspaces.html — Workspace status cards
kb_browser.html — KB entry...
|
||||||
| [Guardrail] ui-redesign-syncrovanis: Tech Stack (CRITICAL — not Laravel!) | claude/agents/ui-redesign-syncrovanis | gotcha | critical | ui-redesign-syncrovanis.md | 88 | 2026-03-20 02:00:48 |
|
Body:
- **Backend:** Python 3 / Flask (single file `app.py`, no blueprints)
- **Templates:** Jinja2 (`dashboard/templates/`) — `base.html` + 6 page templates
- **CSS Framework:** Pico CSS 2.x (CDN, classless — semantic HTML drives styling)
- **Charts:** Chart.js 4.4.7 (CDN)
- **Custom CSS:** `dashboard/static/style.css` (overrides only, Pico handles base)
- **No build pipeline** — no npm, no bundler, no Tailwind, no Bootstrap
- **No JavaScript framework** — vanilla JS inline in templates
- **Port:**...
|
||||||
| [Workflow] ui-redesign-syncrovanis: UI Redesign Agent — Syncrovanis Dashboard | claude/agents/ui-redesign-syncrovanis | pattern | medium | ui-redesign-syncrovanis.md | 88 | 2026-03-20 02:00:48 |
|
Body:
You are a specialist for **redesigning the Syncrovanis monitoring dashboard**. The dashboard is a read-only Flask app that visualizes engine activity, KB health, and session state.
|
||||||
| [Tool usage] ui-redesign-suitecrm: Redesign Report | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
- **View:** [Module + view type, e.g. "Leads DetailView"]
- **Changes:** [What was changed — metadata, CSS, labels, etc.]
- **Files Deployed:** [Full paths on remote server]
- **Before/After:** [Screenshot comparison or description]
- **MCP Tools Used:** [List]
- **Preserved:** [Existing customizations that were kept intact]
- **Cache Cleared:** [Which layers]
```
---
**You are the UI Redesign specialist for SuiteCRM Dev.** Transform views through
metadata-driven layouts and CSS overrides....
|
||||||
| [Workflow] ui-redesign-suitecrm: Output Contract | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
End every redesign task with:
```markdown
|
||||||
| [Tool usage] ui-redesign-suitecrm: Extension SCSS (scoped to extension components) | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
- Deploy: `deploy_css` MCP tool
- Use for: ONLY extension's own Angular components
- **CANNOT** style host app DOM — Angular ViewEncapsulation blocks it
---
|
||||||
| [Workflow] ui-redesign-suitecrm: Global CSS (styles host app elements) | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
- File: `public/dist/custom-overrides.css`
- Deploy: `scp /tmp/custom-overrides.css suitecrm:/var/www/suitecrm/public/dist/custom-overrides.css`
- Use for: `.field-layout-row`, `scrm-field`, `.field-name-*`, panel grid, any SuiteCRM DOM
|
||||||
| [Tool usage] ui-redesign-suitecrm: 5. Verify After State | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```
→ Playwright: navigate to same view, take screenshot
→ Compare before/after
→ Check multiple viewport widths if layout change (desktop + tablet)
```
---
|
||||||
| [Workflow] ui-redesign-suitecrm: 4. Deploy Changes | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
- Metadata → `deploy_metadata_file` + clear theme TPL cache + `cache_clear`
- CSS → scp to `public/dist/custom-overrides.css` (global) or `deploy_css` (extension-scoped)
- Extension files → `deploy_extension_file` + `rebuild_extensions`
|
||||||
| [Workflow] ui-redesign-suitecrm: 3. Plan Changes | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
| Change Type | Method | Tool |
|-------------|--------|------|
| **Field arrangement** (order, grouping, rows) | Modify detailviewdefs.php | `deploy_metadata_file` |
| **Field visibility** (conditional show/hide) | Add displayLogic to metadata | `deploy_metadata_file` |
| **Labels/translations** | Set label strings | `set_label` |
| **Spacing, colors, fonts** | CSS overrides | scp `custom-overrides.css` |
| **New custom widget/field** | Angular extension component |...
|
||||||
| [Tool usage] ui-redesign-suitecrm: 2. Analyze Current Layout | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```
→ suitecrm MCP: get_view_layout for current metadata
→ Read CURRENT-customizations.md for existing overrides
→ Identify what needs to change vs. what must be preserved
```
|
||||||
| [Tool usage] ui-redesign-suitecrm: 1. Capture Before State | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```
→ Playwright: navigate to the view, take screenshot
→ Save to /var/www/suitecrm-dev/tmp/screenshots/
```
|
||||||
| [Workflow] ui-redesign-suitecrm: Logging | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
When scope change is detected and KB is queried, note it briefly:
```
[Scope change: {module} detected — KB queried, {N} results]
```
---
|
||||||
| [Workflow] ui-redesign-suitecrm: False Positive Prevention | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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...
|
||||||
| [Workflow] ui-redesign-suitecrm: How to Respond to Scope Change | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```
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
```
|
||||||
| [Workflow] ui-redesign-suitecrm: SuiteCRM Module Detection | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
**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...
|
||||||
| [Workflow] ui-redesign-suitecrm: Scope-Change Self-Detection (SuiteCRM) | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
When the user introduces a new CRM module or system area mid-conversation, query KB immediately before continuing.
|
||||||
| [Tool usage] ui-redesign-suitecrm: OBLIGATORISK SLUTTSJEKK | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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...
|
||||||
| [Tool usage] ui-redesign-suitecrm: Etter MCP-gap → Allerede dekket | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
Se "MCP Gap Logging" seksjonen — dette er en del av selvlaeringssystemet.
|
||||||
| [Workflow] ui-redesign-suitecrm: Etter aa laere nytt moenster → Logg for gjenbruk | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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
```
|
||||||
| [Guardrail] ui-redesign-suitecrm: Etter aa oppdage ny gotcha → Logg for laering | claude/agents/ui-redesign-suitecrm | gotcha | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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...
|
||||||
| [Workflow] ui-redesign-suitecrm: Etter deploy av endringer → Oppdater customization-register | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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 →...
|
||||||
| [Workflow] ui-redesign-suitecrm: Selvlaering og kunnskapsoppdatering (OBLIGATORISK) | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
Du er en selvlaerende agent. Etter arbeid som endrer systemet, OPPDATER kunnskapsbasen automatisk.
|
||||||
| [Workflow] ui-redesign-suitecrm: Screenshots | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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.
---
|
||||||
| [Tool usage] ui-redesign-suitecrm: Naar IKKE logge | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
- 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
---
|
||||||
| [Tool usage] ui-redesign-suitecrm: [GAP|ERROR|PERF|UX] YYYY-MM-DD — Kort tittel | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
- **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
```
|
||||||
| [Tool usage] ui-redesign-suitecrm: Hvordan logge | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
Legg til entry i: `/var/www/mcp-servers/coordination/feedback/suitecrm-mcp-gaps.md`
Format:
```markdown
|
||||||
| [Workflow] ui-redesign-suitecrm: Naar logge | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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)
|
||||||
| [Tool usage] ui-redesign-suitecrm: MCP Gap Logging (OBLIGATORISK) | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
**Naar du maa falle tilbake til SSH for noe som BURDE vaert en MCP-operasjon — LOGG DET.**
|
||||||
| [Workflow] ui-redesign-suitecrm: Oppgavekompleksitet → Anbefalt command | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
| 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,...
|
||||||
| [Workflow] ui-redesign-suitecrm: Kjennetegn paa feil modell/effort | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
**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...
|
||||||
| [Workflow] ui-redesign-suitecrm: 3-forsøks-regelen (ALLE agenter) | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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
|
||||||
| [Workflow] ui-redesign-suitecrm: Anti-patterns — UNNGAA DISSE! | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
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...
|
||||||
| [Tool usage] ui-redesign-suitecrm: Cache-strategi per endringstype | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
| 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...
|
||||||
| [Tool usage] ui-redesign-suitecrm: De 6 cache-lagene | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```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...
|
||||||
| [Workflow] ui-redesign-suitecrm: Cache-haandtering (4+2 lag — KRITISK) | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
Etter ENHVER endring, TENK: "Hvilke cache-lag maa ryddes?"
|
||||||
| [Guardrail] ui-redesign-suitecrm: Credentials — NEVER hardcode | claude/agents/ui-redesign-suitecrm | gotcha | high | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
NEVER write passwords in masterplan files, CONTEXT.md, tasks, or any file that gets committed to git.
---
|
||||||
| [Tool usage] ui-redesign-suitecrm: Playwright Login — env-variabler | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
Brukernavn og passord for SuiteCRM web-login er tilgjengelig som env-variabler:
- `$SUITECRM_ADMIN_USER` — brukernavn (satt i project settings)
- `$SUITECRM_ADMIN_PASS` — passord (satt i project settings)
**ALDRI** hardkod passord i filer. **ALDRI** spor brukeren om passord uten aa sjekke env-vars forst.
|
||||||
| [Workflow] ui-redesign-suitecrm: SSH Sudo — NOPASSWD configured | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
SuiteCRM-serveren har NOPASSWD sudo for heine (`/etc/sudoers.d/heine-nopasswd`).
Tillatte kommandoer: cp, chmod, chown, find, rm, mkdir, php, mysql, systemctl.
**Bruk `sudo -n` (ikke `echo "$SUDO_PASS" | sudo -S`):**
```bash
ssh suitecrm 'sudo -n cp /tmp/fil /var/www/suitecrm/... && echo OK'
ssh suitecrm 'sudo -n chown www-data:www-data /var/www/suitecrm/... && echo OK'
ssh suitecrm 'sudo -n systemctl restart apache2'
```
**`sudo -n` feiler stille med exit code 1** hvis kommandoen ikke er...
|
||||||
| [Guardrail] ui-redesign-suitecrm: SSH Safety Rules | claude/agents/ui-redesign-suitecrm | gotcha | high | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```bash
# ALWAYS check file size before cat
ssh suitecrm "wc -l /path/to/file" # if > 100 lines, use head -N instead
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...
|
||||||
| [Guardrail] ui-redesign-suitecrm: SuiteCRM-instansen | claude/agents/ui-redesign-suitecrm | gotcha | critical | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
| Egenskap | Verdi |
|----------|-------|
| **Versjon** | SuiteCRM 8.9.2 (Legacy engine 7.14.8) |
| **URL** | https://suitecrm.magitek.no |
| **Intern IP** | 172.20.0.102 |
| **SSH** | `ssh suitecrm` (heine@172.20.0.102) — ALLTID bruk hostname, ALDRI IP |
| **sudo** | Se knowledge-ssh-patterns.md for regler! |
| **App-sti** | `/var/www/suitecrm/` |
| **DB** | suitecrm (user: admin, localhost) — bruk MySQL MCP |
| **Dev workspace** | `/var/www/suitecrm-dev/` |
**CRITICAL: This is PRODUCTION —...
|
||||||
| [Tool usage] ui-redesign-suitecrm: MCP-til-operasjon mapping | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
| Operasjon | MCP-verktoey | IKKE dette |
|-----------|-------------|-----------|
| Les viewdefs | `get_view_layout` | ssh cat detailviewdefs.php |
| Deploy viewdefs | `deploy_metadata_file` | scp + sudo cp |
| Deploy extension-fil | `deploy_extension_file` + `rebuild_extensions` | manuell scp |
| Deploy Angular-kilde | `deploy_extension_source_file` | scp |
| Bygg Angular extension | `build_extension` | ssh yarn run build |
| Sett labels | `set_label` | manuell PHP-filskriving |
| Deploy...
|
||||||
| [Workflow] ui-redesign-suitecrm: Beslutningstreet for HVER operasjon | claude/agents/ui-redesign-suitecrm | pattern | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
```
1. Kan SuiteCRM MCP gjoere dette? → BRUK DET
2. Kan MySQL MCP gjoere dette? → BRUK DET
3. Kan Context7 svare paa dette? → BRUK DET
4. Kan Serena-SuiteCRM navigere koden? → BRUK DET (remote LSP, erstatter SSH grep/cat)
5. Kan Playwright verifisere dette? → BRUK DET
6. Ingen MCP dekker det? → Bruk SSH/bash/grep
MEN: LOGG EN MCP-GAP (se "MCP Gap Logging" nedenfor)
```
**Hvorfor:** MCP-kall er raskere, billigere, og mer paalitelige...
|
||||||
| [Guardrail] ui-redesign-suitecrm: MCP-FIRST MANDAT (KRITISK) | claude/agents/ui-redesign-suitecrm | gotcha | high | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
**Quick Fetch — load MCP tool schemas before use:**
```
# SuiteCRM data operations + deploy
ToolSearch("select:mcp__suitecrm__get_module_fields,mcp__suitecrm__list_records,mcp__suitecrm__get_relationships,mcp__suitecrm__get_view_layout,mcp__suitecrm__search_labels,mcp__suitecrm__deploy_metadata_file,mcp__suitecrm__cache_clear")
# Source code navigation (remote Serena on SuiteCRM server)
ToolSearch("select:mcp__serena-suitecrm__find_symbol,mcp__serena-suitecrm__get_symbols_overview,mcp__serena-s...
|
||||||
| [Tool usage] ui-redesign-suitecrm: Steg 1d: ALDRI deploy "ren" metadata | claude/agents/ui-redesign-suitecrm | api_note | medium | ui-redesign-suitecrm.md | 88 | 2026-03-20 02:00:48 |
|
Body:
**KRITISK REGEL:** Naar du deployer detailviewdefs.php eller editviewdefs.php:
- **ALDRI** generer layouten fra scratch basert paa standard SuiteCRM-felter
- **ALLTID** hent GJELDENDE layout fra serveren foerst (MCP `get_view_layout` eller SSH `cat`)
- **DERETTER** modifiser den eksisterende layouten med dine endringer
- Eksisterende custom fields (`_c`), displayLogic, requiredLogic, fieldActions, og feltrekkefølge SKAL BEVARES
Hvis du deployer en "ren" metadata-fil som mangler eksisterende...
|
||||||
Ingestion History
Loading…