fullstack-guardian

Implement secure full-stack features across frontend, backend, and database layers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kamelmh/opencode-config --skill fullstack-guardian-kamelmh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fullstack-guardian
Source: https://github.com/kamelmh/opencode-config/tree/main/skills/fullstack-guardian
Command: npx skills add https://github.com/kamelmh/opencode-config --skill fullstack-guardian-kamelmh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you build complete web features without leaving security, validation, or backend integration as afterthoughts. It is designed for work that spans UI, APIs, databases, and deployment decisions, where mistakes in one layer can compromise the whole product.

Core Features & Use Cases

  • End-to-end feature delivery: Plans and implements connected frontend, backend, and data changes in one workflow.
  • Security-first implementation: Applies authentication, authorization, input validation, output encoding, parameterized queries, and logging across layers.
  • Architecture and integration guidance: Supports REST API design, monorepo coordination, real-time features, deployment planning, and technology selection.
  • Use case: Use this Skill when adding an authenticated CRUD flow with a form, API endpoint, database query, error handling, and secure response shaping.

Quick Start

Ask the fullstack-guardian skill to design and implement a secure full-stack feature with frontend, backend, database, and security considerations.

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 web feature across frontend and backend?

Building a secure full-stack web feature requires coordinating frontend, backend, and database changes in one workflow while enforcing client and server validation, authorization, and parameterized queries across all layers.

What security measures do I need for authenticated CRUD API endpoints?

Authenticated CRUD API endpoints require input validation, output encoding, parameterized queries, authorization checks, error handling, and security logging applied across both the API backend and the frontend interface.

Can I use this approach for REST API design and real-time features in a monorepo?

Yes, this approach supports REST API design, real-time features, and monorepo architecture decisions by providing end-to-end implementation guidance that coordinates frontend, backend, and data layers securely.

What's the best way to implement end-to-end validation and error handling for a web app?

The best way to implement end-to-end validation and error handling is to enforce both client and server validation simultaneously, paired with structured error handling and security logging across the full stack.

When should I not use a full-stack security workflow for feature development?

You should not use a full-stack security workflow for isolated frontend tweaks or single-layer backend scripts that lack database queries, authentication flows, or cross-layer API integration requirements.