project-init 0.3.0__py3-none-any.whl

project_init/templates/base/LICENSE.tmpl

@@ -0,0 +1,231 @@
+{{#if license_mit}}MIT License
+
+Copyright (c) {{created_year}} {{license_holder}}
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+{{/if license_mit}}{{#if license_apache}}                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We recommend that a file or
+      class name and description of purpose be included on the same
+      "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {{created_year}} {{license_holder}}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+{{/if license_apache}}{{#if license_proprietary}}Copyright (c) {{created_year}} {{license_holder}}. All rights reserved.
+
+This software and its documentation are proprietary and confidential.
+Internal use only: no part of this repository may be copied, modified,
+distributed, sublicensed, or disclosed outside the organization without
+prior written permission from the copyright holder.
+
+Provided "AS IS", without warranty of any kind.
+{{/if license_proprietary}}

project_init/templates/base/SECURITY.md.tmpl

@@ -0,0 +1,26 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+Please do **not** open a public issue for security problems.
+
+- Preferred: use GitHub's private vulnerability reporting on this
+  repository (Security tab → "Report a vulnerability").
+{{#if project_owner}}
+- Or contact the maintainer directly: {{project_owner}}
+{{/if project_owner}}
+You should receive an acknowledgement within a few business days. Please
+include reproduction steps and the affected version or commit.
+
+## Supported versions
+
+| Version | Supported |
+|---|---|
+| latest release / `main` | ✅ |
+| older releases | ❌ |
+
+## Scope notes
+
+Secrets must never be committed — the scaffolded pre-commit hook runs a
+gitleaks scan, and CI re-checks. If you find a leaked credential in the
+history, report it privately first so it can be rotated before disclosure.

project_init/templates/base/docs/explanation/index.md

@@ -0,0 +1,9 @@
+# Explanation
+
+Understanding-oriented discussion: why the system is shaped the way it is,
+trade-offs considered, context that doesn't fit a recipe or a reference
+table. Architectural decisions belong in `.claude/docs/adr/` — link them
+from here when they need narrative.
+
+*No explanation pages yet. Add the first one as
+`docs/explanation/<topic>.md` and link it here.*

project_init/templates/base/docs/how-to/index.md

@@ -0,0 +1,7 @@
+# How-to guides
+
+Goal-oriented recipes for someone already working with the project: "How do
+I X?" Each guide solves one real problem, assumes basic familiarity, and
+skips teaching.
+
+*No guides yet. Add the first one as `docs/how-to/<task>.md` and link it here.*

project_init/templates/base/docs/index.md.tmpl

@@ -0,0 +1,20 @@
+# {{project_name}}
+
+{{project_description}}
+
+This documentation follows the [Diátaxis](https://diataxis.fr/) structure —
+put each page where its *purpose* fits, not where its topic fits:
+
+| Section | Purpose | Reader is… |
+|---|---|---|
+| [Tutorials](tutorials/index.md) | Learning by doing | new, following along |
+| [How-to guides](how-to/index.md) | Solving a specific problem | working, goal in hand |
+| [Reference](reference/index.md) | Looking up facts (API, config) | working, needs precision |
+| [Explanation](explanation/index.md) | Understanding why | studying, wants context |
+
+Architectural decisions live in `.claude/docs/adr/` in the repository (not
+part of this site) — use the `add_adr` skill to record one.
+
+> Tip (public repos): [DeepWiki](https://deepwiki.com/) generates free,
+> always-current architecture docs from the repository — link
+> `deepwiki.com/<owner>/<repo>` from your README.

project_init/templates/base/docs/reference/index.md

@@ -0,0 +1,13 @@
+# Reference
+
+Information-oriented technical description: API signatures, configuration
+keys, CLI flags. Reference states facts — it does not explain or instruct.
+
+For Python projects, render API docs from docstrings with a
+[mkdocstrings](https://mkdocstrings.github.io/) directive:
+
+```markdown
+::: your_package.your_module
+```
+
+*Add reference pages as `docs/reference/<area>.md` and link them here.*

project_init/templates/base/docs/tutorials/index.md

@@ -0,0 +1,7 @@
+# Tutorials
+
+Learning-oriented, step-by-step lessons. A tutorial takes a newcomer from
+zero to a working result — it teaches by doing, not by explaining.
+
+*No tutorials yet. Add the first one as `docs/tutorials/<topic>.md` and link
+it here.*

project_init/templates/base/dot_claude/agents/README.md

@@ -0,0 +1,30 @@
+# `.claude/agents/`
+
+Claude Code subagent definitions. Define custom subagent personas here when you need specialized agents for repeatable tasks (e.g., a code reviewer, a documentation specialist, a performance analyzer).
+
+## How to create a subagent
+
+1. Create a `.md` file with a frontmatter block:
+
+```yaml
+---
+name: agent-name
+description: What this agent does and when to invoke it
+model: sonnet                    # optional: sonnet or opus
+tools:                           # list of tools this agent can use
+  - Read
+  - Grep
+  - Bash
+maxTurns: 15                     # optional: max conversation depth
+---
+
+<Detailed instructions for the agent's behavior, role, and approach>
+```
+
+2. Name the file after the agent (e.g., `reviewer.md` for a `reviewer` agent)
+
+3. Invoke the agent in skills or from the CLI using `Agent({"description": "...", "subagent_type": "agent-name", "prompt": "..."})`
+
+## Reference
+
+See the [Claude Code subagents documentation](https://docs.claude.com/en/docs/claude-code/sub-agents) for full details on agent capabilities, tool access, and context management.

project_init/templates/base/dot_claude/config.yaml.tmpl

@@ -0,0 +1,31 @@
+# project-init: record of choices made at init time.
+# Safe to hand-edit; re-running `project-init` will reconcile with this file.
+
+project:
+  name: "{{project_name}}"
+  description: "{{project_description}}"
+  created: {{created_date}}
+  project_init_version: {{project_init_version}}
+  project_key: ""          # e.g. "PI" → branches use feat/PI-42-slug, PR titles use feat(PI-42):
+  github_project_number: 1 # numeric GitHub Project V2 board number (used by board-automation.yml and create_issue.sh)
+
+language: {{language}}            # python | node | go | none
+
+memory:
+  stack: {{memory_stack}}         # obsidian-only | obsidian-graphify
+  vault_path: .claude/vault
+  memory_path: .claude/memory
+
+mcps:
+  installed: {{installed_mcps_yaml}}
+
+safety:
+  # prod_guard escape hatch: JSON list of regex patterns for commands the
+  # destructive-operation guard should never flag (e.g. a dev-cluster
+  # kubectl context). Keep it narrow.
+  allow: []
+
+tooling:
+  lint_command: "{{lint_command}}"
+  format_command: "{{format_command}}"
+  test_command: "{{test_command}}"

project_init/templates/base/dot_claude/docs/README.md

@@ -0,0 +1,26 @@
+# .claude/docs — Internal Knowledge Base
+
+This folder is the **system of record** for architectural decisions and development standards. It is version-controlled alongside code and is the primary source of context for AI agents.
+
+## Structure
+
+```
+docs/
+├── adr/           # Architecture Decision Records — why decisions were made
+├── development/   # Standards, conventions, testing strategy
+└── guides/        # How-to guides for common workflows
+```
+
+## How to use
+
+**Agents:** Read `adr/` before starting tasks. If you establish a new pattern or make a non-obvious decision, write a brief ADR.
+
+**Humans:** When an exploratory note in `.claude/vault/` solidifies into a real decision, move it here as an ADR and commit it.
+
+## One-way flow
+
+```
+vault/knowledge/ (exploratory)  →  docs/adr/ (permanent)
+```
+
+Never duplicate content. If it's in `docs/adr/`, don't repeat it in `vault/decisions/`.

project_init/templates/base/dot_claude/docs/adr/adr-001-memory-stack.md.tmpl

@@ -0,0 +1,22 @@
+# ADR-001: Memory Stack
+
+**Date:** {{created_date}}
+**Status:** Accepted
+
+## Context
+
+{{project_name}} needs a memory system for AI agents to retain context across sessions.
+
+## Decision
+
+- **`.claude/vault/`** (Obsidian) — human-authored notes, session logs, exploratory content
+- **`.claude/memory/`** — flat markdown facts for quick agent recall
+{{#if graphify}}- **`graphify-out/`** (Graphify) — queryable code knowledge graph, rebuilt per commit; agents query it before grepping
+{{/if graphify}}
+Obsidian provides a local app for humans; agents read markdown files directly.
+
+## Consequences
+
+- Session logs written to `vault/sessions/YYYY-MM-DD.md` by the `/session_summary` skill
+- Memory facts indexed in `memory/MEMORY.md` with per-file frontmatter
+- AI agents read `memory/MEMORY.md` at session start, then `docs/adr/` for decisions

project_init/templates/base/dot_claude/docs/adr/adr-002-mcp-choices.md.tmpl

@@ -0,0 +1,32 @@
+# ADR-002: MCP Choices
+
+**Date:** {{created_date}}
+**Status:** Accepted
+
+## Context
+
+Model Context Protocol (MCP) servers extend Claude Code's toolset. Each server loads its full tool-definition set into the conversation on startup — even tools never used. This adds token overhead proportional to the number of tools.
+
+## Decision
+
+Three MCPs are intentionally absent to reduce token overhead:
+
+| MCP | Tokens saved | Replacement |
+|---|---|---|
+| GitHub MCP (~35 tools) | ~2000 tokens | `gh` CLI built-in |
+| Linear MCP (~15 tools) | ~800 tokens | `gh` CLI + GitHub Issues |
+| Filesystem MCP (~10 tools) | ~500 tokens | Claude Code built-in Read/Write/Edit/Glob/Grep |
+
+**Selected at init:** {{installed_mcps}}
+
+Retained MCPs:
+- **Context7** — targeted library doc lookups; no CLI equivalent
+- **Playwright** — browser automation; no CLI equivalent
+- **Postgres / SQLite** — direct DB access; no CLI equivalent
+
+## Consequences
+
+- Agents use `gh issue list`, `gh pr create`, etc. for project management
+- File ops use Claude Code built-ins — no MCP config needed
+- Token budget stays ~3300 tokens lower per session; more context for actual work
+- `MCP_CATALOG` in project-init contains only context7 (and optional DB/browser)

project_init/templates/base/dot_claude/docs/adr/adr-template.md

@@ -0,0 +1,29 @@
+# ADR-NNN: {short title: the problem and the chosen solution}
+
+<!-- MADR-style template (https://adr.github.io/madr/). Copy to
+     adr-NNN-<kebab-slug>.md with the next free number — the add_adr skill
+     does this for you. Delete comments before committing. -->
+
+- Status: proposed <!-- proposed | accepted | rejected | deprecated | superseded by ADR-XXX -->
+- Date: YYYY-MM-DD
+
+## Context and Problem Statement
+
+<!-- 2-5 sentences: what forces this decision? What breaks or stalls if it
+     is not made? Phrase the problem as a question when possible. -->
+
+## Considered Options
+
+- Option 1
+- Option 2
+- Option 3
+
+## Decision Outcome
+
+Chosen option: "Option 1", because <!-- justification: meets criterion X,
+resolves the problem, fewest downsides -->.
+
+### Consequences
+
+- Good: <!-- what becomes easier -->
+- Bad: <!-- what becomes harder; accepted trade-offs -->

project_init/templates/base/dot_claude/docs/development/conventions.md.tmpl

@@ -0,0 +1,31 @@
+# Development Conventions
+
+## Code style
+
+{{#if python}}
+- Lint/format/test via `just` recipes — `just --list` shows them; linter is `ruff`
+- Docstrings required on public functions (Google style — enforced by the ruff `D` rules in `ruff.toml`, with complexity caps)
+- No type annotations required unless they clarify non-obvious interfaces
+{{/if}}
+{{#if node}}
+- Lint/format/test via `just` recipes — `just --list` shows them; linter is ESLint (`eslint.config.mjs`, jsdoc/tsdoc + complexity gates)
+- TypeScript preferred for non-trivial modules
+{{/if}}
+
+## Commit messages
+
+Format: `type(PROJECT-123): short description` or `type: short description` (no linked issue)
+
+Types: `feat`, `fix`, `test`, `docs`, `chore`
+
+Example: `feat(PI-42): Add OAuth login`
+
+## Pull requests
+
+- Title: `type(PROJECT-123): Short description`
+- Body must include `Closes #<number>` for auto-close on merge
+- All tests must pass before merging
+
+## Comments
+
+Only comment when the **why** is non-obvious — a hidden constraint, a workaround for a specific bug, or a counter-intuitive decision. Never describe what the code does.

project_init/templates/base/dot_claude/docs/development/testing.md

@@ -0,0 +1,25 @@
+# Testing Strategy
+
+## Principles
+
+- **Test-driven** — write failing tests before implementation. Tests define the contract.
+- **No mocks for external systems** — integration tests hit real instances (DB, APIs). Mocks mask divergence between test and production.
+- **One assertion per test** — narrow tests pinpoint failures immediately.
+- **Name tests descriptively** — `test_<unit>_<scenario>` (e.g. `test_auth_rejects_expired_token`)
+
+## Test boundaries
+
+| What to test | How |
+|---|---|
+| Business logic | Unit tests, no I/O |
+| DB queries | Integration tests against real DB |
+| External APIs | Integration tests or contract tests |
+| UI behaviour | E2E tests (Playwright if configured) |
+
+## Running tests
+
+See `.claude/project-init.md` for the test command for this project's language/runtime.
+
+## Coverage
+
+Coverage is a signal, not a target. Aim for high coverage of critical paths; don't write tests just to hit a number.

project_init/templates/base/dot_claude/docs/guides/developer-onboarding.md

@@ -0,0 +1,110 @@
+# Developer onboarding — personal machine setup
+
+This page covers **per-developer machine state** that the scaffolder
+deliberately does not manage: global git configuration and editor sync are
+personal, not repository state, so they are documented here instead of being
+scaffolded (see the project-init decision in PI-140).
+
+Everything repo-level (linting, commands, env examples) ships with the
+repository. The one per-clone step: run `.claude/scripts/install_hooks.sh`
+once to activate the `pre-commit` (gitleaks secret scan), `commit-msg`,
+and `pre-push` git hooks — git does not enable repository hooks
+automatically. Install [gitleaks](https://github.com/gitleaks/gitleaks#installing)
+for fast local secret scanning; without it the pre-commit scan is skipped
+and CI catches leaks instead.
+
+## Dependency updates (Renovate)
+
+The repo ships a `renovate.json` (weekly grouped updates, GitHub Actions
+pinned by digest, lockfile maintenance — managers activate automatically
+from the files present). Renovate PRs arrive as `chore: Update …`, the
+canonical no-issue title format the PR validators accept. One per-org
+step: install the [Renovate GitHub App](https://github.com/apps/renovate)
+on the repository.
+
+To centralize policy across an organization, replace the `extends` list
+with a shared preset. Keep the PR-title settings unless the org preset
+provides them — Renovate's defaults (`chore(deps): …`) fail this repo's
+PR-title validator:
+
+```json
+{
+  "extends": ["github>your-org/renovate-config"],
+  "semanticCommits": "disabled",
+  "commitMessagePrefix": "chore:"
+}
+```
+
+## Global gitignore
+
+Keep OS and editor junk out of every repo you touch, without bloating each
+project's `.gitignore`:
+
+```bash
+git config --global core.excludesFile ~/.gitignore_global
+cat >> ~/.gitignore_global <<'EOF'
+.DS_Store
+Thumbs.db
+*.swp
+.idea/
+EOF
+```
+
+Project `.gitignore` files stay focused on project artifacts (build output,
+env files, caches) — never add personal editor noise to them.
+
+## Recommended global git config
+
+```bash
+git config --global init.defaultBranch main
+git config --global pull.rebase true          # no accidental merge commits on pull
+git config --global push.autoSetupRemote true # first push sets upstream
+git config --global fetch.prune true          # drop deleted remote branches
+```
+
+Identity (use your work email on work machines):
+
+```bash
+git config --global user.name  "Your Name"
+git config --global user.email "you@example.com"
+```
+
+## Commit signing (if your org requires it)
+
+```bash
+git config --global gpg.format ssh
+git config --global user.signingkey ~/.ssh/id_ed25519.pub
+git config --global commit.gpgsign true
+```
+
+## Editor settings
+
+- **VS Code Settings Sync** is an account-level feature — enable it in VS Code
+  itself (`Settings Sync: Turn On`). It is intentionally not configured by the
+  repository.
+- Repo-level editor settings (format-on-save, recommended extensions) live in
+  the repository's `.vscode/` directory when the project opted into that
+  overlay — personal themes and keybindings never belong there.
+
+## Checklist
+
+- [ ] Global gitignore configured
+- [ ] Global git config applied (rebase pulls, pruning, identity)
+- [ ] Commit signing set up, if required
+- [ ] Repo hooks installed: run `.claude/scripts/install_hooks.sh` once per clone
+- [ ] gitleaks installed for the local pre-commit secret scan
+
+## Multi-agent support tiers
+
+Only the Claude Code path is functionally CI-tested; treat other agents as
+best-effort. If the project was scaffolded with extra agents (`--agents`):
+
+| Agent | What you get | Setup per clone |
+|---|---|---|
+| Claude Code | full tier: hooks, skills, settings | none (plus `install_hooks.sh` like everyone) |
+| Codex | shared skills at `.agents/skills/`, command guard via `.codex/hooks.json` | none |
+| Gemini CLI | workflow /commands + command guard from the project extension | `.claude/scripts/setup_gemini.sh` |
+| Ollama-based (Aider, Goose, …) | AGENTS.md instructions, portable scripts, markdown memory | none |
+
+The git hooks and CI checks are the real enforcement boundary for every
+agent — agent-side hooks are fast-feedback guardrails only.