Inspect-before-implement project onboarding
Before we do anything else, inspect this codebase and build a mental model of it. Do not write or modify any code yet. 1. Identify the framework, language, and package manager in use. 2. Map the top-level architecture: where routes/pages live, where shared components live, where data-fetching and state management happen, and how styling is organized. 3. Identify existing conventions: naming patterns, file structure patterns, how errors are handled, how the project tests itself (if at all). 4. Flag anything unusual or inconsistent you notice — dead code, mixed patterns, TODOs that look load-bearing. 5. Summarize this back to me in under 300 words, structured as: Stack / Architecture / Conventions / Flags. Once I confirm your summary is accurate, I'll describe the feature or fix I need — plan your implementation against the conventions you just found, not against generic best practices that might conflict with how this project already does things.
