Skip to content

Tagged AgentDocs

15 agentdocs tagged

frommattpocock

Zoom Out

I don't know this area of code well. Go up a layer of abstraction. Give me a map of all the relevant modules and callers. --- Mirrored from https://github.com/mattpocock/skills — original author:...

@mattpocock·
5h ago
·
52 words

To Issues

Break a plan into independently-grabbable GitHub issues using vertical slices (tracer bullets). Process 1. Gather context Work from whatever is already in the conversation context. If the user passes...

@mattpocock·
5h ago
·
427 words

Triage Issue

Investigate a reported problem, find its root cause, and create a GitHub issue with a TDD fix plan. This is a mostly hands-off workflow - minimize questions to the user. Process 1. Capture the...

@mattpocock·
5h ago
·
593 words

QA Session

Run an interactive QA session. The user describes problems they're encountering. You clarify, explore the codebase for context, and file GitHub issues that are durable, user-focused, and use the...

@mattpocock·
5h ago
·
779 words

Improve Codebase Architecture

Explore a codebase like an AI would, surface architectural friction, discover opportunities for improving testability, and propose module-deepening refactors as GitHub issue RFCs. A deep module (John...

@mattpocock·
5h ago
·
605 words

Test-Driven Development

Philosophy Core principle: Tests should verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. Good tests are integration-style: they...

@mattpocock·
5h ago
·
637 words

Domain Model

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For...

@mattpocock·
5h ago
·
356 words

Design an Interface

Based on "Design It Twice" from "A Philosophy of Software Design": your first idea is unlikely to be the best. Generate multiple radically different designs, then compare. Workflow 1. Gather...

@mattpocock·
5h ago
·
480 words

Grill Me

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For...

@mattpocock·
5h ago
·
83 words

To PRD

This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know. Process 1. Explore the repo to...

@mattpocock·
5h ago
·
403 words

Caveman Mode

Respond terse like smart caveman. All technical substance stay. Only fluff die. Persistence ACTIVE EVERY RESPONSE once triggered. No revert after many turns. No filler drift. Still active if unsure....

@mattpocock·
5h ago
·
260 words

Edit Article

1. First, divide the article into sections based on its headings. Think about the main points you want to make during those sections. Consider that information is a directed acyclic graph, and that...

@mattpocock·
5h ago
·
110 words

Write a Skill

Writing Skills Process 1. Gather requirements - ask user about: - What task/domain does the skill cover? - What specific use cases should it handle? - Does it need executable scripts or just...

@mattpocock·
5h ago
·
459 words

GitHub Triage

GitHub Issue Triage Triage issues in the current repo using a label-based state machine. Infer the repo from git remote. Use gh for all GitHub operations. AI Disclaimer Every comment or issue posted...

@mattpocock·
5h ago
·
1470 words

Git Guardrails Claude Code

Setup Git Guardrails Sets up a PreToolUse hook that intercepts and blocks dangerous git commands before Claude executes them. What Gets Blocked - git push (all variants including --force) - git reset...

@mattpocock·
5h ago
·
278 words