aiactio-backend

Enforce backend patterns and verification checks for aiactio Server Actions and Supabase queries.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Hamza-037/AI-ACT --skill aiactio-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiactio-backend
Source: https://github.com/Hamza-037/AI-ACT/tree/main/skills/backend
Command: npx skills add https://github.com/Hamza-037/AI-ACT --skill aiactio-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Enforces backend best-practice patterns and verification checks for aiactio Server Actions, Supabase queries, business logic, guard plans, and OpenRouter calls within aiactio.

Core Features & Use Cases

  • Patterns and gotchas documentation for backend components.
  • Scripted verifications (verify-actions.sh) to ensure authentication is present on Server Actions.
  • References covering Supabase patterns, AI integration, and templates for actions.

Quick Start

Run the verify-actions.sh script in this skill to validate that all Server Actions include an auth check.

Frequently Asked Questions about aiactio-backend

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

FAQPage Schema
How do I enforce Supabase RLS and auth checks on server actions?

You can enforce Supabase RLS and auth checks on server actions by running scripted verifications like verify-actions.sh, ensuring user_id matches auth.uid() and RLS is active on all user-data tables.

How do I verify authentication is present on all Server Actions?

Run the verify-actions.sh script provided in this skill to validate that all Server Actions include an auth check before execution.

What backend patterns should I follow for Supabase queries and OpenRouter calls?

Follow backend patterns that restrict SUPABASE_SERVICE_ROLE_KEY to lib/supabase/service.ts, use forward-only migrations in supabase/migrations, and treat logAiUsage as fire-and-forget for OpenRouter calls.

Why should I use unknown with type guards instead of any in server-side code?

Using unknown with type guards instead of any enforces strict type safety in server-side code, allowing safe type narrowing or casting via 'as unknown as DTO' specifically for database JOINs.

Can I use this skill to enforce guard plans and business logic in aiactio projects?

Yes, this skill enforces backend best-practice patterns and verification checks for aiactio Server Actions, Supabase queries, business logic, guard plans, and OpenRouter calls.

What are the limitations of placing server-actions outside lib/actions?

Placing server-actions outside lib/actions violates enforced strict requirements, which mandate that server-actions only reside in lib/actions to maintain consistent auth checks and migration rules.