Read the relevant development guidelines before starting your task.

Execute these steps:

1. Discover packages and their spec layers:

   python3 ./.trellis/scripts/get_context.py --mode packages

2. Identify which specs apply to your task based on:

   • Which package you're modifying (e.g., cli/, docs-site/)
   • What type of work (backend, frontend, unit-test, docs, etc.)

3. Read the spec index for each relevant module:

   cat .trellis/spec/<package>/<layer>/index.md

   Follow the "Pre-Development Checklist" section in the index.

4. Read the specific guideline files listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g., error-handling.md, conventions.md, mock-strategies.md). Read those files to understand the coding standards and patterns.

   Frontend reminder:

   • If the task touches dialogs, menus, auth pages, dashboard chrome, typography, spacing, density, or dark-mode polish, you MUST read .trellis/spec/frontend/quality-guidelines.md before editing.
   • For these tasks, check shared tokens and shells first (app/app.css, shared button/dialog/auth/dashboard wrappers). Do not start by resizing one component in isolation.

5. Always read shared guides:

   cat .trellis/spec/guides/index.md

6. Understand the coding standards and patterns you need to follow, then proceed with your development plan.

This step is mandatory before writing any code.