fullstack-guardian

Implements security-focused full-stack features spanning frontend, backend, and database layers.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ArMaTeC/Redball --skill fullstack-guardian-armatec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fullstack-guardian
Source: https://github.com/ArMaTeC/Redball/tree/main/.devin/skills/fullstack-guardian
Command: npx skills add https://github.com/ArMaTeC/Redball --skill fullstack-guardian-armatec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building features that span frontend and backend often leads to inconsistent validation, missing authorization checks, and security gaps between layers. This Skill enforces a three-perspective workflow (Frontend, Backend, Security) so every feature ships with authentication, input validation, output encoding, and parameterized queries addressed at every layer. ## Core Features & Use Cases - Three-Perspective Design: Generates technical design documents covering UI components, API endpoints, and security controls before any code is written. - Layered Security Enforcement: Applies a per-feature security checklist covering auth, authorization, rate limiting, SQL injection prevention, and XSS sanitization. - End-to-End Implementation Guidance: Provides reference patterns for CRUD flows, REST/GraphQL API design, microservices, real-time WebSocket features, monorepo structure, and CI/CD deployment. - Use Case: When asked to build an authenticated user profile API with a corresponding React form, it produces the backend endpoint with parameterized queries, the frontend component with validation, and explicit security notes. ## Quick Start Ask the AI to implement a new full-stack feature, such as an authenticated REST endpoint with a matching frontend form, and request that security be addressed at every layer.

Frequently Asked Questions about fullstack-guardian

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

FAQPage Schema
How do I build a secure full-stack feature with frontend and backend?▼

Start with a three-perspective design covering UI components, API endpoints, and security controls. Then implement backend endpoints with parameterized queries and auth guards, build frontend components with client-side validation, and verify the security checklist before handoff.

What should a REST API design include for production use?▼

A production REST API needs consistent URL conventions, semantic HTTP status codes, standardized error responses with request IDs, pagination with metadata, URL path versioning, per-endpoint rate limiting, whitelist-based CORS, and schema-based input validation.

Should I choose a monolith or microservices architecture?▼

Choose a modular monolith for new products, teams under ten developers, or simple domains. Choose microservices when you have clear bounded contexts, independent scaling needs, multiple teams, and sufficient DevOps infrastructure.

How do I prevent SQL injection and XSS in web applications?▼

Use parameterized queries for all database access and never interpolate user input into SQL strings. Prevent XSS by sanitizing output, encoding responses, and configuring Content Security Policy headers.

When should I use JWT versus session-based authentication?▼

JWT suits stateless horizontal scaling and mobile or SPA clients, while sessions allow simple revocation. A hybrid approach with short-lived JWT access tokens and revocable refresh tokens stored in httpOnly cookies balances both.