backend-agent

Design type-safe server-side logic for CraftFlow ERP APIs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/akkpol/crafe-flow-nextjs --skill backend-agent-akkpol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-agent
Source: https://github.com/akkpol/crafe-flow-nextjs/tree/main/.codex/skills/backend-agent
Command: npx skills add https://github.com/akkpol/crafe-flow-nextjs --skill backend-agent-akkpol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines building robust server-side logic for CraftFlow ERP by combining Next.js Server Actions, Zod validation, and Supabase client.

Core Features & Use Cases

  • Server Actions orchestration and API integration
  • Zod schemas for data validation
  • Supabase client integration
  • Clear error handling patterns and type-safe API design
  • File ownership and collaboration guidelines

Quick Start

Create a sample server action following the provided patterns to validate input, perform a database operation, and return a structured result.

Frequently Asked Questions about backend-agent

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

FAQPage Schema
How do I build type-safe Next.js Server Actions with Supabase and Zod?

Next.js Server Actions integrate with Supabase and Zod by applying validation schemas to inputs, orchestrating database operations, and returning structured results. This enforces type-safe APIs and deterministic server-side execution.

What is the best way to structure data validation for backend API design?

Structure backend API data validation using Zod schemas to define explicit input types. This ensures type-safe APIs by catching validation errors early and maintaining deterministic server-side actions across your modules.

How does Zod validation work with Supabase integrations in server-side logic?

Zod validation works with Supabase integrations by validating input data against defined schemas before executing database operations. This combination guarantees type-safe API design and explicit error handling patterns for server-side logic.

Can I use this approach for large-scale ERP API modules?

Yes, this approach suits ERP API modules by enforcing explicit file ownership rules and deterministic server-side actions. It scales across backend modules while maintaining type-safe APIs and clear error handling patterns.

Why do my Next.js Server Actions return untyped errors during database operations?

Untyped errors in Next.js Server Actions occur without clear error handling patterns. Implement structured error handling alongside Zod schemas and Supabase integrations to ensure type-safe APIs and return deterministic server-side results.