@mattpocock
TypeScript wizard. Building Total TypeScript - a comprehensive, production-grade TypeScript course. Ex-Vercel, Stately.
59 skills7 repositories 318.8K
Set up Claude Code hooks that block Git commands such as push, hard reset, and forced deletion before execution. Choose project-wide or global settings, customize the blocked commands, and verify that the hook rejects a test command.
Choose which related skill to use and in what order for planning, building, debugging, or maintaining software. It explains routes through the available workflows and helps select the next step based on your situation and project size.
Ask the agent to explain its last message again with some context. The revised explanation uses ASD-STE100, a simplified technical English standard, and the vocabulary defined in the project's glossary.
Turn an existing discussion and codebase knowledge into a specification, then publish it to the project's issue tracker. Organize the problem, user needs, implementation decisions, testing approach, and work excluded from scope.
Set up dependency-cruiser in a TypeScript project to enforce package boundaries, keep internal files private, and detect circular dependencies. Includes an example package, verification of the rules, and documentation for future development.
Explore a writing topic through probing questions and collect promising sentences, anecdotes, metaphors, and unfinished thoughts. It saves these fragments in a single Markdown file, giving you raw material to develop before deciding on an outline.
Turn a decision that needs someone else’s knowledge into a Markdown questionnaire. Clarify who will answer and what information is needed, then create prioritized questions with answer spaces for asynchronous replies or a meeting.
Turn plans, specifications, or conversations into small development tickets that each deliver verifiable behavior. Identify which tickets must finish first, review the breakdown together, and publish approved tickets to local files or the configured issue tracker.
Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.
Investigate a question using official documentation, source code, specifications, and first-party APIs. A background agent records the findings in one Markdown file with sources for each claim, following the repository’s existing conventions for research notes.
Set up automated checks before each Git commit using Husky and lint-staged. Format staged files with Prettier, run existing type checks and tests, and verify the setup using the repository's package manager.
Write a pull request description that helps reviewers understand a code change. Use a compact diagram or diff, show before-and-after evidence, and explain how reversible the change is and what areas it may affect.
Prepare a repository for engineering skills by documenting where issues are tracked, which triage labels organize incoming work, and where glossaries and architecture decision records belong. Review the existing setup and confirm drafts before writing configuration files.
Examine a plan, decision, or idea through structured rounds of questions with recommended answers. Organize dependent decisions into a branching map, resolve assumptions, and build a shared understanding before taking action.
Investigate why TypeScript uses a particular built-in type by tracing issues, proposed changes, and team comments. Produces a linked timeline and explanation of past trade-offs to help assess type overrides in ts-reset or proposed typing changes.
Review release notes stored in changeset files before a release. Check that entries describe user-facing changes, group related updates, remove unnecessary implementation details, and commit the resulting edits.
Investigate a Sandcastle GitHub issue, classify the report, check for duplicates or existing fixes, and attempt reproduction with Docker. Return a minimal reproduction script, observed results, and a likely cause, noting any environment limitations.
Ship a Drizzle schema change end to end — generate the migration, merge, hand Matt the migrate command, redeploy apps/remote, confirm it is green. Use whenever a change adds or edits a file under packages/core/db/migrations/ or changes packages/core/db/schema.ts, or when an apps/remote deploy failed with "production has not applied".
The English summary is being prepared. Showing the original description.
Optimize slow React Router loaders by eliminating redundant DB queries, creating slim query variants, and parallelizing independent fetches. Use proactively when writing or reviewing loader code that calls domain operations services (e.g. CourseOperationsService, VideoOperationsService), or when triaging a slow page load.
The English summary is being prepared. Showing the original description.
Turn the current conversation context into a PRD and publish it as a GitHub issue that is ready to receive sub-issues from /to-issues-project. Project-local variant of /to-prd, adapted for this repo's PRD-as-parent-issue + sub-issues + agent:implement workflow.
The English summary is being prepared. Showing the original description.
Install @effect/* packages safely. Use whenever adding a new Effect ecosystem dependency.
The English summary is being prepared. Showing the original description.
Break a PRD into native GitHub sub-issues attached to the parent PRD. Project-local variant of /to-issues, adapted for this repo's PRD-as-parent + native sub-issues + agent:implement multi-session workflow. Argument is the parent PRD issue number.
The English summary is being prepared. Showing the original description.
Survey the codebase, pick ONE high-leverage deepening opportunity (filtering out anything already proposed), and publish it as a PRD-shaped GitHub issue via /to-prd-project. Designed to run unattended in the daily architecture-review workflow.
The English summary is being prepared. Showing the original description.
Generate or update documentation for the AI Hero API by reading the source code at ~/repos/ai/course-builder. Use when user wants to document, update docs for, or understand the AI Hero API endpoints.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)