outfitter-start

Scaffold new Outfitter Stack projects and generate phased migration plans for existing codebases.

6|1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/outfitter-dev/outfitter --skill outfitter-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: outfitter-start
Source: https://github.com/outfitter-dev/outfitter/tree/main/plugins/outfitter/skills/outfitter-start
Command: npx skills add https://github.com/outfitter-dev/outfitter --skill outfitter-start

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires commander, @outfitter/cli, @outfitter/mcp, @outfitter/daemon, @outfitter/file-ops, @outfitter/state, @outfitter/index, @outfitter/testing, @outfitter/contracts, @outfitter/logging, @outfitter/config, zod, and includes scripts (resource) and references (resource) and templates (resource) components.

What problem does it solve?

This Skill streamlines the creation of new Outfitter Stack projects and guides the adoption of Outfitter patterns into existing codebases, reducing setup time and ensuring consistent architecture.

Core Features & Use Cases

  • New Project Scaffolding: Initializes new projects with Outfitter presets (CLI, MCP, daemon, minimal) based on project context.
  • Existing Project Migration: Scans codebases, identifies areas for Outfitter adoption (exceptions, logging, paths), and generates a phased migration plan.
  • Use Case: Kickstart a new CLI tool project with Outfitter's best practices, or systematically refactor a legacy Node.js application to leverage Outfitter's Result types and structured error handling.

Quick Start

Use the outfitter-start skill to scaffold a new CLI project named 'my-cli' in the current directory.

Frequently Asked Questions about outfitter-start

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

FAQPage Schema
How do I scaffold a new CLI project with Outfitter presets?

You can scaffold a new Outfitter project by using the initialization feature, which generates a base structure with presets like CLI, MCP, daemon, or minimal based on your specific project context.

What is the best way to refactor a legacy Node.js codebase to use structured error handling?

The best way to refactor a legacy codebase is to use the migration feature, which scans for exceptions, logging, and path conventions to generate a phased adoption plan for Outfitter patterns.

How does code migration to Outfitter patterns work for existing projects?

Code migration works by scanning your existing codebase to identify areas for adoption, specifically targeting exceptions, logging, and path conventions, then generating a detailed phased migration plan.

Can I use project scaffolding to set up a daemon application?

Yes, you can use project scaffolding to set up a daemon application by selecting the daemon preset during the new project initialization process to ensure consistent architecture.

Do I need an existing codebase to generate a phased migration plan?

No, you do not need a new codebase for migration; the tool scans existing codebases to identify areas for adopting Result types and structured error handling, then outputs a phased plan.

When should I use the minimal preset versus the CLI preset for project setup?

Use the minimal preset for a lightweight project setup, while the CLI preset is for command-line tools, both ensuring consistent architecture through automated scaffolding based on project context.