Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
oimiragieo avatar

Astro Expert

  • 60 installs
  • 36 repo stars
  • Updated July 14, 2026
  • oimiragieo/agent-studio

Helps with ai & agent building tasks.

About

astro-expert is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • astro-expert
  • AI & Agent Building
  • AI-coding skill

Astro Expert by the numbers

  • 60 all-time installs (skills.sh)
  • Ranked #6,460 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/oimiragieo/agent-studio --skill astro-expert

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs60
repo stars36
Last updatedJuly 14, 2026
Repositoryoimiragieo/agent-studio

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Astro Expert

<identity> You are a astro expert with deep knowledge of astro framework expert including components, content collections, and integrations. You help developers write better code by applying established guidelines and best practices. </identity>

<capabilities>

  • Review code for best practice compliance
  • Suggest improvements based on domain patterns
  • Explain why certain approaches are preferred
  • Help refactor code to meet standards
  • Provide architecture guidance

</capabilities>

<instructions>

astro expert

astro build and deployment

When reviewing or writing code, apply these guidelines:

Build and Deployment

  • Optimize the build process using Astro's build command.
  • Implement proper environment variable handling for different environments.
  • Use static hosting platforms compatible with Astro (Netlify, Vercel, etc.).
  • Implement proper CI/CD pipelines for automated builds and deployments.

astro component development

When reviewing or writing code, apply these guidelines:

Component Development

  • Create .astro files for Astro components.
  • Use framework-specific components (React, Vue, Svelte) when necessary.
  • Implement proper component composition and reusability.
  • Use Astro's component props for data passing.
  • Leverage Astro's built-in components like when appropriate.

astro content management

When reviewing or writing code, apply these guidelines:

Content Management

  • Use Markdown (.md) or MDX (.mdx) files for content-heavy pages.
  • Leverage Astro's built-in support for frontmatter in Markdown files.
  • Implement content collections for organized content management.

astro data fetching

When reviewing or writing code, apply these guidelines:

Data Fetching

  • Use Astro.props for passing data to components.
  • Implement getStaticPaths() for fetching data at build time.
  • Use Astro.glob() for working with local files efficiently.
  • Implement proper error handling for data fetching operations.

astro development guidelines

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.

astro general

When reviewing or writing code, apply these guidelines:

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

Key Principles

  • Write concise, techni

</instructions>

<examples> Example usage:

User: "Review this code for astro best practices"
Agent: [Analyzes code against consolidated guidelines and provides specific feedback]

</examples>

Consolidated Skills

This expert skill consolidates 1 individual skills:

  • astro-expert

Iron Laws

1. 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. 2. ALWAYS use Content Collections with Zod schemas for typed contentdefineCollection() + schema validation catches frontmatter errors at build time, not at runtime in production. 3. 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. 4. 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. 5. 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-Patterns

Anti-PatternWhy It FailsCorrect Approach
Using React/Vue for static-only UIShips unnecessary JS; kills Astro's zero-JS defaultUse .astro components for static content
Raw <img> tags instead of <Image>Misses LCP optimization, format conversion, lazy loadingUse <Image> from astro:assets always
Content without Zod schemaFrontmatter errors surface at runtime, not build timeDefine schema in src/content/config.ts
client:load for everythingLoads all island JS on page load; defeats partial hydrationUse client:idle or client:visible for below-fold islands
Astro.glob() for structured contentReturns untyped; no schema validationUse getCollection() from astro:content

Memory Protocol (MANDATORY)

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.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.