playbooks

home / skills / baz-scm / awesome-reviewers / full-stack-development

full-stack-development skill

/_skills/full-stack-development

This skill helps you design and build end-to-end applications by integrating front-end interfaces with back-end services and databases.

npx playbooks add skill baz-scm/awesome-reviewers --skill full-stack-development

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.7 KB
---
name: full-stack-development
description: Ability to develop both front-end and back-end systems, integrating user interfaces with server logic and databases.
version: '1.0'
---
# Full-Stack Development

Full-stack developers can build end-to-end applications, handling both the client-side and server-side. This is the most common developer role – about one in three developers identifies as full-stack. Mastery of front-end technologies (HTML, CSS, JavaScript/TypeScript) and back-end technologies (server frameworks, databases) allows for building complete features independently. Modern tooling (e.g. Node.js) even enables using one language across the stack, improving efficiency.

## Examples
- Creating a web application with a React (front-end) and Node.js/Express (back-end) stack.
- Designing an API server and the accompanying front-end interface that consumes it.

## Guidelines
- **Front & Back Proficiency:** Build competency in both front-end (e.g. React or other JS frameworks) and back-end (e.g. Node.js, Python, Java) development. Most developers today are expected to span both areas in a **full-stack** capacity.
- **Unified Tech Stack:** Leverage technologies that allow sharing code or language between client and server. For example, using Node.js for server-side enables using JavaScript/TypeScript in both front-end and back-end, allowing real-time, scalable applications with a single language.
- **Integrate Databases & APIs:** Be comfortable designing database schemas and building RESTful or GraphQL APIs. Full-stack work often involves linking the UI to persistent storage and external services, requiring knowledge of SQL/NoSQL databases and API design best practices.

Overview

This skill covers building end-to-end applications by integrating user interfaces with server logic and databases. It emphasizes practical competency across front-end and back-end technologies and patterns for delivering complete, production-ready features. The skill enables developers to design APIs, wire UIs to persistent storage, and choose unified tech stacks for efficiency.

How this skill works

The skill inspects and guides the full lifecycle of a feature: UI design, client-side logic, server routes, and data persistence. It recommends stack choices that allow code reuse (for example, JavaScript/TypeScript across Node.js and React) and outlines how to connect front-end components to RESTful or GraphQL endpoints. It also surfaces common integration tasks like schema design, authentication, and deployment considerations.

When to use it

  • Building a new web application that needs both front-end UI and back-end services
  • Designing or refactoring an API and its consuming front-end
  • Prototyping features quickly using a single language across client and server
  • Integrating a front-end with databases or external services
  • Reviewing pull requests that touch both UI and server logic

Best practices

  • Maintain clear separation of concerns: UI components manage presentation, back-end handles business logic and data access
  • Prefer a unified language (e.g., JavaScript/TypeScript) when it reduces friction and duplicated models
  • Design APIs with versioning and predictable error handling; document endpoints and contracts
  • Model your database schemas to match application access patterns and use migrations for schema changes
  • Automate testing across the stack: unit tests for components, integration tests for APIs, and end-to-end tests for user flows

Example use cases

  • Create a React single-page app with a Node.js/Express API and a PostgreSQL database for user and product data
  • Design a GraphQL server that aggregates multiple microservices and build a front-end that queries only required fields
  • Refactor a legacy monolith by extracting an API layer and creating a modern client using a JS framework
  • Implement authentication, session management, and role-based access control across client and server
  • Review a pull request that introduces schema changes and update both back-end migrations and front-end data models

FAQ

What tech stack should I pick for full-stack work?

Choose based on team skills and project needs; favor stacks that enable shared language and tooling (e.g., React + Node.js/TypeScript) to simplify development and reuse models.

How do I keep front-end and back-end models in sync?

Use shared type definitions when possible, generate client code from API schemas (OpenAPI/GraphQL), and include integration tests that validate contracts.