Knowledge
codexFind, capture, place, move, process, and maintain knowledge and repository agent charters.
7 skills
A small development workflow with Occam-driven solution design, requirements, implementation, debugging, verification, review, and authorized delivery.
Plugin dev in aperep/my-ai-plugins. Commands read from the repo's manifest — 21 days ago.
auditAudit a whole repository only for over-engineering: rank what to delete, simplify, or replace with stdlib or native features. Use for explicit requests to audit for over-engineering, find bloat, or identify what can be deleted across a codebase. Do not use for correctness, security, performance, or
debugInvestigate bugs, regressions, failing tests, or broken behavior by tracing evidence to the root cause, then implement and verify a scoped fix when requested. For explanation-only requests, diagnose without editing. Does not handle new feature design or commit-message-only requests.
flowGovern an end-to-end development change from a safe start through requirements, investigation, implementation, and verified delivery. Use when asked to begin, perform, resume, or finish a code change, including explicit Ponytail, YAGNI, or simplest-solution requests that change code. Do not use for
grill-docsClarify feature requirements, pressure-test scope and domain terms, and produce a feature spec before implementation. Use for fuzzy requirements, PRD/spec requests, 需求对齐, 拷问需求, or 设计文档. Read existing evidence before asking focused questions. A generic "do not edit code" instruction alone does not tr
reviewReview a requested Git diff for correctness risks, unnecessary complexity, or both. Use for review requests and the review phase of commit requests; infer the requested lens from bugs/regressions versus over-engineering/deletion language. Do not use for whole-repository audits, verification-only req
tddImplement scoped behavior changes using meaningful tests before code where practical. Use for features, behavior-preserving refactors, and direct fixes with a known cause; use debug for bug investigation. Documentation, formatting, and asset-only edits do not need this coding workflow.
verifyVerify implemented changes before claiming they are complete, fixed, passing, or ready for delivery. Match checks to requested behavior and risk, inspect current evidence, and report limits. Use for completion checks, not general factual answers or a replacement for code review.
Find, capture, place, move, process, and maintain knowledge and repository agent charters.
7 skills
Mathematical writing, LaTeX and Typst scaffolding, proofreading, plain English, authorial voice, and translation workflows.
6 skills
Bibliography verification, Zotero library maintenance, MathSciNet retrieval, and personal bibliography maintenance.
4 skills
Project documentation, repository maintenance, and plugin feedback tests.
3 skills · hooks
Research reading, contextual reasoning, and opt-in Lean formalization.
4 skills
Write, migrate, template, and validate idiomatic Typst documents.
1 skill
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
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
Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.
5 commands
5 skills + 35 modes + Material Passport pipeline. Includes v3.6.7 cross-model audit gate and v3.6.8 generator-evaluator contract.
5 skills · 16 commands · 4 agents · hooks
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
8 skills · 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.