tracer-bullets

Included with Lifetime

$97 forever

Builds multi-layer features as vertical end-to-end slices instead of horizontal layers. Each slice is verified before the next begins. Use when: starting any task that spans 2+ layers (DB, API, UI, tests), building CRUD features, implementing multi-step flows, decomposing features into subtasks, or planning implementation order.

Design

What this skill does


# Tracer Bullets

Build features as vertical slices through all layers, verifying each slice before starting the next. From The Pragmatic Programmer: get feedback as quickly as possible. Don't build horizontal layers in isolation (all endpoints, then all UI, then all tests). Build one thin vertical path, verify it works, then expand.

Skip for single-layer changes, one-file bug fixes, or work already decomposed into ordered vertical slices by a task tracker.

## Quick Reference

| Principle                  | Practice                                                              |
| -------------------------- | --------------------------------------------------------------------- |
| Vertical over horizontal   | Build one slice through all layers, not one layer across all features |
| Verify before advancing    | Tests pass, page renders, round-trip works before next slice          |
| One slice per session      | Each slice should be completable in a single agent session            |
| First feature sets pattern | First CRUD establishes conventions; subsequent CRUDs go faster        |
| Check before building      | Task trackers may already decompose the work into slices              |
| Skip when trivial          | Single-layer work or proven patterns don't need this ceremony         |

## CRUD Feature Slices

| Slice | Scope                       | Verifies                                           |
| ----- | --------------------------- | -------------------------------------------------- |
| 1     | Backend/API + tests (no UI) | Data layer works, conventions set, tests prove it  |
| 2     | List page with real data    | Data flows DB -> server -> rendered page           |
| 3     | Create dialog               | Full round-trip: form -> server -> DB -> refresh   |
| 4     | Edit + delete               | Full CRUD cycle, mutation patterns, confirm dialog |
| 5     | E2E test                    | Locks in the whole feature                         |

## Non-CRUD Adaptations

Same principle, different slices:

- **Import flow**: parse one row -> display one row -> validate + dedupe -> review + commit
- **Dashboard**: one widget with real data -> empty/onboarding state -> layout with all widgets
- **Search/palette**: one entity type -> all entity types -> quick actions
- **Multi-step wizard**: first step end-to-end -> add steps one at a time -> final submission

## Common Mistakes

| Mistake                                              | Correct Pattern                                                    |
| ---------------------------------------------------- | ------------------------------------------------------------------ |
| Building all API endpoints before any UI             | Build one endpoint + its UI + its test, then the next              |
| Starting UI before the backend is tested             | Slice 1 is backend-only with tests; prove the data layer first     |
| Building the full create/edit/delete UI in one pass  | Create dialog first (slice 3), then edit + delete (slice 4)        |
| Skipping verification between slices                 | Run tests and check output before starting the next slice          |
| Making slices too large for one session              | Split further; a slice that can't finish in one session is too big |
| Applying tracer bullets to trivial single-layer work | Skip for one component, one utility, or patterns already proven    |

## Delegation

- **Decompose into subtasks**: Use the project's task tracker to create ordered vertical subtasks before writing code
- **Isolate each slice**: Delegate each slice to a subagent so failures stay contained and context stays fresh
- **Find slice boundaries for non-CRUD work**: Pick the smallest path through all layers as slice 1, then expand

## References

No reference files. Source: [Tracer Bullets: Keeping AI Slop Under Control](https://www.aihero.dev/tracer-bullets)

Files: 1

Size: 4.3 KB

Complexity: 15/100

Category: Design

Source: https://github.com/oakoss/agent-skills/tree/main/skills/tracer-bullets

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts