6 Commits
Author SHA1 Message Date
阿白叔andClaude Opus 4.7 eafd46a8ba feat: add .codex-plugin/plugin.json for Codex / Codex++ install
Codex CLI's /plugin add accepts arbitrary git URLs and installs into
~/.codex/plugins/cache, not just OpenAI's curated catalog. Modeled the
manifest on Superpowers' .codex-plugin/plugin.json (skills field points
at ./skills/, interface block for UI metadata).

Bump both .claude-plugin/{plugin,marketplace}.json from 0.1.0 to 0.2.0
to signal Codex support.

README updated:
- Three install paths now: Claude Code plugin / Codex plugin / external spec
- Codex section explains the "no SessionStart hook" caveat — agents need
  to invoke using-praxis manually on first turn (or get prompted by the
  user)

Codex / Cursor users without plugin support continue to fall back to
the AGENTS.md / skills/ direct-read path documented in the next section.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-26 10:06:17 +08:00
阿白叔andClaude Opus 4.7 4fa489691f docs: switch plugin install to token-embedded URL
simgreek org requires login for git access, so anonymous /plugin
marketplace add fails. Members generate a Gitea access token (read-only
on repository) and embed it in the plugin URL. Token is stored in
Claude Code settings — documented as a caveat with revocation guidance.

Verified: token-embedded clone over HTTPS retrieves all .claude-plugin
manifest files and skills/.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-25 18:17:09 +08:00
阿白叔andClaude Opus 4.7 ea1819f1d2 feat: rename to praxis, package as Claude Code plugin
Reframe team-guide as praxis (Greek for "practice"): Simgreek's coding
agent rulebook, distributed as a Claude Code plugin so SessionStart
hook can force-inject the using-praxis bootstrap.

- Add .claude-plugin/{marketplace,plugin}.json: makes this repo a
  one-plugin marketplace installable via /plugin marketplace add.
- Add hooks/{hooks.json,session-start,run-hook.cmd}: SessionStart
  hook reads using-praxis SKILL.md and injects it into context as
  hookSpecificOutput.additionalContext (Claude Code) or
  additional_context (Cursor) or additionalContext (Copilot CLI).
- Migrate library/<topic>/SPEC.md → skills/<topic>/SKILL.md with
  YAML frontmatter (name + when-to-invoke description).
- Add skills/using-praxis: bootstrap with iron law, red-flags table,
  catalog, instruction priority, sub-agent stop, Codex/Cursor fallback.
- Add skills/debugging: 4-phase root-cause investigation with
  3-fixes-failed → architectural problem rule.
- Add skills/verification: evidence-before-claims gate with
  rationalization table.
- Drop library/, references in AGENTS.md updated to skills/.
- Rename throughout: team-guide → praxis.
- README rewritten with both install paths (plugin / external spec)
  and updated bootstrap prompt.

Codex / Cursor / non-Claude users still get the spec by reading
AGENTS.md and skills/ files manually — only the auto-injection
requires Claude Code.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-25 18:02:48 +08:00
阿白叔andClaude Opus 4.7 161559a83d docs: add new-project bootstrap prompt to README
Add a copy-pasteable prompt for humans to drop into Claude Code /
Codex when starting a new project. The prompt makes the AI fetch
team-guide, ask consolidated questions, scaffold project files
(AGENTS.md, CLAUDE.md, .gitignore, .gitattributes, .env.example,
README.md), and stop for confirmation before first commit.

Also covers the existing-project case (补规范) by swapping the
scaffolding step.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-21 13:15:40 +08:00
阿白叔andClaude Opus 4.7 17671b2b22 docs: add library/nodejs-project SOP with encoding checks
8-phase AI execution sequence for Node.js / Next.js projects:
entry → frame → sync → edit → encoding → verify → commit → push
→ release. Phase 4 covers BOM / CRLF / non-UTF-8 detection and
fixes — these are the most common silent corruption when AI edits
files on Windows-default encoding systems.

- library/nodejs-project/SPEC.md (new)
- library/README.md catalog updated
- AGENTS.md §5 Team library entry list updated

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-21 12:31:14 +08:00
阿白叔andClaude Opus 4.7 c8ce92a2ed docs: refocus on AI behavior, drop human-only sections
team-guide is for AI to read at task start. Removed sections that
only describe human ceremonies and rewrote rules so AI can act on
them directly.

AGENTS.md:
- Replace §6 Planning cadence (Weekly/Quarterly/anti-Jira rhetoric)
  with §6 Per-task spec — the only planning rule AI actually executes.
- §1 Vibe coding rewritten to be AI-actionable: explicit spec
  requirement, observable stop-conditions (300-line / 5-file
  thresholds), self-verification 6 steps phrased as AI behaviors.
- §2 Claude Code & Codex config compressed: each rule = decision +
  one-line rationale, removed prose around skills/memory/sub-agents.
- §3 Git: drop branch owner-prefix rule, draft-PR rhythm, comment
  etiquette. Keep PR description structure and reviewer 5-step.
  Tag examples use <YYYYMMDD> placeholder so AI doesn't anchor on
  a specific date.
- §Editing rules: drop snark ("No 🚀 Getting started! energy") that
  could be misread; plain "No emoji".
- §Working directory: remove hardcoded "~10 files" count.

README.md:
- Drop "速查" cheatsheet (was for humans, redundant with AGENTS.md).
- Drop hardcoded tag examples (20260520).
- Trim positioning explanation in half.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-21 11:52:53 +08:00
14 changed files with 1225 additions and 400 deletions

No files matched your search

+20
View File
@@ -0,0 +1,20 @@
{
"name": "praxis",
"description": "Simgreek team's coding agent SOP marketplace.",
"owner": {
"name": "Simgreek",
"url": "https://git.simgreek.com/simgreek"
},
"plugins": [
{
"name": "praxis",
"description": "Simgreek team's AI coding agent rulebook: SOP for Node.js projects, git hygiene, debugging, verification.",
"version": "0.2.0",
"source": "./",
"author": {
"name": "Simgreek",
"url": "https://git.simgreek.com/simgreek"
}
}
]
}
+20
View File
@@ -0,0 +1,20 @@
{
"name": "praxis",
"description": "Simgreek team's AI coding agent rulebook: SOP for Node.js projects, git hygiene, debugging, verification — practice over theory.",
"version": "0.2.0",
"author": {
"name": "Simgreek",
"url": "https://git.simgreek.com/simgreek"
},
"homepage": "https://git.simgreek.com/simgreek/praxis",
"repository": "https://git.simgreek.com/simgreek/praxis",
"license": "Internal",
"keywords": [
"skills",
"sop",
"nodejs",
"git",
"debugging",
"team-rules"
]
}
+38
View File
@@ -0,0 +1,38 @@
{
"name": "praxis",
"version": "0.2.0",
"description": "Simgreek team's AI coding agent rulebook: SOP for Node.js projects, git hygiene, debugging, verification.",
"author": {
"name": "Simgreek",
"url": "https://git.simgreek.com/simgreek"
},
"homepage": "https://git.simgreek.com/simgreek/praxis",
"repository": "https://git.simgreek.com/simgreek/praxis",
"license": "Internal",
"keywords": [
"skills",
"sop",
"nodejs",
"git",
"debugging",
"team-rules"
],
"skills": "./skills/",
"interface": {
"displayName": "Praxis",
"shortDescription": "Simgreek team's AI coding agent SOP",
"longDescription": "Use Praxis to make AI coding agents follow Simgreek team conventions: project entry, task framing, git workflow, encoding checks, root-cause debugging, and verification before completion.",
"developerName": "Simgreek",
"category": "Coding",
"capabilities": [
"Interactive",
"Read",
"Write"
],
"defaultPrompt": [
"I'm starting a new task in this project — what should I check first?",
"Help me bootstrap this project to follow Praxis conventions."
],
"websiteURL": "https://git.simgreek.com/simgreek/praxis"
}
}
+218 -276
View File
@@ -1,10 +1,13 @@
# AGENTS.md — team-guide
# AGENTS.md — praxis
Working agreements for our 1–3 person AI-assisted development team.
Working agreements for the Simgreek team's AI-assisted development.
This is the canonical spec for AI coding agents (Claude Code, Codex,
and any other `AGENTS.md`-aware tool). Claude Code reads this via
`CLAUDE.md`'s `@AGENTS.md` import, so there's exactly one source of
truth.
`CLAUDE.md`'s `@AGENTS.md` import.
If installed as a Claude Code plugin (`/plugin install praxis`), the
`SessionStart` hook also injects the `using-praxis` skill into the
session — see [`skills/using-praxis/SKILL.md`](skills/using-praxis/SKILL.md).
> Human-facing entry point: [`README.md`](README.md) (Chinese,
> condensed). When humans want the full ruleset, they read this file.
@@ -15,14 +18,15 @@ Before starting non-trivial work in any team project, an agent should:
1. **Read this `AGENTS.md`** — general rules (vibe coding, Git, code
style, planning, handoff).
2. **Scan [`library/README.md`](library/README.md)** — focused specs
for narrower topics. Read the entries that match the current task.
2. **Scan [`skills/`](skills/)** — narrower SOPs. The
[`using-praxis` skill](skills/using-praxis/SKILL.md) lists the full
catalog and tells you when to invoke each.
3. **Read the project's own `AGENTS.md`** — project-specific stuff
(how to run it, architecture, project-only don'ts). Project AGENTS.md
files do **not** repeat team-guide content; they reference it.
files do **not** repeat praxis content; they reference it.
In short: team-guide is the external rulebook every project's agent
reads at task start. Project AGENTS.md files stay small and specific.
In short: praxis is the external rulebook every project's agent reads
at task start. Project AGENTS.md files stay small and specific.
## Project
@@ -36,15 +40,16 @@ read the change and would have written the same."
split the rule out and put the reason on a `**Why:**` line.
- Lead with the rule, then `**Why:**`, then `**How to apply:**` only
when the rule isn't self-evident.
- No emoji. No decorative headers. No "🚀 Getting started!" energy.
- Keep AGENTS.md under ~800 lines. Past that, split.
- No emoji.
- Keep AGENTS.md under ~600 lines. Past that, split a section into
`skills/`.
- Examples beat prose. A 3-line code block beats a paragraph.
## Language policy
- **Human-facing**: Chinese — `README.md` only.
- **AI-facing**: English — this file, `CLAUDE.md`, anything under
`library/`.
`skills/`.
- **Git metadata**: English — commit messages, PR titles, branch
names, tag annotations. AI tools and search work better on English.
@@ -74,9 +79,9 @@ When starting a new project, prefer the single-file approach: write
### The premise
Claude / Codex write most of the code. Humans steer: framing problems,
making decisions, deciding what's good enough. We're not racing the AI
— we're skipping typing so we spend more time thinking.
AI writes most of the code. Humans steer: framing problems, making
decisions, deciding what's good enough. The point of AI assistance is
to skip typing, not to skip thinking.
### The split
@@ -96,59 +101,72 @@ making decisions, deciding what's good enough. We're not racing the AI
- Approve any change with non-local consequences (deps, schema, infra,
auth, secrets)
- Read every diff before merging
- Make the call when AI has tried twice and is going in circles
- Sign off on commit messages and PR descriptions (AI drafts; you sign)
- Stop AI when it's tried twice and is going in circles
- Sign off on commit messages and PR descriptions (AI drafts; human signs)
If a task feels like it's drifting toward "AI decides", stop and write
a spec yourself first.
### Spec requirement
### Prompt habits
If the task description from the human is shorter than ~3 sentences and
the work touches more than one file, the AI must **stop and ask for a
5-line spec** before writing code:
- **Frame, don't dictate.** Tell AI the goal, the constraints, and what
you've ruled out. Don't prescribe steps unless the steps are the point.
- **Name the file.** "Fix the bug in `eval-agent/runner.py`" beats "fix
the bug." Save AI a search.
- **Say what done looks like.** "Tests pass and the new flag defaults
to off" — measurable. "Make it cleaner" — not.
- **One task per turn.** Three unrelated asks → three messages or three
sessions.
- **Push back on bad output.** If the diff is wrong, say so plainly and
point at what's wrong. Don't accept code you wouldn't write yourself.
```
Goal: <what should be true after this task>
Why: <one sentence>
Done when: <measurable acceptance>
Out of scope: <things explicitly not to touch>
Risks: <what could go wrong>
```
### When to take over
Don't infer the spec silently. Vague task + silent inference is the most
common cause of AI rework.
Stop letting AI drive when:
### Prompt habits (rules for human input that improve AI output)
- It's failed the same approach twice and the error is unchanged.
- It's adding "safety" code the task didn't ask for.
- The diff has grown past what you can read in one sitting.
- You can't explain the change to a teammate without re-reading the diff.
- It's about to do something irreversible — confirm explicitly.
- **Frame, don't dictate.** Goal + constraints + what's been ruled out.
Don't prescribe steps unless the steps are the point.
- **Name files.** "Fix the bug in `<repo>/<file>.py`" beats "fix the bug."
- **Say what done looks like.** Measurable phrasing — "tests pass and
the new flag defaults to off." Not "make it cleaner."
- **One task per session.** Unrelated asks → separate sessions.
- **Push back on bad output.** Point at the wrong part specifically.
When you take over, write *why* in the PR description so the next person
doesn't repeat the loop.
### When AI must stop and surface to the human
### Verifying AI output
AI stops driving and surfaces the situation to the human when:
Treat every AI diff like a fast junior's PR:
- The same approach has failed twice with the same error.
- The task is asking AI to add code (validation, retry logic, defensive
guards) the spec didn't request.
- The current diff has grown past ~300 lines or touches >5 files when
the spec called for a narrower change.
- AI is about to do something irreversible (delete data, force-push,
rotate auth, drop a database, modify a production config).
1. Does it build?
2. Do tests pass — and do new tests actually test the new code?
3. Did it touch files outside the stated scope? Look at every one.
4. Did it add deps? Check the lockfile diff.
5. Read every comment AI added. Half are noise — delete those.
6. Run user-facing features end-to-end. Type checks ≠ working software.
In each case, AI summarizes the situation and asks for direction. Don't
keep iterating.
### Anti-patterns
### Output verification (AI runs this on its own diffs before declaring done)
- **Snowballing context.** Long sessions accumulate stale assumptions.
New task → new session.
- **Approval-by-default.** "Looks good" without reading the diff is how
bugs ship.
- **Outsourcing the spec.** "Figure out what we should do" is avoidance,
not a prompt.
- **Letting AI rewrite history.** If AI wants to refactor unrelated code
"while we're here", say no. Open a separate task.
1. Does the build / typecheck pass?
2. Do tests pass — and do new tests actually exercise the new code?
3. Are there files in the diff outside the stated scope? If yes, justify
each or revert.
4. Did this PR add dependencies? If yes, name them in the summary.
5. Are there AI-generated comments restating what the code says? Delete.
6. For user-facing changes: state how the change was exercised end-to-end.
Type-check passing is not evidence of working software.
### Anti-patterns AI must avoid
- **Snowballing context.** Long single session covering multiple
unrelated tasks; stale assumptions leak across tasks.
- **Refactor drift.** "While I'm here, let me also clean up X." Open a
separate task instead.
- **Comment padding.** Adding obvious or restating comments to make a
diff look thorough.
- **Silent scope expansion.** Touching files not implied by the task
without flagging them in the summary.
---
@@ -158,64 +176,49 @@ Treat every AI diff like a fast junior's PR:
```
<repo>/
├── AGENTS.md ← canonical spec, committed
├── CLAUDE.md ← committed, single line: @AGENTS.md
├── AGENTS.md canonical spec, committed
├── CLAUDE.md committed, single line: @AGENTS.md
└── .claude/
├── settings.json ← shared settings, committed
├── settings.local.json ← personal overrides, gitignored
└── skills/ ← project skills, committed
├── settings.json shared settings, committed
├── settings.local.json personal overrides, gitignored
└── skills/ project skills, committed
```
`settings.local.json` is **always** gitignored — personal API keys,
local paths, individual hook tweaks.
### AGENTS.md content per project
### Per-project AGENTS.md content
In this order:
Order: **Project** (≤2 sentences) → **Run it** (bash blocks) →
**Architecture** (one paragraph + key files) → **Conventions specific
to this repo** → **Don'ts** (things AI got wrong here before).
1. **Project** — two sentences max.
2. **Run it** — build, test, lint as bash blocks.
3. **Architecture** — one paragraph. Entry points and data flow. No
diagrams unless they save words.
4. **Conventions specific to this repo** — naming, layout, patterns
that aren't obvious from the code.
5. **Don'ts** — things AI has gotten wrong before. One line each.
A new contributor (human or AI) should be productive after one read.
Past 100 lines, split — it's drifted into "documentation."
Skeleton to copy into a new project's `AGENTS.md`:
Past 100 lines → split. Skeleton:
```markdown
# AGENTS.md — <project name>
> Reference: team-guide (https://git.simgreek.com/simgreek/team-guide)
> for cross-project rules. This file holds only what's specific to
> this project.
> Reference: praxis for cross-project rules. This file holds only
> what's specific to this project.
## Project
<one or two sentences>
## Run it
```bash
<install / run / test / lint commands>
```
## Architecture
<one paragraph: entry points, data flow, major modules>
Key files:
- `<path>` — <one-line role>
## Conventions specific to this repo
<naming patterns, where to add new features, what's auto-generated>
## Don'ts
- Don't <…>
```
@@ -223,143 +226,93 @@ Key files:
### Permissions (Claude Code)
Default: prompt for risky, allow read-only freely.
Default: prompt for risky, allow read-only. **Why:** keeps friction
low for safe ops while preserving review of mutations.
In `.claude/settings.json`, allow without prompting:
Allow without prompt: all `Read`/`Glob`/`Grep`, read-only Bash
(`git status`, `git diff`, `git log`, `git branch`, project test
runners).
- All `Read`, `Glob`, `Grep`
- `Bash(git status)`, `Bash(git diff)`, `Bash(git log)`,
`Bash(git branch)`
- Project-specific read-only commands (`Bash(npm test)`, `Bash(pytest)`)
Always prompt for:
- `Edit` / `Write` outside the working tree
- `Bash` with destructive verbs (`rm`, `mv`, `git push`,
`git reset --hard`, package installs)
- Any MCP tool that talks to a remote service
Approving the same prompt repeatedly → run the
`fewer-permission-prompts` skill to propose an allowlist from your
transcripts.
Always prompt: `Edit`/`Write` outside the working tree; destructive
Bash (`rm`, `mv`, `git push`, `git reset --hard`, package installs);
any MCP tool hitting a remote service.
### Codex approval & sandbox
- **Approval**: default `on-request` (asks before commands). Use
`on-failure` or `never` only on personal, low-risk machines.
Production / shared / unfamiliar repos → keep `on-request`.
- **Sandbox**: default `workspace-write` + network off. Toggle network
on temporarily to install packages or fetch resources, then off.
`danger-full-access` rarely.
- Personal Codex preferences in `~/.codex/config.toml` — never commit.
- **Approval**: default `on-request`. **Why:** unfamiliar repos and
shared machines need command-level review.
- **Sandbox**: default `workspace-write` + network off. Turn network
on only when fetching/installing, then off again.
- Personal Codex prefs go in `~/.codex/config.toml`, never committed.
### Hooks
Hooks enforce rules automatically. AI **does not reliably remember**
"from now on do X" across sessions; hooks do.
AI does not reliably remember "from now on do X" across sessions —
hooks enforce automatically.
Use hooks for:
Use for: auto-format on edit, block writes to protected paths
(`.env`, generated files, `dist/`), auto-test after writing test files,
session-stop notifications.
- Auto-formatting on file edit (Prettier, ruff, gofmt)
- Blocking edits to protected paths (`.env`, generated files, `dist/`)
- Auto-running tests after writing to a known test path
- Notifying on session stop / long-task completion
Don't use hooks for:
- One-off checks ("just remember X this week")
- Anything that depends on AI judgment
Configure via `update-config` skill or edit `.claude/settings.json`
directly. One-line comment per hook.
Don't use for: one-off reminders, anything depending on AI judgment.
### Memory
Per-machine memory system. Use it for:
Per-machine. Use for: who you are (User), corrections that should
persist across sessions with the *why* (Feedback), facts about
ongoing work that aren't in code (Project), pointers to external
resources (Reference).
- **User**: who you are, role, preferences.
- **Feedback**: corrections that should stick across sessions, with
the *why*.
- **Project**: facts about ongoing work that aren't in the code
(deadlines, stakeholder decisions, why a refactor is happening).
- **Reference**: pointers to external resources (Linear, Grafana,
internal wikis).
Don't put memory content in `AGENTS.md`. AGENTS.md is shared with the
team; memory is personal, per-machine, outside the repo. Don't use
memory as a notes app — task-scoped state goes in plans or PR descriptions.
Memory is personal and per-machine — never substitute for AGENTS.md.
Task-scoped state goes in plans or PR descriptions, not memory.
### Skills
Skills live in three places:
Locations: user (`~/.claude/skills/`), project
(`<repo>/.claude/skills/`), plugin marketplace.
- **User skills** (`~/.claude/skills/`) — installed once, available
everywhere
- **Project skills** (`<repo>/.claude/skills/`) — committed, team-shared
- **Plugin skills** — installed via marketplace
Promote a workflow to a skill when **all three** are true:
1. Done it the same way three times.
2. Steps stable enough to write down.
3. Someone else would do it the same way given the spec.
Only two true → leave it as a prompt snippet.
Promote a workflow to a skill when **all three** hold: done the same
way 3+ times, steps stable enough to write down, someone else would do
it the same way given the spec.
Skill design:
- One skill, one job. Branching skills are two skills.
- Verb-phrase names: `review-pr`, `cut-release`, `rebuild-fixtures` —
not `pr-helper`.
- Description (the line the model sees) says **when to invoke**, not
what the skill does.
- `SKILL.md` under 200 lines; long skills split into stages.
- Examples beat instructions.
- Verb-phrase names (`review-pr`, `cut-release`), not nouns
(`pr-helper`).
- Description tells the model **when to invoke**, not what the skill
does.
- `SKILL.md` under 200 lines.
Recommended installs:
Recommended installs (read each skill's own description for what it
does):
```
anthropic-skills:consolidate-memory periodic memory cleanup
simplify review changed code for reuse/quality
fewer-permission-prompts propose allowlist from transcripts
review review a pull request
security-review security pass on pending changes
consolidate-memory simplify fewer-permission-prompts review security-review
```
Review skills like PRs — read, run once on a real task, merge. Skills
nobody runs after a month → archive (`.claude/skills/_archive/`).
### Sub-agents
Spawn a sub-agent (Claude `Agent` tool) when:
- Task needs cross-file search and you don't want results in main context.
- You want a second independent read on a design or diff.
- Work is genuinely parallel (e.g. researching three options).
Don't spawn for tasks the main agent can do in two tool calls.
Spawn one when: cross-file search and you don't want results in main
context, second independent read on a design or diff, genuinely parallel
work (e.g. three options to research). Don't spawn for tasks doable in
two tool calls.
### Sessions
- One task per session. New task → new session.
- Long session, context bar filling → finish current step, summarize
into a plan or PR draft, start fresh.
- Don't `--continue` yesterday's session for a new topic. Stale context
leaks in.
- Don't `--continue` yesterday's session for a new topic.
### Tool selection (mixing Claude Code + Codex)
### Mixing Claude Code + Codex
Both fine; mild preferences:
Both fine. **Don't** run two tools editing the same file simultaneously
— overwrites are hard to trace.
- **Writing docs / specs** — Claude Code (this repo was written that way).
- **Large refactors / cross-file features** — Claude Code (plan mode +
sub-agents).
- **Narrow edits, run a test, change a config** — Codex CLI (faster
startup).
- **In-IDE inline edits** — Codex IDE plugin or Cursor.
Don't run two tools editing the same file simultaneously — overwrites
are hard to trace.
Mild preferences: docs/specs and large refactors → Claude Code (plan
mode, sub-agents); narrow edits and quick test runs → Codex CLI
(faster startup); in-IDE inline → Codex IDE plugin or Cursor.
---
@@ -368,10 +321,10 @@ are hard to trace.
### Branches
- `main` (spec repos) / `dev` (product repos) is always shippable. No
direct pushes, no exceptions.
- Feature branches: `<owner>/<short-slug>` — `bai/auth-retry`,
`bai/eval-agent-rerun`. Lowercase, hyphens, handle prefix.
- Long-lived integration: `integration/<topic>` — only by team agreement.
direct pushes.
- Feature branches: `<short-slug>`, lowercase, hyphenated. Project may
prefix with owner (`<owner>/<slug>`) — follow the project's existing
convention.
- Delete branches after merge.
### Commits
@@ -382,10 +335,8 @@ are hard to trace.
<optional body — what changed and why, not how>
```
- `<area>` is a directory or component, lowercase: `eval-agent`,
`task_assistant`, `docs`, `git-workflow`.
- `<area>` is a directory or component, lowercase.
- Imperative: "add", "fix", "rename" — not "added" / "adding".
- Body wraps at ~72 chars. Skip it for trivial commits.
- One topic per commit. "and" in the summary → split.
- Always include `Co-Authored-By` for AI-assisted commits.
- English.
@@ -404,42 +355,35 @@ task_assistant: drop unused legacy export path
- Title under 70 chars, same shape as commit summary.
- Description structure: **Summary** (1 sentence + bullets if needed) /
**Why** / **What changed** (bulleted by file or area) / **Test plan**
(checkbox list, honest) / **Out of scope** (optional) / **Notes for
reviewer** (optional, for surprising AI decisions). Add a
`🤖 AI-assisted` trailer for AI-assisted PRs.
(checkbox list, honest about what was and wasn't tested) /
**Out of scope** (optional) / **Notes for reviewer** (optional, for
surprising AI decisions). Add an `AI-assisted` trailer for
AI-assisted PRs.
- First push of a feature branch uses `-u`.
- Open as draft once runnable. Review-as-you-go beats review-at-the-end.
### Review
### Review (when AI is reviewer)
Every PR reviewed before merge — own AI-assisted PRs included.
When AI reviews a PR, run these checks in order:
Reviewer:
1. Description matches diff? Surprises → ask.
2. Read every changed file. Off-topic file → ask why it's in this PR.
3. Run locally if not obviously correct from reading.
4. New deps, schema changes, env vars, auth-touching code → block until
justified.
5. Comment on least-important issue first; merge-blocker last so it's
clearly the gate.
Author follow-ups:
- Address every comment, even with "agreed, fixed in <commit>".
- Disagree → push back in writing. Don't silently ignore.
- Squash fixup commits before merge if history is noisy.
1. Does the PR description match the actual diff? Flag surprises.
2. Read every changed file. Files outside the stated topic → flag with
"this file is not implied by the description".
3. Run the change locally if correctness isn't obvious from reading.
4. Block until justified: new deps, schema changes, env var additions,
auth-touching code, anything affecting persisted data.
5. Output critical findings (merge-blockers) last in the review summary
so they're visually distinct from minor comments.
### Merging
- Squash for feature branches. Merge commits reserved for integration.
- Squash for feature branches.
- Final squash message follows commit format.
- Delete the branch on merge.
### Tagging
### Tagging (this repo)
Tags are dated: `YYYYMMDD`, with `-N` suffix for same-day reissues
(`20260520-2`). Tag from `main`.
Tags are dated: `<YYYYMMDD>`, with `-N` suffix for same-day reissues
(e.g. `<YYYYMMDD>-2`). Tag from `main`.
Rules:
@@ -447,29 +391,28 @@ Rules:
- Tag message summarizes what changed since the previous tag.
- Tags are immutable once pushed. Wrong tag → cut a new one.
- Don't tag on feature branches.
- Max one tag per day, use `-N` for same-day reissues.
- Max one tag per day; use `-N` for same-day reissues.
Cut a tag:
```bash
git checkout main && git pull --ff-only
git tag -a 20260520 -m "team-guide 20260520: bilingual policy"
git push origin 20260520
git tag -a <YYYYMMDD> -m "praxis <YYYYMMDD>: <summary>"
git push origin <YYYYMMDD>
```
Inspect:
```bash
git tag --sort=-creatordate
git show 20260520
git log --oneline 20260513..20260520
git show <YYYYMMDD>
git log --oneline <prev-tag>..<this-tag>
```
When to cut a tag:
- Docs changed in a way teammates need to re-read.
- A new convention is now in effect (not just proposed).
- A library/ entry was added, removed, or restructured.
- Rules changed in a way that affects how AI should behave on tasks.
- A skill was added, removed, or restructured.
When **not** to cut a tag:
@@ -482,15 +425,14 @@ semver `vX.Y.Z`). Each project documents its own scheme in its own
### Don'ts
- No `git push --force` to `main`. Period. To your own branch only if
certain nobody pulled it.
- No `git push --force` to `main` / `dev` — ever.
- No `--no-verify` to skip hooks. Fix what the hook reports.
- No amending pushed commits. Add a new commit instead.
- No deleting or moving pushed tags. Cut a new one.
- No committing `.env`, secrets, or files >5 MB without a Git LFS
conversation.
- No `git add .` / `git add -A` when there are unrecognized untracked
files. Stage by name.
- No committing `.env`, secrets, or files >5 MB without explicit
approval (Git LFS or out-of-band).
- No `git add .` / `git add -A` when untracked files are present that
weren't explicitly part of the task. Stage by name.
---
@@ -579,65 +521,65 @@ Shorter than this is fine — drop sections that don't apply.
---
## 5. Team library
## 5. Skills catalog
Narrower specs that don't fit cleanly in this file live under
[`library/`](library/). Catalog: [`library/README.md`](library/README.md).
Narrower SOPs live under [`skills/`](skills/). Each `SKILL.md` has a
YAML `description` frontmatter telling the AI **when to invoke it**.
The `using-praxis` skill is the bootstrap — read it first; it lists the
catalog with full triggering criteria.
When an agent picks up a task, it should scan the catalog after reading
this file and read entries that match. Each entry leads with a "When
to read this" section so the decision is fast.
Current skills:
Current entries:
- [`library/git-upload/`](library/git-upload/SPEC.md) — what to commit,
- [`skills/using-praxis/`](skills/using-praxis/SKILL.md) — bootstrap,
iron-law / red-flags / catalog. Loaded automatically by the
`SessionStart` hook when the praxis plugin is installed.
- [`skills/git-upload/`](skills/git-upload/SKILL.md) — what to commit,
what not to, how to recover from leaked secrets.
- [`skills/nodejs-project/`](skills/nodejs-project/SKILL.md) — task
execution SOP for Node.js / Next.js projects (8 phases, includes
encoding checks).
- [`skills/debugging/`](skills/debugging/SKILL.md) — root-cause
investigation before any fix; 4-phase process.
- [`skills/verification/`](skills/verification/SKILL.md) — evidence
before completion claims.
Promotion criteria, layout, and adding rules: see
[`library/README.md`](library/README.md).
A skill graduates from "this seems like a good idea" to a real entry
when **all three** hold:
1. Done the same way 3+ times.
2. Steps stable enough to write down.
3. Someone else would do it the same way given the spec.
Skill design rules: one skill, one job; verb-phrase name; description
field tells the model **when to invoke**, not what the skill does;
under ~300 lines.
---
## 6. Planning cadence
## 6. Per-task spec
1–3 person team. Lightest process that keeps us aligned.
Before AI writes code on a task that touches more than one file:
### Weekly
1. Confirm or produce a 5-line spec.
- Async written sync (Monday morning). Each person posts:
1. What I shipped last week (one line per item).
2. What I'm picking up this week (one line per item).
3. What's blocked or unclear (the only section worth reading carefully).
- 30-minute live call mid-week. Agenda is the "blocked or unclear" lines.
```
Goal: <what should be true after this task>
Why: <one sentence>
Done when: <measurable acceptance>
Out of scope: <things explicitly not to touch>
Risks: <what could go wrong>
```
### Per task
2. Put the spec at the top of the PR description (draft PR is fine)
**before** writing code.
3. Reuse the spec as the AI prompt when handing the task off.
Before starting work that takes more than ~half a day:
After the task ships:
1. Write a 5-line spec: *Goal / Why / Done when / Out of scope / Risks*.
2. Drop in PR description (draft PR fine) **before** writing code.
3. If AI does most of the typing, the spec is also the prompt.
After:
1. PR description matches what shipped.
2. Lessons future-you would want → Claude memory (feedback / project
types). See [Memory](#memory).
### Quarterly
Half a day to:
- Re-read this `AGENTS.md`. Open PRs for what's stale.
- Review skill catalog. Archive unused.
- Run `consolidate-memory` on personal memory files.
### What planning is *not*
- Not Jira tickets. Two people don't need a board.
- Not Gantt charts. Need one → building the wrong thing.
- Not status theater. Monday post is for spotting blocks, not proving
you worked.
- Update the PR description to match what actually shipped (not what
was originally proposed).
- Lessons future tasks would want → Claude memory (feedback / project
types). See [Memory](#memory).
---
@@ -789,7 +731,7 @@ Fill it before declaring handoff done.
## Working directory expectations (this repo)
- Small repo (~10 files). `Read` everything before acting; no need to
spawn a sub-agent for exploration.
- This is a small docs-only repo. `Read` everything in scope before
acting; don't spawn a sub-agent for exploration.
- Don't introduce `package.json`, `Makefile`, CI configs, or other
toolchain files unless explicitly asked. This is a docs repo.
toolchain files. There is no build/test/lint here.
+129 -61
View File
@@ -1,92 +1,160 @@
# team-guide
# praxis
我们小团队的 AI 协作(vibe coding)开发约定。1–3 人规模,规则不多但都是真踩过的坑。
Simgreek 团队的 AI 协作开发约定。**给 AI 看的**——每个项目里 AI 开干前先读这里。
完整规则在 [`AGENTS.md`](AGENTS.md)(英文,给 AI 看)——本仓库的**唯一规则来源**。
这份 README 是给人的导览,知道去哪查、怎么参与就行。
完整规则在 [`AGENTS.md`](AGENTS.md)(英文)。skill 库在 [`skills/`](skills/)。这份 README 是给人的入口说明。
## 这个仓库给谁用
## praxis 是什么
**给 AI 用**。每个团队项目里 AI 开干前应该先读 team-guide:
源自希腊语 *praxis*(实践)。Simgreek 团队的"踩过坑就写下来"的总和,给 AI agent 用。
1. 读 [`AGENTS.md`](AGENTS.md)——团队通用规则
2. 扫 [`library/README.md`](library/README.md)——按当前任务挑相关条目读
3. 再读项目自己的 `AGENTS.md`——只放项目特定的东西
支持三种用法(按完整度排序):
项目自己的 `AGENTS.md` **不重复**这里的规则,引用就行,保持小而具体。
- **作为 Claude Code 插件** —— `/plugin install praxis` 之后,session 一开 SessionStart hook 就把 `using-praxis` 强制注入 context,AI 行为受铁律约束。
- **作为 Codex / Codex++ 插件** —— `/plugin add <praxis-url>` 装上,Codex 把 skills/ 里的 SKILL.md 注册成可调用的 skill。Codex 没有 SessionStart hook,但 skill 的 description 会让模型按需 invoke。
- **作为外部规范**—— 不装插件也能用:AI 进项目前读 `AGENTS.md` + 扫 `skills/`,靠提示词显式调用。Cursor / 其他工具走这条。
## 怎么用(人)
## 安装(Claude Code)
1. **新成员** —— 读这份 README 五分钟,再扫一眼 [AGENTS.md](AGENTS.md) 的目录。具体规则用到再翻。
2. **新项目** —— 在新仓库根目录放 `AGENTS.md`(骨架在 [AGENTS.md](AGENTS.md) 的 Claude Code & Codex 节),再放一行 `@AGENTS.md` 的 `CLAUDE.md`。让两边 AI 工具读同一份项目说明。
3. **不同意某条规则** —— 在本仓库开 PR 改它,不要私下绕开。
simgreek 仓库要求登录访问,所以 plugin URL 里要带个人 access token。每个团队成员一次性配一下。
**第 1 步**:在 Gitea 生成 token
登录 [git.simgreek.com](https://git.simgreek.com) → 右上角头像 → Settings → Applications → 「Manage Access Tokens」 → 生成一个新 token:
- Token 名字:`claude-code-plugin`(或你喜欢的)
- 权限只勾 `repository: read` 就够,越小越好
- **生成后立刻复制保存**——离开页面就看不到了
**第 2 步**:在 Claude Code 装
把下面的 `<YOUR_USERNAME>` 和 `<YOUR_TOKEN>` 替换掉:
```
/plugin marketplace add https://<YOUR_USERNAME>:<YOUR_TOKEN>@git.simgreek.com/simgreek/praxis
/plugin install praxis
```
装完之后每次开新 session,praxis 的 `SessionStart` hook 会把 `using-praxis` 内容直接灌进 system context——AI 在做任何事之前都会读到铁律和 red flags。
升级:`/plugin update praxis`(自动用同一个 token 拉新版本)
卸载:`/plugin uninstall praxis`
## 安装(Codex / Codex++)
token 准备方式与 Claude Code 一致(上面第 1 步)。
**在 Codex CLI 或 Codex++ 里**:
```
/plugin add https://<YOUR_USERNAME>:<YOUR_TOKEN>@git.simgreek.com/simgreek/praxis
```
Codex 拉取仓库后会读 `.codex-plugin/plugin.json`,把 `skills/` 下所有带 frontmatter 的 SKILL.md 注册成可调用 skill。需要时 AI 自己 invoke。
**和 Claude 的差别**:Codex 没有 SessionStart hook,所以 `using-praxis` 不会被强制注入。AI 进项目时,建议你**第一句话**说:
```
先读 using-praxis skill,了解我们团队的 SOP 再开始。
```
让 Codex 主动 invoke 一次,铁律就在 context 里了。后续任务正常用。
**安全提醒(两边都适用)**:
- token 会被工具写进本地配置——别让别人翻你电脑、别把 config 分享出去
- token 不要提交进任何仓库
- 共用电脑 / 临时机器装完用完,去 Gitea token 页面 revoke 掉
- token 失效或换了,重新跑 install 命令用新 URL
## 不装插件怎么用
把这段提示词丢给 AI 当首句话:
```text
请按以下顺序为本项目做初始化或推进任务:
1. 拉取并阅读 https://git.simgreek.com/simgreek/praxis 的最新内容
(至少读 AGENTS.md 和 skills/using-praxis/SKILL.md,再扫 skills/
下的其他 SKILL.md,匹配当前任务的读完)。
2. 读完后,如果是新项目初始化,问我以下信息(一次性问完):
- 项目名 / 一句话定位
- 技术栈(Node 版本、是否 Next.js / Express / 其他)
- 远端仓库地址(gitee / git.simgreek.com / 其他)
- 协作主分支名(main / dev)
- 是否产品项目(要发分发渠道);是的话,分发渠道是什么
- 需要哪些环境变量(只要变量名,不要值)
3. 拿到回答后,按 praxis 的规范:
- git init(如果还没)+ 配 .gitignore(含 node_modules / .env*
/ 构建产物 / .claude/settings.local.json 等)
- 落 .gitattributes(强制 LF,.bat/.cmd 用 CRLF,二进制标 binary)
- 写 .env.example(仅变量名)
- 写项目根 AGENTS.md,遵循 praxis AGENTS.md §2 的骨架,引用 praxis
而不是复制规则
- CLAUDE.md 写一行:@AGENTS.md
- 写 README.md(中文,给人看,三段:是什么 / 怎么跑 / 怎么配 .env)
4. 全部建好后列出改动,等我确认再 commit。第一个 commit 不直接 push。
5. 整个过程严格遵守 praxis 的「AI 必须停下问人」规则——任务模糊、
范围敏感、远端冲突、--force、上传分发渠道,这些必须停下来确认。
```
老项目补规范,把第 3 步换成"补齐缺失的文件,不要覆盖现有的内容;冲突先列出来问我"。
## 语言策略
- **给人看的(中文)**:本 README。
- **给 AI 看的(英文)**:[`AGENTS.md`](AGENTS.md)、[`CLAUDE.md`](CLAUDE.md)、`library/` 下所有内容。
- **Git 元数据(英文)**:commit、PR 标题、分支名、tag 注释。
理由:AI 工具和搜索更吃英文 metadata;规则只需要一份不需要两份;中文给人在入口处看到。
- **本 README 中文**——给人读的入口
- **AGENTS.md / CLAUDE.md / skills/ 全英文**——给 AI 读
- **commit、PR 标题、分支名、tag 注释全英文**——AI 工具和搜索吃英文 metadata 更准
## 目录
```
team-guide/
├── README.md ← 你正在看(中文,给人)
├── AGENTS.md ← 全部团队规则(英文,给 AI)
├── CLAUDE.md ← 一行 @AGENTS.md import
└── library/ ← 窄主题专项规范目录
├── README.md ← catalog
└── git-upload/ ← 第一篇:什么该传什么不该传
└── SPEC.md
praxis/
├── README.md ← 中文入口(你正在看)
├── AGENTS.md ← 全部团队规则(英文)
├── CLAUDE.md ← 一行 @AGENTS.md import
├── .claude-plugin/ ← Claude Code 插件元数据
│ ├── marketplace.json
│ └── plugin.json
├── hooks/ ← SessionStart hook,强制注入 using-praxis
│ ├── hooks.json
│ ├── session-start
│ └── run-hook.cmd
└── skills/ ← AI 行为约束
├── using-praxis/ ← bootstrap:铁律 / red flags / 目录
├── git-upload/ ← 该传 / 不该传 / 泄密恢复
├── nodejs-project/ ← Node 项目 8 阶段执行 SOP(含编码检查)
├── debugging/ ← 4 阶段根因调查
└── verification/ ← 完成前必须有证据
```
[`AGENTS.md`](AGENTS.md) 内含:
项目背景 · 编辑规则 · 语言策略 · Vibe coding · Claude Code & Codex 配置 ·
Git 工作流 · 代码与产出风格 · Team library 索引 · 规划节奏 · Handoff。
## Library 怎么扩
碰到一个跨项目的具体话题、AGENTS.md 里塞进去会拖肿(比如"git 上传到底什么该传"、"PII 处理"、"eval 报告格式"),就在 `library/` 下开一个子目录写 `SPEC.md`。
收录标准(同时满足):
1. 至少踩过两次。
2. 比 AGENTS.md 通用规则窄,inline 进去会拖肿。
3. 步骤稳定到能写下来。
每加一条在 [`library/README.md`](library/README.md) 的 catalog 表里加一行"什么时候读它"。
## 版本管理
本仓库(规范类)按日期打 tag:`YYYYMMDD`,比如 `20260520`。同一天多次发布加 `-N` 后缀(`20260520-2`)。从 `main` 打 tag。
本仓库按日期打 tag:`YYYYMMDD`(同一天多次发布加 `-N` 后缀)。tag 不可改、不可删、不可 force-push。
通用规则:
具体规则见 [`AGENTS.md`](AGENTS.md) §3 Git workflow。项目仓库自己用各自的 tag 方案(通常 semver `vX.Y.Z`),写在项目的 `AGENTS.md` 里。
- `main` 永远是当前工作副本。
- 只用 annotated tag(`git tag -a`)。
- Tag 一旦推到远端就不能改、不能删、不能 force-push。错了切新的。
- 谁要"用某一版",告诉对方 tag 名(`team-guide @ 20260520`)就行。
## Skill 怎么扩
项目仓库自己(task_assistant 这类)用各自的 tag 方案(通常是 semver `vX.Y.Z`),写在项目自己的 `AGENTS.md` 里。
碰到跨项目的具体话题、塞进 AGENTS.md 会拖肿(比如"PII 处理"、"eval 报告格式"),就在 `skills/<topic>/` 下写 `SKILL.md`。
具体命令和什么时候切 tag——见 [`AGENTS.md`](AGENTS.md) 的 Git workflow 节。
收录标准(同时满足):
## 几条最容易踩的线(速查)
1. 至少踩过两次
2. 比 AGENTS.md 通用规则窄
3. 步骤稳定到能写下来
完整版在 AGENTS.md 和 library/,这里挑人最常忘的:
- 长 session 的上下文会污染输出,新任务开新 session
- 不读 diff 就 "looks good" 是 bug 上线的标准姿势
- 一个 session 不要同时让 Claude Code 和 Codex 改同一个文件
- AI 试同一个方案两次报同样的错——叫停,自己上
- `git add .` 前先 `git status` 看一眼,确认没有不该传的文件
- 提交前 `git diff --cached` 扫一眼;密钥误提交的应急流程在 [`library/git-upload/SPEC.md`](library/git-upload/SPEC.md)
新加的 skill 要同时更新 AGENTS.md §5 Skills catalog 和 `using-praxis/SKILL.md` 的目录表。
## 远端
[git.simgreek.com/simgreek/team-guide](https://git.simgreek.com/simgreek/team-guide) ·
[tags 列表](https://git.simgreek.com/simgreek/team-guide/tags)
[git.simgreek.com/simgreek/praxis](https://git.simgreek.com/simgreek/praxis) ·
[tags 列表](https://git.simgreek.com/simgreek/praxis/tags)
## License
+16
View File
@@ -0,0 +1,16 @@
{
"hooks": {
"SessionStart": [
{
"matcher": "startup|clear|compact",
"hooks": [
{
"type": "command",
"command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd\" session-start",
"async": false
}
]
}
]
}
}
+47
View File
@@ -0,0 +1,47 @@
@echo off
REM Windows shim that invokes a bash hook script. Claude Code passes the
REM hook name as the first argument; we forward stdin and arguments to the
REM matching POSIX script under hooks/.
setlocal
REM Find git's bash. Required because Claude Code on Windows installations
REM does not always have a bash on PATH.
set "BASH_EXE="
for %%P in (
"%ProgramFiles%\Git\bin\bash.exe"
"%ProgramFiles(x86)%\Git\bin\bash.exe"
"%LocalAppData%\Programs\Git\bin\bash.exe"
) do (
if exist "%%~P" (
set "BASH_EXE=%%~P"
goto :found
)
)
REM Fallback: hope bash is on PATH.
where bash >nul 2>&1
if %ERRORLEVEL%==0 (
set "BASH_EXE=bash"
)
:found
if not defined BASH_EXE (
echo praxis hook: bash not found, skipping > nul
exit /b 0
)
set "HOOK_NAME=%~1"
if "%HOOK_NAME%"=="" (
echo praxis hook: no hook name provided 1>&2
exit /b 1
)
set "HOOK_SCRIPT=%~dp0%HOOK_NAME%"
if not exist "%HOOK_SCRIPT%" (
echo praxis hook: %HOOK_NAME% script not found 1>&2
exit /b 1
)
"%BASH_EXE%" "%HOOK_SCRIPT%"
exit /b %ERRORLEVEL%
+37
View File
@@ -0,0 +1,37 @@
#!/usr/bin/env bash
# SessionStart hook for praxis plugin.
# Loads using-praxis SKILL.md and injects it into the session context so the
# agent reads the iron-law / red-flags content before its first response.
set -euo pipefail
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
PLUGIN_ROOT="$(cd "${SCRIPT_DIR}/.." && pwd)"
using_praxis_content=$(cat "${PLUGIN_ROOT}/skills/using-praxis/SKILL.md" 2>&1 || echo "Error reading using-praxis skill")
# Escape string for JSON embedding using bash parameter substitution.
escape_for_json() {
local s="$1"
s="${s//\\/\\\\}"
s="${s//\"/\\\"}"
s="${s//$'\n'/\\n}"
s="${s//$'\r'/\\r}"
s="${s//$'\t'/\\t}"
printf '%s' "$s"
}
using_praxis_escaped=$(escape_for_json "$using_praxis_content")
session_context="<EXTREMELY_IMPORTANT>\nYou are working in a Simgreek project that has the praxis plugin installed.\n\n**Below is the full content of your 'praxis:using-praxis' skill — your introduction to using praxis skills. For all other skills, use the 'Skill' tool:**\n\n${using_praxis_escaped}\n</EXTREMELY_IMPORTANT>"
# Output context injection. Claude Code expects hookSpecificOutput.additionalContext.
# Cursor expects additional_context (snake_case). Copilot CLI expects additionalContext top-level.
if [ -n "${CURSOR_PLUGIN_ROOT:-}" ]; then
printf '{\n "additional_context": "%s"\n}\n' "$session_context"
elif [ -n "${CLAUDE_PLUGIN_ROOT:-}" ] && [ -z "${COPILOT_CLI:-}" ]; then
printf '{\n "hookSpecificOutput": {\n "hookEventName": "SessionStart",\n "additionalContext": "%s"\n }\n}\n' "$session_context"
else
printf '{\n "additionalContext": "%s"\n}\n' "$session_context"
fi
exit 0
-50
View File
@@ -1,50 +0,0 @@
# Team library
A small catalog of focused specs and reusable assets. Read the entries
that match the current task; ignore the rest.
This directory is **not** the team's general working agreements — those
live in [`../AGENTS.md`](../AGENTS.md). The library is for narrower,
deeper specs that would bloat AGENTS.md if inlined.
## How to use this
When starting a non-trivial task:
1. Read [`../AGENTS.md`](../AGENTS.md) (general rules).
2. Scan this catalog. If an entry matches your task, read its `SPEC.md`.
3. If nothing matches, proceed.
## Catalog
| Entry | Read it when… |
| -------------------------------------- | ---------------------------------------------------------- |
| [`git-upload/`](git-upload/SPEC.md) | Pushing code to a remote, especially first push or new files |
(More entries will be added as the team encounters recurring questions
worth standardizing.)
## Adding to the library
Promote a topic to a library entry when **all** are true:
1. The topic has bitten us at least twice.
2. It's narrower than AGENTS.md general rules and would make AGENTS.md
bloated to inline.
3. Steps are stable enough to write down.
Layout for a new entry:
```
library/<entry-name>/
└── SPEC.md ← English, the actual spec
```
`SPEC.md` follows the same editing rules as AGENTS.md (one rule per
bullet, no emoji, examples beat prose, ~300 lines max). Lead with a
**When to read this** section so agents can decide quickly whether the
entry applies.
If a future entry needs scripts or skill packages, add them next to
`SPEC.md`. The catalog table above gets a one-line "read it when…" for
each new entry.
+202
View File
@@ -0,0 +1,202 @@
---
name: debugging
description: Use when encountering any bug, test failure, or unexpected behavior, before proposing a fix — requires root-cause investigation before any code change
---
# Debugging — root cause before fix
## The Iron Law
```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```
Random fixes waste time and create new bugs. Quick patches mask the
real problem and the same bug shows up later in a different form.
If you have not completed Phase 1 below, you cannot propose fixes.
## When to invoke this skill
Any technical issue:
- Test failures
- Bugs in dev or production
- Unexpected behavior
- Performance problems
- Build / typecheck failures
- Integration issues
**Especially when:**
- Time pressure (emergencies make guessing tempting)
- "Just one quick fix" looks obvious
- You've already tried multiple fixes
- Previous fix didn't work
- You don't fully understand what broke
**Don't skip when:**
- Issue seems simple — simple bugs have root causes too
- You're in a hurry — systematic is faster than thrashing
- The user wants it fixed NOW — guess-and-check makes it slower
## The four phases
You must complete each phase before proceeding to the next.
### Phase 1: Root cause investigation
Before attempting any fix:
1. **Read error messages carefully.** Don't skim past errors or
warnings. Read stack traces completely. Note line numbers, file
paths, error codes. The exact answer is often in the message.
2. **Reproduce consistently.** Can you trigger it reliably? What are
the exact steps? Every time? If not reproducible, gather more data
— don't guess.
3. **Check recent changes.** What changed that could cause this?
`git log --oneline -10`. New deps, config changes, environment
differences.
4. **Multi-component systems: gather evidence at boundaries.** When
the system has layers (CI → build → signing, API → service → DB),
add diagnostic logging at each layer before proposing fixes. Run
once to see WHERE it breaks, then investigate that specific layer.
Example layering:
```
For each component boundary:
- Log what data enters
- Log what data exits
- Verify env / config propagation
- Check state at each layer
Run once → identify failing layer → investigate that layer
```
5. **Trace data flow backward.** When the error is deep in the call
stack: where does the bad value originate? What called this with
the bad value? Keep tracing up until you find the source. Fix at
the source, not at the symptom.
### Phase 2: Pattern analysis
1. **Find a working example.** Locate similar code in the same
codebase that works. What does it do that the broken code doesn't?
2. **Compare against references.** If the broken code follows a
pattern (a library's example, a sister module), read the reference
completely. Don't skim. Understand it before applying it.
3. **Identify differences.** What's different between working and
broken? List every difference, however small. Don't assume "that
can't matter" — that assumption is usually how the bug got there.
4. **Understand dependencies.** What other components does this need?
What config / env / assumptions does it make?
### Phase 3: Hypothesis and minimal test
1. **Form a single hypothesis.** State it: "I think X is the root
cause because Y." Be specific. Vague hypothesis = vague fix.
2. **Test minimally.** Make the smallest possible change to test the
hypothesis. One variable at a time. Don't bundle multiple changes
"while you're in there."
3. **Verify before continuing.** Did it work? Yes → Phase 4. No →
form a NEW hypothesis. Don't pile fixes on top of fixes.
4. **When you don't know, say so.** "I don't understand why X happens"
is a valid status. Don't pretend. Ask, research, or surface to the
human.
### Phase 4: Fix and verify
1. **Write a failing test first.** Simplest possible reproduction.
Automated if the project has a framework; one-off script otherwise.
The test must fail with the current code — that's how you know it
actually targets the bug.
2. **Implement a single fix.** Address the root cause from Phase 1.
One change. No "while I'm here" cleanups, no bundled refactors.
3. **Verify.** Test passes? Other tests still pass? The original
reported symptom is gone?
4. **If the fix doesn't work:** stop. Count: how many fixes have you
tried?
- **<3**: return to Phase 1 with what you learned.
- **≥3**: stop and question the architecture (next step). Do **not**
try fix #4.
5. **3+ fixes failed = architectural problem, not a fix problem.**
Pattern indicators:
- Each fix reveals a new shared-state / coupling issue elsewhere.
- Fixes require "massive refactoring" to land cleanly.
- Each fix creates new symptoms in different places.
Surface to the human: "I've tried 3 approaches, each surfaces a
different downstream issue. I think the underlying pattern is wrong.
Want to discuss before I try more fixes?"
## Red Flags — STOP and follow the process
If you catch yourself thinking any of these, you are skipping the
process. Stop. Return to Phase 1.
| Thought | Reality |
|---------|---------|
| "Quick fix for now, investigate later" | "Later" never comes; the bug returns |
| "Just try changing X and see if it works" | That's guess-and-check, not debugging |
| "Add multiple changes, run tests" | Can't isolate what worked |
| "Skip the test, I'll manually verify" | Manual ≠ regression-proof |
| "It's probably X, let me fix that" | "Probably" is not a hypothesis |
| "Pattern says X but I'll adapt it" | Partial pattern = bug |
| "Here are the main problems: <list>" (without investigation) | Symptoms ≠ causes |
| Proposing fixes before tracing data flow | Always wrong |
| "One more fix attempt" (after 2+ failures) | Architectural problem |
| Each fix reveals new problem in different place | Architectural problem |
## Common rationalizations
| Excuse | Reality |
|--------|---------|
| "Issue is simple, no need for process" | Simple issues have root causes too. The process is fast for simple bugs. |
| "Emergency, no time for process" | Systematic debugging is **faster** than guess-and-check. |
| "Just try this first, then investigate" | First fix sets the pattern. Do it right from the start. |
| "I'll write the test after confirming the fix" | Untested fixes don't stick. Test first proves the fix. |
| "Multiple fixes at once saves time" | Can't isolate what worked. Causes new bugs. |
| "I see the problem, let me fix it" | Seeing symptoms ≠ understanding root cause. |
| "One more fix" (after 2+ failures) | Three failures = architectural problem. Don't fix again. |
## Quick reference
| Phase | Activity | Done when |
|-------|---------|-----------|
| 1. Root cause | Read errors, reproduce, check changes, trace data | You can describe WHAT and WHY |
| 2. Pattern | Find working example, compare, list differences | You know what to change |
| 3. Hypothesis | State theory, test minimally | Confirmed or new hypothesis |
| 4. Fix | Failing test → fix → verify | Original symptom is gone, no regressions |
## When the process reveals "no root cause"
If systematic investigation reveals the issue is genuinely
environmental, timing-dependent, or external:
1. You've completed the process — that's the answer.
2. Document what you investigated.
3. Implement appropriate handling: retry, timeout, clear error
message, monitoring.
But: 95% of "no root cause" diagnoses are incomplete investigation.
Be honest about which you're in.
## Related skills
- `verification` — verify the fix actually worked before claiming done
- `nodejs-project` — Phase 3 of nodejs SOP says "fail twice, invoke this skill"
@@ -1,16 +1,13 @@
---
name: git-upload
description: Use when pushing code to a remote, especially first push, adding a new file type the repo hasn't committed before, cleaning up .gitignore, or after suspecting a leaked secret
---
# git-upload — what to commit, what not to
## When to read this
- Pushing to a remote for the first time on a project.
- Adding a new file type the project hasn't committed before (data
dumps, generated artifacts, model weights, .env files, screenshots).
- About to run `git add .` or `git add -A`.
- Cleaning up a `.gitignore`.
- Suspect or confirmed a secret was committed.
This is a focused spec, not the full Git workflow. Branch / commit /
PR / tagging rules live in [`../../AGENTS.md`](../../AGENTS.md) §3.
This is a focused spec for what belongs in version control and what
doesn't. Branch / commit message / PR / tagging rules live in praxis
AGENTS.md §3.
## The first rule
@@ -262,8 +259,7 @@ A short checklist when initializing a project:
- [ ] `.gitignore` covers secrets, build outputs, editor state, agent
local state
- [ ] No `.env` (or any `.env.*` other than `.env.example`) in the tree
- [ ] No files >5 MB in the tree (check with `find . -size +5M
-not -path "./.git/*"` or equivalent)
- [ ] No files >5 MB in the tree
- [ ] `git status` shows only files you mean to commit
- [ ] `git diff --cached` reads cleanly — no surprise content
- [ ] Repo URL on the remote matches the one you intend; no token in
+233
View File
@@ -0,0 +1,233 @@
---
name: nodejs-project
description: Use in any project with a package.json — task execution SOP from project entry through release, including encoding/line-ending checks that prevent silent file corruption
---
# nodejs-project — AI execution SOP
This is the AI's task-execution sequence in any Node.js / Next.js
project. Each phase is a concrete set of commands or checks the AI runs
**on its own** before declaring the task done. The only points that
pause for the human are flagged explicitly.
## Phase 0 — Project entry
Run on first action in the repo:
```bash
ls AGENTS.md CLAUDE.md package.json .gitignore
node --version
cat package.json | grep -A 20 '"scripts"'
```
- **No `AGENTS.md`** → stop. Ask the human: "this project has no
AGENTS.md; create one before proceeding?"
- **No `.gitignore` or it's <100 bytes** → stop. The project is missing
basic ignore rules; flag before any commit.
- **`node --version` doesn't match what AGENTS.md says** → stop, ask.
## Phase 1 — Task framing
Trigger conditions, in order:
- Task description < 3 sentences AND scope > 1 file → ask for the
5-line spec (`Goal / Why / Done when / Out of scope / Risks`).
- Task touches: `package.json` deps, schema, auth, secrets, production
config, build scripts → confirm scope with human before any edit.
- Otherwise: write the implicit spec into the PR description draft and
proceed.
## Phase 2 — Pre-edit sync
```bash
git status # working tree clean?
git pull --ff-only # remote ahead?
```
- Working tree dirty with unrelated changes → stop, ask.
- `pull --ff-only` fails (diverged history) → stop, ask. Don't
force-pull, don't merge silently.
## Phase 3 — Edit & verify
After each meaningful change run:
```bash
npm run check # if defined
npm test # if defined
npx tsc --noEmit # for TypeScript / Next.js
```
For projects with `build-release` or similar build scripts: do **not**
run them automatically — they produce large artifacts. Run only when
the task is "release."
Failure handling:
- Fix the error, re-run.
- **Same error twice** → stop, surface to human. Don't keep retrying.
Invoke the `debugging` skill — that's what it's for.
## Phase 4 — Encoding & line-ending checks
Run before staging any text file changes. Source code is **UTF-8
without BOM**, line endings follow the project's existing convention
(typically LF, except `.bat` / `.cmd` which need CRLF).
Detection commands:
```bash
# Find files with UTF-8 BOM (EF BB BF) — should be empty output
git diff --cached --name-only -z | xargs -0 -I{} sh -c \
'head -c 3 "{}" | od -An -tx1 | grep -q "ef bb bf" && echo "BOM: {}"'
# Find CRLF in source files that should be LF (skip .bat/.cmd)
git diff --cached --name-only -z | xargs -0 grep -lI $'\r' 2>/dev/null \
| grep -vE '\.(bat|cmd)$'
# Find non-UTF-8 bytes in source
git diff --cached --name-only -z | xargs -0 -I{} sh -c \
'iconv -f UTF-8 -t UTF-8 "{}" >/dev/null 2>&1 || echo "non-UTF8: {}"'
```
Hits → fix before commit:
- BOM in `.js` / `.mjs` / `.json` / `.md` / `.html` / `.css` → strip.
Node `JSON.parse` rejects BOM in `package.json`. Some bundlers ship
BOM into the output and break browsers.
- CRLF in `.js` / `.mjs` / `.ts` / `.tsx` / `.json` / `.md` / `.sh` →
convert to LF. CRLF in `.sh` makes the script silently fail on Linux.
- CRLF in `.bat` / `.cmd` → keep, this is correct.
- Non-UTF-8 bytes (typically GBK on Windows) → re-save the file as
UTF-8 in the editor. This is the most common silent corruption when
AI edits a Chinese-content file on a system with Windows-default
encoding — symptom is "好" appearing as "濂" or similar mojibake.
`.gitattributes` baseline (commit it once per project):
```
* text=auto eol=lf
*.bat text eol=crlf
*.cmd text eol=crlf
*.png binary
*.jpg binary
*.zip binary
```
This forces normalization on commit and prevents future drift.
## Phase 5 — Pre-commit verification
```bash
git status
git diff --cached
```
The AI must read the entire `--cached` diff and answer in its own
output:
1. Build / typecheck pass?
2. Tests pass (or honestly: "didn't run because <reason>")?
3. Files outside the stated scope? List + justify each, or revert.
4. New deps? List them in PR description and Phase 1 confirmation.
5. AI-generated comments restating the code? Delete.
6. End-to-end exercised (for user-visible changes)?
Plus **Node-specific Phase 5 checks**:
- `package-lock.json` in diff but no change to `package.json` deps →
stop. This is usually IDE auto-install. Revert the lockfile diff.
- `package.json` deps changed but no lockfile diff → stop. Run
`npm install` once, commit lockfile in same commit.
- `.env` / `.env.local` / `.env.production` / `*.pem` / `*.key` in diff
→ **stop, do not commit**. Add to `.gitignore` if missing.
- `node_modules/` / `.next/` / `dist/` / `build/` / `out/` in diff →
stop. Gitignore is broken; fix before commit.
- Files >5 MB in diff (`git diff --cached --stat | awk '$3 > 5120'`) →
stop, ask human about LFS or out-of-band delivery.
- Any encoding hit from Phase 4 unresolved → stop.
## Phase 6 — Commit
```bash
git add <specific files> # NOT git add . / git add -A
git commit -m "<area>: <imperative summary under 60 chars>"
```
- Always include `Co-Authored-By: Claude <noreply@anthropic.com>` (or
the project's tool-specific trailer) for AI-assisted commits.
- One topic per commit. "and" in summary → split.
- English message.
## Phase 7 — Push
```bash
git push origin <branch>
```
- First push of a new feature branch: include `-u`.
- Branch is `main` or `dev` → **stop, ask human** before push.
- `--force` push → **stop, ask human**, regardless of branch. Quote the
reason and the branch back to the human.
## Phase 8 — Release (product projects only)
Only run when the task is explicitly "release vX.Y.Z." Skip otherwise.
```bash
# 1. Read project's AGENTS.md "release-bump checklist"
# 2. For each listed file: edit, then verify no stale version remains
git grep -nE 'V?[0-9]+\.[0-9]+\.[0-9]+' -- <changed-files>
# 3. Standard checks
npm run check
npm test
# 4. Commit + tag
git add <changed files>
git commit -m "chore: release vX.Y.Z"
git tag -a vX.Y.Z HEAD -m "<Project> VX.Y.Z"
git push origin <branch>
git push origin vX.Y.Z
# 5. Build
npm run release # or project's build script
# 6. List artifacts
ls -lh release/ # or wherever the build outputs
# 7. STOP — ask human:
# "Artifacts ready: <list>. Sizes: <sizes>. Upload to <distribution
# channel>?"
```
The upload step is **always human-confirmed**. It's the only
externally-visible irreversible action in the flow.
## Where the human pauses
In total, AI stops and asks the human only at:
- Phase 0: missing AGENTS.md
- Phase 1: vague task or scope-sensitive change
- Phase 2: dirty tree or diverged history
- Phase 3: same error twice (invoke `debugging`)
- Phase 4 / 5: encoding / lockfile / secret / large-file anomalies
- Phase 7: push to `main`/`dev` or `--force`
- Phase 8: distribution upload
Everything else is self-running.
## Quick reference
```
[entry] read AGENTS.md → no? stop.
[frame] vague task? → spec. scope-sensitive? → confirm.
[sync] git status / pull --ff-only.
[edit] npm run check / test / tsc. fail twice? invoke debugging.
[encode] no BOM / LF for src / CRLF for .bat / valid UTF-8.
[verify] git diff --cached → 6 questions + Node-specific 5.
[commit] git add by name. <area>: <imperative>.
[push] main/dev/force? stop. else push.
[release] follow project's bump checklist. STOP before upload.
```
+117
View File
@@ -0,0 +1,117 @@
---
name: using-praxis
description: Use when starting any conversation in a Simgreek project — establishes how to find and use praxis skills, requiring Skill tool invocation before ANY response including clarifying questions
---
<SUBAGENT-STOP>
If you were dispatched as a subagent to execute a specific task, skip this skill — your dispatcher already loaded praxis context.
</SUBAGENT-STOP>
<EXTREMELY-IMPORTANT>
If you think there is even a 1% chance a praxis skill might apply to what you are doing, you ABSOLUTELY MUST invoke it.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
</EXTREMELY-IMPORTANT>
# Using Praxis
Praxis is the Simgreek team's coding agent rulebook — Greek for "practice." It exists because human teammates have been bitten by every shortcut you are about to take. The skills below encode those scars.
## Instruction Priority
Praxis skills override default agent behavior, but **the user's explicit instructions always take precedence**:
1. **User's explicit instructions** (project AGENTS.md, CLAUDE.md, direct chat) — highest
2. **Praxis skills** — override default behavior where they conflict
3. **Default agent behavior** — lowest
If a project's AGENTS.md says "skip the encoding check this once" and a skill says "always check encoding," follow the user. They own the project. You are a guest.
## How to Access Skills
**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its full content is loaded — follow it directly. Never use `Read` on a skill file when `Skill` is available.
**In Codex / Cursor / others:** Skills live as markdown files under `<plugin-root>/skills/`. Read the relevant ones with the file-reading tool.
# The Rule
**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means you must check. If an invoked skill turns out to be wrong for the situation, drop it — but you have to check first.
This includes:
- Before answering a clarifying question
- Before exploring the codebase
- Before "just running git status"
- Before reading docs to understand the project
- Before announcing what you're going to do
The skill check is the **first thing** that happens after you receive a message in a praxis-enabled project. Not the second. Not "after I look around real quick." First.
## Red Flags — These Thoughts Mean STOP
If you catch yourself thinking any of these, you are rationalizing past a skill. Stop, invoke the skill, then proceed.
| Thought | Reality |
|---------|---------|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "I can just check git status / read a file quickly" | Files lack conversation context. Check for skills. |
| "Let me gather information first" | Skills tell you HOW to gather information. |
| "This doesn't need a formal skill" | If a skill exists, use it. |
| "I remember this skill" | Skills evolve. Read the current version. |
| "This is a small change" | Small changes ship the bugs. Use the skill. |
| "The skill is overkill" | Simple things become complex when skipped. |
| "I'll just do this one thing first" | "One thing first" is how skills get bypassed. |
| "This feels productive" | Undisciplined motion wastes time. Skills prevent it. |
| "The user is in a hurry" | Skipping skills makes everything slower, not faster. |
| "I know what that means" | Knowing the concept ≠ following the procedure. Invoke. |
## The Praxis Skill Catalog
Read the catalog before your first action in this project. Match each candidate skill against the current task.
| Skill | When it applies |
|-------|-----------------|
| `git-upload` | Pushing to a remote, first push, adding new file types, leaked secret |
| `nodejs-project` | Any project with `package.json` — task execution SOP including encoding checks |
| `debugging` | Any bug, test failure, unexpected behavior, before proposing a fix |
| `verification` | About to claim work is complete, fixed, or passing |
If multiple apply, use them in order: process skills (`debugging`) before implementation skills (`nodejs-project`); verification (`verification`) before declaring done.
## Skill Priority
When multiple skills could apply:
1. **Process skills first** (`debugging`) — they determine HOW to approach the task
2. **Implementation skills second** (`nodejs-project`, `git-upload`) — they guide execution
3. **Verification last** (`verification`) — before declaring done
"Fix this bug" → `debugging` first, then `nodejs-project` if Node-relevant.
"Push my changes" → `git-upload` first, then `verification` before declaring done.
## Skill Types
**Rigid skills** (debugging, verification): follow exactly. The discipline is the value. Don't adapt away the steps you find inconvenient.
**Flexible skills** (nodejs-project SOP, git-upload pitfall list): adapt principles to context. The SOP is a default; deviate when the context demands and **state the deviation explicitly**.
The skill itself tells you which type it is.
## User Instructions
User instructions describe **what** to do, not **how**. "Add this feature" or "fix this bug" does not mean skip the workflow. The user sets the destination; praxis sets the route.
## What to Do Now
Before your next action:
1. Identify which skills in the catalog above might apply (1% threshold).
2. Invoke each one via the `Skill` tool (or read the file).
3. Follow its checklist.
4. Then proceed.
If the task is something praxis genuinely doesn't cover (e.g., "summarize this article"), proceed without a skill — but the check itself is mandatory.
+139
View File
@@ -0,0 +1,139 @@
---
name: verification
description: Use before claiming work is complete, fixed, or passing — requires running verification commands and reading output before making any success claim; evidence before assertions
---
# Verification — evidence before claims
## The Iron Law
```
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
```
Claiming work is complete without verification is dishonesty, not
efficiency. If you haven't run the verification command in this turn,
you cannot claim it passes.
## The gate
Before claiming any status or expressing satisfaction:
1. **Identify** the command that proves the claim.
2. **Run** it (fresh and complete — not a partial check, not a
remembered previous run).
3. **Read** the full output. Check the exit code. Count failures.
4. **Verify** the output confirms the claim.
- If yes: state the claim **with the evidence**.
- If no: state the actual status with the evidence.
5. **Only then** make the claim.
Skipping any step is lying, not verifying.
## Common claims and what proves them
| Claim | What proves it | What does NOT prove it |
|-------|----------------|------------------------|
| Tests pass | Test command output: 0 failures | "Should pass", a run from earlier |
| Linter clean | Linter output: 0 errors | Partial check, extrapolation |
| Build succeeds | Build command exits 0 | Linter passing, logs look good |
| Bug fixed | Test the original symptom — passes | Code changed, "assumed fixed" |
| Regression test works | Red → green: test fails before fix, passes after | Test passes once after fix |
| Sub-agent completed | VCS diff shows the changes | Sub-agent reports "success" |
| Requirements met | Line-by-line checklist | "All tests pass" |
## Red Flags — STOP
If you catch yourself doing any of these, you're about to make an
unverified claim. Stop, run the verification, then continue.
- Using "should", "probably", "seems to", "I think"
- Saying "Great!", "Perfect!", "Done!" before running anything
- About to commit / push / open a PR without re-running checks in
this turn
- Trusting a sub-agent's success report without diff inspection
- Relying on partial verification (one file checked, claim covers
many)
- "Just this once"
- Tired and wanting the work over
- **Any wording implying success without evidence in this turn**
## Rationalizations
| Excuse | Reality |
|--------|---------|
| "Should work now" | RUN the verification |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ compiler ≠ tests |
| "Agent said success" | Verify independently |
| "I'm tired" | Exhaustion ≠ excuse |
| "Partial check is enough" | Partial proves nothing about the rest |
| "Different words, so the rule doesn't apply" | Spirit over letter |
## Patterns
**Tests:**
```
✅ Run `npm test` → output: "34 passing" → "All tests pass (34/34)."
❌ "Should pass now." / "Looks correct."
```
**Regression test (red-green):**
```
✅ Write test → run (pass) → revert fix → run (FAIL) → restore fix → run (pass)
❌ "I've added a regression test." (without red-green proof)
```
**Build:**
```
✅ Run `npm run build` → exit 0 → "Build passes."
❌ "Linter passed, build should be fine." (linter doesn't compile)
```
**Requirements:**
```
✅ Re-read the spec → check each line → report gaps or completion
❌ "Tests pass, so we're done." (tests ≠ requirements)
```
**Sub-agent delegation:**
```
✅ Sub-agent reports success → run `git diff` → confirm the changes
exist and are correct → report actual state
❌ Trust the sub-agent report
```
## When to apply
Always before:
- Any variation of "done", "complete", "fixed", "passing"
- Any expression of satisfaction about work state
- Committing, opening a PR, declaring task complete
- Moving to the next task in a multi-step plan
- Delegating verification to a sub-agent (verify their result yourself)
The rule applies to exact phrases, paraphrases, synonyms, and any
implication of success. "Spirit over letter."
## Why this matters
Unverified claims:
- Break the user's trust ("I don't believe you")
- Ship undefined functions or missing requirements
- Waste time on false completion → redirect → rework
Honesty is a core value. The cost of running the verification command
is small. The cost of being wrong is large.
## Bottom line
Run the command. Read the output. **Then** claim the result. Every
time.