Menu
Guidelines for writing and structuring Astro components, pages, layouts, routing, and data fetching in this project.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Instructions on leveraging DaisyUI predefined components and handling theming.
Instructions on how to run and fix formatting/linting using prettier and eslint.
Rules for structuring content, using frontmatter, and handling rich text formatting.
Best practices and conventions for styling the project using Tailwind CSS v4.
TypeScript conventions, strictness rules, and interface/type definitions.
Based on SOC occupation classification
| name | astro |
| description | Guidelines for writing and structuring Astro components, pages, layouts, routing, and data fetching in this project. |
You are working in an Astro web project (hungvu.tech). Follow these conventions when creating or modifying Astro files (.astro):
src/pages/.src/layouts/ for page wrappers that provide common HTML structure (e.g., <head>, main navigation, footer).src/components/.Props.---
interface Props {
title: string;
description?: string;
}
const { title, description } = Astro.props;
---
<div class="...">
<h1>{title}</h1>
{description && <p>{description}</p>}
</div>
--- using standard fetch or local content collections (src/content/).<script> tags unless interactive behavior is strictly required. If needed, prefer scoping them or using framework components if any are integrated.<style> blocks in Astro components.When generating, debugging, or modifying Astro code in this project, you MUST fetch and utilize the official Astro LLM documentation sets for context if you have doubts about specific APIs or Astro capabilities:
https://docs.astro.build/llms.txthttps://docs.astro.build/llms-full.txthttps://docs.astro.build/llms-small.txthttps://docs.astro.build/_llms-txt/api-reference.txthttps://docs.astro.build/_llms-txt/how-to-recipes.txtIf encountering an error with Astro components, config, or features, use the read_url_content tool on these URLs for accurate ground truth instead of solely relying on pre-existing knowledge.