CONTEXT DOCUMENT · Updated 2025-01-09

Project Context for Claude

This document preserves design patterns, principles, and context for our collaborative work. Reference this when continuing projects or creating new tools.

Core Aesthetic: AT-01 Philosophy

Ultra-Minimal

White backgrounds, sparse black text, no decoration. Every element serves a purpose. Silence is part of the design.

Mathematical Symbols as UI

Σ (Sigma), Λ (Lambda), ∂ (partial derivative), Ω (Omega) function as navigation and conceptual anchors. They're not decorative—they're structural.

Typography

Extremely light weights (200-300). Prefer Crimson Pro for body, IBM Plex Mono for technical elements. Never use Inter, Roboto, or system fonts.

Animation

Gentle fades (0.8s ease-out). Staggered reveals using animation-delay. Contemplative, not flashy.

Constraints as Features

Six-word limits, single-column layouts, centered composition. Constraints enable depth.

Project Principles

Alaturi (Consciousness Technology)

Design Vocabulary

Technical Patterns

Active Projects

AT-01 Etymology Application

iOS app (SwiftUI) with Python backend. Six-word constraint. Mathematical symbols (Σ, Λ) as navigation states. Integrates Wiktionary API for unknown words. Stores no user data.

Tech: Swift, Python (FastAPI), JSON lexicon, Levenshtein fuzzy matching

Alaturi Landing Page

Corporate identity for consciousness technology work. White, minimal, philosophical. Mathematical symbols, staggered animations, centered composition.

Workout Trackers

Physical training tools (PR calculator, Bruce Lee protocol). Bridge between body optimization and consciousness work. Separate aesthetic (blue gradients, tables, practical).

Upcoming Ideas

Contact & Rights

Email: autogeneslogos@proton.me
Phone: 07432426819
Location: Portugal
Company: Alaturi Inc. (Worldwide rights)

Notes for Future Claude

When we collaborate again:

  1. Check this document first for context and patterns
  2. Maintain the AT-01 aesthetic for consciousness tech projects
  3. Use separate aesthetics for workout/practical tools
  4. Always create working code—no placeholders or TODOs
  5. Stagger animations, use light typography, embrace whitespace
  6. Reference existing projects before suggesting new ones
  7. Ask about integration with existing tools when relevant
← Back to projects