Skip to content

chore(agents): sync portable agent core v8f7a8070 #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdardash merged 1 commit into from
Aug 17, 2026
Merged

chore(agents): sync portable agent core v8f7a8070 #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion .cursor/rules/agent-core.mdc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ description: Portable agent operating rules
alwaysApply: true
---

<!-- BEGIN AGENT CORE vbc556c4e (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
<!-- BEGIN AGENT CORE v8f7a8070 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
# Agent Core (portable operating rules)

Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
Expand All @@ -19,6 +19,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
- Keep answers short. Lead with what changed and the result.
- Always cite `file:line` when explaining code.
- 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.
- 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

Expand Down
5 changes: 4 additions & 1 deletion .gemini/styleguide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<!-- BEGIN AGENT CORE vbc556c4e (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
<!-- BEGIN AGENT CORE v8f7a8070 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
# Agent Core (portable operating rules)

Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
Expand All @@ -19,6 +19,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
- Keep answers short. Lead with what changed and the result.
- Always cite `file:line` when explaining code.
- 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.
- 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

Expand Down
5 changes: 4 additions & 1 deletion .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

> Generated mirror of the portable agent core. See AGENTS.md.

<!-- BEGIN AGENT CORE vbc556c4e (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
<!-- BEGIN AGENT CORE v8f7a8070 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
# Agent Core (portable operating rules)

Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
Expand All @@ -18,6 +18,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
- Keep answers short. Lead with what changed and the result.
- Always cite `file:line` when explaining code.
- 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.
- 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

Expand Down
5 changes: 4 additions & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
> Cross-tool agent contract for this repo. Spec: <https://agents.md/>
> Project-specific rules go ABOVE the managed block and override it.

<!-- BEGIN AGENT CORE vbc556c4e (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
<!-- BEGIN AGENT CORE v8f7a8070 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
# Agent Core (portable operating rules)

Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
Expand All @@ -19,6 +19,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
- Keep answers short. Lead with what changed and the result.
- Always cite `file:line` when explaining code.
- 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.
- 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

Expand Down
5 changes: 4 additions & 1 deletion GEMINI.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

> Generated mirror of the portable agent core. See AGENTS.md.

<!-- BEGIN AGENT CORE vbc556c4e (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
<!-- BEGIN AGENT CORE v8f7a8070 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
# Agent Core (portable operating rules)

Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
Expand All @@ -18,6 +18,9 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
- Keep answers short. Lead with what changed and the result.
- Always cite `file:line` when explaining code.
- 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.
- 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

Expand Down
Loading