outfitter-dev
- 224 skills
- 0 followers
- last month last updated
- ▌ Tenets · outfitter-devTrails framework design tenets — the foundational beliefs, promises, primitives, and patterns that govern the framework. Use when evaluating architectural decisions, reviewing feature proposals, checking alignment with framework principles, or when tenets, principles, or design philosophy are mentioned.
- ▌ Be Clark · outfitter-dev bundleEmbody Clark, Trails' co-architect and architectural conscience. Use when the current agent should be Clark inline for framework architecture, doctrine, vocabulary, ADRs, tenet alignment, long-horizon coherence, pathfinding, assessment, calibration, debriefs, or a direct request to "be Clark" or answer as Clark. Do not use merely to ask a separate Clark subagent; use ask-trails-crew for that.
- ▌ Be Lewis · outfitter-dev bundleEmbody Lewis, Trails' co-architect and execution conscience. Use when the current agent should be Lewis inline to turn doctrine into landed work, shape goals and Graphite stacks, coordinate agents, run evidence and review loops, settle releases, debrief execution, or answer a direct request to "be Lewis" or work as Lewis.
- ▌ Trails Adrs · outfitter-dev bundleAuthor, update, and manage Trails ADRs. Use when creating new ADRs, promoting drafts to accepted, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.
- ▌ Clark Survey · outfitter-devAutonomous codebase health scan for vocabulary drift, naming convention violations, structural anti-patterns, documentation staleness, and test health. Produces prioritized findings as Linear issues. Use for health checks, scheduled scans, or after heavy unreviewed agent work.
- ▌ Regrade Loop · outfitter-devRun a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.
- ▌ Clark Decision · outfitter-devAuthoritative architectural ruling on a specific Trails framework question — naming choices, vocabulary compliance, pattern fitness, scope decisions. Consults the constitutional hierarchy, decides, and logs. Use when a definitive call is needed or when 'let Clark decide' is the instruction.
- ▌ Ask Trails Crew · outfitter-dev bundleRoute a Trails question to native Clark and/or Lewis subagents and synthesize their distinct judgments. Use when the user asks the Trails crew, asks Clark or Lewis, requests an architectural or execution second opinion, wants both co-architects to review a question, or delegates a Trails judgment to the appropriate persona. Do not use when the current agent should embody Clark or Lewis inline; use be-clark or be-lewis instead.
- ▌ Building Trails · outfitter-devThe working-on-Trails doctrine digest — what governs the framework, the decision tools for framework work, and where truth lives. Use at the start of any session that changes Trails itself (framework code, docs, vocabulary, governance), when orienting a new agent or persona, or when deciding which governing source answers a question. Not for building apps with Trails; the trails skill covers consuming the framework.
- ▌ Trails Editorial · outfitter-devComplete Trails editorial review workflow. Use when reviewing docs, ADRs, README changes, release notes, agent guidance, or docs-heavy PRs for voice, style, structure, correctness, and readiness.
- ▌ Trails Goal Loop · outfitter-dev bundleDefine, execute, and settle durable Trails goals. Use for non-trivial Trails work spanning issues, Graphite branches or stacks, agents, review loops, CI, release or publication gates, or whenever a Trails goal needs an explicit completion horizon, authority boundary, evidence contract, and resumable packet.
- ▌ Clark Pathfinding · outfitter-devBig-picture architectural planning and exploration for the Trails framework. Socratic, principle-anchored exploration of features, ADRs, tenets, and horizon planning. Use when planning new capabilities, drafting or revising ADRs, exploring architectural questions, reviewing tenets, or doing horizon planning.
- ▌ Trails Error Format · outfitter-devUse when reviewing Trails error taxonomy, surface error rendering, redaction, retryability, or Result-vs-throw boundaries. Helps distinguish runtime failures from intentional construction and host-boundary throws.
- ▌ Trails Writing Docs · outfitter-devTrails documentation structure and maintenance guidance. Use when creating or reorganizing Trails docs, READMEs, guides, reference pages, release docs, or agent-facing documentation.
- ▌ Trails Local Review · outfitter-dev bundleReview a Trails branch, Graphite stack, milestone, generated artifact, migration, documentation set, or implementation slice against current repository doctrine and written acceptance. Use for pre-submit review, targeted risk review, review-fix loops, or a final readiness judgment with evidence-backed P0-P3 findings.
- ▌ Trails Dogfood Check · outfitter-devUse when reviewing Trails-owned framework code for Result-shaped failures, resource and cwd boundaries, app loading, and documented host construction exceptions.
- ▌ Trails Writing Style · outfitter-dev bundleTrails prose craft and lexicon style. Use when writing or reviewing docs, ADRs, examples, release notes, agent prompts, comments, PR descriptions, or issue language for rhythm, clarity, and vocabulary precision.
- ▌ Trails Writing Voice · outfitter-devTrails writing voice and values. Use when drafting or reviewing Trails docs, ADRs, README content, release notes, agent guidance, or public explanations for stance, audience, and tone.
- ▌ Trails Warden Advisory · outfitter-devUse when deciding whether a Trails hardening finding belongs in Warden, repo-local Oxlint, docs, an advisory skill, or no rule. Helps agents classify prevention candidates by owner source, Warden tier, lifecycle, diagnostic shape, and false-positive risk.
- ▌ Trails Primitive Parity · outfitter-devUse when comparing maturity across Trails primitives without assuming every primitive must match trail capabilities. Helps agents identify deliberate gaps, real user-facing gaps, and future-facing symmetry pressure.
- ▌ Trails Derive From Source · outfitter-devUse when a Trails change derives framework facts, derived views, rule data, or surface metadata. Helps agents find authoritative owner exports and avoid shadow registries, duplicated maps, and canonical-source indirection.
- ▌ Trails Discriminate Union · outfitter-devUse when reviewing public or queryable Trails outputs that expose union-like shapes to agents or surfaces. Helps decide whether stable discriminants are required and whether the issue is schema cleanup, advisory guidance, or Warden work.
- ▌ Trails Language Styleguide · outfitter-devCompatibility pointer for older Trails prompts. Prefer `trails-writing-voice`, `trails-writing-style`, `trails-writing-docs`, or `trails-editorial` when writing or reviewing Trails docs, ADRs, agent prompts, examples, comments, or contributor guidance.
- ▌ Docs Worker · outfitter-devWrites package documentation from code analysis — READMEs, pattern guides, API docs.
- ▌ Scaffold Trial · outfitter-dev bundleOrchestrate scaffold smoke testing across presets. Dispatches parallel tester agents, collects reports, synthesizes findings, and files Linear issues. Use when scaffold trial, smoke test presets, or /scaffold-trial are mentioned.
- ▌ Library Worker · outfitter-devImplements code changes in the Outfitter monorepo — bug fixes, utilities, testing primitives, refactors.
- ▌ Scaffold Testing · outfitter-dev bundleSmoke test a scaffold preset end-to-end. Runs init, install, build, test, explores output, and writes a structured report.json with quality scores. Use when scaffold testing, preset smoke test, or scaffold report are mentioned.
- ▌ Scaffold Reporting · outfitter-dev bundleSynthesize scaffold test reports into cross-preset summaries with score aggregation, trend analysis, and Linear issue recommendations. Use after scaffold testing completes.
- ▌ Debug · outfitter-devTroubleshoots Outfitter Dev Kit issues including Result handling, MCP problems, CLI output, exit codes, and logging. Use when debugging stack-specific issues, unexpected errors, wrong output modes, or when "debug Result", "MCP not working", "wrong exit code", or "logging issue" are mentioned.
- ▌ Outfitter Voice · outfitter-devOutfitter's philosophical voice and values — opinionated stance, agent-first design, earned confidence. Use when writing content, reviewing drafts, or establishing tone.
- ▌ Review · outfitter-devAudits code for Outfitter Dev Kit compliance including Result types, error handling, logging patterns, and path safety. Use for pre-commit reviews, code quality checks, migration validation, or when "audit", "check compliance", "review stack", or "stack patterns" are mentioned.
- ▌ Bun First · outfitter-dev bundleBun-first development: prefer native APIs over npm packages, audit for migration opportunities, eliminate unnecessary dependencies. Use when evaluating packages, starting projects, or migrating from Node.js.
- ▌ CLI Craft · outfitter-dev bundleThis skill should be used when designing, implementing, or reviewing CLI tools, or when flags, subcommands, help text, exit codes, or CLI patterns are mentioned.
- ▌ Check Skill Formatting · outfitter-dev bundleChecks skill files for formatting violations — preprocessing patterns, placeholder conventions, and frontmatter. Use when validating skills, checking formatting, or when check formatting, lint skills, or skill quality are mentioned.
- ▌ Skillcheck · outfitter-dev bundleValidates skill quality — preprocessing safety, frontmatter, line counts, references. Use when checking skills, validating SKILL.md, or when skillcheck, lint skill, or validate skill are mentioned.
- ▌ Scaffold · outfitter-dev bundleCreates handlers, CLI commands, MCP tools, and daemon services following Outfitter Dev Kit conventions. Use when adding new components to a project, scaffolding code, or when "create handler", "new command", "add tool", or "daemon service" are mentioned.
- ▌ Migration · outfitter-dev bundleAudits existing code and recommends migration paths to Outfitter Dev Kit patterns. Use when adopting the stack in an existing project, converting throw to Result, migrating console to structured logging, or when "migrate", "adopt stack", "convert to Result", or "upgrade to outfitter" are mentioned.
- ▌ Claude Craft · outfitter-dev bundleClaude Code extensibility — agents, commands, hooks, skills, rules, and configuration. Use when creating, configuring, or troubleshooting Claude Code components, or when agent.md, /command, hooks.json, SKILL.md, .claude/rules, settings.json, MCP server, PreToolUse, or create agent/command/hook are mentioned.
- ▌ Sanity Check · outfitter-dev bundleThis skill should be used when evaluating complexity, planning features, or when over-engineering, simpler, is this overkill, or keep it simple are mentioned.
- ▌ Outfitter Editorial · outfitter-dev bundleComplete editorial review for Outfitter documentation — voice, style, correctness, and completeness. Use when reviewing docs, auditing before merge, or checking content quality.
- ▌ Linear Project Management · outfitter-dev bundleGuides Linear project management — creates projects over tracking issues, structures PRDs, phases milestones, sizes issues, applies labels, and formats cross-references. Use when creating Linear projects, planning work, or organizing issues.
- ▌ Find Patterns · outfitter-dev bundleThis skill should be used when recognizing recurring themes, identifying patterns in work or data, or when pattern, recurring, or repeated are mentioned. For implementation, see codify skill.
- ▌ Use Subagents · outfitter-dev bundleThis skill should be used when coordinating agents, delegating tasks to specialists, or when dispatch agents, which agent, or multi-agent are mentioned.
- ▌ Debug Outfitter · outfitter-dev bundleSystematic debugging process for @outfitter/* package issues. Use when debugging Result handling, MCP problems, CLI output, exit codes, logging, or unexpected behavior. Produces structured investigation reports with root cause analysis.
- ▌ Outfitter Atlas · outfitter-devGenerates patterns, templates, and guides for @outfitter/* packages. Covers transport-agnostic handler systems, Result types, error taxonomy, and package APIs. Use when working with @outfitter/*, Result types, Handler contract, error taxonomy, or when Result, Handler, ValidationError, NotFoundError, OutfitterError, or package names like contracts, cli, mcp, schema, tui, daemon, config, logging are mentioned.
- ▌ Outfitter Check · outfitter-dev bundleVerify Outfitter compliance in a codebase. Scans for anti-patterns (throws, console, hardcoded paths) and produces a severity-ranked compliance report. Use for pre-commit checks, code review, or migration validation.
- ▌ Outfitter Issue · outfitter-dev bundleSubmit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.
- ▌ Outfitter Start · outfitter-dev bundleStart with Outfitter — scaffold new projects or adopt patterns in existing codebases. Detects context, scans for adoption candidates, and orchestrates phased conversion.
- ▌ Outfitter Styleguide · outfitter-dev bundleWriting craft and style patterns for Outfitter content — sentence rhythm, metaphors, enthusiasm calibration. Use when drafting or reviewing blog posts, docs, announcements, or READMEs.
- ▌ Bun Fieldguide · outfitter-dev bundleThis skill should be used when working with Bun runtime, bun:sqlite, Bun.serve, bun:test, or when Bun, bun:test, or Bun-specific patterns are mentioned.
- ▌ Prove It Works · outfitter-dev bundleThis skill should be used when validating features end-to-end without mocks, testing integrations, or when scenario test, e2e test, or no mocks are mentioned.
- ▌ Systems Design · outfitter-dev bundleThis skill should be used when designing systems, evaluating architectures, making technology decisions, or planning for scale. Provides technology selection frameworks, scalability planning, and architectural tradeoff analysis.
- ▌ Tdd Fieldguide · outfitter-dev bundleThis skill should be used when implementing features with TDD, writing tests first, or refactoring with test coverage. Applies disciplined Red-Green-Refactor cycles with TypeScript/Bun and Rust tooling.
- ▌ Hono Fieldguide · outfitter-dev bundleThis skill should be used when building APIs with Hono, using hc client, implementing OpenAPI, or when Hono, RPC, or type-safe API are mentioned.
- ▌ Outfitter Upgrade · outfitter-dev bundleManages @outfitter/* package upgrades — handles version detection, dependency bumps, mechanical codemods, and test verification. Use when upgrading dependencies, migrating breaking changes, or running outfitter upgrade.
- ▌ Outfitter Agents Check · outfitter-dev bundleChecks and configures Outfitter marketplaces and plugins. Use when setting up projects or checking plugin configuration.
- ▌ Outfitter Agents Setup · outfitter-dev bundleDocumentation patterns for AI agents — AGENTS.md, CLAUDE.md, and agent-readable content. Use when creating agent entry points or structuring .claude/ directories.
- ▌ Outfitter CLI · outfitter-devDeep patterns for @outfitter/cli including output modes, pagination, input parsing, and Commander.js integration. Use when building CLI commands, handling output formatting, implementing pagination, or when "CLI output", "pagination", "exitWithError", or "@outfitter/cli" are mentioned.
- ▌ Outfitter MCP · outfitter-devDeep patterns for @outfitter/mcp including tool registration, Zod schemas, resources, and server configuration. Use when building MCP servers, registering tools, defining resources, or when "MCP server", "MCP tool", "registerTool", or "@outfitter/mcp" are mentioned.
- ▌ React Fieldguide · outfitter-dev bundleThis skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and TanStack Router integration.
- ▌ Skill Distillery · outfitter-dev bundleDistills tool patterns from external repositories into teachable skills and plugins. Use when build plugin for, create skills for CLI, package as plugin, repo to plugin, or turn into plugin are mentioned.
- ▌ Outfitter Documentation · outfitter-dev bundleDocumentation structure and templates for READMEs, API docs, guides, and CLI references. Use when creating docs, writing READMEs, or structuring a docs/ directory.
- ▌ Codebase Analysis · outfitter-dev bundleThis skill should be used when analyzing codebases, understanding architecture, or when analyze, investigate, explore code, or understand architecture are mentioned.
- ▌ Outfitter Daemon · outfitter-devPatterns for @outfitter/daemon including lifecycle management, IPC communication, health checks, and PID files. Use when building background services, daemons, or when "daemon", "IPC", "health check", "background service", or "@outfitter/daemon" are mentioned.
- ▌ Outfitter Logging · outfitter-devPatterns for @outfitter/logging including structured logging, sinks, redaction, and child loggers. Use when configuring logging, adding redaction, creating sinks, or when "logger", "structured logging", "redaction", "log level", or "@outfitter/logging" are mentioned.
- ▌ Outfitter Testing · outfitter-devTesting patterns for @outfitter/* packages using test harnesses, fixtures, and Bun test runner. Use when writing tests, setting up test harnesses, mocking context, or when "test handler", "test CLI", "test MCP", or "@outfitter/testing" are mentioned.
- ▌ Migration Feedback · outfitter-devCreates GitHub issues for problems discovered during migration to Outfitter Dev Kit. Use when migration reveals bugs, missing features, unclear documentation, or improvement opportunities in @outfitter/* packages.
- ▌ Typescript Fieldguide · outfitter-dev bundleThis skill should be used when writing TypeScript, eliminating any types, implementing Zod validation, or when strict type safety is needed. Covers modern TS 5.5+ features and runtime validation patterns.
- ▌ Cc Actions · outfitter-dev bundleConfigure Claude Code GitHub Actions workflows effectively. Covers automatic mode detection, event routing, subagent coordination, hooks for quality gates, MCP server integration, reusable workflows, performance optimization, and security best practices for fork-based PRs. Use when working with GitHub Actions, CI/CD automation, PR reviews, issue automation, claude-code-action, chatops, MCP servers, fork safety, or reusable workflows.
- ▌ Software Craft · outfitter-dev bundleThis skill should be used when making design decisions, evaluating trade-offs, assessing code quality, or when "engineering judgment" or "code quality" are mentioned.
- ▌ Typescript Dev · outfitter-dev bundleThis skill should be used when writing TypeScript, eliminating any types, implementing Zod validation, or when strict type safety is needed. Covers modern TS 5.5+ features and runtime validation patterns.
- ▌ Claude Commands · outfitter-dev bundleThis skill should be used when creating slash commands, writing command files, or when "/command", ".claude/commands", "$ARGUMENTS", or "create command" are mentioned.
- ▌ Multi Agent Vcs · outfitter-devThis skill should be used when dispatching subagents for parallel development, coordinating multi-branch implementations, or when "parallel agents", "orchestrator commits", "subagent filesystem only", "multi-agent git", or "prevent stack corruption" are mentioned. Prevents stack corruption through orchestrator-only git policy.
- ▌ Plugin Engineer · outfitter-dev bundleTransforms external repositories (CLIs, libraries, MCP servers) into Claude Code plugins with skills. Use when "build plugin for", "create skills for CLI", "package as plugin", "repo to plugin", or "turn into plugin" are mentioned.
- ▌ Report Findings · outfitter-dev bundleThis skill should be used when synthesizing multi-source research, presenting findings with attribution, or when "report", "findings", or "synthesis" are mentioned.
- ▌ Find Root Causes · outfitter-dev bundleThis skill should be used when diagnosing failures, investigating incidents, finding root causes, or when "root cause", "diagnosis", "investigate", or "--rca" are mentioned.
- ▌ Session Analysis · outfitter-dev bundleThis skill should be used when analyzing conversation patterns, identifying frustration or success signals, or when "analyze conversation", "what went wrong", or "patterns" are mentioned.
- ▌ Skills Discovery · outfitter-dev bundleFind and evaluate community skills, plugins, and marketplaces. Use when searching for existing skills, evaluating safety, or when "find skill", "discover plugin", "community skills", or "marketplace" are mentioned.
- ▌ Skills Workflows · outfitter-dev bundleDesign multi-skill workflow systems with artifact-based state handoff. Use when building skill pipelines, sequenced workflows, or when "workflow system", "skill pipeline", "state handoff", or "artifacts" are mentioned.
- ▌ Stack Audit · outfitter-dev bundleScan codebase for Outfitter Stack adoption candidates. Identifies throw statements, console usage, hardcoded paths, and custom errors. Use when assessing adoption scope or checking readiness.
- ▌ Stack Debug · outfitter-devTroubleshoots Outfitter Stack issues including Result handling, MCP problems, CLI output, exit codes, and logging. Use when debugging stack-specific issues, unexpected errors, wrong output modes, or when "debug Result", "MCP not working", "wrong exit code", or "logging issue" are mentioned.
- ▌ Stack Review · outfitter-devAudits code for Outfitter Stack compliance including Result types, error handling, logging patterns, and path safety. Use for pre-commit reviews, code quality checks, migration validation, or when "audit", "check compliance", "review stack", or "stack patterns" are mentioned.
- ▌ Context Management · outfitter-dev bundleManage context window, survive compaction, persist state. Use when planning long tasks, coordinating agents, approaching context limits, or when "context", "compaction", "tasks", or "persist state" are mentioned.
- ▌ Claude Plugin Audit · outfitter-devAudits Claude Code plugins for structure, quality, and best practices. Use when validating plugins, checking plugin health, or before publishing.
- ▌ Stack Feedback · outfitter-dev bundleCreates GitHub issues for problems discovered while using @outfitter/* packages. Use when finding bugs, missing features, unclear documentation, or improvement opportunities.
- ▌ Stack Patterns · outfitter-dev bundleReference for Outfitter Stack patterns including Result types, Handler contract, Error taxonomy, and @outfitter/* package conventions. Use when learning the stack, looking up patterns, understanding packages, or when "Result", "Handler", "error taxonomy", "OutfitterError", "CLI output", "pagination", "MCP server", "MCP tool", "structured logging", "redaction", "test handler", "daemon", "IPC", or "@outfitter/*" are mentioned.
- ▌ Stack Templates · outfitter-dev bundleTemplates for creating handlers, CLI commands, MCP tools, and daemon services following Outfitter Stack conventions. Use when scaffolding new components, creating handlers, adding commands, or when "create handler", "new command", "add tool", "scaffold", "template", or "daemon service" are mentioned.
- ▌ Stack Architecture · outfitter-devDesign 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.
- ▌ Code Review · outfitter-dev bundleThis skill should be used when reviewing code before commit, conducting quality gates, or when "review", "fresh eyes", "pre-commit review", or "quality gate" are mentioned.
- ▌ Pathfinding · outfitter-dev bundleThis skill should be used when requirements are unclear, brainstorming ideas, or when "pathfind", "brainstorm", "figure out", "clarify requirements", or "work through" are mentioned.
- ▌ Performance · outfitter-dev bundleThis skill should be used when profiling code, optimizing bottlenecks, benchmarking, or when "performance", "profiling", "optimization", or "--perf" are mentioned.
- ▌ Architecture · outfitter-dev bundleThis skill should be used when designing systems, evaluating architectures, making technology decisions, or planning for scale. Provides technology selection frameworks, scalability planning, and architectural tradeoff analysis.
- ▌ Check Status · outfitter-dev bundleThis skill should be used when checking project status, starting sessions, reviewing activity, or when "sitrep", "status report", or "what's changed" are mentioned.
- ▌ Claude Hooks · outfitter-dev bundleThis skill should be used when creating hooks, automating workflows, or when "PreToolUse", "PostToolUse", "hooks.json", "event handler", or "create hook" are mentioned.
- ▌ Claude Rules · outfitter-devThis skill should be used when creating rule files, organizing conventions, or when ".claude/rules/", "FORMATTING.md", "create rule", or "project conventions" are mentioned.
- ▌ Codex Config · outfitter-dev bundleThis skill should be used when configuring Codex CLI, setting up profiles, or when "config.toml", "sandbox mode", "Codex config", or "approval policy" are mentioned.
- ▌ Claude Agents · outfitter-dev bundleThis skill should be used when creating agents, writing agent frontmatter, configuring subagents, or when "create agent", "agent.md", "subagent", or "Task tool" are mentioned.
- ▌ Claude Config · outfitter-dev bundleThis skill should be used when configuring Claude, setting up MCP servers, or when "settings.json", "claude_desktop_config", "MCP server", or "Claude config" are mentioned.
- ▌ Claude Skills · outfitter-dev bundleThis skill should be used when creating Claude Code skills with Claude-specific features like allowed-tools, context modes (fork/inherit), argument-hint, or model overrides. Triggers on "Claude skill", "allowed-tools", "context fork", "skill arguments".
- ▌ Claude Plugins · outfitter-dev bundleThis skill should be used when creating plugins, publishing to marketplaces, or when "plugin.json", "marketplace", "create plugin", or "distribute plugin" are mentioned.