AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 27, 2026, 01:00 JST

development-standards: one shared repo for AI agent rules

Send on LINE
development-standards: one shared repo for AI agent rules

3 Key Points

  1. What happened

    A developer consolidated AI coding rules into a shared repository named development-standards, split into instructions for agents (read via AGENTS.md) and settings for VS Code's generate button, and copies them into projects like my-project with a Node.js script.

  2. Why it matters

    Rule text lives in one place instead of copies, so a fix made once can be pulled into other projects and the latest version is always clear — the sync script writes, but commits and pull requests are left to the developer.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The setup draws a line between two ways instructions reach an AI: work delegated to an agent like Codex, and the generate button in VS Code. Those use different entry points, but both point back to the same source text — PR creation, for example, uses the same pull-request.instructions.md whether an agent or the button is asking.

The repository layout reflects that split. AGENTS.md is kept as a reference list rather than a place to write rule text, and .github/copilot-instructions.md only tells the reader to read AGENTS.md instead of duplicating the list. Rule bodies live under docs/rules/, while form structure sits in Issue forms and PR templates and writing style in the generate-button files.

Syncing is deliberate rather than automatic. The script is run first without --write to preview, then with --write to apply, and finally re-run to confirm zero additions, updates, or deletions. Some files are overwritten wholesale, while AGENTS.md and the Copilot guidance are updated only inside management markers, and VS Code settings are partially updated with Microsoft's jsonc-parser so project-specific keys survive. The stated aim is to return judgments from real work back into the source over time, so the same standards carry across projects and even across different agents.

FAQ
What is the difference between agent instructions and generate-button settings?
Agent instructions (branch names, comments, Issue/PR operations, releases) are read through AGENTS.md. Generate-button settings (commit messages, PR titles and bodies) are specified as files from VS Code's settings.json.
What do I need to run the sync script?
Node.js 22 or later and Git, with the two repositories placed in the same parent folder. Dependencies are installed in the shared repository with npm ci.
Does the script commit or open pull requests?
No. The script does not commit, push, or create PRs; you review the diff in the target project and open a PR there when you want the rules to persist.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOracle launches 25 Claw-powered Agentic Applications