mattpocock-skills
claudeMatt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Codex-native software specialist framework with tc-backed workflow discipline and Claude Copilot parity contracts.
Ships a Codex manifest but no marketplace file, so Codex can't add it by name yet. Add it to a local marketplace (.agents/plugins/marketplace.json).
Plugin codex-copilot in Everyone-Needs-A-Copilot/knowledge-copilot. Commands read from the repo's manifest — 5 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
doDevOps Engineer for CI, deployment, infrastructure, environment setup, observability, and operational safety.
docDocumentation specialist for README updates, onboarding material, API docs, setup guides, and durable technical explanations.
indIndustrial Designer for physical, hardware, connected-product, and physical-digital software experiences. Use for tangible product design, material honesty, product form, hardware/software touchpoints, lifecycle design, repairability, and Rams/Ive-style reduction before engineering or UI work.
launcherUse when you want to invoke codex-copilot specialist agents natively in Codex, either by selecting the right specialist skill for the main session or by mapping specialists onto real Codex spawned-agent roles for delegated work.
meEngineer for software implementation. Use for coding, bug fixes, refactors, tests, CLI/backend/frontend changes, integration work, and applying a framed technical plan while preserving existing repo conventions.
orchestrateUse when you need the Codex Copilot equivalent of Claude Copilot /orchestrate: plan stream-based work, validate dependencies, and coordinate explicit user-approved Codex subagent execution.
protocol-routerUse when a request needs specialist routing before implementation, including bugs, feature work, architecture changes, UX work, security-sensitive changes, or tc-backed delivery planning.
protocolUse as the primary Codex Copilot entrypoint for new work. It classifies the request, chooses the right specialist workflow, creates tc-backed planning context when needed, and routes execution through codex-copilot agents similarly to Claude Copilot's /protocol command.
qaQA Engineer for software quality. Use for bug reproduction, regression analysis, edge-case design, test strategy, writing or reviewing tests, verification plans, acceptance checks, and deciding whether implementation work actually satisfies the request.
sdService Designer for software product work. Use for end-to-end experience framing, service blueprints, journey stages, frontstage/backstage coordination, touchpoints, failure paths, and deciding what user problem a feature should solve before UX or engineering starts.
secSecurity Engineer for authentication, authorization, secrets, trust boundaries, unsafe inputs, data exposure, and practical security review.
specialist-agentsUse when you need specialist role guidance for architecture, engineering, QA, security, docs, devops, service design, UX, UI design, UI implementation, or industrial design in a Codex session or delegated subagent.
taTechnical Architect for software systems. Use for architecture, decomposition, technical planning, tradeoff analysis, dependency mapping, PRD/task breakdowns, migration planning, interfaces, data flows, and implementation boundaries before coding.
uidUI Developer for software interfaces. Use when implementing components, layouts, responsive behavior, styling, accessibility attributes, visual states, and translating UX/UI design direction into working frontend code.
uidsUI Designer for software interfaces. Use for visual direction, hierarchy, typography, color, spacing, component composition, design systems, visual critique, and making an interface feel intentional before UI implementation.
uxdUX Designer for software workflows. Use for interaction design, task flows, information architecture, page states, usability, accessibility flow, form behavior, empty/loading/error/success states, and making a service concept usable before visual design or implementation.
/bin/bash -c 'root="${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"; [ -n "$root" ] && [ -f "$root/hooks/$1" ] || exit 0; exec /bin/bash "$root/hooks/$1"' _ user-prompt-protocol.sh
/bin/bash -c 'root="${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"; [ -n "$root" ] && [ -f "$root/hooks/$1" ] || exit 0; exec /bin/bash "$root/hooks/$1"' _ debug-circuit-breaker.sh
/bin/bash -c 'root="${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"; [ -n "$root" ] && [ -f "$root/hooks/$1" ] || exit 0; exec /bin/bash "$root/hooks/$1"' _ design-feedback.sh
/bin/bash -c 'root="${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"; [ -n "$root" ] && [ -f "$root/hooks/$1" ] || exit 0; exec /bin/bash "$root/hooks/$1"' _ debug-circuit-breaker.sh
/bin/bash -c 'root="${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}"; [ -n "$root" ] && [ -f "$root/hooks/$1" ] || exit 0; exec /bin/bash "$root/hooks/$1"' _ subagent-return-contract.sh
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.