fieldguides

Plugin fieldguides from marketplace outfitter in outfitter-dev/outfitter. Commands read from the repo's manifest — 1 month ago.

Skills (37)

• bun-fieldguide

  This 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.

• bun-first

  Bun-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.

• check-status

  This skill should be used when checking project status, starting sessions, reviewing activity, or when sitrep, status report, or what's changed are mentioned.

• claude-craft

  Claude 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 m

• claude-plugins

  This skill should be used when creating plugins, publishing to marketplaces, or when plugin.json, marketplace, create plugin, or distribute plugin are mentioned.

• cli-craft

  This skill should be used when designing, implementing, or reviewing CLI tools, or when flags, subcommands, help text, exit codes, or CLI patterns are mentioned.

• code-review

  This 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.

• codebase-analysis

  This skill should be used when analyzing codebases, understanding architecture, or when analyze, investigate, explore code, or understand architecture are mentioned.

• codex-config

  This skill should be used when configuring Codex CLI, setting up profiles, or when config.toml, sandbox mode, Codex config, or approval policy are mentioned.

• codify

  This 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.

• context-management

  Manage 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.

• debugging

  This 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

  Comprehensive 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.

• find-patterns

  This 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.

• find-root-causes

  This skill should be used when diagnosing failures, investigating incidents, finding root causes, or when root cause, diagnosis, investigate, or --rca are mentioned.

• hono-fieldguide

  This skill should be used when building APIs with Hono, using hc client, implementing OpenAPI, or when Hono, RPC, or type-safe API are mentioned.

• maintain-tasks

  Task 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.

• pathfinding

  This skill should be used when requirements are unclear, brainstorming ideas, or when pathfind, brainstorm, figure out, clarify requirements, or work through are mentioned.

• performance

  This skill should be used when profiling code, optimizing bottlenecks, benchmarking, or when performance, profiling, optimization, or --perf are mentioned.

• prove-it-works

  This 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.

• react-fieldguide

  This 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.

• report-findings

  This skill should be used when synthesizing multi-source research, presenting findings with attribution, or when report, findings, or synthesis are mentioned.

• research

  This skill should be used when researching best practices, evaluating technologies, comparing approaches, or when research, evaluation, or comparison are mentioned.

• sanity-check

  This skill should be used when evaluating complexity, planning features, or when over-engineering, simpler, is this overkill, or keep it simple are mentioned.

• security

  This 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.

• session-analysis

  This skill should be used when analyzing conversation patterns, identifying frustration or success signals, or when analyze conversation, what went wrong, or patterns are mentioned.

• skill-distillery

  Distills 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.

• skillcheck

  Validates 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.

• skillcraft

  Creates and validates Agent Skills (SKILL.md). Use when creating skills, writing frontmatter, or validating skill structure.

• skills-workflows

  Design 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.

• software-craft

  This skill should be used when making design decisions, evaluating trade-offs, assessing code quality, or when engineering judgment or code quality are mentioned.

• systems-design

  This 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

  This 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.

• trails

  This 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.

• typescript-fieldguide

  This 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.

• use-subagents

  This skill should be used when coordinating agents, delegating tasks to specialists, or when dispatch agents, which agent, or multi-agent are mentioned.

• which-tool

  This skill should be used when choosing CLI tools, a tool seems slow, or when best tool, which tool, or tool alternatives are mentioned.

Slash commands (12)

• /fieldguides:cc:session

  Display current session ID

• /fieldguides:crew:dispatch

  Orchestrate multiple agents for complex multi-domain tasks

• /fieldguides:debug

  Systematic debugging with root cause investigation - no random trial-and-error

• /fieldguides:pathfind

  Collaborative Q&A to clarify unclear requirements and reach a clear path

• /fieldguides:plugin:audit

  Audit plugin and optionally apply auto-fixes

• /fieldguides:pr:check

  Check open PR status, review comments, and CI status

• /fieldguides:sanity-check

  Challenge complexity and find simpler alternatives before implementing

• /fieldguides:sitrep

  Generate comprehensive status report across VCS, PRs, issues, and CI/CD

• /fieldguides:toolcheck

  Check available CLI tools and get recommendations

• /fieldguides:trail:handoff

  Create a handoff note for session continuity

• /fieldguides:trail:log

  Create a timestamped log note

• /fieldguides:trail:read

  Read recent trail notes

Subagents (11)

• analyst

  Use this agent when exploring options, researching technologies, investigating issues, analyzing patterns, or discovering architectural insights. Trigger verbs include investigate, research, explore, analyze, compare, evaluate, discover, clarify, recall, and understand.\n\n<example>\nContext: User n

• debugger

  Use this agent when debugging failures, investigating errors, or troubleshooting unexpected behavior. Trigger verbs include debug, investigate, troubleshoot, diagnose, fix, and trace. Enforces evidence-based diagnosis and prevents guess-and-fix thrashing.\n\n<example>\nContext: User encounters a fai

• engineer

  Use this agent when implementing features, fixing bugs, refactoring code, or building new functionality. Triggers on verbs like: build, fix, implement, refactor, create, add, develop, write (code), update (code), migrate.\n\n<example>\nContext: User requests feature implementation in a TypeScript pr

• librarian

  Documentation discovery agent that finds and retrieves technical documentation across MCP servers (context7, octocode, firecrawl). Use proactively when documentation is needed - API references, installation guides, troubleshooting, or implementation patterns.

• quartermaster

  Builds and validates agentic development components for Claude Code and compatible agent platforms. Covers Claude plugins (plugin.json, marketplace.json), agents (.claude/agents/*.md, plugins/*/agents/*.md), skills (SKILL.md, scripts/, references/), slash commands (.claude/commands/*.md), hooks (hoo

• reviewer

  Use this agent when the user wants to review, critique, audit, or validate code, PRs, plans, or architectural decisions. Triggers include requests for code review, security audits, performance analysis, architecture critique, PR feedback, or when the user uses verbs like 'review', 'critique', 'check

• scout

  Use this agent for read-only status reconnaissance across version control, pull requests, issues, and CI/CD systems. Triggers include status, sitrep, scout, report, what's happening, project health, what's changed, show me the stack, and pr status. This agent gathers intelligence without modificatio

• skeptic

  Use this agent when evaluating proposed solutions for unnecessary complexity before implementation. Triggers include: explicit requests to challenge architecture or simplify approaches, /sanity-check command invocations, reviewing another agent's recommendations for potential over-engineering, and a

• specialist

  Use this agent when the task requires domain-specific expertise, infrastructure work, or capabilities outside core developer/reviewer/analyst workflows. This includes CI/CD pipelines, deployment, containers, cloud configuration, security audits, performance optimization, accessibility audits, build

• tester

  Use this agent when validating implementations through systematic testing with real dependencies. Triggers include: testing features, validating implementations, verifying behavior, checking integrations, proving correctness, or when verbs like test, validate, verify, check, prove, or scenario appea

• workflow-architect

  Use this agent when designing multi-skill workflow systems with artifact-based state handoff. Triggers include \"workflow system\", \"skill pipeline\", \"sequenced workflow\", \"state handoff\", and \"workflow design\".\n\n<example>\nContext: User wants to build a development workflow.\nuser: \"Help

Hooks (1)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/validate-skill-frontmatter.ts

Similar plugins