What are the package tiers in the Outfitter stack?

The stack is divided into Foundation (zero-dependency core), Runtime (application-specific logic), and Tooling (dev-time utilities) to manage dependencies cleanly.

What is a transport-agnostic handler?

A transport-agnostic handler is a business logic function designed to operate independently of its entry point, allowing the same code to serve a CLI, an MCP tool, or an HTTP endpoint.

Why does this skill discourage throwing exceptions?

It promotes using Result types to make error states explicit and type-safe, which prevents unexpected runtime crashes and improves the reliability of AI-generated code.

How does the error taxonomy work?

It maps domain-specific errors into ten standardized categories (such as validation, conflict, or internal) to ensure consistent error reporting and exit codes across the entire stack.

Stack Architecture Design

Name: Stack Architecture Design
Author: outfitter-dev

byoutfitter-dev

•

Desarrollo de API

Architects transport-agnostic handler systems and robust error taxonomies using the tiered Outfitter ecosystem.

Acerca de

The Stack Architecture skill provides a standardized framework for designing resilient, scalable software systems. It guides developers through creating transport-agnostic handlers that function seamlessly across CLI, MCP, and HTTP interfaces while enforcing a strict 10-category error taxonomy. By prioritizing Result types over traditional exceptions and utilizing a tiered package structure (Foundation, Runtime, and Tooling), this skill ensures that new projects are built with clean separation of concerns, type-safe input validation via Zod, and consistent domain logic.

Características Principales

Structured directory and context flow templates for project consistency
18 GitHub stars
Tiered package selection (Foundation, Runtime, Tooling) for optimized dependencies
Standardized 10-category error taxonomy for unified failure handling
Transport-agnostic handler design for CLI, MCP, and HTTP surfaces
Explicit Result-type enforcement to eliminate unhandled exceptions

Casos de Uso

Designing a new multi-interface application that requires both a CLI and an MCP server
Standardizing error handling and domain logic across complex TypeScript microservices
Refactoring legacy exception-heavy codebases into predictable, Result-based architectures

Acerca de

Características Principales

Structured directory and context flow templates for project consistency
18 GitHub stars
Tiered package selection (Foundation, Runtime, Tooling) for optimized dependencies
Standardized 10-category error taxonomy for unified failure handling
Transport-agnostic handler design for CLI, MCP, and HTTP surfaces
Explicit Result-type enforcement to eliminate unhandled exceptions

Casos de Uso

Designing a new multi-interface application that requires both a CLI and an MCP server
Standardizing error handling and domain logic across complex TypeScript microservices
Refactoring legacy exception-heavy codebases into predictable, Result-based architectures