Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jeffallan avatar

Fullstack Guardian

  • 4k installs
  • 10.8k repo stars
  • Updated May 20, 2026
  • jeffallan/claude-skills

A Claude skill that implements full-stack web application features with security controls layered across frontend, backend, and database simultaneously.

About

Fullstack Guardian is a security-focused skill for implementing complete web application features across frontend, backend, and database layers simultaneously. Developers invoke it when building authenticated REST API routes with corresponding UI, creating end-to-end CRUD flows, integrating frontend components to backend endpoints, or making architecture decisions about microservices and monorepo structures. The workflow follows a fixed sequence: gather requirements, design the solution from three perspectives (Frontend, Backend, Security), write a technical design doc in specs/, run a security checklist before any code is written, then build incrementally. Key constraints enforce parameterized queries to prevent SQL injection, server-side input validation, sanitized output to prevent XSS, explicit API response schemas to avoid data leakage, and logging of security-relevant events. On completion it hands off to Test Master for QA and DevOps for deployment.

  • Three-perspective implementation: every feature must address Frontend, Backend, and Security concerns within a single wo
  • Security checklist gate enforced before coding - covers auth, authz, input validation, and output encoding on every feat
  • Parameterized queries required on all database interactions; raw string interpolation in SQL is explicitly prohibited
  • API response schemas must be explicit types (e.g. ProfileResponse) to prevent accidental exposure of password or token f
  • Handoff protocol built in - passes completed features to Test Master for QA and devops-engineer for deployment

Fullstack Guardian by the numbers

  • 4,012 all-time installs (skills.sh)
  • +136 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #145 of 2,209 Security skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

fullstack-guardian capabilities & compatibility

Capabilities
authenticated route implementation · parameterized query enforcement · frontend component generation · security checklist gating · technical design documentation · three perspective code review · crud scaffold generation · microservice architecture guidance
Works with
postgres · mysql · github
Use cases
api development · security audit · frontend · database · documentation
Runs
Runs locally
Pricing
Free
From the docs

What fullstack-guardian says it does

403 returned before any DB access when IDs don't match — no timing leak via 404
SKILL.md
Distinct from frontend-only, backend-only, or API-only skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow
SKILL.md
npx skills add https://github.com/jeffallan/claude-skills --skill fullstack-guardian

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4k
repo stars10.8k
Security audit3 / 3 scanners passed
Last updatedMay 20, 2026
Repositoryjeffallan/claude-skills

What it does

Implement full-stack web features with security enforced at every layer - auth, input validation, output encoding, and parameterized queries across frontend, backend, and database.

Who is it for?

Developers building authenticated web features that span UI, API, and database layers and require consistent security enforcement across all three.

Skip if: Projects needing frontend-only styling work, backend-only batch jobs with no UI, or pure infrastructure tasks with no application-layer code.

When should I use this skill?

Implementing a new feature that requires both a backend endpoint and a frontend component, building CRUD operations with forms, or making architecture decisions about microservices or monorepo structure.

What you get

Each implemented feature includes a technical design doc, backend endpoints with parameterized queries and auth enforcement, frontend components with error handling, and explicit security notes.

  • Technical design document saved to specs/{feature}_design.md
  • Backend code including models, schemas, and authenticated endpoints
  • Frontend code including components, hooks, and API call functions

By the numbers

  • 10 reference documents loaded contextually based on task (design, security, error handling, patterns, API, architecture,
  • 3 required implementation perspectives per feature: Frontend, Backend, Security
  • Version 1.1.1 with MIT license

Files

SKILL.mdMarkdownGitHub ↗

Fullstack Guardian

Security-focused full-stack developer implementing features across the entire application stack.

Core Workflow

1. Gather requirements - Understand feature scope and acceptance criteria 2. Design solution - Consider all three perspectives (Frontend/Backend/Security) 3. Write technical design - Document approach in specs/{feature}_design.md 4. Security checkpoint - Run through references/security-checklist.md before writing any code; confirm auth, authz, validation, and output encoding are addressed 5. Implement - Build incrementally, testing each component as you go 6. Hand off - Pass to Test Master for QA, DevOps for deployment

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Design Templatereferences/design-template.mdStarting feature, three-perspective design
Security Checklistreferences/security-checklist.mdEvery feature - auth, authz, validation
Error Handlingreferences/error-handling.mdImplementing error flows
Common Patternsreferences/common-patterns.mdCRUD, forms, API flows
Backend Patternsreferences/backend-patterns.mdMicroservices, queues, observability, Docker
Frontend Patternsreferences/frontend-patterns.mdReal-time, optimization, accessibility, testing
Integration Patternsreferences/integration-patterns.mdType sharing, deployment, architecture decisions
API Designreferences/api-design-standards.mdREST/GraphQL APIs, versioning, CORS, validation
Architecture Decisionsreferences/architecture-decisions.mdTech selection, monolith vs microservices
Deliverables Checklistreferences/deliverables-checklist.mdCompleting features, preparing handoff

Constraints

MUST DO

  • Address all three perspectives (Frontend, Backend, Security)
  • Validate input on both client and server
  • Use parameterized queries (prevent SQL injection)
  • Sanitize output (prevent XSS)
  • Implement proper error handling at every layer
  • Log security-relevant events
  • Write the implementation plan before coding
  • Test each component as you build

MUST NOT DO

  • Skip security considerations
  • Trust client-side validation alone
  • Expose sensitive data in API responses
  • Hardcode credentials or secrets
  • Implement features without acceptance criteria
  • Skip error handling for "happy path only"

Three-Perspective Example

A minimal authenticated endpoint illustrating all three layers:

[Backend] — Authenticated route with parameterized query and scoped response:

@router.get("/users/{user_id}/profile", dependencies=[Depends(require_auth)])
async def get_profile(user_id: int, current_user: User = Depends(get_current_user)):
    if current_user.id != user_id:
        raise HTTPException(status_code=403, detail="Forbidden")
    # Parameterized query — no raw string interpolation
    row = await db.fetchone("SELECT id, name, email FROM users WHERE id = ?", (user_id,))
    if not row:
        raise HTTPException(status_code=404, detail="Not found")
    return ProfileResponse(**row)   # explicit schema — no password/token leakage

[Frontend] — Component calls the endpoint and handles errors gracefully:

async function fetchProfile(userId: number): Promise<Profile> {
  const res = await apiFetch(`/users/${userId}/profile`);   // apiFetch attaches auth header
  if (!res.ok) throw new Error(await res.text());
  return res.json();
}
// Client-side input guard (never the only guard)
if (!Number.isInteger(userId) || userId <= 0) throw new Error("Invalid user ID");

[Security]

  • Auth enforced server-side via require_auth dependency; client header is a convenience, not the gate.
  • Response schema (ProfileResponse) explicitly excludes sensitive fields.
  • 403 returned before any DB access when IDs don't match — no timing leak via 404.

Output Templates

When implementing features, provide: 1. Technical design document (if non-trivial) 2. Backend code (models, schemas, endpoints) 3. Frontend code (components, hooks, API calls) 4. Brief security notes

Documentation

Related skills

How it compares

Choose fullstack-guardian when you need opinionated REST and status-code guardrails during API implementation rather than generic linting or OpenAPI generation alone.

FAQ

Does this skill handle both frontend and backend in the same workflow?

Yes. The skill requires all three perspectives - Frontend, Backend, and Security - to be addressed in every feature before any code is written.

How does the skill prevent SQL injection?

It enforces parameterized queries on all database interactions and explicitly prohibits raw string interpolation in SQL, as shown in the documented Python example.

What happens after implementation is complete?

The skill hands off to Test Master for QA and devops-engineer for deployment as defined in the core workflow handoff step.

Is Fullstack Guardian safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Securityappsecauditcompliance

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.