Skip to content

Latest commit

 

History

History
66 lines (48 loc) · 2.31 KB

File metadata and controls

66 lines (48 loc) · 2.31 KB

claude.md — Project Constitution (Autoblysk)

This file is LAW. All schemas, rules, and architectural invariants live here. Only updated when a schema changes, a rule is added, or architecture is modified.


Project Identity

  • Project: Autoblysk
  • Base Template: Polaris360 Starter (pushly-template)
  • Type: Whitelabel auto-industry website
  • Stack: React 19 / TypeScript / Vite 7 / Tailwind 4 / Framer Motion

Discovery Answers

# Question Answer
1 North Star Reusable mockup website for auto detailing businesses, starting with Auto-Błysk
2 Integrations Vercel + Google Maps embed now; prepared for GoHighLevel webhooks later
3 Source of Truth Facebook page data → site.config.ts
4 Delivery Payload Local build for now
5 Behavioral Rules Polish only, orange/dark/white color scheme, premium + friendly tone, Pexels videos

Data Schemas

Input: site.config.ts

(To be fully defined after reading the complete config shape)

Output: Static SPA

  • Vite build → dist/ folder
  • Single-page app with Polish-only routing
  • Deployment: local for now, Vercel later

Behavioral Rules

  1. Language: Polish only — remove all multi-language switching
  2. Color scheme: Match logo — orange (#E8872A), white (#FFFFFF), dark background (#1A1A1A / carbon texture)
  3. Tone: Premium but friendly — professional without being cold
  4. Videos: Use Pexels stock footage (auto detailing / car care)
  5. GoHighLevel: App structure must support future webhook integration (contact forms, lead capture)
  6. No public pricing: TBD (user to confirm)
  7. Reusable: Config must remain easy to swap for a different client

Architectural Invariants

  1. site.config.ts is the single source of truth for all client-specific data
  2. Locale JSON files (src/i18n/locales/) hold all user-facing text
  3. No backend — pure static SPA deployed to Vercel
  4. All temporary/intermediate files go in .tmp/
  5. Architecture SOPs live in architecture/
  6. Deterministic tool scripts live in tools/
  7. .env holds secrets (verified in Link phase)
  8. Golden Rule: If logic changes, update the SOP before updating the code

Maintenance Log

(Updated during Trigger phase)