When reviewing or writing code, apply these guidelines:

Build and Deployment

When reviewing or writing code, apply these guidelines:

Component Development

When reviewing or writing code, apply these guidelines:

Content Management

When reviewing or writing code, apply these guidelines:

Data Fetching

When reviewing or writing code, apply these guidelines:

Enforce strict TypeScript settings, ensuring type safety across the project.
Use TailwindCSS for all styling, keeping the utility-first approach in mind.
Ensure Astro components are modular, reusable, and maintain a clear separation of concerns.

When reviewing or writing code, apply these guidelines:

You are an expert in JavaScript, TypeScript, and Astro framework for scalable web development.

Key Principles

Consolidated Skills

This expert skill consolidates 1 individual skills:

Iron Laws

ALWAYS use Astro components for static content; reserve framework components for interactive islands — shipping React/Vue/Svelte for non-interactive content bloats JS bundles; Astro compiles to zero JS by default.
ALWAYS use Content Collections with Zod schemas for typed content — defineCollection() + schema validation catches frontmatter errors at build time, not at runtime in production.
ALWAYS specify island hydration directives explicitly — use client:load, client:idle, or client:visible intentionally; never rely on defaults; wrong hydration strategy defeats Astro's performance model.
NEVER bypass Astro's built-in image optimization — always use <Image> or getImage() from astro:assets; raw <img> tags skip width/height inference, format conversion, and LCP optimization.
NEVER use Astro.glob() for typed content — it returns untyped data; use Content Collections API (getCollection(), getEntry()) for all structured content to get full TypeScript support.

Anti-Pattern	Why It Fails	Correct Approach
Using React/Vue for static-only UI	Ships unnecessary JS; kills Astro's zero-JS default	Use `.astro` components for static content
Raw `<img>` tags instead of `<Image>`	Misses LCP optimization, format conversion, lazy loading	Use `<Image>` from `astro:assets` always
Content without Zod schema	Frontmatter errors surface at runtime, not build time	Define schema in `src/content/config.ts`
`client:load` for everything	Loads all island JS on page load; defeats partial hydration	Use `client:idle` or `client:visible` for below-fold islands
`Astro.glob()` for structured content	Returns untyped; no schema validation	Use `getCollection()` from `astro:content`

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.