stacks-actions

Automate creation, registration, and orchestration of Stacks server actions.

622|17|Updated Apr 26, 2022
One-click install
npx skills add https://github.com/stacksjs/stacks --skill stacks-actions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-actions
Source: https://github.com/stacksjs/stacks/tree/main/.claude/skills/stacks-actions
Command: npx skills add https://github.com/stacksjs/stacks --skill stacks-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stacks Actions solve the challenge of coordinating server-side actions across app/Actions, generated API actions, and default framework actions, providing consistent execution and registration.

Core Features & Use Cases

  • Centralized action creation, registration, and execution across the application and framework.
  • Auto-generated API actions from the useApi model trait, plus the standard framework actions (auth, dashboard, etc.).
  • Use cases include route or event-driven action invocation, testing, and deployment workflows.

Quick Start

Register and invoke server actions across your app and framework components.

Frequently Asked Questions about stacks-actions

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

FAQPage Schema
How do I coordinate server actions across a Stacks framework application?

To coordinate server actions in a Stacks framework application, automate the creation, registration, and orchestration of actions across app/Actions, generated API actions, and default framework actions for consistent execution.

How do I auto-generate API actions from a model trait?

You can auto-generate API actions from the useApi model trait. The framework integrates these generated actions with standard framework actions like auth and dashboard, plus your custom actions, for unified route or event-driven invocation.

Do I need a specific project layout to use Stacks actions?

Yes, you need a compatible Stacks project layout. This includes access to app/Actions, storage/framework/defaults/actions, and generated actions from useApi, along with a SKILL.md frontmatter specifying name and description.

What is the best way to handle route-driven and event-driven action invocation?

The best way to handle route-driven and event-driven action invocation is by using centralized action orchestration. This allows consistent execution across custom app actions, generated API actions, and default framework actions for testing and deployment workflows.

Can I use this to manage default framework actions like auth and dashboard?

Yes, you can manage default framework actions like auth and dashboard. The system orchestrates these standard framework-provided actions alongside your custom app actions and auto-generated API actions for centralized registration and execution.