stack-architecture

Design stack-based systems using @outfitter/* packages. Use when planning new projects, choosing packages, designing handler architecture, or when "architecture", "design", "structure", "plan handlers", or "error taxonomy" are mentioned.

Aller à l'installation

Dépôt: outfitter-dev/agents
Dernière activité de la source: 28 janvier 2026 à 02:18
Langue détectée de SKILL.md: anglais
Étoiles: 28
Forks: 1

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/outfitter-dev/agents --skill stack-architecture

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

gitbutler-complete-branch

This skill should be used when the user asks to "complete a branch", "merge to main", "finish my feature", "ship this branch", "integrate to main", "create a PR from GitButler", or when `--complete-branch` flag is mentioned. Guides completion of GitButler virtual branches with safety snapshots, integration workflows, and cleanup.

2026-02-06

gitbutler-multi-agent

This skill should be used when coordinating multiple AI agents working concurrently, handling agent handoffs, transferring commits between agents, or when "multi-agent", "concurrent agents", "parallel agents", "agent collaboration", or "parallel execution" are mentioned with GitButler. Provides virtual branch patterns for parallel execution without coordination overhead.

2026-02-06

gitbutler-stacks

This skill should be used when creating stacks, dependent branches, or when "stack", "stacked branches", "anchor", "--anchor", "but branch new -a", "create dependent branch", or "break feature into PRs" are mentioned with GitButler. Covers anchor-based stacking for dependent features and reviewable PR breakdown.

2026-02-06

Tout voir dans ce dépôt

// Input schema
const CreateUserInputSchema = z.object({
  email: z.string().email(),
  name: z.string().min(1),
});

// Output type
interface User {
  id: string;
  email: string;
  name: string;
}

// Handler signature
const createUser: Handler<unknown, User, ValidationError | ConflictError>;

Domain Error	Stack Category	Error Class
Not found	`not_found`	`NotFoundError`
Invalid input	`validation`	`ValidationError`
Already exists	`conflict`	`ConflictError`
No permission	`permission`	`PermissionError`
Auth required	`auth`	`AuthError`
Timed out	`timeout`	`TimeoutError`
Connection failed	`network`	`NetworkError`
Limit exceeded	`rate_limit`	`RateLimitError`
Bug/unexpected	`internal`	`InternalError`
User cancelled	`cancelled`	`CancelledError`

┌─────────────────────────────────────────────────────────────────┐
│                        TOOLING TIER                              │
│  Build-time, dev-time, test-time packages                       │
│  @outfitter/testing                                             │
└─────────────────────────────────────────────────────────────────┘
                              ▲
                              │ depends on
┌─────────────────────────────────────────────────────────────────┐
│                        RUNTIME TIER                              │
│  Application-specific packages for different deployment targets  │
│  @outfitter/cli    @outfitter/mcp    @outfitter/daemon          │
│  @outfitter/config @outfitter/logging @outfitter/file-ops       │
│  @outfitter/state                                               │
└─────────────────────────────────────────────────────────────────┘
                              ▲
                              │ depends on
┌─────────────────────────────────────────────────────────────────┐
│                       FOUNDATION TIER                            │
│  Zero-runtime-dependency core packages                          │
│  @outfitter/contracts    @outfitter/types                       │
└─────────────────────────────────────────────────────────────────┘

Tier	Packages	Dependency Rule
Foundation	`contracts`, `types`	No @outfitter/* deps
Runtime	`cli`, `mcp`, `daemon`, `config`, `logging`, `file-ops`, `state`	May depend on Foundation
Tooling	`testing`	May depend on Foundation + Runtime

Package	Purpose	When to Use
`@outfitter/contracts`	Result types, errors, Handler contract	Always (foundation)
`@outfitter/types`	Type utilities, collection helpers	Type manipulation
`@outfitter/cli`	CLI commands, output modes, formatting	CLI applications
`@outfitter/mcp`	MCP server, tool registration	AI agent tools
`@outfitter/config`	XDG paths, config loading	Configuration needed
`@outfitter/logging`	Structured logging, redaction	Logging needed
`@outfitter/daemon`	Background services, IPC	Long-running services
`@outfitter/file-ops`	Secure paths, atomic writes, locking	File operations
`@outfitter/state`	Pagination, cursor state	Paginated data
`@outfitter/testing`	Test harnesses, fixtures	Testing

Project: {PROJECT_NAME}
Transport Surfaces: {CLI | MCP | HTTP | ...}

Directory Structure:
├── src/
│   ├── handlers/           # Transport-agnostic business logic
│   │   ├── {handler-1}.ts
│   │   └── {handler-2}.ts
│   ├── commands/           # CLI adapter (if CLI)
│   ├── tools/              # MCP adapter (if MCP)
│   └── index.ts            # Entry point
└── tests/
    └── handlers/           # Handler tests

Dependencies:
├── @outfitter/contracts    # Foundation (always)
├── @outfitter/{package-2}  # {reason}
└── @outfitter/{package-3}  # {reason}

Handler	Input	Output	Errors	Description
`getUser`	`GetUserInput`	`User`	`NotFoundError`	Fetch user by ID
`createUser`	`CreateUserInput`	`User`	`ValidationError`, `ConflictError`	Create new user
`deleteUser`	`DeleteUserInput`	`void`	`NotFoundError`, `PermissionError`	Remove user

Domain Errors → Stack Taxonomy:

{domain-error-1} → {stack-category} ({ErrorClass})
  - When: {condition}
  - Exit code: {code}

{domain-error-2} → {stack-category} ({ErrorClass})
  - When: {condition}
  - Exit code: {code}

name	stack-architecture
version	0.1.0
description	Design stack-based systems using @outfitter/* packages. Use when planning new projects, choosing packages, designing handler architecture, or when "architecture", "design", "structure", "plan handlers", or "error taxonomy" are mentioned.
context	fork
agent	stacker
allowed-tools	Read Grep Glob

name	stack-architecture
version	0.1.0
description	Design stack-based systems using @outfitter/* packages. Use when planning new projects, choosing packages, designing handler architecture, or when "architecture", "design", "structure", "plan handlers", or "error taxonomy" are mentioned.
context	fork
agent	stacker
allowed-tools	Read Grep Glob

stack-architecture

Options d'installation

Vérifiez les fichiers source