dotfiles

Systematic analysis and reasoning workflows. Use when performing audits, investigation, requirements analysis, risk analysis, scenario/edge-case enumeration, or design analysis that demands evidence-based, comprehensive coverage.

Code quality and safety standards. Activates when editing or reviewing code. Use for quality priorities, safety checks, and code correctness verification.

Use when performing coding tasks (implement features, fix bugs, refactor code). Orchestrates language detection, mode switching (normal/autopilot/full-auto), quality enforcement, and verification.

Break a problem into atomic, testable subproblems. Use when facing complex tasks, unclear requirements, or planning implementation strategy.

Start structured feature implementation workflow. Use when implementing new features, adding functionality, or building complete user-facing capabilities.

Use when starting work that needs isolated branches or parallel feature development using git worktrees.

Develop, maintain, and audit Go analyzers (go/analysis). Use when creating/updating analyzers, suggested fixes, analysistest golden files, or integration analyzer harnesses.

Go development practices and tooling. Use when working with Go code (*.go files, go.mod, go.sum). Activates for Go code style, testing, linting, concurrency patterns, and Go idioms.

Lint and format Go code via golangci-lint. Use when asked to lint code, fix lint errors, or check code quality.

Run full pre-commit workflow for Go code. Use when preparing to commit Go changes, before creating pull requests, or ensuring code quality.

Review Go code for style, idioms, safety, and correctness. Use when reviewing Go code changes, pull requests, or auditing Go codebase quality.

Run Go tests with race detection and coverage. Use when asked to run tests, check test coverage, or verify Go code functionality.

Use when building MCP servers or integrating external APIs/services via MCP (TypeScript or Python).

Use when planning parallel execution of independent tasks via subagents or concurrent tool calls; for workflow planning or throughput optimization.

Use when extracting, creating, merging, splitting, or analyzing PDFs, or when filling PDF forms programmatically.

Use when planning complex features, architecture design, multi-session work, or when plans need to be shared/reviewed. Activates for requests like "create a plan", "design implementation", "blueprint", or "plan out".

Structured problem-solving methodology. Activates for planning, design, debugging, or complex multi-step tasks. Use for systematic analysis and evidence-based reasoning.

Use when receiving code review feedback before implementing suggestions, especially if unclear or questionable.

General code review for staged changes or specified files. Use when reviewing pull requests, commits, or code changes across any language.

Audit code for runtime safety and security vulnerabilities. Use when reviewing code, before commits, or performing security assessments.

Use when asked to create or update skills or extend agent capabilities in this configuration.

Use when encountering bugs, test failures, unexpected behavior, or performance issues before proposing fixes.

TODO list discipline for task tracking. Activates for multi-step tasks (3+), complex work, or when systematic organization is needed. Use for tracking progress and ensuring completeness.

Use when strict test-first discipline is explicitly requested or required for a change.

Use when about to claim work is complete, fixed, or passing, or before committing/creating PRs; requires fresh verification evidence before any success claim.