Agent skill

Fullstack Guardian

by Jeffallan in Jeffallan/claude-skills

Plans and builds full-stack features with frontend, backend and security handled together, including a written design and a security checklist before any code.

MITAuto-check passedDevelopment

Install Fullstack Guardian

skills CLI
$ npx skills add Jeffallan/claude-skills --skill fullstack-guardian -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Jeffallan/claude-skills fullstack-guardian --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Jeffallan/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/fullstack-guardian .claude/skills/fullstack-guardian && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fullstack-guardian
GitHub stars
12k
Token cost
~1.5k tokens
SKILL.md length
349 words
Files
11 (incl. references)
Skills in repo
58
Repo updated
First seen
Licence
MIT

At a glance

Plans and builds full-stack features with frontend, backend and security handled together, including a written design and a security checklist before any code.

  • Works in 6 steps: Gather requirements - Understand feature… → Design solution - Consider all three… → Write technical design - Document… → …
  • Building a feature that spans the database, API and UI in one pass
  • SKILL.md covers Core Workflow, Reference Guide, Constraints and Three-Perspective Example, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill sets a six-step flow: gather requirements and acceptance criteria, weigh the frontend, backend and security angles together, write a technical design file under specs/, pass a security checkpoint, build and test each component, then hand off to QA and deployment. The checkpoint means going through references/security-checklist.md before writing code to confirm authentication, authorization, validation and output encoding are covered.

Rules include validating input on both client and server, using parameterized queries against SQL injection, sanitizing output against XSS, logging security-relevant events and never trusting client-side validation alone or hardcoding secrets. Ten reference files cover design templates, error handling, CRUD and form patterns, backend and frontend patterns, integration, REST and GraphQL API standards, architecture decisions and a deliverables checklist.

When your agent uses it

  • Building a feature that spans the database, API and UI in one pass
  • Adding an authenticated REST endpoint together with its form or view
  • Checking a feature design for gaps in auth, validation and output encoding
  • Choosing between a monolith and microservices for a new project
  • Preparing a finished feature for handoff to QA and deployment

Example prompts

  • “Build a CRUD screen for customer notes with the API, form validation and permission checks.”
  • “Write the design doc for the invite-a-teammate feature before touching any code.”
  • “Walk through the security checklist for our new file upload endpoint.”
  • “Decide whether the reporting module should stay in the monolith or become its own service.”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  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…
  5. Implement - Build incrementally, testing each component as you go
  6. Hand off - Pass to Test Master for QA, DevOps for deployment

What it can do on your machine

Read from SKILL.md and the folder at commit 1be15d8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • synergetic.solutions
    • jeffallan.github.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fullstack Guardian loads about 1.5k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 236 tokens; SKILL.md has 349 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~236
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Jeffallan/claude-skills at commit 1be15d8, republished under its MIT licence (© Jeffallan). 349 words, ~1,496 tokens.

Download SKILL.mdSave it as .claude/skills/fullstack-guardian/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
fullstack-guardian
description
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 skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow. Invoke for full-stack feature work, web app development, authenticated API routes with views, microservices, real-time features, monorepo architecture, or technology selection decisions.
license
MIT
metadata.author
https://github.com/Jeffallan
metadata.company
https://synergetic.solutions
metadata.version
1.1.1
metadata.domain
security
metadata.triggers
fullstack, implement feature, build feature, create API, frontend and backend, full stack, new feature, implement, microservices, websocket, real-time…
metadata.role
expert
metadata.scope
implementation
metadata.output-format
code
metadata.related-skills
feature-forge, test-master, devops-engineer, secure-code-guardian, architecture-designer, react-expert, typescript-pro

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:

python
@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:

typescript
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

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

© Jeffallan, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in skills/fullstack-guardian of Jeffallan/claude-skills.

  • SKILL.md
  • 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

Open the folder on GitHubat commit 1be15d8

Compare with similar skills

Fullstack Guardian next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fullstack Guardian compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fullstack Guardian this skillJeffallan/claude-skills12k—~1.5kAutomated safety check: PassMIT
Project Workflow Analysis Blueprint Generatorgithub/awesome-copilot40k1 repos~2.7kAutomated safety check: PassMIT
Evolutionary Modular Architecturetech-leads-club/agent-skills7k—~3.7kAutomated safety check: PassCC-BY-4.0
Designing ArchitectureCloudAI-X/claude-workflow-v21.4k1 repos~1.4kAutomated safety check: PassMIT
Akka.NET Best PracticesAaronontheweb/dotnet-skills1.2k1 repos~3.3kAutomated safety check: PassMIT
Senior Architectalirezarezvani/claude-skills28k4 repos~2.7kAutomated safety check: PassMIT

Similar skills

  • Official

    Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows.

    40k GitHub starsUsed in 1 repo~2.7k tokens
    Backend & APIsAuto-check passed
  • Evolutionary Modular Architecture

    tech-leads-club/agent-skills

    Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.

    7k GitHub stars~3.7k tokensUpdated 17 days ago
    DevelopmentAuto-check passed
  • Designing Architecture

    CloudAI-X/claude-workflow-v2

    Designs software architecture and selects appropriate patterns for projects.

    1.4k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Akka.NET Best Practices

    Aaronontheweb/dotnet-skills

    Guidance for Akka.NET actor systems covering EventStream versus DistributedPubSub, supervision, Props versus DependencyResolver, work distribution and testable cluster code.

    1.2k GitHub starsUsed in 1 repo~3.3k tokens
    DevelopmentAuto-check passed
  • Senior Architect

    alirezarezvani/claude-skills

    This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan…

    28k GitHub starsUsed in 4 repos~2.7k tokens
    DevelopmentAuto-check passed
  • Robotics Design Patterns

    arpitg1304/robotics-agent-skills

    Architecture patterns, design principles, and proven recipes for building robust robotics software.

    368 GitHub stars~5.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from Jeffallan/claude-skills

All 58 skills in this repo
  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 2 repos~2k tokens
    Auto-check passed
  • CLI Developer

    Jeffallan/claude-skills

    Walks through designing, building and polishing a command-line tool: user workflow and command hierarchy, implementation in commander, click, typer or cobra, completions and cross-platform testing.

    12k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Fine-Tuning Expert

    Jeffallan/claude-skills

    Guides LLM fine-tuning with LoRA and QLoRA through Hugging Face PEFT, from dataset validation and training checks to adapter merging, quantization and deployment.

    12k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • GraphQL Architect

    Jeffallan/claude-skills

    Designs GraphQL schemas and Apollo Federation graphs, with DataLoader resolvers, subscriptions, query complexity limits and caching.

    12k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Kubernetes Specialist

    Jeffallan/claude-skills

    Creates and checks Kubernetes manifests, Helm charts, RBAC and network policies, and helps debug pod problems, with kubectl checks and rollback steps.

    12k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Laravel Specialist

    Jeffallan/claude-skills

    Builds Laravel 10+ applications with Eloquent models, Sanctum authentication, Horizon queues, API resources and Livewire components, tested with Pest or PHPUnit.

    12k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

Questions about Fullstack Guardian

What does Fullstack Guardian do?

Plans and builds full-stack features with frontend, backend and security handled together, including a written design and a security checklist before any code. The skill sets a six-step flow: gather requirements and acceptance criteria, weigh the frontend, backend and security angles together, write a technical design file under specs/, pass a security checkpoint, build and test each component, then hand off to QA and deployment.md before writing code to confirm authentication, authorization, validation and output encoding are covered.

When should I use Fullstack Guardian?

Fullstack Guardian fits situations like: building a feature that spans the database, API and UI in one pass; adding an authenticated REST endpoint together with its form or view; checking a feature design for gaps in auth, validation and output encoding; choosing between a monolith and microservices for a new project.

How do I install Fullstack Guardian in Claude Code?

Run `npx skills add Jeffallan/claude-skills --skill fullstack-guardian -a claude-code`. Or copy the skill folder (skills/fullstack-guardian in Jeffallan/claude-skills) into .claude/skills/fullstack-guardian in your project. Claude Code loads it when a task matches its description.

How do I install Fullstack Guardian in Codex?

Run `npx skills add Jeffallan/claude-skills --skill fullstack-guardian -a codex`. Or copy the skill folder (skills/fullstack-guardian in Jeffallan/claude-skills) into .agents/skills/fullstack-guardian in your project. Codex loads it when a task matches its description.

Can I use Fullstack Guardian in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jeffallan/claude-skills --skill fullstack-guardian -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fullstack-guardian, .gemini/skills/fullstack-guardian, .github/skills/fullstack-guardian and .opencode/skills/fullstack-guardian in your project.

What does Fullstack Guardian need to run?

SKILL.md names no scripts, command-line tools or credentials: Fullstack Guardian is instructions for the agent only.

Does Fullstack Guardian access the network?

SKILL.md names 3 domains. As links in the text: github.com, synergetic.solutions and jeffallan.github.io. This is read from the text; nothing was executed.

Is Fullstack Guardian safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fullstack Guardian use?

Fullstack Guardian is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fullstack Guardian use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Fullstack Guardian?

Skills that share tags, products or a category with Fullstack Guardian: Project Workflow Analysis Blueprint Generator (github/awesome-copilot, 40k stars), Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars), Designing Architecture (CloudAI-X/claude-workflow-v2, 1.4k stars) and Akka.NET Best Practices (Aaronontheweb/dotnet-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fullstack Guardian?

Jeffallan (a GitHub user) maintains it in Jeffallan/claude-skills, which has 11,754 GitHub stars. The repository holds 58 skills in this directory. The repository was last updated on October 3, 2026.

Source: Jeffallan/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.