feat(ultraplan-local): v1.6.0 — /ultraresearch-local deep research command
Add /ultraresearch-local for structured research combining local codebase analysis with external knowledge via parallel agent swarms. Produces research briefs with triangulation, confidence ratings, and source quality assessment. New command: /ultraresearch-local with modes --quick, --local, --external, --fg. New agents: research-orchestrator (opus), docs-researcher, community-researcher, security-researcher, contrarian-researcher, gemini-bridge (all sonnet). New template: research-brief-template.md. Integration: --research flag in /ultraplan-local accepts pre-built research briefs (up to 3), enriches the interview and exploration phases. Planning orchestrator cross-references brief findings during synthesis. Design principle: Context Engineering — right information to right agent at right time. Research briefs are structured artifacts in the pipeline: ultraresearch → brief → ultraplan --research → plan → ultraexecute. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen
commit
baa2d0220b
488 changed files with 213221 additions and 0 deletions
|
|
@ -0,0 +1,256 @@
|
|||
# Diagram Prompt Templates for Imagen 3
|
||||
|
||||
**Sist oppdatert:** 2026-02 (v1.0)
|
||||
**Målgruppe:** diagram-generation-agent
|
||||
**Format:** Prompt-maler for `mcp__mcp-image__generate_image` (Imagen 3 / Nano Banana Pro)
|
||||
|
||||
---
|
||||
|
||||
## Azure-stilkonstanter
|
||||
|
||||
Alle diagrammer skal følge Microsofts visuelle identitet:
|
||||
|
||||
| Element | Verdi |
|
||||
|---------|-------|
|
||||
| Primærfarge | `#0078D4` (Azure Blue) |
|
||||
| Sekundærfarge | `#50E6FF` (Azure Cyan) |
|
||||
| Aksentfarge | `#FFB900` (Warning/Gold) |
|
||||
| Bakgrunn | Hvit eller svært lys grå |
|
||||
| Fontstil | Clean sans-serif (Segoe UI-lignende) |
|
||||
| Ikondesign | Flat, moderne, Microsoft Fluent-stil |
|
||||
| Layout | Venstre-til-høyre eller topp-til-bunn |
|
||||
| Aspect ratio | 16:9 (standard for presentasjoner) |
|
||||
|
||||
### Generelle regler for alle diagrammer
|
||||
|
||||
- Bruk flat design med tydelige bokser og piler
|
||||
- Unngå 3D-effekter, skygger eller gradienter
|
||||
- Tekst skal være stor nok til å lese i en presentasjon
|
||||
- Bruk Azure-ikoner der mulig (stiliserte, ikke detaljerte)
|
||||
- Grupper relaterte komponenter med fargebokser
|
||||
- Nummerer steg i dataflyt-diagrammer
|
||||
|
||||
---
|
||||
|
||||
## Mal 1: Arkitekturoversikt
|
||||
|
||||
**Brukes i:** S8.2 (alltid, alle kompleksitetsnivåer)
|
||||
**Formål:** Vise hele løsningens arkitektur med komponenter og dataflyten mellom dem.
|
||||
|
||||
### Prompt-mal
|
||||
|
||||
```
|
||||
Professional Microsoft Azure architecture diagram in flat design style.
|
||||
|
||||
Components: [KOMPONENT_LISTE]
|
||||
|
||||
Layout: Clean left-to-right or top-to-bottom flow diagram showing data flow between components.
|
||||
|
||||
Visual style:
|
||||
- Azure blue (#0078D4) for primary services
|
||||
- Cyan (#50E6FF) for data stores
|
||||
- White background with light gray grouping boxes
|
||||
- Flat modern icons for each Azure service (Fluent design style)
|
||||
- Clear labeled arrows showing data flow direction
|
||||
- Component names in clean sans-serif font
|
||||
- Grouped by layer: User → Orchestration → AI Services → Data
|
||||
|
||||
Technical diagram, presentation quality, 16:9 aspect ratio, no 3D effects, no gradients.
|
||||
```
|
||||
|
||||
### Eksempel (Copilot Studio + RAG)
|
||||
|
||||
```
|
||||
Professional Microsoft Azure architecture diagram in flat design style.
|
||||
|
||||
Components:
|
||||
- User (browser/Teams) connects to Copilot Studio
|
||||
- Copilot Studio orchestrates the flow
|
||||
- Azure OpenAI (GPT-4o) processes queries
|
||||
- Azure AI Search provides RAG retrieval
|
||||
- SharePoint Online as document source
|
||||
- Azure AI Content Safety filters content
|
||||
- Microsoft Entra ID handles authentication
|
||||
- Application Insights monitors the system
|
||||
|
||||
Layout: Clean top-to-bottom flow diagram showing data flow between components.
|
||||
|
||||
Visual style:
|
||||
- Azure blue (#0078D4) for primary services
|
||||
- Cyan (#50E6FF) for data stores
|
||||
- White background with light gray grouping boxes
|
||||
- Flat modern icons for each Azure service (Fluent design style)
|
||||
- Clear labeled arrows showing data flow direction
|
||||
- Grouped by layer: User → Orchestration → AI/Search → Data → Security/Monitoring
|
||||
|
||||
Technical diagram, presentation quality, 16:9 aspect ratio, no 3D effects, no gradients.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Mal 2: Sikkerhetssoner
|
||||
|
||||
**Brukes i:** S5.1 (middels + kompleks)
|
||||
**Formål:** Vise sikkerhetslag, tilgangskontroll og databeskyttelse.
|
||||
|
||||
### Prompt-mal
|
||||
|
||||
```
|
||||
Microsoft Azure security zones architecture diagram in flat design style.
|
||||
|
||||
Security layers:
|
||||
- External zone: [EKSTERNE_KOMPONENTER]
|
||||
- DMZ / Edge: [EDGE_KOMPONENTER]
|
||||
- Application zone: [APP_KOMPONENTER]
|
||||
- Data zone: [DATA_KOMPONENTER]
|
||||
- Management zone: [MGMT_KOMPONENTER]
|
||||
|
||||
Visual style:
|
||||
- Concentric colored zones from outside (red-tinted) to inside (green-tinted)
|
||||
- Azure blue (#0078D4) for identity services
|
||||
- Gold (#FFB900) for security checkpoints
|
||||
- Lock icons at zone boundaries
|
||||
- Shield icon for Content Safety
|
||||
- Key icon for encryption/Key Vault
|
||||
- Clean labeled arrows showing allowed traffic flow
|
||||
|
||||
Security architecture diagram, presentation quality, 16:9 aspect ratio, no 3D effects.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Mal 3: Dataflyt / RAG-pipeline
|
||||
|
||||
**Brukes i:** S4.3 (når RAG er involvert)
|
||||
**Formål:** Vise how data flows through the RAG pipeline from source to response.
|
||||
|
||||
### Prompt-mal
|
||||
|
||||
```
|
||||
Microsoft Azure RAG (Retrieval-Augmented Generation) pipeline diagram in flat design style.
|
||||
|
||||
Pipeline steps:
|
||||
1. Data ingestion: [DATAKILDER] → Document processing
|
||||
2. Chunking: [CHUNKING_STRATEGI]
|
||||
3. Embedding: [EMBEDDING_MODELL] generates vectors
|
||||
4. Indexing: Vectors stored in [INDEKS_TJENESTE]
|
||||
5. Query flow: User query → [ORKESTRERING] → Hybrid search → Reranking
|
||||
6. Generation: Retrieved context + query → [LLM_MODELL] → Response
|
||||
7. Safety: [SIKKERHETSTILTAK]
|
||||
|
||||
Visual style:
|
||||
- Numbered steps flowing left to right
|
||||
- Azure blue (#0078D4) for AI services
|
||||
- Cyan (#50E6FF) for data stores and indexes
|
||||
- Green for successful output
|
||||
- Orange arrows for data ingestion pipeline (top)
|
||||
- Blue arrows for query pipeline (bottom)
|
||||
- Two parallel lanes: Ingestion (top) and Query (bottom)
|
||||
|
||||
Technical RAG pipeline diagram, presentation quality, 16:9 aspect ratio, no 3D effects.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Mal 4: Problem → Løsning
|
||||
|
||||
**Brukes i:** S2.1 (middels + kompleks)
|
||||
**Formål:** Visuelt kontrastere nåsituasjon (problem) med fremtidig situasjon (løsning).
|
||||
|
||||
### Prompt-mal
|
||||
|
||||
```
|
||||
Before and after comparison diagram for AI solution implementation.
|
||||
|
||||
Left side (BEFORE - current state):
|
||||
- Title: "Nåsituasjon"
|
||||
- [PROBLEM_ELEMENTER]
|
||||
- Visual tone: Gray, cluttered, manual process indicators
|
||||
- Red warning indicators for pain points
|
||||
|
||||
Right side (AFTER - with AI solution):
|
||||
- Title: "Med AI-løsning"
|
||||
- [LØSNING_ELEMENTER]
|
||||
- Visual tone: Azure blue, streamlined, automated flow
|
||||
- Green checkmarks for improvements
|
||||
|
||||
Center: Large arrow pointing from left to right with "[PLATTFORM]" label
|
||||
|
||||
Visual style:
|
||||
- Split layout: left (gray/red) vs right (blue/green)
|
||||
- Clean icons representing users, processes, systems
|
||||
- Metrics showing improvement (e.g., "14 dager → 2 timer")
|
||||
- Azure blue (#0078D4) dominates the right side
|
||||
- Professional infographic style
|
||||
|
||||
Comparison diagram, presentation quality, 16:9 aspect ratio, no 3D effects.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Mal 5: Implementeringstidslinje
|
||||
|
||||
**Brukes i:** S9.1 (middels + kompleks)
|
||||
**Formål:** Vise faseplan med milepæler og leveranser over tid.
|
||||
|
||||
### Prompt-mal
|
||||
|
||||
```
|
||||
Implementation roadmap timeline diagram for Microsoft AI project.
|
||||
|
||||
Phases:
|
||||
- Phase 0: Preparation - [FORBEREDELSE_AKTIVITETER]
|
||||
- Phase 1: POC - [POC_AKTIVITETER]
|
||||
- Phase 2: MVP - [MVP_AKTIVITETER]
|
||||
- Phase 3: Production - [PRODUKSJON_AKTIVITETER]
|
||||
- Phase 4: Optimization - [OPTIMALISERING_AKTIVITETER]
|
||||
|
||||
Key milestones: [MILEPÆLER]
|
||||
|
||||
Visual style:
|
||||
- Horizontal timeline flowing left to right
|
||||
- Phase blocks as colored segments growing in width
|
||||
- Azure blue (#0078D4) gradient from light (Phase 0) to dark (Phase 3)
|
||||
- Gold (#FFB900) diamond markers for milestones
|
||||
- Small icons above each phase representing key activities
|
||||
- Clean sans-serif labels
|
||||
- Go/No-Go decision points marked clearly
|
||||
|
||||
Project roadmap diagram, presentation quality, 16:9 aspect ratio, no 3D effects.
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Imagen 3-spesifikke tips
|
||||
|
||||
### Hva fungerer godt
|
||||
- Klare, beskrivende prompts med eksplisitt layout
|
||||
- Spesifisering av farger med hex-koder
|
||||
- "Professional", "technical diagram", "flat design" som stilord
|
||||
- Eksplisitt aspect ratio (16:9)
|
||||
- Numbered lists for sekvensielle flytsteg
|
||||
|
||||
### Hva bør unngås
|
||||
- For mye tekst i prompten (hold under 300 ord)
|
||||
- Vage instruksjoner ("make it look nice")
|
||||
- Krav om spesifikke fonter (modellen velger selv)
|
||||
- Detaljerte Azure-ikonkrav (beskriv heller stilen)
|
||||
- Forventning om lesbar tekst i diagrammet (bruk heller få, store labels)
|
||||
|
||||
### Bildekvalitet
|
||||
- Be alltid om "presentation quality"
|
||||
- Spesifiser 16:9 for slides, 1:1 for dokumenter
|
||||
- Unngå å be om for mange elementer (maks 10-12 bokser)
|
||||
- Grupper elementer i lag for bedre lesbarhet
|
||||
|
||||
---
|
||||
|
||||
## For diagram-generation-agent
|
||||
|
||||
Bruk disse malene som utgangspunkt, men tilpass til det spesifikke scenarioet:
|
||||
|
||||
1. **Velg riktig mal** basert på diagramtype fra oppdraget
|
||||
2. **Erstatt placeholder-tekst** ([KOMPONENT_LISTE] etc.) med reelle verdier fra arkitekturbeslutningene
|
||||
3. **Tilpass visuell stil** til kompleksitetsnivået — enklere for enkel, mer detaljert for kompleks
|
||||
4. **Generer bildet** med `mcp__mcp-image__generate_image`
|
||||
5. **Hvis generering feiler** — returner den ferdig utfylte promptteksten så brukeren kan bruke den manuelt
|
||||
Loading…
Add table
Add a link
Reference in a new issue