lattice-init

# Lattice Init ## Required Skills Read apply skills order: 1. `framework:knowledge-priming` -- Load project context understand what project is what already exists ## Workflow ### Step 1: Scan the Project Detect signals about project understand shape existing Lattice state. **Language/framework detection** -- check files in repo root: - `package.json` → Node.js / TypeScript - `tsconfig.json` → TypeScript (confirm over JavaScript) - `go.mod` → Go - `pom.xml` or `build.gradle` or `build.gradle.kts` → Java or Kotlin - `Cargo.toml` → Rust - `requirements.txt` or `pyproject.toml` or `setup.py` → Python - `Gemfile` → Ruby - `*.csproj` or `*.sln` → C# / .NET - `Package.swift` → Swift <!-- synced with language-idioms-refiner "Detect the language" -- edit both --> If multiple language markers are found in the repo root, note all of them and ask the user which is the primary stack before continuing. **Directory structure** -- list top-level dirs. Identify common patterns: - `src/`, `lib/`, `app/` → source code - `test/`, `tests/`, `spec/` → test suites - `docs/` → documentation - `cmd/`, `internal/`, `pkg/` → Go project structure - `domain/`, `infrastructure/`, `application/` → layered architecture **Existing `.lattice/` state** -- check what Lattice artifacts already exist: - `.lattice/config.yaml` → central config (check for `language` key) - `.lattice/standards/language-idioms.md` → language idioms refiner output - `.lattice/standards/knowledge-base.md` → knowledge priming...