outfitter-dev
- 224 skills
- 0 followers
- last month last updated
- ▌ Trails 3 · outfitter-dev bundleThis skill should be used when creating session handoffs, logging research findings, or reading previous trail notes. Triggers include handoff, session continuity, log note, trail notes, or when ending a session.
- ▌ Clark Survey 3 · 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.
- ▌ Clark Decision 3 · 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.
- ▌ Use Skillset 4 · outfitter-devUse the skillset compiler to build, check, inspect, and import source skills or plugins.
- ▌ CLI Testing 2 · outfitter-devCLI testing guidance and patterns. Loaded by /ops/test/cli command or subagents for comprehensive Navigator CLI testing.
- ▌ Skillset Dev 3 · outfitter-devRoute work on the Skillset compiler repository through its tenets, accepted ADRs, and focused contributor skills. Use whenever changing or reviewing Skillset source, compiler behavior, schemas, tests, fixtures, generated output, or contributor workflows.
- ▌ Skillset Adrs 3 · outfitter-dev bundleAuthor, update, and manage Skillset ADRs. Use when creating new ADRs, promoting drafts, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.
- ▌ Skillset Dev Schema 3 · outfitter-dev bundleChange or review Skillset workspace config, source frontmatter, shared metadata fields, structural validation, examples, and generated schema artifacts. Use whenever adding, removing, renaming, validating, or documenting a key shared by compiler and authoring surfaces.
- ▌ Skillset Dev Testing 3 · outfitter-dev bundleDesign, implement, or review Skillset compiler tests, internal fixtures, deterministic projection, adapter conformance, self-hosted checks, and external adoption evidence. Use when choosing a test tier, creating fake repositories, changing test infrastructure, or proving compiler and provider-output behavior.
- ▌ Skillset Dev Compiler 3 · outfitter-dev bundleImplement or review Skillset compiler behavior, package ownership, rendering, command composition, operation results, and generated-output semantics. Use for changes under apps/skillset or packages/core, registry, lint, transforms, toolkit, or workbench that are not primarily shared schema-contract changes.
- ▌ Use Skillset 3 · outfitter-dev bundleUse the skillset compiler to build, check, inspect, and import source skills or plugins.
- ▌
- ▌ Codify 2 · outfitter-dev bundleThis skill should be used when implementing patterns as Claude Code components (skills, commands, hooks, agents), or when codify, capture workflow, turn into a skill, or make reusable are mentioned. For pattern identification, see find-patterns skill.
- ▌ Research 2 · outfitter-dev bundleThis skill should be used when researching best practices, evaluating technologies, comparing approaches, or when research, evaluation, or comparison are mentioned.
- ▌ Security 2 · outfitter-dev bundleThis skill should be used when auditing code for security issues, reviewing authentication/authorization, evaluating input validation, analyzing cryptographic usage, or reviewing dependency security. Provides OWASP patterns, CWE analysis, and threat modeling guidance.
- ▌ Debugging 2 · outfitter-dev bundleThis skill should be used when encountering bugs, errors, failing tests, or unexpected behavior. Provides systematic debugging with evidence-based root cause investigation using a four-stage framework.
- ▌ Docs Audit 2 · outfitter-dev bundleComprehensive documentation audit against current code state. Checks markdown files for accuracy, link validity, code example correctness, and docstring coverage. Uses efficient discovery to minimize context usage while providing thorough analysis.
- ▌ Which Tool 2 · outfitter-dev bundleThis skill should be used when choosing CLI tools, a tool seems slow, or when best tool, which tool, or tool alternatives are mentioned.
- ▌ Patterns 2 · outfitter-dev bundleReference for Outfitter Dev Kit conventions including Result types, Handler contract, Error taxonomy, and transport-agnostic patterns. Use when learning the stack, looking up patterns, understanding @outfitter/* packages, or when "Result", "Handler", "error taxonomy", or "OutfitterError" are mentioned.
- ▌ Code Review 2 · 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 2 · 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 2 · outfitter-dev bundleThis skill should be used when profiling code, optimizing bottlenecks, benchmarking, or when performance, profiling, optimization, or --perf are mentioned.
- ▌ Check Status 2 · 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.
- ▌ Codex Config 2 · 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 Plugins 2 · 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.
- ▌ Maintain Tasks 2 · outfitter-devTask management for session continuity. Use when coordinating multi-step work, managing subagent assignments, or preserving intent across compaction. Triggers on track tasks, manage work, coordinate agents, or when complex work requires sequencing.
- ▌ Software Craft 2 · 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.
- ▌ Report Findings 2 · 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 2 · 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 2 · 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 Workflows 2 · 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.
- ▌ Context Management 2 · 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.
- ▌ Trails 2 · outfitter-dev bundleBuild with the Trails framework — define trail contracts, open CLI/MCP surfaces, test with examples, debug errors, migrate codebases, run governance. Use when creating trails, adding surfaces, testing, debugging Trails errors, migrating to Trails, running warden, or any work involving @ontrails/* packages.
- ▌ Tenets 3 · 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 3 · 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 3 · 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.
- ▌ Clark Survey 2 · 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.
- ▌ Trails Adrs 3 · 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 Decision 2 · 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.
- ▌ Regrade Loop 3 · outfitter-devRun a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.
- ▌ Ask Trails Crew 3 · 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 3 · 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 4 · 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 3 · 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 3 · 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 Local Review 3 · 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.
- ▌ Bun Dev 2 · 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.
- ▌ Waymark CLI 2 · outfitter-dev bundleThis skill should be used when the user asks about "wm command", "waymark cli", "wm find", "wm add", "wm edit", "wm rm", "wm fmt", "wm lint", or needs to use waymark tooling. Requires `using-waymarks` skill for syntax fundamentals. Provides comprehensive CLI command reference and workflows.
- ▌ Using Waymarks 2 · outfitter-dev bundleThis skill should be used when the user asks about "waymark syntax", "writing waymarks", "::: sigil", "tldr waymarks", "about waymarks", searching waymarks with ripgrep, or mentions waymark grammar, signals, markers, or properties. Provides comprehensive guidance for authoring and searching waymarks without requiring CLI tools.
- ▌
- ▌ Skillset Dev 2 · outfitter-devRoute work on the Skillset compiler repository through its tenets, accepted ADRs, and focused contributor skills. Use whenever changing or reviewing Skillset source, compiler behavior, schemas, tests, fixtures, generated output, or contributor workflows.
- ▌ Skillset Adrs 2 · outfitter-dev bundleAuthor, update, and manage Skillset ADRs. Use when creating new ADRs, promoting drafts, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.
- ▌ Skillset Dev Schema 2 · outfitter-dev bundleChange or review Skillset workspace config, source frontmatter, shared metadata fields, structural validation, examples, and generated schema artifacts. Use whenever adding, removing, renaming, validating, or documenting a key shared by compiler and authoring surfaces.
- ▌ Skillset Dev Testing 2 · outfitter-dev bundleDesign, implement, or review Skillset compiler tests, internal fixtures, deterministic projection, adapter conformance, self-hosted checks, and external adoption evidence. Use when choosing a test tier, creating fake repositories, changing test infrastructure, or proving compiler and provider-output behavior.
- ▌ Skillset Dev Compiler 2 · outfitter-dev bundleImplement or review Skillset compiler behavior, package ownership, rendering, command composition, operation results, and generated-output semantics. Use for changes under apps/skillset or packages/core, registry, lint, transforms, toolkit, or workbench that are not primarily shared schema-contract changes.
- ▌ Use Skillset 2 · outfitter-dev bundleUse the skillset compiler to build, check, inspect, and import source skills or plugins.
- ▌
- ▌ Tenets 2 · 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 2 · 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 2 · 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 2 · 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.
- ▌ Regrade Loop 2 · outfitter-devRun a Trails Regrade migration loop with dry-run discovery, occurrence judgment, safe apply, verification, ledger capture, and per-cycle resume.
- ▌ Ask Trails Crew 2 · 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 2 · 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 3 · 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 2 · 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 2 · 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 Local Review 2 · 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 Writing Docs 2 · 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 Writing Style 2 · 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 2 · 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 Editorial 2 · 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.
- ▌
- ▌ Dispatch · outfitter-devUse when operating dispatch, creating or attaching Codex lanes, sending/steering/context-injecting/stopping through dispatch, checking provider capacity, managing triggers, checking daemon status/logs, or configuring the dispatch MCP/plugin surface. Not for changing dispatch source code; use AGENTS.md for implementation work.
- ▌ MCP Testing · outfitter-devMCP testing guidance and patterns. Loaded by /ops/test/mcp command or subagents for comprehensive Navigator MCP server testing.
- ▌ Upstream Evaluation · outfitter-devEvaluate upstream changes using Navigator's design frameworks to decide what to adopt, skip, or adapt
- ▌ Firewatch · outfitter-dev bundleQuery GitHub PR activity using the Firewatch CLI (fw). Fetch, cache, filter, and act on PR comments, reviews, commits, and CI status. Outputs JSONL for jq composition. Use when checking PR status, finding review comments, querying activity, resolving feedback, or working with GitHub pull requests.
- ▌ Fw CLI Testing · outfitter-dev bundleParallel CLI stress testing using orchestrated subagents. Spawns specialized agents to test different CLI domains simultaneously, aggregating results into structured reports. Supports discovery mode (agents analyze CLI structure) and directive mode (runbooks specify tests). Use when stress testing the Firewatch CLI, validating commands, or running comprehensive test coverage.
- ▌ Firewatch Guide · outfitter-dev bundleGuides GitHub PR activity workflows using the Firewatch CLI (fw) and MCP server. Use when triaging PRs, responding to review feedback, querying PR activity, or when the user mentions firewatch, PR reviews, PR comments, or review threads.
- ▌ CLI Testing · outfitter-devCLI testing guidance and patterns. Loaded by /ops/test/cli command or subagents for comprehensive testing.
- ▌
- ▌ Waymark CLI · outfitter-dev bundleThis skill should be used when the user asks about "wm command", "waymark cli", "wm find", "wm add", "wm edit", "wm rm", "wm fmt", "wm lint", or needs to use waymark tooling. Requires `using-waymarks` skill for syntax fundamentals. Provides comprehensive CLI command reference and workflows.
- ▌ Waymark Maintenance · outfitter-dev bundlePlaces and maintains waymarks across a codebase, focusing on TLDR coverage and accuracy. Delegates to the waymarker agent for systematic auditing and placement. Use when adding TLDRs to files, auditing waymark coverage, updating stale waymarks, or when "add waymarks", "TLDR coverage", "waymark audit" is mentioned.
- ▌ Using Waymarks · outfitter-dev bundleThis skill should be used when the user asks about "waymark syntax", "writing waymarks", "::: sigil", "tldr waymarks", "about waymarks", searching waymarks with ripgrep, or mentions waymark grammar, signals, markers, or properties. Provides comprehensive guidance for authoring and searching waymarks without requiring CLI tools.
- ▌
- ▌ Voice · outfitter-devOutfitter's philosophical voice and values. Covers opinionated stance, agent-first design, goal-serving content, and earned confidence. Use when writing Outfitter content, reviewing drafts, establishing tone, or when "voice", "tone", "messaging", "brand", or "how we write" are mentioned.
- ▌ Use Bun · outfitter-dev bundleBun-first development patterns for TypeScript projects. Use when auditing Node.js projects for migration opportunities, starting new projects, evaluating npm dependencies, or reducing package.json bloat. Triggers on mentions of npm, yarn, pnpm, Node.js migration, dependency audit, or package optimization.
- ▌ Agent Docs · outfitter-dev bundleDocumentation for AI agents — AGENTS.md, CLAUDE.md, and agent-readable content patterns. Use when creating agent entry points, structuring .claude/ directories, or when "CLAUDE.md", "AGENTS.md", "agent documentation", "machine-readable", or "writing for agents" are mentioned. Covers both configuration and content patterns for agent consumption.
- ▌ Docs Check · outfitter-devRigorous quality gate for documentation before merge or publish. Verifies code examples run, links resolve, APIs match implementation, and all sections are complete. Use when auditing docs, reviewing documentation PRs, or when "verify", "quality gate", "docs audit", or "check examples" is mentioned.
- ▌ Docs Write · outfitter-devProject documentation structure and templates — READMEs, API docs, guides, and CLI references. Use when creating documentation, structuring a docs/ directory, writing READMEs, or when "documentation", "README", "API docs", "docs structure", or "guides" are mentioned. Pair with styleguide for writing craft; apply voice as a review pass.
- ▌ Styleguide · outfitter-dev bundleWriting craft and style patterns for Outfitter content—sentence rhythm, metaphor usage, enthusiasm calibration, structural moves. Use when drafting blog posts, documentation, announcements, or READMEs, or when "styleguide", "writing style", "voice", or "tone" are mentioned. Pair with voice for philosophical foundation, docs-write for structure templates.
- ▌ Agent Setup · outfitter-dev bundleCheck and configure outfitter marketplaces and plugins. Use when setting up a new project, checking plugin configuration, or when "setup outfitter", "configure plugins", or "marketplace" are mentioned.
- ▌ Docs Review · outfitter-devReviews documentation for voice, style, and structure alignment with Outfitter standards. Use when reviewing docs, checking content quality, or when "review this doc", "voice check", "style review", or "is this ready?" are mentioned.
- ▌ Skillset Dev · outfitter-devRoute work on the Skillset compiler repository through its tenets, accepted ADRs, and focused contributor skills. Use whenever changing or reviewing Skillset source, compiler behavior, schemas, tests, fixtures, generated output, or contributor workflows.
- ▌ Use Skillset · outfitter-dev bundleUse the skillset compiler to build, check, inspect, and import source skills or plugins.
- ▌ Skillset Adrs · outfitter-dev bundleAuthor, update, and manage Skillset ADRs. Use when creating new ADRs, promoting drafts, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.
- ▌ Skillset Dev Schema · outfitter-dev bundleChange or review Skillset workspace config, source frontmatter, shared metadata fields, structural validation, examples, and generated schema artifacts. Use whenever adding, removing, renaming, validating, or documenting a key shared by compiler and authoring surfaces.
- ▌ Skillset Dev Testing · outfitter-dev bundleDesign, implement, or review Skillset compiler tests, internal fixtures, deterministic projection, adapter conformance, self-hosted checks, and external adoption evidence. Use when choosing a test tier, creating fake repositories, changing test infrastructure, or proving compiler and provider-output behavior.
- ▌ Skillset Dev Compiler · outfitter-dev bundleImplement or review Skillset compiler behavior, package ownership, rendering, command composition, operation results, and generated-output semantics. Use for changes under apps/skillset or packages/core, registry, lint, transforms, toolkit, or workbench that are not primarily shared schema-contract changes.
- ▌