- You are a web developer specializing in Astro
- Use **Astro** as the primary framework.
- Prefer **static site generation (SSG)** unless dynamic behavior is strictly required.
- Write all code in **TypeScript**.
- Use **Astro Content Collections** (Markdown/MDX/Markdoc) to manage structured content.
- Ensure all routes are accessible, SEO-friendly, and properly typed.
- Favor a component-driven design with reusable layouts and minimal global state.
- Prioritize readability, simplicity, and performance across the codebase.
- Use Astro’s official project structure:
```
src/
     components/
     layouts/
     pages/
     styles/
     utils/
     content/
```

- Use **SolidJS** exclusively for client-side interactivity inside Astro islands.
- Favor **fine-grained reactivity** using Solid’s built-in primitives:
  - `createSignal`, `createEffect`, etc.
- Keep components **small**, **stateless** when possible, and **reactive** by default.
- Avoid over-abstracting — prefer clean composition over complex logic.
- Use Solid’s `onCleanup` and reactive lifecycles when needed for precise control.
- All Solid code must be written in **TypeScript**.

- Use **TailwindCSS utility classes** for all layout and styling.
- Avoid writing raw CSS unless Tailwind cannot cover the use case.
- Use responsive, dark mode, and hover/focus utilities when applicable.
- Prefer **semantic HTML** with Tailwind classes applied directly to elements.

- Extend styling via **DaisyUI components** where appropriate.
  - Use DaisyUI’s default themes unless a project-specific theme is defined.
  - Customize DaisyUI via Tailwind’s plugin system when needed.
  - The global style contains the themes
- All Tailwind/DaisyUI usage must respect accessibility and responsiveness.

- Use **Supabase** for backend services: authentication, database (PostgreSQL), and storage.
- Integrate Supabase via its official client SDK.
- Store all Supabase credentials and project secrets in `.env` files and never expose them to the frontend.
- Prefer **Row-Level Security (RLS)** and Supabase **Policies** to secure database operations.
- Use Supabase Auth for sign-in/sign-up, and persist session client-side securely.
- Use strongly typed APIs (via Supabase's TypeScript types) when querying or mutating data.

<!-- Sequential Thinking Workflow -->
<assistant>
    <toolbox>
        <mcp_server name="sequential-thinking"
                        role="workflow_controller"
                        execution="sequential-thinking"
                        description="Initiate the sequential-thinking MCP server">
            <tool name="STEP" value="1">
                <description>Gather context by reading the relevant file(s).</description>
                <arguments>
                    <argument name="instructions" value="Seek proper context in the codebase to understand what is required. If you are unsure, ask the user." type="string" required="true"/>
                    <argument name="should_read_entire_file" type="boolean" default="true" required="false"/>
                </arguments>
                <result type="string" description="Context gathered from the file(s). Output can be passed to subsequent steps."/>
            </tool>
            <tool name="STEP" value="2">
                <description>Generate code changes based on the gathered context (from STEP 1).</description>
                <arguments>
                    <argument name="instructions" value="Generate the proper changes/corrections based on context from STEP 1." type="string" required="true"/>
                    <argument name="code_edit" type="object" required="true" description="Output: The proposed code modifications."/>
                </arguments>
                <result type="object" description="The generated code changes (code_edit object). Output can be passed to subsequent steps."/>
            </tool>
            <tool name="STEP" value="3">
                <description>Review the generated changes (from STEP 2) and suggest improvements.</description>
                <arguments>
                    <argument name="instructions" type="string" value="Review the changes applied in STEP 2 for gaps, correctness, and adherence to guidelines. Suggest improvements or identify any additional steps needed." required="true"/>
                </arguments>
                <result type="string" description="Review feedback, suggested improvements, or confirmation of completion. Final output of the workflow."/>
            </tool>
        </mcp_server>
    </toolbox>
</assistant>