From 9f9fc7e9ae04ccae61b10b4320e07dbd5570e57f Mon Sep 17 00:00:00 2001 From: Joshua Dardashti Date: Tue, 1 Sep 2026 19:57:10 -0700 Subject: [PATCH] chore(agents): sync portable agent core vfbbb8f0b Generated from ~/.claude/portable/AGENT_CORE.md by sync_agent_context.py and published by publish_agent_context.py, so agents running on GitHub read the same operating rules as agents running locally: Claude Code (.claude/rules/agent-core.md), Codex and Aider (AGENTS.md), Copilot (.github/copilot-instructions.md), Gemini (GEMINI.md, .gemini/styleguide.md). Only the block between the AGENT CORE markers is generated. Anything outside it is untouched and overrides it. --- .claude/rules/agent-core.md | 3 ++- .cursor/rules/agent-core.mdc | 3 ++- .gemini/styleguide.md | 3 ++- .github/copilot-instructions.md | 3 ++- AGENTS.md | 3 ++- GEMINI.md | 3 ++- 6 files changed, 12 insertions(+), 6 deletions(-) diff --git a/.claude/rules/agent-core.md b/.claude/rules/agent-core.md index 4aaff6d..d333eb1 100644 --- a/.claude/rules/agent-core.md +++ b/.claude/rules/agent-core.md @@ -4,7 +4,7 @@ > portable core reaches Claude -- locally, in subagents, and in GitHub-hosted runs. > Generated from ~/.claude/portable/AGENT_CORE.md. Edit there, not here. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -22,6 +22,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body. - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/.cursor/rules/agent-core.mdc b/.cursor/rules/agent-core.mdc index 2cbc854..549628c 100644 --- a/.cursor/rules/agent-core.mdc +++ b/.cursor/rules/agent-core.mdc @@ -3,7 +3,7 @@ description: Portable agent operating rules alwaysApply: true --- - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -21,6 +21,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body. - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/.gemini/styleguide.md b/.gemini/styleguide.md index 8807bd0..ccd7d0c 100644 --- a/.gemini/styleguide.md +++ b/.gemini/styleguide.md @@ -3,7 +3,7 @@ > Read by the Gemini Code Assist GitHub app when it reviews pull requests. > Generated mirror of the portable agent core. See AGENTS.md. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -21,6 +21,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body. - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md index f2e39df..452613d 100644 --- a/.github/copilot-instructions.md +++ b/.github/copilot-instructions.md @@ -2,7 +2,7 @@ > Generated mirror of the portable agent core. See AGENTS.md. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -20,6 +20,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body. - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/AGENTS.md b/AGENTS.md index 29b08bd..e88dce0 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -3,7 +3,7 @@ > Cross-tool agent contract for this repo. Spec: > Project-specific rules go ABOVE the managed block and override it. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -21,6 +21,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body. - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer diff --git a/GEMINI.md b/GEMINI.md index 933da3f..2795942 100644 --- a/GEMINI.md +++ b/GEMINI.md @@ -2,7 +2,7 @@ > Generated mirror of the portable agent core. See AGENTS.md. - + # Agent Core (portable operating rules) Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code, @@ -20,6 +20,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`. - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks. - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence. - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims. +- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body. - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it. ## 2. Concurrency: you are never the only writer