learn-agent: Instructions file for Codex

Repository Guidelines

Project Structure & Module Organization

This repository is an Astro-based content site. Application code lives in src/: pages in src/pages/, shared layouts in src/layouts/, UI components in src/components/, styles in src/styles/, and site constants in src/consts.ts. Blog content is stored in src/content/blog/ and validated through src/content.config.ts. Static assets that should be served directly belong in public/; bundled images and fonts belong in src/assets/. Planning and design notes live in docs/.

Build, Test, and Development Commands

• This project uses pnpm as the default package manager. Prefer pnpm commands and keep pnpm-lock.yaml authoritative; do not update package-lock.json for normal dependency changes.
• pnpm install — install dependencies; use Node.js >=22.12.0 as defined in package.json.
• pnpm dev — start the local Astro dev server at http://localhost:4321.
• pnpm build — generate the production site into dist/.
• pnpm preview — serve the built output locally for a final check.
• pnpm astro check — run Astro’s project checks when validating routes, content, and types.

Coding Style & Naming Conventions

Follow the existing style: TypeScript, Astro, and CSS use tabs for indentation. Name Astro components in PascalCase, for example BaseHead.astro; React components also use PascalCase and live in focused folders such as src/components/home/HomePage.tsx. Keep constants in uppercase snake case when exported globally, such as SITE_TITLE. Use kebab-case for content filenames like welcome.md. Prefer small, composable components and keep copy or content-specific data close to the page or component that uses it.

Testing Guidelines

There is no dedicated test suite yet. Before opening a PR, run pnpm build and pnpm astro check to catch content schema, routing, and type issues. When adding tests in the future, place them near the feature they cover or under a clear tests/ directory, and use names that mirror the target module.