skill/tool that solves it -- finding the right tool is
itself a key capability under test, so naming it hands the model the answer. A prompt names only the
**delivery-protocol
when working with code in this repository.
## Project Overview
HttpRunner v5 is a comprehensive testing framework written in Go that supports API testing, load testing, and UI automation across multiple
/cmd/kubefwd/kubefwd.go
# Build with version information
go build -ldflags "-X main.Version=dev" -o kubefwd ./cmd/kubefwd/kubefwd.go
```
### Testing
```bash
# Run all tests
go test ./...
# Run tests for a specific package
go test ./pkg/fwdport
coisa.**
- [`docs/harness-audit.md`](docs/harness-audit.md) — onde a verificação tem buraco. Importante: `pnpm gov:verify` **não** cobre `test:db` nem `test:e2e` — verde ali não é prova para mudança de schema
skills, agents, hooks)
- User-facing documentation (README.md, CHANGELOG.md, docs/)
- Build/config files (package.json, tsconfig.json, .gitignore)
- Test files in `tests/` directory
### Enforcement
If you need to track progress or create working files
near zero with AI. Do the whole thing. Do it right. Do it with tests. Do it with documentation. Do it so well that Ben is genuinely impressed — not politely
stripe-php
## Testing
- Run all tests: `just test`
- Run specific test: `just test --filter testMethodName`
- Run specific test file: `just test tests/Stripe/SomeTest.php`
- Tests use PHPUnit
## Formatting & Linting
- Format: `just format
协议转换、多渠道调度、会话管理、指标与日志记录、配置热重载。
## 启动命令
```bash
make dev
make run
make build
make test
make test-cover
make fmt
make lint
make deps
```
说明:实际命令以 `backend-go/Makefile` 为准
后端开发 (backend-go/)
make dev # 热重载开发模式
make run # 复制前端产物后直接运行
make build # 构建生产版本
make test # 运行所有测试
make test-cover # 测试 + 覆盖率报告
make fmt # 格式化代码
make lint # 代码检查
make deps # 更新依赖
# 前端开发
browser # headless/manual code input
npm run accounts:list
npm run accounts:verify
npm test # requires server running on port 8080
node tests/run-all.cjs # run matching tests only
node tests/test-strategies.cjs # strategy unit
default branch. Those branches get force-pushed, so rebase with `git rebase --onto `.
## Build, test, lint
The entry points are `./scripts/{bootstrap,format,lint,test}`. Always use them to format
workflow recurs or the bug pattern is reusable, encode it as a test, guardrail, skill, or automation.
## Agent entry points (single sources of truth)
- **`AGENTS.md`** — the universal skill resolver. Every
migrations or legacy/compat code. Verification is:
1. `pnpm typecheck` — must be clean.
2. `pnpm test` — vitest; must be clean. Tests live next to the code they
cover (`src/lib/foo.ts` → `src/lib/foo.test.ts`). Default
build # Production build (esbuild → dist/index.js)
npm run dev # Dev build
npm run test # Unit/integration tests (Vitest)
npm run test:cli # Real CLI black-box tests against dist/index.js
npm run verify
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.