@mattpocock
TypeScript wizard. Building Total TypeScript - a comprehensive, production-grade TypeScript course. Ex-Vercel, Stately.
59 skills7 repositories 318.2K
Turn recurring work or life activities into workflow specifications through focused questions with recommended answers. Clarify triggers, human review, and decision summaries so an implementation agent can build the workflow without further questions.
Coordinate subagents, separate agents assigned tasks, to pursue a long-running goal in one session. Maintain dialogue with the user while improving working conditions, shared rules, and access to information needed for future tasks.
Plan work too large for one agent session by mapping decisions and their dependencies in an issue tracker. Resolve questions one at a time, preserve the reasoning, and identify what must be settled before execution can begin.
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.
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.
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.
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.
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.
Refine a plan or design through a persistent interview that asks probing questions. This skill starts the conversation by invoking the related grilling skill, providing an entry point for examining and sharpening what you have in mind.
Summarize the current conversation into a handoff document so another agent can continue the work. Reference existing project materials, suggest skills for the next session, and redact sensitive information.
Turn notes, fragments, or transcripts into an article through a paragraph-by-paragraph discussion. Compare opening options, establish what readers need to know, and save agreed sections in a separate document while preserving the original material.
Turn collected Markdown material into an article by choosing one narrative step at a time. Compare possible directions, introduce concepts before relying on them, and build the article while preserving the user's edits.
Sort issues and external pull requests, which are proposed code changes, by category and readiness. Verify reports, identify missing information, and record clear briefs so an agent or a person can take the next step.
Build a disposable prototype to answer a design question. Explore logic and changing states through a shareable HTML demo, or compare distinct interface variations, then record the findings and carry validated decisions into real code.
Sharpen a plan or design through persistent questioning while creating documentation along the way. The resulting documents include architecture decision records, which capture design choices, and a glossary of terms used in the discussion.
Create an interactive bash script for setup or migration steps that require a person. It guides dashboard actions, captures values, saves configuration and GitHub secrets, and requests confirmation at each stage.
Turn a specification and its tickets into code by coordinating multiple agents around task dependencies. Combine their work on one integration branch, use test-driven development, review the result, and close tickets through the issue tracker’s workflow.
Investigate difficult bugs and performance slowdowns by building a repeatable test or script that detects the exact symptom. Reduce the failing case, compare possible causes, and verify the fix with checks that catch the bug if it returns.
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.
Build features or fix bugs by writing one failing test, then the smallest implementation that passes it. Tests check behavior through public interfaces, the entry points callers use, so they remain useful when internal code changes.
Learn a new skill or concept through short, interactive lessons tailored to your goals and previous learning. The skill creates HTML lessons, reference sheets, and learning records to support practice and review across multiple sessions.
Replace TypeScript type assertions in tests with functions from @total-typescript/shoehorn. Use partial objects when only a few properties matter, or deliberately invalid data for error tests, then run a type check to verify the migration.
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.
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.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)