@adamchanadam/agent-handoff-kit 0.4.1 → 0.4.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -21
- package/README.en.md +1 -1
- package/README.md +1 -1
- package/bin/agent-handoff-kit.mjs +7107 -6887
- package/bin/commands.mjs +134 -134
- package/bin/handoff-read.mjs +88 -88
- package/bin/installed-file-contract.mjs +154 -90
- package/bin/migration-baselines/official-origin-catalog.json +514 -1
- package/bin/official-origin-catalog.mjs +294 -267
- package/bin/progress/ICON-LICENSE.txt +21 -21
- package/bin/progress/assets.mjs +6 -6
- package/bin/progress/dashboard.mjs +134 -134
- package/bin/progress/icons.svg +36 -36
- package/bin/progress/index.html +31 -31
- package/bin/progress/launch.mjs +40 -40
- package/bin/progress/open.mjs +43 -43
- package/bin/progress/project-version.mjs +121 -121
- package/bin/progress/projection.mjs +144 -144
- package/bin/progress/renderer.js +152 -152
- package/bin/progress/server.mjs +78 -78
- package/bin/progress/styles.css +31 -31
- package/bin/prompt-mirror-core.mjs +84 -84
- package/bin/upgrade-inventory.mjs +243 -243
- package/bin/user-rules-router.mjs +4 -4
- package/docs/commands.md +2 -2
- package/docs/progress.md +73 -73
- package/package.json +22 -22
- package/packs/agent-governance.md +120 -120
- package/packs/closeout.md +91 -91
- package/packs/coding.md +28 -28
- package/packs/integrations.md +20 -20
- package/packs/knowledge.md +3 -3
- package/packs/onboarding.md +43 -39
- package/packs/research.md +30 -30
- package/packs/safety.md +2 -2
- package/runtime-core/AGENTS.core.md +161 -147
- package/runtime-core/CLAUDE.md +13 -13
- package/runtime-core/DOC_SYNC_REGISTRY.md +24 -24
- package/runtime-core/GEMINI.md +17 -17
- package/runtime-core/PROJECT_DECISIONS.md +43 -43
- package/runtime-core/PROJECT_INDEX.md +16 -16
- package/runtime-core/RULE_PACKS.md +1 -1
- package/runtime-core/SESSION_HANDOFF.md +180 -180
- package/runtime-core/SESSION_LOG.md +37 -37
- package/runtime-core/START_NEXT_SESSION_PROMPT.txt +1 -1
- package/runtime-core/USER_RULES_ENTRY.md +2 -0
|
@@ -1,24 +1,24 @@
|
|
|
1
|
-
# Doc Sync Registry
|
|
2
|
-
|
|
3
|
-
Purpose: map change types to documents and checks. Keep this as rows, not long prose.
|
|
4
|
-
|
|
5
|
-
## Status Vocabulary
|
|
6
|
-
|
|
7
|
-
Use: `confirmed`, `unverified`, `pending`, `blocked`, `not_applicable`.
|
|
8
|
-
|
|
9
|
-
| Change type | Also check/update | Verification |
|
|
10
|
-
|---|---|---|
|
|
11
|
-
| New file or directory | `dev/PROJECT_INDEX.md` Directory Map | path listed |
|
|
12
|
-
| Generated Markdown or durable artifact | `dev/PROJECT_INDEX.md` Directory Map / Fact Base / Entry Points, and this registry when future updates need sync | artifact classified as indexed / synced / temporary / one-time evidence; duplicate source-of-truth risk checked |
|
|
13
|
-
| Stack or command change | `dev/PROJECT_INDEX.md` Stack / Entry Points | command verified or marked unverified |
|
|
14
|
-
| Public behavior change | README, public docs, changelog | docs mention current behavior |
|
|
15
|
-
| API or SDK behavior change | API docs, examples, tests | tests or documented reason |
|
|
16
|
-
| Runbook change | runbook path in `PROJECT_INDEX.md` | procedure still executable |
|
|
17
|
-
| Governance rule change | relevant pack/core, registry, README if public-facing | complexity budget checked |
|
|
18
|
-
| Closeout/startup contract change | `AGENTS.md`, `dev/SESSION_HANDOFF.md`, `dev/SESSION_LOG.md`, `dev/PROJECT_INDEX.md`, README quick usage | opening message schema + workspace identity present |
|
|
19
|
-
| Workspace identity change | `dev/SESSION_HANDOFF.md`, `dev/PROJECT_INDEX.md` | root/branch/commit/status recorded or marked unverified |
|
|
20
|
-
| Release | release notes, README version, changelog | release pack checklist |
|
|
21
|
-
|
|
22
|
-
## Registry Rule
|
|
23
|
-
|
|
24
|
-
If a change has no matching row, add a row before closeout or record why no durable sync rule is needed. At closeout, record sync status for every row touched by the session.
|
|
1
|
+
# Doc Sync Registry
|
|
2
|
+
|
|
3
|
+
Purpose: map change types to documents and checks. Keep this as rows, not long prose.
|
|
4
|
+
|
|
5
|
+
## Status Vocabulary
|
|
6
|
+
|
|
7
|
+
Use: `confirmed`, `unverified`, `pending`, `blocked`, `not_applicable`.
|
|
8
|
+
|
|
9
|
+
| Change type | Also check/update | Verification |
|
|
10
|
+
|---|---|---|
|
|
11
|
+
| New durable or discoverable project file or directory | `dev/PROJECT_INDEX.md` Directory Map | path listed; temporary or one-time evidence follows the next row's classification instead |
|
|
12
|
+
| Generated Markdown or durable artifact | `dev/PROJECT_INDEX.md` Directory Map / Fact Base / Entry Points, and this registry when future updates need sync | artifact classified as indexed / synced / temporary / one-time evidence; duplicate source-of-truth risk checked |
|
|
13
|
+
| Stack or command change | `dev/PROJECT_INDEX.md` Stack / Entry Points | command verified or marked unverified |
|
|
14
|
+
| Public behavior change | README, public docs, changelog | docs mention current behavior |
|
|
15
|
+
| API or SDK behavior change | API docs, examples, tests | tests or documented reason |
|
|
16
|
+
| Runbook change | runbook path in `PROJECT_INDEX.md` | procedure still executable |
|
|
17
|
+
| Governance rule change | relevant pack/core, registry, README if public-facing | complexity budget checked |
|
|
18
|
+
| Closeout/startup contract change | `AGENTS.md`, `dev/SESSION_HANDOFF.md`, `dev/SESSION_LOG.md`, `dev/PROJECT_INDEX.md`, README quick usage | opening message schema + workspace identity present |
|
|
19
|
+
| Workspace identity change | `dev/SESSION_HANDOFF.md`, `dev/PROJECT_INDEX.md` | root/branch/commit/status recorded or marked unverified |
|
|
20
|
+
| Release | release notes, README version, changelog | release pack checklist |
|
|
21
|
+
|
|
22
|
+
## Registry Rule
|
|
23
|
+
|
|
24
|
+
If a change has no matching row, add a row before closeout or record why no durable sync rule is needed. At closeout, record sync status for every row touched by the session.
|
package/runtime-core/GEMINI.md
CHANGED
|
@@ -1,17 +1,17 @@
|
|
|
1
|
-
# Antigravity / Gemini Entry Bridge
|
|
2
|
-
|
|
3
|
-
This file is a bridge only. It exists for Google Antigravity CLI, Gemini CLI during migration, and compatible tools that still read `GEMINI.md`.
|
|
4
|
-
|
|
5
|
-
Authoritative operating rules remain in `AGENTS.md`.
|
|
6
|
-
|
|
7
|
-
Do not expand, summarize, replace, or "improve" this file during onboarding, setup, or project documentation work. Do not add command lists, architecture summaries, project state, or handoff notes here.
|
|
8
|
-
|
|
9
|
-
Antigravity CLI may read both `AGENTS.md` and `GEMINI.md` from the active workspace. If `AGENTS.md` has already been loaded, do not treat this bridge as a second rule source and do not repeat the same instructions.
|
|
10
|
-
|
|
11
|
-
At session startup:
|
|
12
|
-
|
|
13
|
-
1. Confirm the current root is the intended project root.
|
|
14
|
-
2. Read `AGENTS.md`.
|
|
15
|
-
3. Follow the startup read order in `AGENTS.md`.
|
|
16
|
-
|
|
17
|
-
If the current root does not match the intended project root, stop and ask the user to confirm the workspace before reading or editing project state.
|
|
1
|
+
# Antigravity / Gemini Entry Bridge
|
|
2
|
+
|
|
3
|
+
This file is a bridge only. It exists for Google Antigravity CLI, Gemini CLI during migration, and compatible tools that still read `GEMINI.md`.
|
|
4
|
+
|
|
5
|
+
Authoritative operating rules remain in `AGENTS.md`.
|
|
6
|
+
|
|
7
|
+
Do not expand, summarize, replace, or "improve" this file during onboarding, setup, or project documentation work. Do not add command lists, architecture summaries, project state, or handoff notes here.
|
|
8
|
+
|
|
9
|
+
Antigravity CLI may read both `AGENTS.md` and `GEMINI.md` from the active workspace. If `AGENTS.md` has already been loaded, do not treat this bridge as a second rule source and do not repeat the same instructions.
|
|
10
|
+
|
|
11
|
+
At session startup:
|
|
12
|
+
|
|
13
|
+
1. Confirm the current root is the intended project root.
|
|
14
|
+
2. Read `AGENTS.md`.
|
|
15
|
+
3. Follow the startup read order in `AGENTS.md`.
|
|
16
|
+
|
|
17
|
+
If the current root does not match the intended project root, stop and ask the user to confirm the workspace before reading or editing project state.
|
|
@@ -1,43 +1,43 @@
|
|
|
1
|
-
# Project Decisions Log
|
|
2
|
-
|
|
3
|
-
This file stores long-term project evolution, decisions, architecture trade-offs, and accumulated learning observations. It is a warm narrative layer. AI agents do not need to read this file at startup unless the current task asks for historical rationale or the closeout maintenance trigger says to update it.
|
|
4
|
-
|
|
5
|
-
Short single-task projects can leave this file nearly empty. Long-running projects use it
|
|
6
|
-
|
|
7
|
-
The user is not expected to maintain this file manually. The AI updates it during closeout when required, and may record major decisions when they happen.
|
|
8
|
-
|
|
9
|
-
Research-derived decisions use this compact evidence-chain format inside the relevant section, without creating a new section:
|
|
10
|
-
|
|
11
|
-
```text
|
|
12
|
-
- YYYY-MM-DD [research-derived] Decision summary. Evidence chain: Source=source:<id>; Summary=<source finding>; Inference=<reasoning>; Decision impact=<what changed>; Uncertainty=<limits or none>.
|
|
13
|
-
```
|
|
14
|
-
|
|
15
|
-
The `source:<id>` token must also appear in `dev/PROJECT_INDEX.md` under `Fact Base` or `External Sources`, so later sessions can trace the decision back to its source map.
|
|
16
|
-
|
|
17
|
-
This file does not store raw build / upload / QC evidence, current next actions, one-time task results, or reusable operating procedures. Keep those in `dev/SESSION_LOG.md`, `dev/SESSION_HANDOFF.md`, or the relevant rule pack / registered reference.
|
|
18
|
-
|
|
19
|
-
---
|
|
20
|
-
|
|
21
|
-
## Evolution Timeline
|
|
22
|
-
|
|
23
|
-
Long-term narrative of task or product evolution. Newest first. Append when the AI observes substantive task evolution.
|
|
24
|
-
|
|
25
|
-
(empty)
|
|
26
|
-
|
|
27
|
-
## Decisions Archive
|
|
28
|
-
|
|
29
|
-
Older decision entries
|
|
30
|
-
|
|
31
|
-
(empty)
|
|
32
|
-
|
|
33
|
-
## Architecture Choices
|
|
34
|
-
|
|
35
|
-
Major architecture choices and rationale. Append when planning involves a multi-option trade-off and the selected path has been confirmed.
|
|
36
|
-
|
|
37
|
-
(empty)
|
|
38
|
-
|
|
39
|
-
## Insights & Learnings
|
|
40
|
-
|
|
41
|
-
Accumulated lessons, reflections, and cross-session patterns. Append when the AI observes a recurring pattern across sessions.
|
|
42
|
-
|
|
43
|
-
(empty)
|
|
1
|
+
# Project Decisions Log
|
|
2
|
+
|
|
3
|
+
This file stores long-term project evolution, decisions, architecture trade-offs, and accumulated learning observations. It is a warm narrative layer. AI agents do not need to read this file at startup unless the current task asks for historical rationale or the closeout maintenance trigger says to update it.
|
|
4
|
+
|
|
5
|
+
Short single-task projects can leave this file nearly empty. Long-running projects use it for substantive task evolution, a multi-option architectural choice with rationale, or cross-session learning. Closeout count thresholds are maintenance advisories, not a reason to invent a decision entry or sweep unknown historical material. When the user asks why earlier choices were made, this file is the first long-term narrative reference.
|
|
6
|
+
|
|
7
|
+
The user is not expected to maintain this file manually. The AI updates it during closeout when required, and may record major decisions when they happen.
|
|
8
|
+
|
|
9
|
+
Research-derived decisions use this compact evidence-chain format inside the relevant section, without creating a new section:
|
|
10
|
+
|
|
11
|
+
```text
|
|
12
|
+
- YYYY-MM-DD [research-derived] Decision summary. Evidence chain: Source=source:<id>; Summary=<source finding>; Inference=<reasoning>; Decision impact=<what changed>; Uncertainty=<limits or none>.
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
The `source:<id>` token must also appear in `dev/PROJECT_INDEX.md` under `Fact Base` or `External Sources`, so later sessions can trace the decision back to its source map.
|
|
16
|
+
|
|
17
|
+
This file does not store raw build / upload / QC evidence, current next actions, one-time task results, or reusable operating procedures. Keep those in `dev/SESSION_LOG.md`, `dev/SESSION_HANDOFF.md`, or the relevant rule pack / registered reference.
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## Evolution Timeline
|
|
22
|
+
|
|
23
|
+
Long-term narrative of task or product evolution. Newest first. Append when the AI observes substantive task evolution.
|
|
24
|
+
|
|
25
|
+
(empty)
|
|
26
|
+
|
|
27
|
+
## Decisions Archive
|
|
28
|
+
|
|
29
|
+
Older decision entries may move from `SESSION_HANDOFF.md` only when `dev/rules/closeout.md` identifies an actual preservation, continuation, semantic, or project-specific need. A threshold advisory alone does not force splitting or sweeping unknown material. Newest first.
|
|
30
|
+
|
|
31
|
+
(empty)
|
|
32
|
+
|
|
33
|
+
## Architecture Choices
|
|
34
|
+
|
|
35
|
+
Major architecture choices and rationale. Append when planning involves a multi-option trade-off and the selected path has been confirmed.
|
|
36
|
+
|
|
37
|
+
(empty)
|
|
38
|
+
|
|
39
|
+
## Insights & Learnings
|
|
40
|
+
|
|
41
|
+
Accumulated lessons, reflections, and cross-session patterns. Append when the AI observes a recurring pattern across sessions.
|
|
42
|
+
|
|
43
|
+
(empty)
|
|
@@ -1,19 +1,19 @@
|
|
|
1
1
|
# Project Index
|
|
2
2
|
|
|
3
|
-
Purpose: give a stateless AI a compact map of the project before it reads or edits files.
|
|
4
|
-
|
|
5
|
-
## Project
|
|
6
|
-
|
|
7
|
-
- Name: TBD
|
|
8
|
-
- Goal: TBD
|
|
9
|
-
|
|
10
|
-
Use the actual project name and one plain-language project-wide outcome, not the current task's goal. Optional `Name zh-Hant` and `Goal zh-Hant` fields provide a short Traditional Chinese display counterpart. Maintain these here only when the project's identity or outcome changes; the dashboard reads them without generating another report.
|
|
3
|
+
Purpose: give a stateless AI a compact map of the project before it reads or edits files.
|
|
4
|
+
|
|
5
|
+
## Project
|
|
6
|
+
|
|
7
|
+
- Name: TBD
|
|
8
|
+
- Goal: TBD
|
|
9
|
+
|
|
10
|
+
Use the actual project name and one plain-language project-wide outcome, not the current task's goal. Optional `Name zh-Hant` and `Goal zh-Hant` fields provide a short Traditional Chinese display counterpart. Maintain these here only when the project's identity or outcome changes; the dashboard reads them without generating another report.
|
|
11
11
|
|
|
12
12
|
## Stack
|
|
13
13
|
|
|
14
14
|
| Field | Value | Last verified |
|
|
15
15
|
|---|---|---|
|
|
16
|
-
| Agent Handoff Kit template version | 0.3.64 | current template version |
|
|
16
|
+
| Agent Handoff Kit template version | 0.3.64 | current template version |
|
|
17
17
|
| Runtime | TBD | TBD |
|
|
18
18
|
| Framework | TBD | TBD |
|
|
19
19
|
| Package manager | TBD | TBD |
|
|
@@ -46,7 +46,7 @@ Use the actual project name and one plain-language project-wide outcome, not the
|
|
|
46
46
|
| Test suite | TBD | TBD |
|
|
47
47
|
| Runbook | TBD | TBD |
|
|
48
48
|
| Public docs | TBD | TBD |
|
|
49
|
-
| Durable artifact review | `dev/PROJECT_INDEX.md` + `dev/DOC_SYNC_REGISTRY.md` | After creating docs, generated outputs, specs, runbooks, checklists, research notes, or other durable artifacts, classify each file as indexed / synced / temporary / one-time evidence before completion; doctor validates explicit Kit contracts and formal typed user-rule paths only, not arbitrary project artifacts |
|
|
49
|
+
| Durable artifact review | `dev/PROJECT_INDEX.md` + `dev/DOC_SYNC_REGISTRY.md` | After creating docs, generated outputs, specs, runbooks, checklists, research notes, or other durable artifacts, classify each file as indexed / synced / temporary / one-time evidence before completion; doctor validates explicit Kit contracts and formal typed user-rule paths only, not arbitrary project artifacts |
|
|
50
50
|
|
|
51
51
|
## Fact Base
|
|
52
52
|
|
|
@@ -119,14 +119,14 @@ Do not store credential values or machine-private paths here. Local machine-only
|
|
|
119
119
|
## Local QC Commands
|
|
120
120
|
|
|
121
121
|
| Check | Command | Run before | Last verified |
|
|
122
|
-
|---|---|---|---|
|
|
123
|
-
| Agent Handoff Kit doctor | `npx --yes @adamchanadam/agent-handoff-kit@latest doctor --root .` | closeout / Kit contract health / explicit registered-path checks | package latest |
|
|
124
|
-
| Agent Handoff Kit workspace health | `npx --yes @adamchanadam/agent-handoff-kit@latest workspace-health --root .` | closeout workspace identity read-back / suspected wrong root or worktree drift | package latest |
|
|
125
|
-
| Project governance check | Check newly created durable artifacts against `dev/PROJECT_INDEX.md` and `dev/DOC_SYNC_REGISTRY.md`; register, sync, consolidate, or explicitly classify as temporary / one-time evidence. This is an AI responsibility, not a root-discovery doctor scan. | closeout / durable file changes | unverified until project-specific command exists |
|
|
122
|
+
|---|---|---|---|
|
|
123
|
+
| Agent Handoff Kit doctor | `npx --yes @adamchanadam/agent-handoff-kit@latest doctor --root .` | closeout / Kit contract health / explicit registered-path checks | package latest |
|
|
124
|
+
| Agent Handoff Kit workspace health | `npx --yes @adamchanadam/agent-handoff-kit@latest workspace-health --root .` | closeout workspace identity read-back / suspected wrong root or worktree drift | package latest |
|
|
125
|
+
| Project governance check | Check newly created durable artifacts against `dev/PROJECT_INDEX.md` and `dev/DOC_SYNC_REGISTRY.md`; register, sync, consolidate, or explicitly classify as temporary / one-time evidence. This is an AI responsibility, not a root-discovery doctor scan. | closeout / durable file changes | unverified until project-specific command exists |
|
|
126
126
|
|
|
127
127
|
## Workspace Identity
|
|
128
128
|
|
|
129
|
-
Record the last closeout snapshot here so the next AI can detect wrong-root or workspace drift. Live root / Git / worktree truth is read with `agent-handoff-kit workspace-health --root <project root>` or equivalent read-only Git probes; do not maintain a long-term dynamic worktree list here.
|
|
129
|
+
Record the last closeout snapshot here so the next AI can detect wrong-root or workspace drift. Live root / Git / worktree truth is read with `agent-handoff-kit workspace-health --root <project root>` or equivalent read-only Git probes; do not maintain a long-term dynamic worktree list here.
|
|
130
130
|
|
|
131
131
|
| Field | Value | Last verified |
|
|
132
132
|
|---|---|---|
|
|
@@ -144,7 +144,7 @@ Record the last closeout snapshot here so the next AI can detect wrong-root or w
|
|
|
144
144
|
| UI behavior | TBD | build + visual/manual check |
|
|
145
145
|
| Data model | TBD | migration/checks |
|
|
146
146
|
| Governance behavior | `AGENTS.md`, `dev/*` | doc sync registry |
|
|
147
|
-
| Durable artifacts | docs, generated outputs, project-specific reference folders, specs, runbooks, checklists, research notes | classify as indexed / synced / temporary / one-time evidence when created or modified by the AI; update `dev/PROJECT_INDEX.md` or `dev/DOC_SYNC_REGISTRY.md` when durable |
|
|
147
|
+
| Durable artifacts | docs, generated outputs, project-specific reference folders, specs, runbooks, checklists, research notes | classify as indexed / synced / temporary / one-time evidence when created or modified by the AI; update `dev/PROJECT_INDEX.md` or `dev/DOC_SYNC_REGISTRY.md` when durable |
|
|
148
148
|
| Closeout/startup contract | `AGENTS.md`, `dev/rules/closeout.md`, `START_NEXT_SESSION_PROMPT.txt`, `dev/SESSION_HANDOFF.md`, `dev/SESSION_LOG.md`, `dev/PROJECT_INDEX.md` | hot-path reads stay minimal; lifecycle state agrees; log has no full prompt; prompt mirror regenerated from handoff at closeout |
|
|
149
149
|
|
|
150
150
|
## External Services
|
|
@@ -5,7 +5,7 @@ Read only the packs needed for the current task.
|
|
|
5
5
|
| Task signal | Pack | Purpose |
|
|
6
6
|
|---|---|---|
|
|
7
7
|
| Clear end-of-session or handoff intent: "收工" / "wrap up" / "closeout" / "handoff" / "Wrap up Agent Handoff", including closeout plus a handoff instruction | `dev/rules/closeout.md` | <!-- ack:route:closeout --> full closeout, lifecycle reconciliation, maintenance triggers, prompt regeneration, read-back, and honest stop conditions |
|
|
8
|
-
| Explicit onboarding requests: "I'm new" / "new user" / "teach me" / "help me start" / "how do I start" / "show me how" / "getting started" / "what can agent handoff kit do"; or genuinely unresolved intent after current state has been read. Also recognize equivalent Chinese phrases such as "新手", "教我用", "點開始", and "能力". A fresh install with `First-use guidance state: eligible` enters onboarding when no executable objective remains; upgrade never resets consumed / not_applicable first-use state. `Start Agent Handoff` / "開工" is continuity. Capability / teaching answers must surface normal-language public command categories instead of reducing the help answer to CLI maintenance commands. | `dev/rules/onboarding.md` | <!-- ack:route:onboarding --> infer when sufficient and begin a concrete task directly; ask one concise question or offer guided scenarios only when the user requests guidance or first-use state is eligible with no executable objective |
|
|
8
|
+
| Explicit onboarding requests: "I'm new" / "new user" / "teach me" / "help me start" / "how do I start" / "show me how" / "getting started" / "what can agent handoff kit do"; or genuinely unresolved intent after current state has been read. Also recognize equivalent Chinese phrases such as "新手", "教我用", "點開始", and "能力". A fresh install with `First-use guidance state: eligible` enters onboarding when no executable objective remains; upgrade never resets consumed / not_applicable first-use state. `Start Agent Handoff` / "開工" is continuity. Capability / teaching answers must surface normal-language public command categories instead of reducing the help answer to CLI maintenance commands. | `dev/rules/onboarding.md` | <!-- ack:route:onboarding --> infer when sufficient and begin a concrete task directly; ask one concise question or offer guided scenarios only when the user requests guidance or first-use state is eligible with no executable objective |
|
|
9
9
|
| Destructive file operations, shell writes, Git state changes, package managers, installers, deploy, release, cloud tools, external APIs, credentials, locked files, permission errors | `dev/rules/safety.md` | safety checks for data loss, external systems, secrets, and high-risk operations |
|
|
10
10
|
| Code, tests, build, package manager, SDK, CLI, API | `dev/rules/coding.md` | development workflow and verification |
|
|
11
11
|
| Draft, edit, style, publication content | `dev/rules/writing.md` | writing workflow and tone control |
|