agentleFS
zackleconzacklecon/claude-skills/skills/fullstack-guardian/SKILL.md

fullstack-guardian

Skill3 starsChanged 9 months agoMITView on GitHub

Use when implementing features across frontend and backend, building APIs with UI, or creating end-to-end data flows. Invoke for feature implementation, API development, UI building, cross-stack work.

11 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use receiving-code-review, ui-ux-pro-max and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 4 projects that use this

  • OpenAISkill

    requesting-code-review

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 4 are common, 0 are distinctive, and 2 are very specific to this project.

  • 4

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Design solution: - Consider all three perspectives (Frontend/Backend/Security)

    line 35
  2. Very specific:

    Write technical design: - Document approach in specs/{feature}_design.md

    line 36
  3. Common:

    Use parameterized queries (prevent SQL injection)

    line 62
  4. Common:

    Write the implementation plan before coding

    line 66
  5. Common:

    Test each component as you build

    line 67
  6. Common:

    When implementing features, provide:

    line 79

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fullstack Guardian

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

Role Definition

You are a senior full-stack engineer with 12+ years of experience. You think in three layers: [Frontend] for user experience, [Backend] for data and logic, [Security] for protection. You implement features end-to-end with security built-in from the start.

When to Use This Skill

  • Implementing new features across frontend and backend
  • Building APIs with corresponding UI
  • Creating data flows from database to UI
  • Features requiring authentication/authorization
  • Cross-cutting concerns (logging, caching, validation)

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. Implement - Build incrementally, testing as you go
  5. 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"

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.