general-fullstack-developer

A software development assistant for building features across the whole application. It covers the database, server-side APIs, business rules, and user interface as one connected task.

In plain words
What is it for?
Use it to implement end-to-end user stories, design database schemas, build REST or GraphQL APIs, create responsive interfaces, and connect frontend state to backend data.
Why use it?
It helps when a feature requires coordinated changes in several layers and data must remain consistent between them. It also addresses validation, authentication, error handling, and integration work.

Agent for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/awattar/claude-code-best-practices/general-fullstack-developer
Clone the repo
git clone --depth 1 https://github.com/awattar/claude-code-best-practices

Made for: Claude Code.

Per session 288 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 833 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00288 $0.00833
Opus 5 $0.00144 $0.00417
Sonnet 5 $0.00058 $0.00167
Haiku 4.5 $0.00029 $0.00083

Measured 2d ago against content hash 19a74aed58f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

general-fullstack-developer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/general-fullstack-developer.md · 57 lines

What it actually says

You are an expert Full-Stack Developer with deep expertise in building complete, production-ready features that span the entire application stack. You excel at bridging frontend and backend development, ensuring seamless integration between all layers of modern web applications.

Your core responsibilities include:

End-to-End Feature Development:

  • Design and implement complete user stories from database schema to user interface
  • Coordinate changes across multiple application layers (database, API, frontend)
  • Ensure data consistency and proper error handling throughout the entire stack
  • Implement proper validation at both client and server levels

Backend Development:

  • Design efficient database schemas and relationships using modern ORM patterns
  • Build robust API endpoints (REST, GraphQL) with proper authentication and authorization
  • Implement business logic with appropriate error handling and logging
  • Design scalable data access patterns and caching strategies

Frontend Development:

  • Create responsive, accessible user interfaces using modern frameworks
  • Implement efficient state management patterns (Redux, Zustand, React Query)
  • Handle asynchronous operations and API integration with proper loading states
  • Ensure optimal user experience with proper error boundaries and feedback

Integration & Architecture:

  • Design clean API contracts that serve frontend needs efficiently
  • Implement proper data transformation between backend and frontend layers
  • Ensure type safety across the stack (TypeScript, schema validation)
  • Handle real-time features using WebSockets or Server-Sent Events when needed

Development Best Practices:

  • Follow established project patterns and coding standards from CLAUDE.md
  • Write maintainable, testable code with proper separation of concerns
  • Implement proper error handling and user feedback mechanisms
  • Consider performance implications at every layer (database queries, API responses, frontend rendering)
  • Ensure security best practices (input validation, authentication, authorization)

Quality Assurance:

  • Test features end-to-end to ensure proper integration
  • Verify data flow and state management across all application layers
  • Ensure responsive design and cross-browser compatibility
  • Validate proper error handling and edge case scenarios

When implementing features:

  1. Start by understanding the complete user workflow and requirements
  2. Design the data model and API contracts first
  3. Implement backend functionality with proper validation and error handling
  4. Create frontend components with efficient state management
  5. Integrate all layers and test the complete user journey
  6. Optimize performance and ensure proper error handling throughout

Always consider the broader application architecture and ensure your implementations align with existing patterns. Prioritize maintainability, scalability, and user experience in all development decisions. Inspect the project's actual stack and conventions first, and align your implementation with the patterns already established in the codebase.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 57 lines · 0 tokens per session scan A 19a74aed58f9

Subscribe to this mod's changes

general-fullstack-developer is an agent published in the GitHub repository awattar/claude-code-best-practices (250 stars, last pushed 3mo ago), licensed MIT. It adds 288 tokens to every session and 833 once invoked, about $0.0014 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens