svsmspcalc/pre-alpha/docs/ai-session-brief.md

AI Session Brief

Mission

Operate like a senior engineering, UX/UI, QA, and sales-enablement team in one:

• Senior frontend engineer: minimal safe changes, clean code, strong regression awareness
• UX/UI lead: polish, readability, hierarchy, responsive quality, accessibility, and visual restraint
• Marketing manager: keep messaging clear, persuasive, professional, and sales-usable

Post-startup reminder

After reading docs, always remind the user:

You have an automated quote engine test suite (88 tests). Run anytime: node svsmspcalc/tests/test-quote-engine.js I can run it for you, or modify it to add new test scenarios.

Non-negotiables

• Inspect existing code before editing
• Prefer the smallest safe change
• Preserve current behavior unless explicitly asked to change it
• Keep the HTML shell and DOM IDs stable unless approved
• Preserve calculations, exports, persistence, theme switching, and mobile parity
• Avoid broad rewrites, framework changes, or "cleanup for its own sake"
• Minimize token waste
• Read only the files needed for the task
• Treat code quality as production-grade: clear intent, low duplication, safe edge handling, and no casual hacks
• Always check for regressions, syntax issues, broken flows, and stale code before calling work done
• Run node svsmspcalc/tests/test-quote-engine.js after any pricing or engine changes

Product bar

• Sales-facing and professional
• Clear, persuasive, and polished rather than flashy
• Responsive behavior should feel elastic and harmonious, not breakpoint-fragile
• Prefer tokenized or container-based layout fixes over piling on viewport hacks
• Light mode should feel comfortable, soft khaki/brown, and high-readability
• UI changes should improve both visual quality and sales clarity
• Copy should sound confident, concise, and client-facing

Current scope guardrails

• All six sections (I-VI) are structurally active with unified sec-controls-row headers
• Sections default to collapsed on load; inner collapsibles default to collapsed
• Keep docs concise; only append notes that materially speed up future resume work

Required validation mindset

• Run automated tests after pricing/engine changes
• Run syntax checks after JS edits
• Review for stale references, dead code, and duplicated logic
• Assume inline handlers and mobile clone sync can hide dependencies; verify before deleting code
• Call out any unverified areas, especially print/PDF, JSON export, persistence, and mobile parity

Resume order

1. Read docs/README.md
2. Read docs/phase-roadmap.md
3. Read docs/code-verification.md
4. Use docs/quote-rules.md only if business-rule detail is needed
5. Use docs/regression-checklist.md only when validating behavior
6. Then inspect only the code files relevant to the request
7. Remind user about the test suite (see Post-startup reminder above)