Files
astrolabe/CLAUDE.md
T
oleh 094e5f6e4e Add visual design language (IBM/Carbon-inspired) and schedule it as M1.5
Defines the visual contract before the design-application work, so M2+ build on settled tokens.

- docs/architecture/09-visual-design.md: principles + deliberate divergences (square chrome, free color/theming), token system (IBM Plex type, 8px spacing, role-based color, motion), component conventions, and a source-repo map for extending the research
- docs/architecture/visual-specimen.html: standalone kitchen-sink specimen with a live theme x accent switcher; doubles as the tokens.css sandbox
- IMPLEMENTATION-PLAN: new M1.5 'Visual design foundation' milestone, plus ground-rule/cross-cutting/reference wiring
- index links: 00-overview, CLAUDE.md, AGENTS.md (architecture playbook now 00-09)

Applying the design to the M1 surfaces is deferred to a separate session.
2026-06-05 00:25:11 +03:00

1.6 KiB
Raw Blame History

Claude Context — Astrolabe

See @AGENTS.md for project overview, architecture rules, and the AI developer protocol.

Documentation Index

  • SOUL.md — project philosophy and identity. Read first.
  • docs/spec/ — authoritative behavioral specification (sections 0010): the what. This is the contract; implement to it.
  • docs/architecture/ — architecture playbook (0009): the how (state, persistence, modals, routing, rendering, inference, relationships, vega-editor techniques, visual design). Self-contained — no external repo needed.
  • docs/IMPLEMENTATION-PLAN.md — incremental milestone plan (M0M6), MVP boundary, per-milestone tests + manual checks, and an architecture reference index.
  • AGENTS.md — onboarding, stack, directory map, scripts, conventions.

Quick Orientation

  • Astrolabe is a spec-driven rebuild — the behavior is fixed in docs/spec/; the architecture is adapted from Syto. Implement to the spec; don't port legacy code.
  • src/core/ is portable and tested hardest. Browser specifics live in src/app/infrastructure/. UI is React + Zustand.
  • Editor is Monaco, charts render via vega-embed, storage is IndexedDB.
  • Work milestone by milestone (see the plan): core-first, then UI, then tests, then a manual smoke check against the spec's acceptance points.

Conventions

  • No git actions unless explicitly invited.
  • Run npm run typecheck and npm test after changes.
  • Single-line commit subjects; no Co-Authored-By trailers.