zerolovesea.top-2.0

Imported from zerolovesea/zerolovesea.top-2.0 (AGENTS.md). Install upstream with npx skills add zerolovesea/zerolovesea.top-2.0. Copyright stays with the author.

AGENTS.md

This file provides guidance to coding agents when working with code in this repository.

Use Context7 MCP to fetch current documentation whenever the user asks about a library, framework, SDK, API, CLI tool, or cloud service -- even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. This includes API syntax, configuration, version migration, library-specific debugging, setup instructions, and CLI tool usage. Use even when you think you know the answer -- your training data may not reflect recent changes. Prefer this over web search for library docs.

Do not use for: refactoring, writing scripts from scratch, debugging business logic, code review, or general programming concepts.

Context7 Steps

1. Always start with resolve-library-id using the library name and the user's question, unless the user provides an exact library ID in /org/project format.
2. Pick the best match (ID format: /org/project) by exact name match, description relevance, code snippet count, source reputation (High/Medium preferred), and benchmark score (higher is better). If results don't look right, try alternate names or queries (e.g., "next.js" not "nextjs", or rephrase the question). Use version-specific IDs when the user mentions a version.
3. query-docs with the selected library ID and the user's full question (not single words).
4. Answer using the fetched docs.

Rules

• Always use bun as the package manager and script runner; never use npm or node commands for repo workflows.
• Never add Co-Authored-By lines to git commits.
• Prefer lowercase text across the site.
• Keep changes small and aligned with the existing Astro content-site structure.

Commands

# Development
bun dev              # Start dev server
bun run build        # Type-check and build for production
bun run preview      # Preview production build locally

# Code Quality
bun run check        # Run Biome checks on ./src
bun run lint         # Run Biome linter on ./src
bun run format       # Format all files with Biome

Architecture

This is an Astro-based personal website deployed to Cloudflare Workers with server-side rendering. The active Worker script is sanju.

Deployment

Use Workers, not Pages, for production deploys.

bun run build
bunx wrangler deploy --name sanju

The Astro Cloudflare adapter emits server output in dist/server and static assets in dist/client. wrangler.jsonc uses the Cloudflare adapter entrypoint, and deploys follow the generated dist/server/wrangler.json.

Content Collections

Content lives in src/content/ with three collections defined in src/content.config.ts:

• writing: Blog posts with title, description, pubDate, heroImage, and readingTime.
• thought: Short-form content with category and optional showTldr.
• whoami: About page content.

Path Aliases

Configured in tsconfig.json:

• @components/* -> ./src/components/*
• @layouts/* -> ./src/layouts/*
• @pages/* -> ./src/pages/*
• @styles/* -> ./src/styles/*
• @utils/* -> ./src/utils/*
• @data/* -> ./src/data/*

Key Directories

• src/pages/: Astro pages and API routes for sitemap, RSS, robots.txt, and OG images.
• src/layouts/: Layout components for different content types.
• src/components/: Reusable UI components organized by concern.
• src/data/index.ts: Site metadata, menu items, social links, and product listings.