Agent skill · software engineering · aiskillstore
full-stack-orchestration-full-stack-feature
Use when working with full stack orchestration full stack feature
Why this skill is useful
Provides detailed workflows and best practices for orchestrating full-stack feature development, including specific prompts for architecture and implementation phases that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Use this skill when Working on full stack orchestration full stack feature tasks or workflows Needing guidance, best practices, or checklists for full stack orchestration full stack feature Do not use this skill when The task is unrelated to full stack orchestration full stack feature You need a different domain or tool outside this scope Instructions Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. If detailed examples are required, open resources/implementation-playbook.md. Orchestrate full-stack feature development across backend, frontend, and infrastructure layers with modern API-first approach: [Extended thinking: This workflow coordinates multiple specialized agents to deliver a complete full-stack feature from architecture through deployment. It follows API-first development principles, ensuring contract-driven development where the API specification drives both backend implementation and frontend consumption. Each phase builds upon previous outputs, creating a cohesive system with proper separation of concerns, comprehensive testing, and production-ready deployment. The workflow emphasizes modern practices like component-driven UI development, feature flags, observability, and progressive rollout strategies.] Phase 1: Architecture & Design Foundation 1. Database Architecture Design Use Task tool with subagenttype="database-design::database-architect" Prompt: "Design database schema and data models for: $ARGUMENTS. Consider scalability, query patterns, indexing strategy, and data consistency requirements. Include migration strategy if modifying existing schema. Provide both logical and physical data models." Expected output: Entity relationship diagrams, table schemas, indexing strategy, migration scripts, data access patterns Context: Initial requirements and business domain model 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/full-stack-orchestration-full-stack-feature