This file provides the necessary context for any AI agent working on this repository to understand the application's purpose, architecture, and core logic without reading every file.
Vedic Astro Guide is a systematic 4-step Vedic Astrology interpretation tool. It is designed to take raw data from Jagannatha Hora (JHora) and provide a traditional, structured analysis following the Parashara school of astrology.
gemini-2.5-flash, gemini-3-flash, gemini-2.5-flash-lite, and gemma-3 variations to save tokens. Pro models are reserved strictly for highly complex tasks, with a preference for task-splitting to keep using Flash).The project is governed by a specialized agent roster defined in .cursor/rules/agent-roles.mdc: - @AG: Lead Architect & Coordinator. Enforces the "4-Doc Rule" and "Infinite Memory". - @VedicGuru: Astrological Domain Master & Auditor. Enforces the "Sequential Audit Rule". - @AstroDev: Technical Infrastructure & Complexity Manager. - @Chronicle: Archival Scribe (under @AG direction). - @CrashTest: QA, Stability, and Step 0 Verification.
The application has transitioned from a "Data Assembler" to a "Knowledge-Driven Interpreter".
1. Source of Truth: All interpretations are grounded in Vedic- How to_Original.md (Logic) and docs/Vedic - Nhi data full - 19h43.md (Data).
2. Deterministic Baseline: Screen 1 (Step0Input.tsx) ensures 100% fidelity in data capture (ASCII/Table).
3. Execution Protocol: Agents use the Official Gemini APIs to cite the manual for every interpretive step, ensuring zero hallucination.
To save context window tokens, DO NOT read the entirety of Vedic- How to_Original.md unless performing a deep /research task. Instead, use this index to locate the precise headers required for the current Step:
| Astrological Task | Target Header / Section in Original.md |
|---|---|
| Step 1: Foundation | ## Step 1: Foundational "Self Factors" Analysis (Lagna, Surya Lagna, Chandra Lagna & Atmakaraka) |
| Step 2: Promise | ## Step 2: Rashi Chart Promise (Baseline Karma) |
| Step 3: Varga | ## Step 3: Varga (Divisional Chart) Verification (The Micro-Lens) |
| Step 4: Timing | ## Step 4: Event Timing (Dasha & Transit/Gochara Synchronization) |
The project is optimized via these master protocols in .agents/workflows/:
- /research: Systematic, manual-first logic verification.
- /global-flow: Unified meta-engineering prioritizing Flash/Lite models (Inherit vs. Missing vs. Rejected model).
file:///Users/keira/Documents/GitHub/.agents/skills/: Domain expertise (including v-sync-logger).file:///Users/keira/Documents/GitHub/.agents/workflows/: Operational guides (including /sync and /maintenance)..cursor/rules/: Agent personas and "Monday Morning Protocol."CHANGELOG.md, PROJECT_STATUS.md, APP_CONTEXT.md, README.md.src/constants.ts (Application defaults mirrored from the 19h43 Master).src/services/asciiParser.ts: Spatial-coordinate parser for JHora grids (with table support).scripts/sync-user.ts: Command-line profile synchronizer (Markdown Table -> Supabase).src/context/AstroContext.tsx & src/services/importService.ts (Centralized Profile/Chart Loader).docs/UI_WORKFLOW.md (Contains all UI state flow and component rules).The app requires VITE_GEMINI_API_KEY and VITE_SUPABASE_URL / VITE_SUPABASE_ANON_KEY.
To optimize storage, the "1-Week Rule" is enforced for all walkthrough media: - Cleanup Frequency: Weekly or at the start of a major phase. - Criteria: Any media files (screenshots, recordings) stored in the artifacts directory that were created > 7 days ago and are no longer critical for the current active phase.
profiles.