onboardlisted

# Onboard Produce a structured orientation for this codebase. This skill is read-only — it makes no changes. ## 1. Collect project context Read the following in parallel: - `README.md` (or `readme.md`) at the project root - `docs/CONVENTIONS.md` if it exists - `CLAUDE.md` at the project root if it exists - All files in `memory/**/*.md` (skip any with `status: superseded` or `status: archived`) ## 2. Explore the codebase structure Use Glob and Grep to map the project. Tailor the exploration to what you find — not all projects have all layers: **Structure:** - Top-level directories and their apparent purpose - Solution/project files (`.sln`, `package.json`, `pyproject.toml`, etc.) - Key configuration files (`appsettings.json`, `.env.example`, `vite.config.ts`, etc.) **Entry points:** - API controllers or route definitions - Background jobs or scheduled tasks - Frontend pages or top-level components - Main program entry point **Data layer:** - Database context or ORM configuration - Migration files (count and rough date range) - Key entities or models **Frontend (if present):** - Component structure - State management (stores, composables) - API client layer ## 3. Identify key patterns From what you've read, identify: - The architectural style (layered, CQRS, modular monolith, microservices, etc.) - Naming conventions actually in use (may differ from CONVENTIONS.md) - Testing approach (unit, integration, e2e — what framework, where tests live) - Anything flagged in m