app-stack

Selects the smallest justified application stack and coordinates specialist skills for implementation.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill app-stack-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-stack
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/app-stack
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill app-stack-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing technologies for a new or existing application often leads to over-engineered stacks with unnecessary queues, caches, and services. This Skill classifies the application, selects the smallest justified architecture, and marks every component as required, conditional, deferred, or rejected. ## Core Features & Use Cases - Stack Selection Framework: Classify the application archetype, choose architecture boundaries before vendors, and produce a decision record with rationale and revisit triggers. - Opinionated Technology Profiles: Evaluate a Python/FastAPI/PostgreSQL baseline plus frontend, async work, event streaming, and observability options against official vendor sources. - Implementation Coordination: Route concrete work to narrow specialist skills and emit a schema-versioned logical handoff to scaffold-project when repository scaffolding is explicitly requested. - Use Case: When planning a new SaaS product, ask for a stack recommendation and receive a table of required, conditional, deferred, and rejected components with data flow, rejected alternatives, and validation steps. ## Quick Start Ask the agent to recommend the smallest justified technology stack for your new web application, including which components are required now and which should be deferred.

Frequently Asked Questions about app-stack

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

FAQPage Schema
How do I choose a technology stack for a new web application?

Classify the application archetype and quality attributes first, then choose architecture boundaries before vendors. The skill returns a decision table marking each component required, conditional, deferred, or rejected with rationale and revisit triggers.

FastAPI vs Django for a Python web application?

Choose FastAPI with Pydantic for API-first services with a separate backend contract. Choose a batteries-included framework like Django when you need integrated forms, authentication, admin, ORM, and migrations in a server-rendered application.

When should I add Kafka or an event stream to my stack?

Add event streaming only with a concrete need for multiple independent consumer groups, replay, change data capture, or a durable partitioned log. Ordinary background jobs and single API-plus-worker systems do not justify it.

Does this skill modify my repository when recommending a stack?

No. Advisory requests remain read-only. Repository changes happen only when implementation is explicitly requested, and full scaffolding is delegated to the explicit-only scaffold-project skill through a bounded logical handoff.

When should I use Celery versus Temporal for background work?

Use Celery for independent tasks like retries, reports, and file processing with defined timeouts and idempotency. Use Temporal when the process has durable multi-step state, long timers, human approvals, or compensation logic.