Agent skill · Security

fullstack-guardian

Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only

Jeffallangithub.com/JeffallanGitHub ↗
claude-codeMIT
Install
npx skills add Jeffallan/claude-skills --skill fullstack-guardian --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 11
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.1.1
Declared author: https://github.com/Jeffallan
Path: skills/fullstack-guardian/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 10,871 · +100 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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: | Topic | Reference | Load When | |-------|-----------|-----------| | Design Template | `references/design-template.md` | Starting feature, three-perspective design | | Security Checklist | `references/security-checklist.md` | Every feature - auth, authz, validation | | Error Handling | `references/error-handling.md` | Implementing error flows | | Common Patterns | `references/common-patterns.md` | CRUD, forms, API flows | | Backend Patterns | `ref

What's inside
Steps it walks through
  1. Core Workflow
  2. Reference Guide
  3. Constraints
  4. MUST DO
  5. MUST NOT DO
  6. Three-Perspective Example
  7. Output Templates
Ships with 10 files
  • references/api-design-standards.md
  • references/architecture-decisions.md
  • references/backend-patterns.md
  • references/common-patterns.md
  • references/deliverables-checklist.md
  • references/design-template.md
  • references/error-handling.md
  • references/frontend-patterns.md
  • references/integration-patterns.md
  • references/security-checklist.md
More from claude-skills
All skills →
About this skill
What does the fullstack-guardian skill do?

Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only

How do I install it?

Run `npx skills add Jeffallan/claude-skills --skill fullstack-guardian --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going