Grill Me
Clarify plans with a structured interview, adding glossary and architectural records through the Grill with Docs mode when needed.
- Development Workflows
- Planning
- Architecture
Matt Pocock connects TypeScript education with practical AI engineering. Explore his work on type safety, sandboxed coding agents, and reusable engineering Skills, alongside the courses and public repositories that explain how he approaches building and reviewing software.
Matt Pocock is a developer and educator known for teaching TypeScript. He created Total TypeScript, where exercises and explanations address type errors, generics, transformations, and application patterns. That teaching background gives his work a focus on understanding why an approach works, rather than only copying a solution.
His AI Hero work applies engineering discipline to coding agents. Planning, implementation, diagnosis, tests, and review appear as connected parts of a development process. The accompanying Skills turn selected practices into reusable instructions, while the educational material explains the decisions and feedback loops behind those practices.
His public projects also include Sandcastle, a TypeScript interface for orchestrating sandboxed coding agents, and ts-reset, which adjusts types for common JavaScript APIs. These repositories solve implementation problems; the Skills serve as instructions. Knowing which kind of resource is needed helps separate installing software from choosing a way to work.
Configure repository conventions, clarify the problem, and move from evidence to implementation. These guides cover the setup, issue triage, architecture, tests, and handoff decisions that keep engineering work grounded.
Clarify plans with a structured interview, adding glossary and architectural records through the Grill with Docs mode when needed.
Build features and fixes through agreed public interfaces and small failing-test-to-implementation cycles.
Survey concrete architecture friction, compare candidate module improvements, and explore one design before refactoring.
Diagnose difficult bugs through a reproducible signal, minimized case, and verified correction.
Review a fixed Git diff independently for repository standards and originating requirements.
Summarize a session into a focused temporary handoff document with references and suggested skills.
Configure the issue tracker, triage labels and domain documentation for Matt Pocock’s engineering Skills.
Check issue evidence and assign a clear state before handing implementation to an agent or maintainer.
Compare other creators working on developer tools, interfaces, and Agent Skills. Following the author helps connect individual resources to the problems they investigate, rather than treating every repository or instruction as an interchangeable tool.
Start with the engineering task you need to clarify: questioning requirements, building through tests, or investigating a bug. Then review the corresponding Skill and its source before adding it to your project’s working instructions.