KB: suitecrm-dev
← All workspaces4075 results — page 9 of 82
| Title | Domain | Type | Severity | Source | Freshness | Updated |
|---|---|---|---|---|---|---|
| [Workflow] avslutt: ALDRI bruk AskUserQuestion / popup-valgbokser | claude/commands/avslutt | pattern | medium | avslutt.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Alle menyer i denne kommandoen skal vises som **ren tekst** i chatten. Brukeren skriver et tall eller bokstav som svar.
**ALDRI** bruk `AskUserQuestion`-toolen — den mangler ofte valg og er tungvint.
|
||||||
| [Tool usage] audit-masterplan: Code Quality Gate (OBLIGATORISK del av audit — kun for Laravel-apps) | claude/commands/audit-masterplan | api_note | medium | audit-masterplan.md | 88 | 2026-03-20 02:00:03 |
|
Body:
> **Referanse:** Full verktøydetaljer i `coordination/QUALITY-GATES.md`
Audit-rapporten MÅ inkludere en `## Code Quality Verification`-seksjon. Kjør ALLE verktøy:
```bash
# === PHP Quality Gate ===
echo "=== PHPStan + Pint ===" && composer quality:php 2>&1 | tail -10
echo "=== PHPMD ===" && composer quality:phpmd 2>&1 | tail -10
echo "=== PHPArkitect ===" && composer quality:arkitect 2>&1 | tail -5
# === Frontend Quality Gate ===
echo "=== ESLint ===" && npm run lint 2>&1 | tail -5
echo "===...
|
||||||
| [Tool usage] audit-masterplan: Workspace-Deteksjon (OBLIGATORISK FOERSTE STEG) | claude/commands/audit-masterplan | api_note | medium | audit-masterplan.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```bash
if [ -f artisan ]; then basename "$(pwd)"; elif [ "$(basename $(pwd))" = "mcp-servers" ]; then echo "mcp-servers"; elif [ "$(basename $(pwd))" = "magitek-ops" ]; then echo "ops-workspace"; else echo "unknown: $(basename $(pwd))"; fi
```
| Workspace | Agent-fil |
|-----------|----------|
| `reportmaker` / `skymirror` / annen Laravel-app | `~/.claude/agents/audit-masterplan.md` |
| `ops-workspace` (magitek-ops) | `~/.claude/agents/audit-masterplan-ops.md` |
| `mcp-servers` |...
|
||||||
| [Workflow] audit-masterplan: Kontekst-Fordel | claude/commands/audit-masterplan | pattern | medium | audit-masterplan.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Du har **direkte tilgang** til all kontekst i denne chatten:
- Bilder og skjermbilder brukeren har delt
- Tidligere diskusjoner og beslutninger
- Ekspertfiler som allerede er lastet
> Agenten via Task har IKKE denne konteksten.
---
|
||||||
| [Workflow] audit-masterplan: Modell-Forutsetning (VIKTIG!) | claude/commands/audit-masterplan | pattern | medium | audit-masterplan.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Denne kommandoen bruker din **naaværende chat-modell** og innstillinger.
**Anbefalt modell:**
- ✅ Sonnet + Extended Thinking (33x kraft, dyp audit)
- ❌ Haiku (for svak til kode-verifisering)
| Chat-modell | Kraft | Thinking | Egnethet |
|-------------|-------|----------|----------|
| Opus + Thinking | 163x | ✅ Full | Overkill for audit |
| Sonnet + Thinking | 33x | ✅ Begrenset | Anbefalt |
| Sonnet | 8x | ❌ Nei | Ok for smaa MP-er |
| Haiku | 1x | ❌ Nei | For svak |
**Task-delegering...
|
||||||
| [Workflow] audit-masterplan: Post-Implementation Masterplan Audit | claude/commands/audit-masterplan | pattern | medium | audit-masterplan.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**Du er naa i Audit-modus.** Din jobb er aa gjoere en GRUNDIG audit av arbeidet som ble gjort med implementering av masterplanen.
> **Du er IKKE utvikleren.** Du er den paranoide QA-revisoren som IKKE stoler paa noe. Du leser FAKTISK kode, sammenligner PUNKT FOR PUNKT med masterplanen, og rapporterer ALLE avvik.
---
|
||||||
| [Tool usage] architect: Sporsmal 2: Quality Mode (OBLIGATORISK — vent pa svar foer du fortsetter) | claude/commands/architect | api_note | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```
Hvilken Quality Mode vil du bruke for denne masterplanen?
| Mode | Pipeline | Est. kostnad |
|-----------|-------------------------------------------------------|-----------------|
| SPEED | architect → implement | ~150-400k tokens|
| BALANCED | architect → review → implement → audit | ~350-700k tokens|
| THOROUGH | architect → review → revise → implement → audit → quality-audit |...
|
||||||
| [Workflow] architect: Sporsmal 1: Kontekst | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Er vi i en explore → architect flyt? Sjekk:
```bash
ls coordination/explore/ 2>/dev/null | sort -t- -k2 -n | tail -3
```
Hvis relevante EX-rapporter finnes: les dem og bekreft at du refererer til dem i masterplanen.
|
||||||
| [Workflow] architect: OBLIGATORISKE FOERSTESPORSMAL (ALLTID — les disse FOER du gjor noe annet) | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Etter at du har detektert workspace og lest riktig arkitekt-fil, **MUST du stille disse sporsmalene foerst:**
|
||||||
| [Workflow] architect: 5. Bekreft til bruker | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```
Masterplan lagret: coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature-name}/MASTERPLAN.md
Session-state oppdatert med Sources: MP-{NNNN}
Committed og pushet til git.
```
---
|
||||||
| [Tool usage] architect: 4. Fix permissions + Git persistence (OBLIGATORISK!) | claude/commands/architect | api_note | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```bash
./coordination/scripts/fix-permissions.sh
git add coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature-name}/
git add .claude/session-state.md
git commit -m "masterplan: MP-{NNNN} {feature-name}"
git push origin main
```
**Uten steg 3-4 forsvinner masterplanen!** Kun chat-output overlever ikke mellom sesjoner.
|
||||||
| [Workflow] architect: Session Sources | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- MP-{NNNN} ({feature-name})
- EX-{NNNN} ({slug}) — hvis explore-rapport var grunnlag
```
**Hvorfor:** `/avslutt` og `/knowledge-harvest` leser dette feltet for aa propagere kilde-referanser til ekspertfiler. Uten dette mister vi sporbarhet.
|
||||||
| [Workflow] architect: 3. Oppdater session-state med Sources (OBLIGATORISK!) | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Skriv til `.claude/session-state.md` — legg til eller oppdater `## Session Sources` paa toppen:
```markdown
|
||||||
| [Workflow] architect: 2. LAGRE masterplanen til fil (OBLIGATORISK!) | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```bash
# Finn neste MP-nummer
ls coordination/masterplans/active/ 2>/dev/null | sort -t- -k2 -n | tail -1
# Opprett mappe
mkdir -p coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature-name}/
```
**Mappestruktur:**
```
coordination/masterplans/active/MP-{NNNN}-{YYMMDD}-{feature-name}/
├── MASTERPLAN.md # Level 1: Summary + Task Index
├── CONTEXT.md # Level 2: Shared context
└── tasks/ # Level 3: Per-task details
├── TASK-001.md
└── ...
```
|
||||||
| [Workflow] architect: 1. Presenter masterplanen i chatten | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Brukeren skal se den **komplette** masterplanen med alle tasks, konvensjoner og detaljer.
|
||||||
| [Tool usage] architect: Workspace-Deteksjon (OBLIGATORISK FOERSTE STEG) | claude/commands/architect | api_note | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**Foer du gjor noe annet, detekter workspace:**
```bash
# Sjekk workspace-type
if [ -f artisan ]; then
basename "$(pwd)"
elif [ "$(basename $(pwd))" = "mcp-servers" ]; then
echo "mcp-servers"
elif [ "$(basename $(pwd))" = "magitek-ops" ]; then
echo "ops-workspace"
else
echo "unknown: $(basename $(pwd))"
fi
```
**Basert paa resultat, les RIKTIG arkitekt-variant:**
| Workspace | Arkitekt-fil |
|-----------|-------------|
| `reportmaker` |...
|
||||||
| [Workflow] architect: Kontekst-Fordel | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Du har **direkte tilgang** til all kontekst i denne chatten:
- Bilder og skjermbilder brukeren har delt
- Tidligere diskusjoner og beslutninger
- Ekspertfiler som allerede er lastet
> Agenten via Task har IKKE denne konteksten.
---
|
||||||
| [Workflow] architect: Modell-Forutsetning (VIKTIG!) | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Denne kommandoen bruker din **naaværende chat-modell** og innstillinger.
**Anbefalt modell:**
- Opus + Extended Thinking (163x kraft, dyp analyse)
- Sonnet/Haiku er for svak til arkitektur-arbeid
**Task-delegering (garantert riktig modell):**
```
Task(subagent_type=architect,
prompt="Create masterplan for: {feature}")
```
---
|
||||||
| [Workflow] architect: VIKTIG: Vent på instruksjon | claude/commands/architect | pattern | medium | architect.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**IKKE** begynn å jobbe basert på window-tittelen eller konteksten alene.
Rollen er nå satt. Gå videre til workspace-deteksjon og still de obligatoriske spørsmålene. Vent på svar.
**I ready-meldingen, ALLTID inkluder:**
1. Workspace-navn og architect-variant som ble lastet
2. Modell-sjekk: Vis hvilken modell du kjører med, og **advar eksplisitt** hvis du IKKE kjører Opus + Extended Thinking (anbefalt for arkitektur-arbeid). Eksempel:
> ⚠ Du kjører Opus uten Extended Thinking. For dyp...
|
||||||
| [Workflow] agent-meta: VIKTIG: Vent på instruksjon | claude/commands/agent-meta | pattern | medium | agent-meta.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**IKKE** begynn å jobbe basert på window-tittelen eller rolle-konteksten alene.
**IKKE** les filer, analyser kode, eller foreslå løsninger ennå.
Rollen er nå satt. Still dette ene spørsmålet og vent:
> **Hva skal jeg hjelpe med i agent-systemet?**
Vent på brukerens svar før du gjør noe som helst.
---
You are now the **agent-meta meta-agent**.
Read and follow ALL instructions from `~/.claude/agents/agent-meta.md`
The agent file is a **router** — it will detect your workspace from `$PWD`...
|
||||||
| [Workflow] _kb-context: Key Rules | claude/commands/_kb-context | pattern | medium | _kb-context.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- Max 5 results — more wastes tokens
- If 0 results found → say so briefly and continue
- KB gives direction, not complete answers — still read actual files
- Skip if task is purely administrative (commits, renames, etc.)
- Execution time target: under 3 seconds
|
||||||
| [Workflow] _kb-context: 5. Proceed with task | claude/commands/_kb-context | pattern | medium | _kb-context.md | 88 | 2026-03-20 02:00:03 |
|
Body:
After presenting KB context, continue with the actual task. Do NOT ask the user to confirm — just proceed.
|
||||||
| [Workflow] _kb-context: 4. Present results | claude/commands/_kb-context | pattern | medium | _kb-context.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Output the KB results as background context. Format:
```
KB Context for: $TOPIC
[KB output here]
---
Relevant expert files to read:
- [list any expert files mentioned in results]
```
|
||||||
| [Tool usage] _kb-context: 3. Run KB query | claude/commands/_kb-context | api_note | medium | _kb-context.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**Laravel workspace (free-text search):**
```bash
php artisan kb:query "$TOPIC" --limit=5
```
**Laravel workspace (structured lookup — file/domain/masterplan):**
```bash
php artisan kb:context domain:$DOMAIN --limit=5
php artisan kb:context file:$FILE_PATH --limit=5
php artisan kb:context mp:MP-NNNN --limit=5
```
**Non-Laravel workspace:**
```bash
vendor/bin/kb query "$TOPIC" --limit=5 --project-root=$(pwd)
```
|
||||||
| [Tool usage] _kb-context: 2. Detect workspace | claude/commands/_kb-context | api_note | medium | _kb-context.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```bash
PROJECT_ROOT=$(pwd)
```
- If `$PROJECT_ROOT/artisan` exists → Laravel workspace (reportmaker, skymirror)
- Otherwise → non-Laravel workspace (magitek-ops, etc.)
|
||||||
| [Workflow] _kb-context: 1. Extract topic from the user's message | claude/commands/_kb-context | pattern | medium | _kb-context.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Identify 1-3 keywords that represent the main domain or topic:
- "Fix the analysis queue job" → `analysis queue`
- "Update Proxmox backup policy" → `proxmox backup`
- "Add CSV export for customers" → `customer export`
|
||||||
| [Workflow] _kb-context: Instructions | claude/commands/_kb-context | pattern | medium | _kb-context.md | 88 | 2026-03-20 02:00:03 |
|
Body:
You are fetching KB context to inform upcoming work. Follow these steps:
|
||||||
| [Workflow] _kb-context: KB Context | claude/commands/_kb-context | pattern | medium | _kb-context.md | 88 | 2026-03-20 02:00:03 |
|
Body:
Fetch relevant knowledge base context for the current task.
|
||||||
| [Workflow] ui-redesign: Expert Files | claude/commands/ui-redesign | pattern | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- `coordination/experts/suitecrm/CURRENT-architecture.md`
- `~/.claude/agents/suitecrm-specialist/knowledge-metadata.md`
- `~/.claude/agents/suitecrm-specialist/knowledge-extensions.md`
|
||||||
| [Workflow] ui-redesign: SSH Access | claude/commands/ui-redesign | pattern | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```bash
ssh suitecrm "command" # 172.20.0.102
```
|
||||||
| [Workflow] ui-redesign: Key Reference | claude/commands/ui-redesign | pattern | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
SuiteCRM 8 Angular frontend architecture:
```
core/app/core/src/lib/
├── views/ # list, record, create, login, admin, kanban
├── components/ # navbar, table, field-grid, sidebar, pagination
├── fields/ # varchar, email, phone, date, relate, enum, etc.
├── containers/ # sidebar-widget, subpanel, top-widget, record-thread
└── services/ # metadata, API, auth, formatters, extensions
```
These are core paths — **read only, never modify**. Override via `extensions/`.
|
||||||
| [Workflow] ui-redesign: MCP-First Workflow | claude/commands/ui-redesign | pattern | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
1. **Understand current state:**
- `suitecrm` MCP → `get_module_fields` to see field definitions
- `playwright` → navigate to the view, take screenshot, inspect current layout
2. **Design the change:**
- What metadata files need changing?
- What CSS overrides are needed?
- Does this need an Angular extension component?
3. **Implement via override paths only:**
- Metadata → `custom/modules/{Module}/metadata/`
- Extension files → `custom/Extension/modules/{Module}/Ext/`
...
|
||||||
| [Workflow] ui-redesign: Component Overrides (Extension framework) | claude/commands/ui-redesign | pattern | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- **Custom field renderers** — New Angular components for specific field types
- **Custom views** — Override record/list/create views via extension
- **Custom widgets** — Sidebar widgets, top widgets, dashlets
|
||||||
| [Workflow] ui-redesign: Visual Changes (CSS/theme) | claude/commands/ui-redesign | pattern | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- **Colors, spacing, typography** — CSS overrides in extension or custom-overrides.css
- **Component styling** — Target Angular component classes with CSS
- **Responsive adjustments** — Media queries in overrides
|
||||||
| [Workflow] ui-redesign: Layout Changes (metadata overrides) | claude/commands/ui-redesign | pattern | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- **Record views** — Reorder panels, fields, sections in detailviewdefs.php
- **List views** — Change columns, widths, sorting in listviewdefs.php
- **Subpanels** — Add/remove/reorder via layoutdefs.php in Extension framework
- **Search views** — Customize search fields via searchdefs.php
|
||||||
| [Workflow] ui-redesign: FUNDAMENTAL RULE | claude/commands/ui-redesign | pattern | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**ALDRI modifiser SuiteCRM core-kode.** Alt arbeid skjer via:
- `extensions/` — Angular components, custom fields, custom views
- `public/legacy/custom/` — metadata overrides (detailviewdefs, listviewdefs, vardefs)
- CSS overrides — via extension stylesheet eller `public/dist/custom-overrides.css`
- Theme SCSS — via extension, ikke i `core/app/shell/src/themes/`
|
||||||
| [Tool usage] ui-redesign: VIKTIG: Vent på instruksjon | claude/commands/ui-redesign | api_note | medium | ui-redesign.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**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 del av SuiteCRM-UIet skal redesignes?
`[Anbefalt: Sonnet | Effort: high | Thinking: ja]`
---
# UI Redesign — SuiteCRM Dev
You redesign existing SuiteCRM 8 UI through **overrides, extensions, and CSS** — never
by modifying SuiteCRM core code.
|
||||||
| [Workflow] ui-design: Reference Architecture | claude/commands/ui-design | pattern | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- `~/.claude/agents/suitecrm-specialist/knowledge-extensions.md`
- `~/.claude/agents/suitecrm-specialist/knowledge-architecture.md`
- `coordination/experts/suitecrm/CURRENT-architecture.md`
|
||||||
| [Workflow] ui-design: Build & Deploy | claude/commands/ui-design | pattern | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```bash
# After Angular changes in extension:
ssh suitecrm "cd /var/www/suitecrm && yarn run build:{extName}"
# After backend/metadata changes:
ssh suitecrm 'echo "$SUDO_PASS" | sudo -S -u www-data php /var/www/suitecrm/scripts/rebuild_extensions.php 2>/dev/null'
```
|
||||||
| [Workflow] ui-design: Design Process | claude/commands/ui-design | pattern | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
1. **Research:**
- `context7` → SuiteCRM 8 extension documentation, Angular patterns
- `suitecrm` MCP → understand existing module structure
- Read `defaultExt` template: `ssh suitecrm "ls -R /var/www/suitecrm/extensions/defaultExt/"`
2. **Design:**
- Component architecture (which Angular components needed)
- Data model (vardefs, relationships, metadata)
- API needs (does Symfony backend need new endpoints?)
- Styling approach (component SCSS, global overrides)
3....
|
||||||
| [Workflow] ui-design: New Module UI | claude/commands/ui-design | pattern | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- Custom views for new or existing modules
- Custom record layouts via metadata
- Custom list columns and actions
|
||||||
| [Workflow] ui-design: New Widgets & Dashlets | claude/commands/ui-design | pattern | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- Sidebar widgets in `extensions/{ext}/app/src/containers/`
- Top widgets for module views
- Dashboard components
|
||||||
| [Workflow] ui-design: New Custom Field Types | claude/commands/ui-design | pattern | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- Angular component in `extensions/{ext}/app/src/fields/{fieldType}/`
- Template variants: detail, edit, list, filter
- Register in extension module
|
||||||
| [Workflow] ui-design: New Extensions (primary path) | claude/commands/ui-design | pattern | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
```
extensions/{extName}/
├── app/src/
│ ├── extension.module.ts # Entry point
│ ├── components/ # New Angular components
│ ├── fields/ # Custom field type renderers
│ ├── views/ # Custom view components
│ ├── services/ # Custom Angular services
│ └── styles.scss # Extension-specific styling
├── backend/ # Symfony services (autowired)
├── config/
│ ├── extension.php # Extension metadata...
|
||||||
| [Workflow] ui-design: FUNDAMENTAL RULE | claude/commands/ui-design | pattern | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**Vi utvikler ALDRI selve SuiteCRM-koden.** Alt nytt bygges som:
- **Extensions** i `extensions/{extName}/` — Angular frontend + Symfony backend
- **Custom modules** via Module Builder eller Extension framework
- **Custom fields/views** via Extension framework component system
- **Plugins** som selvstendige extensions med egen `extension.php`
|
||||||
| [Tool usage] ui-design: VIKTIG: Vent på instruksjon | claude/commands/ui-design | api_note | medium | ui-design.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**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 designes?
`[Anbefalt: Opus | Effort: high | Thinking: ja]`
---
# UI Design — SuiteCRM Dev
You design **new** SuiteCRM 8 UI: custom modules, plugins, extensions, dashlets, widgets,
and custom views — always upgrade-safe, never modifying core.
|
||||||
| [Tool usage] suitecrm: Workspace Context | claude/commands/suitecrm | api_note | medium | suitecrm.md | 88 | 2026-03-20 02:00:03 |
|
Body:
You are running from `/var/www/suitecrm-dev/` — the dedicated SuiteCRM development workspace.
**Expert files available here:**
- `coordination/experts/suitecrm/CURRENT-architecture.md` — Dual-layer system, stack (v1.1, includes Node.js/Yarn/magitekExt)
- `coordination/experts/suitecrm/CURRENT-customizations.md` — SC-0001 to SC-0009+ registry (v1.3, includes MP-0001)
- `coordination/experts/suitecrm/CURRENT-metadata-patterns.md` — **Komplett PHP metadata-referanse**: displayLogic,...
|
||||||
| [Workflow] suitecrm: VIKTIG: Vent på instruksjon | claude/commands/suitecrm | pattern | medium | suitecrm.md | 88 | 2026-03-20 02:00:03 |
|
Body:
**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):
Klar som SuiteCRM-spesialist. Hva trenger du hjelp med?
`[Anbefalt: Sonnet | Effort: medium | Thinking: nei]`
---
You are now the **SuiteCRM 8 Specialist**.
Read and follow ALL instructions from `~/.claude/agents/suitecrm-specialist.md`
|
||||||
| [Guardrail] solo-dev-light: Safety | claude/commands/solo-dev-light | gotcha | high | solo-dev-light.md | 88 | 2026-03-20 02:00:03 |
|
Body:
- **NEVER modify `core/`** on remote server
- **ALWAYS use `rebuild_extensions.php`** for Extension file changes
- **ALWAYS update customization registry** after changes
|
||||||
| [Workflow] solo-dev-light: When to Escalate | claude/commands/solo-dev-light | pattern | medium | solo-dev-light.md | 88 | 2026-03-20 02:00:03 |
|
Body:
If the change grows beyond 5 files or requires architectural decisions → suggest `/architect`.
|
||||||
Ingestion History
Loading…