ソースを参照

Replace WARP.md with tool-neutral AGENTS.md

Drop the Warp-specific guidance file in favor of AGENTS.md (read by Claude
Code, Codex, Warp, and others). Trim the duplicated install commands and
correct the stale pattern count (was "25", now 29). Keep the maintenance
contract: SKILL.md is source of truth, keep README/version/pattern-count in
sync, stable numbering.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Siqi Chen 3 週間 前
コミット
f86de60c44
2 ファイル変更25 行追加53 行削除
  1. 25 0
      AGENTS.md
  2. 0 53
      WARP.md

+ 25 - 0
AGENTS.md

@@ -0,0 +1,25 @@
+# AGENTS.md
+
+Guidance for AI coding agents (Claude Code, Codex, Warp, etc.) working in this repository.
+
+## What this repo is
+
+A **Claude Code / OpenCode skill** implemented entirely as Markdown. The runtime artifact is `SKILL.md`: the agent reads its YAML frontmatter (metadata + allowed tools) followed by the editor prompt. There is no build step and no code to run.
+
+## Key files
+
+- `SKILL.md` — the skill itself. YAML frontmatter (`name`, `version`, `description`, `allowed-tools`) followed by the canonical, numbered pattern list with before/after examples. **This is the source of truth.**
+- `README.md` — for humans: installation, usage, a summary table of the patterns, and a version history.
+
+## The maintenance contract
+
+`SKILL.md` and `README.md` must stay in sync. When you change behavior or content:
+
+- **Patterns:** the skill currently defines **29 numbered patterns**. If you add, remove, or renumber any, update the README pattern table, its "N Patterns Detected" heading, and every cross-reference in the same change. Keep numbering stable unless you are deliberately renumbering.
+- **Version:** `SKILL.md` frontmatter has a `version:` field and `README.md` has a "Version History" section. Bump both together.
+- **Non-obvious fixes:** if you change the prompt to handle a tricky failure mode (a repeated mis-edit, an unexpected tone shift), add a short note to the README version history explaining what was fixed and why.
+
+## Editing SKILL.md
+
+- Preserve valid YAML frontmatter (formatting and indentation).
+- The prompt below the frontmatter is the product. Edit it like a careful instruction document, not code.

+ 0 - 53
WARP.md

@@ -1,53 +0,0 @@
-# WARP.md
-
-This file provides guidance to WARP (warp.dev) when working with code in this repository.
-
-## What this repo is
-This repository is a **Claude Code skill** implemented entirely as Markdown.
-
-The “runtime” artifact is `SKILL.md`: Claude Code reads the YAML frontmatter (metadata + allowed tools) and the prompt/instructions that follow.
-
-`README.md` is for humans: installation, usage, and a compact overview of the patterns.
-
-## Key files (and how they relate)
-- `SKILL.md`
-  - The actual skill definition.
-  - Starts with YAML frontmatter (`---` … `---`) containing `name`, `version`, `description`, and `allowed-tools`.
-  - After the frontmatter is the editor prompt: the canonical, detailed pattern list with examples.
-- `README.md`
-  - Installation and usage instructions.
-  - Contains a summarized “25 patterns” table and a short version history.
-
-When changing behavior/content, treat `SKILL.md` as the source of truth, and update `README.md` to stay consistent.
-
-## Common commands
-### Install the skill into Claude Code
-Recommended (clone directly into Claude Code skills directory):
-```bash
-mkdir -p ~/.claude/skills
-git clone https://github.com/blader/humanizer.git ~/.claude/skills/humanizer
-```
-
-Manual install/update (only the skill file):
-```bash
-mkdir -p ~/.claude/skills/humanizer
-cp SKILL.md ~/.claude/skills/humanizer/
-```
-
-## How to “run” it (Claude Code)
-Invoke the skill:
-- `/humanizer` then paste text
-
-## Making changes safely
-### Versioning (keep in sync)
-- `SKILL.md` has a `version:` field in its YAML frontmatter.
-- `README.md` has a “Version History” section.
-
-If you bump the version, update both.
-
-### Editing `SKILL.md`
-- Preserve valid YAML frontmatter formatting and indentation.
-- Keep the pattern numbering stable unless you’re intentionally re-numbering (since the README table and examples reference the same numbering).
-
-### Documenting non-obvious fixes
-If you change the prompt to handle a tricky failure mode (e.g., a repeated mis-edit or an unexpected tone shift), add a short note to `README.md`’s version history describing what was fixed and why.