astro

astrolicious/agent-skills · updated May 21, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/astrolicious/agent-skills --skill astro
0 commentsdiscussion
summary

CLI commands, project structure conventions, and deployment adapters for Astro web projects.

  • Core CLI includes dev server, build, type checking, integration management, and TypeScript sync commands
  • Standard project structure uses src/pages for routes, src/components for reusable components, and public/ for static assets
  • Deploy via adapters for Node.js, Cloudflare, Netlify, Vercel, or community-maintained platforms using npx astro add
  • Configuration file ( astro.config.js or variant
skill.md

Astro Usage Guide

Always consult docs.astro.build for code examples and latest API.

Astro is the web framework for content-driven websites.


Quick Reference

File Location

CLI looks for astro.config.js, astro.config.mjs, astro.config.cjs, and astro.config.ts in: ./. Use --config for custom path.

CLI Commands

  • npx astro dev - Start the development server.
  • npx astro build - Build your project and write it to disk.
  • npx astro check - Check your project for errors.
  • npx astro add - Add an integration.
  • npx astro sync - Generate TypeScript types for all Astro modules.

Re-run after adding/changing plugins.

Project Structure

Reference project structure docs.

  • src/* - Project source code (components, pages, styles, images, etc.)
  • src/pages - Required. Defines all pages and routes.
  • src/components - Components (convention, not required).
  • src/layouts - Layout components (convention, not required).
  • src/styles - CSS/Sass files (convention, not required).
  • public/* - Non-code, unprocessed assets (fonts, icons, etc.); copied as-is to build output.
  • package.json - Project manifest.
  • astro.config.{js,mjs,cjs,ts} - Astro configuration file. (recommended)
  • tsconfig.json - TypeScript configuration file. (recommended)

Core Config Options

Option Notes
site Your final, deployed URL. Used to generate sitemaps and canonical URLs.

Example astro.config.ts

import { defineConfig } from 'astro/config';

export default defineConfig({
  site: 'https://example.com',
});

Common Workflows

Creating a Basic Page

Add a file to src/pages/ — the filename becomes the route:

---
// src/pages/index.astro
const title = 'Hello, Astro!';
---
<html>
  <head><title>{title}</title></head>
  <body>
    <h1>{title}</h1>
  </body>
</html>

Creating a Component

---
// src/components/Card.astro
const { title, body } = Astro.props;
---
<div class="card">
  <h2>{title}</h2>
  <p>{body}</p>
</div>

Deploying with an Adapter

  1. Add the adapter: npx astro add vercel --yes (or node, cloudflare, netlify)
  2. Run npx astro check to catch type and configuration errors before building.
  3. Run npx astro build to produce the deployment artifact.
  4. Verify the build output directory (e.g. dist/) exists and is non-empty before proceeding.
  5. Deploy the output per the adapter's documentation.

Adapters

Deploy to your favorite server, serverless, or edge host with build adapters. Use an adapter to enable on-demand rendering in your Astro project.

Add Node.js adapter using astro add:

npx astro add node --yes

Add Cloudflare adapter using astro add:

npx astro add cloudflare --yes

Add Netlify adapter using astro add:

npx astro add netlify --yes

Add Vercel adapter using astro add:

npx astro add vercel --yes

Other Community adapters

Resources

how to use astro

How to use astro on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add astro
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/astrolicious/agent-skills --skill astro

The skills CLI fetches astro from GitHub repository astrolicious/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/astro

Reload or restart Cursor to activate astro. Access the skill through slash commands (e.g., /astro) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.831 reviews
  • Zara Jain· Dec 20, 2024

    Keeps context tight: astro is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ganesh Mohane· Dec 8, 2024

    Useful defaults in astro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Rahul Santra· Nov 27, 2024

    astro has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Tariq Agarwal· Nov 23, 2024

    astro fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Diego Gonzalez· Nov 11, 2024

    Registry listing for astro matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Pratham Ware· Oct 18, 2024

    Solid pick for teams standardizing on skills: astro is focused, and the summary matches what you get after install.

  • James Park· Oct 14, 2024

    We added astro from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Aanya Iyer· Sep 25, 2024

    Useful defaults in astro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Mei Liu· Aug 16, 2024

    I recommend astro for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Zara Malhotra· Jul 7, 2024

    Solid pick for teams standardizing on skills: astro is focused, and the summary matches what you get after install.

showing 1-10 of 31

1 / 4