mmintel/mintel.me
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Refine PDF module labels and styling, and add a divider to the sitemap module.

Browse Source
This commit is contained in:
Marc Mintel
2026-02-03 19:41:06 +01:00
parent 3e70b00abc
commit 38f2b871b9
10 changed files with 176 additions and 151 deletions
Download Patch File Download Diff File Expand all files Collapse all files

78
scripts/ai-estimate.ts
View File

@@ -360,15 +360,16 @@ ${tone}
### OBJECTIVE:
1. **briefingSummary**: Summarize the project's essence for the CUSTOMER.
- FOLLOW PRINCIPLE 1 & 5: Clear, direct, no marketing fluff.
- **MIRROR TEST**: Capture unique customer "hooks" or personality (e.g., if they mention an Instagram account or a specific hobby/preference that influences the project vibe).
- Focus 100% on the BRIEFING (TRUTH SOURCE). Ignore the CRAWL context for this narrative.
- Keep it 2-3 professional, direct sentences.
- FOLLOW PRINCIPLE 1, 5 & 6: Clear, direct, no marketing fluff.
- **TONE**: Write naturally in the Ich-Form. Avoid starting every sentence with "Ich".
- **MIRROR TEST**: Capture unique customer "hooks" or personality.
- Focus 100% on the BRIEFING (TRUTH SOURCE).
2. **designVision**: A solid, grounded, and high-quality description of the look & feel.
- FOLLOW PRINCIPLE 1 & 3: Fact-based, professional, high density of information.
- **BESPOKE ELEMENTS**: If the client mentions specific layout ideas (e.g., "Timeline", "Grid", "Industrial Tiles"), incorporate these as strategic decisions.
- **NO ARROGANCE**: Eliminate all "high-end", "world-class", "dominance" language. Be humble and precise.
- **SIMPLE & CLEAR**: Use simple German. No buzzwords. "Solid Industrial Design" instead of "Technocratic Sovereignty".
- FOLLOW PRINCIPLE 1, 3 & 6: Fact-based, professional, high density of information.
- **TONE**: Natural Ich-Form. Focus on the execution and technical decisions.
- **BESPOKE ELEMENTS**: If the client mentions specific layout ideas, incorporate these.
- **NO ARROGANCE**: Eliminate all "high-end", "world-class" language.
- **SIMPLE & CLEAR**: Use simple German. No buzzwords.
- 3-5 sentences of deep analysis.
### OUTPUT FORMAT (Strict JSON):
@@ -421,34 +422,38 @@ You are a Senior Solution Architect. Your goal is ABSOLUTE TRANSPARENCY for the
Each position in the quote must be perfectly justified and detailed.
### POSITION TITLES:
"Basis Website Setup", "Individuelle Seiten", "System-Module", "Logik-Funktionen", "Schnittstellen (API)", "Inhaltsverwaltung (CMS)".
"Basis Website Setup", "Individuelle Seiten", "System-Module", "Logik-Funktionen", "Visuelle Inszenierung", "Komplexe Interaktion", "Schnittstellen (API)", "Inhaltsverwaltung (CMS)", "Sorglos-Betrieb (Hosting)".
### MAPPING RULES (STRICTLY BASED ON PRICING.MD):
- **Basis Website Setup**: Includes Infrastructure, Hosting Setup, Basic SEO, Cookie-Consent (!), Design-Template.
- **System-Module (Features)**: ONLY closed data systems: [Blog, News, Products, Jobs, Cases/References, Events].
- NEVER put "Video Player", "Cookies", "Animations" here.
- **Logik-Funktionen**: Functional logic like: Search, Filter, Forms, PDF-Export, Multi-lang.
- **Schnittstellen (API)**: REAL Data Syncs (CRM, ERP). DO NOT include Tracking, Google Maps, or simple Video embedding here. Basic embedding is "Basis Website Setup".
- **Sorglos-Betrieb (Hosting)**: Hosting & Maintenance.
- **Basis Website Setup**: Infrastructure, Hosting, SEO-Basics, Cookie-Consent, Staging/Production.
- **Individuelle Seiten**: Layout and structure for specific pages (e.g. Home, Services).
- **System-Module (Features)**: Closed systems with data structures (Blog, News, Products, Jobs, References).
- **Logik-Funktionen**: Pure logic (Search, Filter, Forms, PDF-Export, Multi-lang).
- **Visuelle Inszenierung**: Hero-Story, visual flows, Scroll-effects.
- **Komplexe Interaktion**: UI-experiences like Configurators or multi-step processes.
- **Schnittstellen (API)**: REAL Data Syncs (CRM, ERP, Stripe).
- **Inhaltsverwaltung (CMS)**: Setup and mapping for Headless CMS.
- **Sorglos-Betrieb (Hosting)**: Hosting, Updates, Backups.
### RULES FOR positionDescriptions (STRICT):
1. **ZERO GENERALIZATION**: Do NOT say "Verschiedene Funktionen".
2. **ITEMIZED SYNTHESIS**: Mention EVERY component selected in Pass 1.
3. **HARD SPECIFICS**: Preserve technical details from the briefing (e.g., "110 kV", "HDD-Bohrtechnik", specific industry standards).
4. **BREVITY & DENSITY**: Max 1-2 short sentences. Focus on TASKS not RESULTS.
5. **STYLE**: Direct, engineering-grade, no fluff.
6. **LANGUAGE**: 100% GERMAN.
1. **NO "ICH-FORM"**: Do NOT use "Ich" or "Mein". Lead with the action or component.
2. **CONCISE & ITEM-BASED**: Use short, technical sentences. Focus on WHAT is delivered.
3. **ZERO GENERALIZATION**: Do NOT say "Verschiedene Funktionen".
4. **ITEMIZED SYNTHESIS**: Mention EVERY component selected in Pass 1.
5. **HARD SPECIFICS**: Preserve technical details from the briefing (e.g., "110 kV", "HDD-Bohrtechnik").
6. **STYLE**: Direct, engineering-grade, 100% GERMAN.
7. **SPECIFIC - PAGES**: For "Individuelle Seiten", list the pages as a comma-separated list.
8. **SPECIFIC - API**: Video Uploads, Google Maps, and Tracking are NOT APIs.
9. **SPECIFIC - HOSTING**: Always append: "Inkl. 20GB Speicher. Auto-Erweiterung +10€/10GB."
10. **SPECIFIC - LOGIC**: Describe the ACTUAL logic. NEVER use generic terms like "Erweiterte Formulare" or "Individuelle Formular-Logik".
11. **STRICT KEYS**: Keys MUST be EXACTLY: "Basis Website Setup", "Individuelle Seiten", "System-Module", "Logik-Funktionen", "Schnittstellen (API)", "Inhaltsverwaltung (CMS)", "Sorglos-Betrieb (Hosting)".
8. **SPECIFIC - HOSTING**: Always append: "Inkl. 20GB Speicher."
9. **SPECIFIC - LOGIC**: Describe the ACTUAL logic. NEVER use generic terms.
10. **STRICT KEYS**: Keys MUST be EXACTLY the ones defined in POSITION TITLES.
### EXAMPLES (FEW-SHOT):
- **BAD**: "Individuelle Seiten für die Unternehmensdarstellung."
- **GOOD**: "Erstellung der Seiten: Startseite (Video-Hero), Über uns (Timeline), Leistungen (110kV Montage), Kontakt."
- **BAD**: "Anbindung von externen Systemen."
- **GOOD**: "Native Integration von Google Maps zur Standortermittlung inkl. individueller Marker-Logik."
- **BAD**: "Ich entwickle die Seiten: Startseite, Leistungen, Kontakt."
- **GOOD**: "Erstellung der Seiten: Startseite (Video-Hero), Über uns (Timeline), Leistungen, Kontakt."
- **BAD**: "Ich binde Google Maps an."
- **GOOD**: "Native API-Integration von Google Maps mit individueller Standort-Visualisierung."
- **BAD**: "Ich programmiere Scroll-Effekte."
- **GOOD**: "Visuelle Inszenierung der Meilensteine durch Scroll-aktivierte Timeline-Elemente."
### FORBIDDEN PHRASES:
- "Erweiterte Formulare", "Verschiedene Funktionen", "Allgemeine Logik", "Optimierte Darstellung", "Individuelle Formular-Logik".
@@ -478,11 +483,20 @@ You are the "Industrial Critic". Your goal is to catch quality regressions and e
Analyze the CURRENT_STATE against the BRIEFING_TRUTH.
### CRITICAL ERROR CHECKLIST (FAIL IF FOUND):
1. **Placeholder Leakage**: Catch "null", "undefined", or generic strings like "Verschiedene Funktionen", "Erweiterte Formulare", "Individuelle Formular-Logik".
2. **Detail Loss**: The user mentioned specific terms (e.g., "110 kV", "HDD", "Timeline", "Instagram"). Are they present in the positionDescriptions or sitemap? If not, ADD THEM.
1. **Placeholder Leakage**: Catch "null", "undefined", or generic strings like "Verschiedene Funktionen", "Erweiterte Formulare".
2. **Detail Loss**: The user mentioned specific terms. Are they present? If not, ADD THEM.
3. **Consistency**: Ensure the count of pages in "Individuelle Seiten" matches the sitemap pages.
4. **Deadlines**: Ensure relative dates (e.g., "April / Mai") are resolved to the year 2026.
5. **Tone Drift**: Remove any marketing "fluff" or "sales-y" language. Maintain the "Industrial Design" persona.
5. **TONE & WORDING FAILURE**:
- FAIL if "Ich" or "Mein" is used in positionDescriptions.
- FAIL if "wir" or "unser" is used anywhere.
- FAIL if a sentence in briefingSummary is too long or marketing-heavy.
- FAIL if "möglicherweise", "grundsätzlich", "in der Regel" is used.
- FAIL if passive voice ("es wird") is used.
6. **MAPPING FAILURE**:
- FAIL if visual elements (Scroll-Effekte, Slider, Hover) are in "Logik-Funktionen". They MUST be in "Visuelle Inszenierung".
- FAIL if multi-step forms or calculators are in "Logik-Funktionen". They MUST be in "Komplexe Interaktion".
7. **PROMPT REWRITE**: If you find any of these errors, rewrite the field entirely to be 100% compliant.
### MISSION:
Return updated fields ONLY. Specifically focus on hardening 'positionDescriptions', 'sitemap', and 'briefingSummary'.