Zap MCP工具

⚡ zap

An AI coding agent built in Rust — skill-first context injection, a hard security boundary, and a single binary with no runtime.

  ╭────────────────────────────────────────────────────────────────────╮
  │                                                                    │
  │   _____     _     ___                                              │
  │    ___/    /_\   | _ \   fast AI coding agent  v0.12.5            │
  │   /       / _ \  |  _/                                            │
  │  /_____  /_/ \_\ |_|                                              │
  │                                                                    │
  ├──────────────────────────────────────┬─────────────────────────────┤
  │  model     claude-sonnet-4-6         │  Tips for getting started   │
  │  backend   Anthropic API             │    Tab  ↑↓  autocomplete    │
  │  mode      ask                       │    /          commands      │
  │                                      │    /provider  switch LLM    │
  │  ~/my-project                        │    /help      all commands  │
  ╰──────────────────────────────────────┴─────────────────────────────╯

---

description: Team engineering principles.

We ship small, reversible changes. Every PR needs a test. No console.log in prod.

**Where to put them:**

| Path | Scope | Priority |
|---|---|---|
| `.zap/skills/` | project — check into git, team-shared | highest |
| `~/.zap/skills/` | personal — all projects | middle |
| binary | built-in defaults | lowest |

On first launch zap writes all built-in skills to `~/.zap/skills/` automatically — open any file there to read or edit it. Same-name files you create override the built-in version on the next run.

---

Overview

Order service — handles order lifecycle (create, fulfil, cancel).

description: Engineering principles applied to every task.

Ship small. Write tests first. No magic numbers. Document the why, not the what.

**Where to place skills:**

On first launch zap writes all built-in skills to `~/.zap/skills/`. Open any file there, edit it, and your version takes effect on the next run. Files are never overwritten — only new ones are added when you update zap.

If you delete a file or want to reset a skill to its default, re-export it:

**All commands:**

**Skill trace** — `/skill log` lets you audit which skill fired (or didn't) for every turn this session. If a skill you expected to fire didn't, the log shows "no match" or "casual" with the turn preview so you can tune the trigger keywords:

Same-name skills override lower-priority ones: .zap/skills/ > ~/.zap/skills/ > built-in.

---

Overview

Order service — handles order lifecycle (create, fulfil, cancel). Publishes events to Kafka on state transitions.

Features at a glance

---

Journey 4 — Adding a feature to an existing codebase

Scenario: You need to add a GET /orders/{id}/history endpoint to the existing order service.

Without zap (what most agents do): the agent creates src/main/java/.../controller/HistoryController.java, src/main/java/.../service/HistoryService.java, src/main/java/.../repository/HistoryRepository.java — duplicating the structure that already exists, ignoring the patterns already in use.

With zap:

"add a GET /orders/{id}/history endpoint that returns the state change log"

→ java skill fires
→ index query: WHERE name LIKE '%Order%' AND kind = 'class'
  finds: OrderController, OrderService, OrderRepository, OrderHistory (entity — already exists!)
→ index query: WHERE name LIKE '%Repository%' AND kind = 'interface'
  finds: OrderRepository extends JpaRepository<Order, Long> — this is the pattern to follow
→ index query: WHERE path LIKE '%controller%' ORDER BY line
  finds: all existing controllers — sees they all extend BaseController, use @RestController

zap:  OrderHistory entity already exists at OrderHistory.java:12.
      I'll add a findByOrderId() method to OrderRepository, a getHistory() method
      to OrderService, and a new endpoint to OrderController — no new files needed.
      Shall I proceed?

One file touched in OrderController, one method added to OrderRepository, one to OrderService. No duplicate classes. Follows the existing JpaRepository pattern. Uses BaseController like every other controller.

This is the core difference. The agent knew what existed before it decided what to create.

---

What's next

- Pagination test for edge case: empty cursor on last page - Consider splitting OrderService (34 methods — see /index quality output) ```

Tomorrow's session picks this up automatically. No re-explaining. No lost context.

---