skills.rest
Blaze-sports-Intel
Blaze-sports-IntelOFFICIAL
Explore all skills by this author →
WebsiteGitHub

full-stack-development

Implement full-stack features across frontend, backend, API, database, and deploy.

1|Updated May 15, 2026
Search Tags:#e2e testing#fullstack#feature flags#schema migrations#vertical slice#server-side auth#type contracts
One-click install
npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill full-stack-development-blaze-sports-intel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-stack-development
Source: https://github.com/Blaze-sports-Intel/uber-engineer/tree/main/plugins/uber-engineer/skills/full-stack-development
Command: npx skills add https://github.com/Blaze-sports-Intel/uber-engineer --skill full-stack-development-blaze-sports-intel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Full-stack Development turns vague “ship a feature” requests into an end-to-end plan and execution path that delivers the real user outcome across UI, API, database, and deploy, with verification so “build success” becomes “done.”

Core Features & Use Cases

  • Vertical-slice delivery: coordinates schema, API, UI, tests, and docs so a feature lands end-to-end in one cohesive pass.
  • Contract-first type synchronization: keeps frontend and backend aligned using shared contracts (e.g., Zod, tRPC, OpenAPI/GraphQL codegen) to prevent drift.
  • Operational rollout safety: provides feature-flag and rollback plans (including kill switches) so releases can be toggled and recovered without redeploy.
  • Full UX state coverage: ensures loading, empty, error, and populated states render correctly, including E2E coverage for happy and failure paths.
  • Cross-cutting correctness: enforces auth on the server, manages boundaries (SSR/SSG/RSC/SPA decisions), and handles cross-layer concerns like caching, telemetry, and error boundaries.

Quick Start

Use /fullstack vertical-slice src/features/checkout to plan and implement a complete checkout feature from schema through UI with verification states and E2E coverage.

Frequently Asked Questions about full-stack-development

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

FAQPage Schema
How do I implement a fullstack vertical slice across frontend, backend, and database?▼

A fullstack vertical slice coordinates schema, API, UI, tests, and docs so a feature lands end-to-end in one cohesive pass, translating user intent into a coordinated implementation path from database schema through UI verification.

What is the best way to keep frontend and backend type contracts synchronized?▼

Type contract synchronization prevents frontend and backend drift by using shared contracts like Zod, tRPC, or OpenAPI/GraphQL codegen to ensure both layers remain aligned during end-to-end feature implementation.

How do I add feature flags and rollback plans to a fullstack deployment?▼

Operational rollout safety for fullstack features provides feature-flag and rollback plans, including kill switches, so releases can be toggled and recovered without requiring a redeploy of the application.

Does this fullstack development approach support Next.js, Remix, SvelteKit, and Nuxt stacks?▼

Fullstack vertical slice delivery applies to Next.js, Remix, SvelteKit, Nuxt, Astro, and Hono stacks, coordinating monorepo feature work, RPC/API integration, and SSR/SSG/RSC/SPA rendering boundary decisions.

How do I enforce server-side auth and handle UI state correctness across the stack?▼

Cross-cutting correctness enforces server-side auth and manages UI state coverage, ensuring loading, empty, error, and populated states render correctly with E2E coverage for both happy and failure paths.

When do I need schema migrations for fullstack feature development?▼

Schema migrations are needed when delivering vertical slices across the stack, coordinating database changes with API integration and type-contract synchronization to ensure end-to-end feature correctness without layer drift.

Related Skills

Explore More Software Engineering Skills→
4tikhonov4tikhonov
3

project-init

Initialize a FIRE project by detecting workspace type and generating standards templates.

Community
Basic
thoreinsteinthoreinstein
5

rollback

Analyze deployments and migrations to generate prioritized rollback safety checklists.

Community
Advanced
AgentiveStackAgentiveStack
71

slice

Break a plan into end-to-end vertical slices covering schema, backend, API, UI, and tests.

Official
Intermediate
grasberggrasberg
3

parallel-agents

Coordinate multiple specialized agents to synthesize a unified report.

Community
Advanced