npm run build- Build the projectnpm run dev- Start development servernpm run test- Run testsnpm run astro:dev- Start Astro development servernpm run astro:build- Build Astro sitebun build- Build with Bunbun dev- Start Bun development server
- Astro Pages: Located in
src/pages/ - Components: Organized in
src/components/with.astrofiles - TypeScript: All code uses TypeScript with
src/lib/utils.tsas shared utilities - Assets: Static files in
public/directory - Content: Markdown content in
content/directory
- TypeScript: Use PascalCase for interfaces/classes, camelCase for variables/functions
- Astro Components: Use
.astroextension with PascalCase filenames - CSS: Tailwind classes with custom components following BEM-like structure
- Astro Tests: Located in
__tests__directories alongside components - Testing Framework: Astro's built-in testing with Jest
- Test Structure: Each component has a corresponding test file (e.g.,
Button.astro→Button.astro.test.ts)
- Environment Variables: Use
.envfiles withastro.config.mjsfor configuration - TypeScript Configuration:
tsconfig.jsonmust includepathsfor Astro imports - Build Process: Ensure
astro.config.mjsincludesoutputandbasesettings - Static Assets: Files in
public/are served directly at root - Content Directory: Markdown files in
content/are automatically imported as pages
- Astro Configuration:
astro.config.mjshandles site metadata and build settings - TypeScript Setup:
tsconfig.jsonincludesstrictmode andesModuleInterop - Tailwind Integration:
tailwind.config.tsconfigures CSS framework - Bun Support:
bun.lockmanages dependencies for faster builds
- CI/CD: Vercel configuration in
vercel.json - Documentation: README.md provides project overview
- Codebase Structure: Use
ls -Rto explore nested directories
Generated with Crush - Documented based on observed codebase structure and files