fullstack-dev

Guides API-backed full-stack development from requirements through deployment.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/almazom/agents_slash_skills --skill fullstack-dev-almazom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fullstack-dev
Source: https://github.com/almazom/agents_slash_skills/tree/main/fullstack-dev
Command: npx skills add https://github.com/almazom/agents_slash_skills --skill fullstack-dev-almazom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and delivering robust full-stack applications is complex without a repeatable workflow. This Skill provides a structured, architecture-aware guide to move from requirements to production-ready code, aligning frontend and backend work with clear patterns.

Core Features & Use Cases

  • Stepwise workflow: requirements gathering, architectural decisions, scaffolding, implementation patterns, testing, deployment, and handoff.
  • Applicable to API-backed apps with distinct backend services and frontend integration, emphasizing production hardening, observability, and maintainability.
  • Real-world scenario: design a new backend service with a React frontend, including API clients, auth flows, migrations, and monitoring.

Quick Start

Follow the Step 0–5 workflow to scope requirements, decide architecture, scaffold, implement, test, and deliver.

Frequently Asked Questions about fullstack-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an architecture-first full-stack development workflow?

An architecture-first full-stack workflow establishes repeatable steps from requirements gathering to production deployment, ensuring frontend and backend integration aligns with structured patterns like typed errors and centralized config.

How do I scaffold a new API-backed application with a React frontend?

You scaffold an API-backed application by following a stepwise workflow that scopes requirements, decides architecture, generates project scaffolding, implements API clients, and defines auth flows before coding.

Does this full-stack workflow handle production deployment and handoff?

Yes, the full-stack workflow includes production hardening steps with robust deployment checks, observability setup, and structured handoff to ensure maintainable delivery of API-backed applications.

What's the best way to manage architectural decisions for full-stack apps?

The best way to manage architectural decisions is using a structured workflow that enforces architecture-aware choices, typed errors, centralized config, and production-ready patterns across both frontend and backend.

Can I use this workflow for backend services without a distinct frontend?

This workflow is specifically designed for API-backed apps with distinct backend services and frontend integration, so using it for backend-only services may not fully utilize its frontend alignment patterns.

When do I need a structured workflow for full-stack application development?

You need a structured full-stack workflow when delivering robust applications requires repeatable processes, reducing risk through enforced practices like typed errors, migrations, and monitoring.