astro-remix

Recommend rendering and routing patterns for Astro and Remix workflows.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill astro-remix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: astro-remix
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/astro-remix
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill astro-remix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of making correct architectural and implementation choices when working on Astro and Remix projects, especially for rendering mode, routing, data loading, and interactive UI behavior.

Core Features & Use Cases

  • Astro rendering guidance: Recommend when to use SSG, SSR, hybrid, islands, and the appropriate hydration directives for performance and UX.
  • Astro 5 implementation patterns: Apply content collections, server islands, view transitions, and SEO/performance best practices.
  • Remix v3 / React Router v7 workflows: Structure loaders/actions for data fetching and mutations, plus progressive enhancement, optimistic UI, nested routes, and error boundaries.
  • Use Case: When updating an existing Astro marketing site that needs a content collection and a few interactive components, use this skill to choose islands hydration settings and implement content rendering safely; when working on a Remix CRUD section with forms, use it to design loaders/actions and ensure the UI works with or without JavaScript.

Quick Start

Use this skill to generate a plan and implementation checklist for an Astro page that uses content collections, includes one server island, and sets the correct hydration directives for each component.

Frequently Asked Questions about astro-remix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between SSG, SSR, and hybrid rendering in Astro?

Choosing between SSG, SSR, and hybrid rendering in Astro depends on page dynamism. This skill evaluates your content requirements to recommend the correct rendering mode, ensuring optimal performance for static marketing pages versus dynamic interactive sections.

What is the best way to structure Remix loaders and actions for a CRUD app?

Structuring Remix loaders and actions requires mapping data fetching and mutations to specific routes. This skill guides you through designing loader/action semantics, implementing progressive enhancement for forms, and ensuring the UI functions correctly even without JavaScript enabled.

When should I use Astro island hydration directives like client:load versus client:visible?

Astro island hydration directives control when interactive components hydrate on the page. This skill helps you apply the correct hydration strategy based on component priority and visibility, balancing initial page load performance with necessary user interactivity.

How do I add interactive components to an Astro marketing site using content collections?

Adding interactive components to an Astro marketing site involves combining content collections with server islands. This skill provides implementation patterns to safely render content and select the appropriate hydration settings for your interactive UI elements.

Does Remix work without JavaScript for form submissions and mutations?

Remix supports progressive enhancement, allowing forms to submit and mutate data without client-side JavaScript. This skill outlines how to design loaders and actions that handle mutations server-side, ensuring your application remains functional and accessible without JS.

How do I handle route errors and boundaries in a Remix application?

Handling route errors in Remix requires implementing error boundaries for specific route segments. This skill provides patterns to structure nested routes and error boundaries, ensuring localized error handling without breaking the entire application layout.