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.
The author's original description, preserved in English. It describes intent, not verified performance.
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.
A security-focused full-stack Skill that designs and builds features across frontend, backend and security together, with a written design and a security checklist before any code.
Review scope
Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.
Observable capabilities
Gathers requirements and writes a technical design in specs/{feature}_design.md before coding.
Runs a security checkpoint covering auth, authorization, validation and output encoding.
Implements backend routes with parameterized queries and explicit response schemas.
Builds the matching frontend calls with client-side guards and hands off to test and deployment roles.
Limitations & scope
Hand-off steps refer to other skills such as Test Master and DevOps that must be installed separately.
Broad scope means depth on any single layer relies on the reference files.
Security effectiveness has not been verified here.
Relevant for
Developers building end-to-end features with UI and API
Teams that want security reviewed at every layer
02 / STRUCTURE
What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
{
"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",
"company": "https://synergetic.solutions",
"version": "1.1.1",
"domain": "security",
"triggers": "fullstack, implement feature, build feature, create API, frontend and backend, full stack, new feature, implement, microservices, websocket, real-time, deployment pipeline, monorepo, architecture decision, technology selection, end-to-end",
"role": "expert",
"scope": "implementation",
"output-format": "code",
"related-skills": "feature-forge, test-master, devops-engineer, secure-code-guardian, architecture-designer, react-expert, typescript-pro"
}
}
03 / WORKFLOW
A reading of the operating sequence
This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.
Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.
Attention recommended
158 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.
Network accessObserved
File writesObserved
Credential useObserved
Note
File modification is described or implemented
138 occurrences
This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 138 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 12 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Treat its security checklist as a starting point and review auth, authorization and data exposure in the generated code yourself.
05 / CONTEXT
Where context can be spent
Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.
Exact token counts unavailable
All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.
No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.
06 / EVALUATION
Controlled evaluation
No controlled evaluation
This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.
Not tested
07 / USAGE
Use with the source in view
Install command
git clone https://github.com/Jeffallan/claude-skills.git
cd claude-skills
# Copy this skill directory into one of:
# ~/.claude/skills/fullstack-guardian
# .claude/skills/fullstack-guardian
Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/fullstack-guardian/SKILL.md.
Review the license, prerequisites and all bundled reference files.
Copy the skill directory into a personal or project-level Claude Code skills directory.
Restart or refresh Claude Code so the skill can be discovered.
Verify installation
Ask Claude Code to design a small authenticated endpoint and confirm it writes a design and applies the security checklist first.
Prerequisites
Hand-off steps refer to other skills such as Test Master and DevOps that must be installed separately.
Broad scope means depth on any single layer relies on the reference files.
Security effectiveness has not been verified here.
Example prompts
Representative task
Use the fullstack-guardian skill to add a user profile page: write specs/profile_design.md first, run the security checklist, then implement an authenticated backend route and a frontend fetch with error handling.
Inspect before use
Read the fullstack-guardian skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/fullstack-guardian/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.
08 / VERDICT
A decision, with its limits attached
Strengths
Requires the implementation plan to be written before coding.
Constraints cover server-side validation, parameterized queries, output sanitizing and no hardcoded secrets.
Considerations
The security checklist does not replace a professional security review.
A required design document step may feel heavy for small changes.
Research conclusion
A sound discipline layer for full-stack feature work, best used alongside real testing and review.
09 / PROVENANCE
Traceable by construction
The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.
Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.