Skill

astro-actions

Expert Astro Server Actions — defineAction, astro:actions, Zod validation, ActionError, HTML form actions, accept form, progressive enhancement, redirect patterns. Use when handling form submissions, mutations, or any server-side logic with type safety.

From fuse-astro

Install

Run in your terminal

npx claudepluginhub fusengine/agents --plugin fuse-astro

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

references/defining-actions.md

references/error-handling.md

references/forms.md

references/overview.md

references/progressive-enhancement.md

references/templates/contact-form.md

references/templates/json-action.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitMar 17, 2026

Actions

View Source View Plugin View on GitHub View README

Astro Actions Expert

Type-safe server functions with automatic validation, standardized errors, and progressive enhancement.

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

fuse-ai-pilot:explore-codebase - Check existing actions in src/actions/
fuse-ai-pilot:research-expert - Verify latest Actions docs via Context7/Exa
mcp__context7__query-docs - Get defineAction and ActionError examples

After implementation, run fuse-ai-pilot:sniper for validation.

Overview

When to Use

Handling form submissions with server-side validation
Creating type-safe backend mutations without API boilerplate
Building progressive enhancement (works without JS)
Replacing API endpoints for client-server communication

Why Astro Actions

Feature	Benefit
`defineAction()`	Type-safe server function definition
Zod validation	Automatic JSON and FormData parsing
`ActionError`	Standardized error codes and messages
`accept: 'form'`	Direct HTML form submission support
Progressive enhancement	Works without JavaScript enabled
`astro:actions`	Client import for type-safe calls

Core Concepts

Action Structure

All actions live in src/actions/index.ts and export a server object:

// src/actions/index.ts
import { defineAction } from 'astro:actions';
import { z } from 'astro/zod';

export const server = {
  myAction: defineAction({ /* ... */ })
}

Accept Modes

Mode	Description
`accept: 'json'` (default)	Parses JSON request body
`accept: 'form'`	Parses HTML FormData directly

Error Codes

Standard HTTP-aligned codes: UNAUTHORIZED, FORBIDDEN, NOT_FOUND, BAD_REQUEST, INTERNAL_SERVER_ERROR, CONFLICT, TOO_MANY_REQUESTS.

Reference Guide

Need	Reference
Concepts & architecture	overview.md
defineAction patterns	defining-actions.md
ActionError handling	error-handling.md
HTML form integration	forms.md
Progressive enhancement	progressive-enhancement.md
Contact form template	templates/contact-form.md
JSON action template	templates/json-action.md

Best Practices

Always define input schema — Never skip Zod validation
Use ActionError for known errors — Standardized codes for client handling
accept: 'form' for HTML forms — Native form submission support
Progressive enhancement — Form works without JS, enhanced with it
Check ctx.cookies for auth — Throw UNAUTHORIZED when not logged in