conventionslisted

# Conventions Scaffold or update `docs/CONVENTIONS.md` by grounding it in the actual codebase — not templates or guesses. This skill is interactive. It reads existing code to discover what conventions are already in use, then asks the user to confirm, correct, or extend them. ## 1. Check current state - Does `docs/CONVENTIONS.md` already exist? - **Yes:** read it fully. This is an update run. Identify which sections need revision. - **No:** this is a fresh scaffold. Read `docs/CONVENTIONS.template.md` if it exists for the expected structure. - Check `memory/**/*.md` for any architecture or design decisions that should be reflected in conventions. ## 2. Read the codebase to discover actual conventions Use Glob and Grep to observe what the code actually does — conventions should describe reality, not aspiration. Sample across all layers: | Category | What to look for | |----------|-----------------| | **Naming** | Class/method/variable casing, file naming, interface prefix (`I`?) | | **Architecture** | Directory layers, dependency flow (DI? static?), repo/service/controller separation | | **Error handling** | Catch/log patterns, global error handler, return type (exception/Result\<T\>/tuple) | | **Testing** | Framework, file location pattern, test class naming, mocks vs. real deps | | **Frontend** | Options vs. Composition API, state management, API call pattern (fetch/axios/generated) | | **Other** | Logging levels, auth patterns, compliance requirements visible in