Skip to content

ericrisco/rsc-harness / skills/astro

Use when building a content-driven or marketing site with Astro 6: static-first pages, islands and partial hydration, content collections, server islands, per-route on-demand rendering, deploy adapters, and Astro 5→6 migration. NOT app-router React with server actions and heavy client interactivity (that is `nextjs`).

FileKindSize
SKILL.mdskill md13.0 KB
evals/README.mdmarkdown84 B
evals/cases.yamlconfig2.4 KB
references/content-layer.mdmarkdown5.1 KB
references/deploy-and-integrations.mdmarkdown5.3 KB
scripts/verify.shexecutablescript5.6 KB

evals/cases.yaml

View on GitHub
skill: astro

should_trigger:
  - prompt: "Build an Astro blog with content collections."
    why: "Astro content collections and static-first pages are core to the skill."
  - prompt: "Make this widget hydrate only when it scrolls into view in Astro."
    why: "Partial hydration/client directives are Astro-specific."
  - prompt: "Use a server island to personalize a static Astro page."
    why: "Server islands and static-plus-dynamic composition belong here."
  - prompt: "Migrate this project from Astro 5 to Astro 6."
    why: "Astro version migration and v6 content config are skill-specific."
  - prompt: "Quiero una web de marketing rapida con Astro y cero JS innecesario."
    why: "Spanish marketing site with Astro and zero-JS directive triggers this skill."

should_not_trigger:
  - prompt: "Implement a Next.js server action with App Router."
    route_to: "nextjs"
    why: "Next.js RSC/App Router is not Astro."
  - prompt: "Write conversion copy for this landing page."
    route_to: "landing-copy"
    why: "Copywriting belongs to landing-copy; Astro may implement it later."
  - prompt: "Configure Cloudflare DNS and workers."
    route_to: "cloudflare"
    why: "Platform configuration is the Cloudflare skill."
  - prompt: "Design the visual system for this marketing page."
    route_to: "design"
    why: "Visual design belongs to design."
  - prompt: "Write the hooks and state logic for this React island."
    route_to: "react"
    why: "The component-internals (hooks/state) of a React island are React's job; Astro only decides whether and how the island hydrates (client:* directive), not its internal logic — the closest near-miss sibling."

capability:
  - scenario: "A user wants an Astro 6 marketing site with a static blog, one interactive pricing calculator, and per-request personalization."
    must_include:
      - "Keeps the default static/zero-client-JS model and hydrates only the calculator island."
      - "Chooses the appropriate client directive such as client:visible/client:idle instead of client:load by habit."
      - "Uses content collections for typed blog/content data."
      - "Uses server islands or per-route on-demand rendering only for request-specific personalization."
      - "Checks Astro major version and Node/runtime requirements before giving migration advice."
      - "Routes copy, SEO, deploy-platform details to their matching skills when needed."
      - "Explains that interactivity is the exception, not the default."
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall