3xtrology

Web app for deep Western astrology + 八字 (BaZi) readings, with AI-enriched narration. Save your own and others' birth data; later, run relationship analysis between any two profiles.

Repo layout

AGENTS.md                      ← rules for AI contributors (read first)
docs/
  DESIGN.md                    ← feature catalog (living, F-IDs)
  PLAN.md                      ← MVP 0–5 phased plan + validation
  TASKS.md                     ← actionable tasks (T-IDs) per MVP
  requirements/
    functional.md
    non-functional.md
    infrastructure.md          ← AWS infra requirements (IaC-only)
    accounts-and-roles.md      ← operator + end-user RBAC, phased
  design/
    architecture.md            ← app architecture
    astrology-engine.md        ← Swiss Ephemeris / BaZi lib selection
    data-model.md              ← DB schema
    api.md                     ← REST API contract
    ai-integration.md          ← grounded RAG, model picks, eval
    frontend.md                ← stack, screens, i18n, theming
    security.md                ← threat model + controls
    testing.md                 ← unit / integ / eval / E2E
    observability.md           ← logs / metrics / traces / SLOs
    aws-architecture.md        ← AWS service picks + CDK stack layout
    provisioning-bootstrap.md  ← one-time human bootstrap steps
    cicd-pipeline.md           ← steady-state GitHub Actions pipeline
.claude/skills/                ← invocable skills (refine-requirements,
                                  poc-build, software-dev, self-improve)

Phases

1. Local development — astrology + BaZi calc, reference DB, single- user web flow.
2. Cloud deployment — auth, multi-user, relationship analysis.

Next steps

1. Decide astrology API / library (see open questions in docs/design/architecture.md).
2. Decide frontend + backend stack.
3. Pick the first FR to implement and run the software-dev skill.