skills

Design, build, review, or test command-line interfaces that work well for humans, scripts, agents, pipes, and CI. Use when defining command trees, arguments and flags, stdout/stderr contracts, human and structured output, exit codes, prompts, configuration precedence, destructive-action safeguards, TTY behavior, completion, or CLI compatibility. Also use when a TUI needs a stable non-interactive command surface. Language-agnostic core with optional TypeScript implementation references.

Design, audit, and evolve repository, source, module, and package structures so real ownership, runtime, dependency, and change boundaries are easy to see and enforce. Use when deciding where code belongs; reorganizing flat or layer-first trees; structuring by feature, route, screen, command, workflow, use case, bounded context, or capability; evaluating DDD or ports-and-adapters placement; planning safe folder migrations; or reviewing package and import direction. Do not activate for ordinary file moves whose destination is already established by the repository.

Design, build, review, or refine responsive Terminal User Interfaces (TUIs), especially Rust Ratatui and Ruby TTY/cli-ui applications. Use for TUI state and event architecture, terminal layout, navigation, keyboard and text-input behavior, async data loading, accessibility, rendering, resizing, empty/error/loading states, or visual polish. When the product also exposes scriptable commands, use cli-design alongside this skill for the CLI contract.

Choose and revise Codex model and reasoning effort for multi-stage engineering work. Use when deciding between Sol, Terra, and Luna; balancing judgment, cost, and latency; delegating bounded implementation or research to subagents; planning a model handoff; or escalating work after uncertainty, risk, or failed attempts increase. Apply at the start of substantial coding tasks that have independently executable work, not to trivial tasks where delegation overhead exceeds the work.

Prepare, verify, and publish a scoped GitHub pull request. Use when the user asks to commit local work, push a feature branch, or create or verify a GitHub PR. This workflow always uses main as the PR base branch.

Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, implement selected fixes, reply on every addressed thread, and resolve those threads in GitHub.

Find and safely ship one evidence-backed security improvement using an approved repository contract. Use when reviewing, hardening, or fixing a security issue in an unfamiliar codebase.

Update, add, or delete i18n translation nodes while keeping every accompanying language file structurally in sync. Use /translate for translation files of any format, locale drift, missing keys, or user-facing copy changes.

Project-aware router for Ruby and Rails development. Use for gems, Rails, RSpec, Minitest, Cucumber, SimpleCov, RuboCop, RubyCritic, PostgreSQL, Active Record, debugging, reviews, performance, security, i18n, Sorbet, RBS, Ruby LSP, or Ruby runtime and tooling work.

Build, migrate, maintain, and test Chef Infra cookbooks using modern custom resource patterns for the sous-chefs organization. Use when: building a new Chef cookbook with custom resources, migrating legacy library-based resources to modern resources/, fixing CI failures in a sous-chefs cookbook, adding ChefSpec or InSpec tests, restructuring cookbook directories, writing resource documentation, converting sysvinit/upstart to systemd, or when the user mentions "custom resource", "chef resource", "sous-chefs cookbook", "fix cookbook CI", "cookbook structure", or "chef cookbook".

Take screenshots of MedTracker pages and attach them directly to GitHub issue or PR comments using GitHub's native browser attachment flow. Use when asked to "screenshot for issue", "attach screenshots to PR", "add visual evidence to GitHub", "post UI screenshots on a PR", or any task involving MedTracker screenshots in GitHub comments.

Fish shell scripting reference and enforcement. Activate whenever executing shell commands, writing shell scripts, using run_command, or any shell interaction in the user's environment. The user's shell is fish — never use bash/zsh/POSIX syntax in interactive commands. Trigger on: any shell command, heredoc, string manipulation, variable assignment, loop, conditional, arithmetic, pipe, or script writing.