project-init 0.3.0__py3-none-any.whl

project_init/templates/base/dot_claude/settings.json.tmpl

@@ -0,0 +1,83 @@
+{
+  "$schema": "https://json.schemastore.org/claude-code-settings.json",
+  "env": {
+    "CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "70"
+  },
+  "extraKnownMarketplaces": {
+    "claude-plugins-official": {
+      "source": {
+        "source": "github",
+        "repo": "anthropics/claude-plugins-official"
+      }
+    },
+    "project-init": {
+      "source": {
+        "source": "github",
+        "repo": "{{project_init_repo}}"
+      }
+    }
+  },
+  "enabledPlugins": {
+    "security-guidance@claude-plugins-official": true,
+    "pr-review-toolkit@claude-plugins-official": true{{#if plugin_mode}},
+    "project-init-workflow@project-init": true{{/if plugin_mode}}
+  }{{#if no_plugin}},
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/session_setup.sh",
+            "timeout": 300
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Bash",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/pre_commit_gate.sh",
+            "timeout": 60
+          },
+          {
+            "type": "command",
+            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/github_command_guard.sh",
+            "timeout": 10
+          },
+          {
+            "type": "command",
+            "command": "python3 \"$CLAUDE_PROJECT_DIR\"/.claude/hooks/prod_guard.py",
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/post_edit_lint.sh",
+            "timeout": 30
+          }
+        ]
+      }
+    ],
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/workflow_state_reminder.sh",
+            "timeout": 10
+          }
+        ]
+      }
+    ]
+  }{{/if no_plugin}}
+}

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

@@ -0,0 +1,12 @@
+# `.claude/skills/`
+
+Project-local Claude Code skills. Each skill is a directory `.claude/skills/<name>/SKILL.md`.
+
+| Skill | When to use |
+|---|---|
+| `session_summary` | End of session — summarize work and save to vault |
+| `start_task` | Before any non-trivial task — create a GitHub Issue |
+| `add_hook` | When you need a new deterministic hook (safety, lint, logging) |
+| `add_command` | When you need a new slash command for a recurring workflow |
+
+User-level skills (across all projects) live in `~/.claude/skills/`.

project_init/templates/base/dot_claude/skills/plan/SKILL.md.tmpl

@@ -0,0 +1,40 @@
+---
+name: plan
+description: TDD-style planning — understand requirements, write tests first, then implement with numbered steps
+when_to_use: Use for non-trivial features or bug fixes. Plan before code to reduce rework and improve test coverage.
+allowed-tools: Read Grep Glob Bash
+---
+
+Plan this work in 5 phases. Format output clearly so it's actionable.
+
+## Phase 1 — Understand the requirement
+
+Ask clarifying questions if needed. Answer: What is the core change? Why now? What's the acceptance criteria?
+
+## Phase 2 — Acceptance tests (write them first)
+
+Write the test assertions **before** implementation code:
+
+```bash
+# Example: test that a function returns X when given Y
+assert_equals(parse_config("key=val"), {"key": "val"})
+assert_throws(parse_config("broken"), ParseError)
+```
+
+## Phase 3 — Implementation plan
+
+Numbered steps for implementation. Link to files (`path:line_number`). Estimate scope (1-2h, half-day, day+).
+
+## Phase 4 — Risks and scope
+
+- What could go wrong?
+- Is this change backward compatible?
+- Do other parts of the system depend on this behavior?
+
+## Phase 5 — Definition of done
+
+When is this complete?
+- Tests pass
+- Behavior works end-to-end
+- Error cases handled
+- Documentation updated if needed

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

@@ -0,0 +1,21 @@
+# `.claude/vault/` — Obsidian vault
+
+Human-authored project documentation. Open this directory as an Obsidian vault root.
+
+## Layout
+
+- [`decisions/`](decisions/) — architectural decisions (ADRs). One note per decision.
+- [`design/`](design/) — design notes, system sketches, spec drafts.
+- [`sessions/`](sessions/) — session logs (append-only, dated).
+- [`knowledge/`](knowledge/) — domain notes, research, references.
+
+## Why inside `.claude/`
+
+Keeps everything agentic-dev-related under a single root folder. Obsidian doesn't care that the path is hidden — point it at `.claude/vault/` and use normally.
+
+## Conventions
+
+- Plain markdown, nothing Obsidian-proprietary in note content (wikilinks are fine).
+- Dates in filenames as `YYYY-MM-DD` for chronological sort.
+- One topic per note.
+- Use `#tags` for lightweight categorization.

project_init/templates/base/dot_claude/vault/decisions/README.md

@@ -0,0 +1,22 @@
+# decisions/
+
+Architectural decision records. One note per decision.
+
+Suggested template:
+
+```markdown
+# <decision title>
+
+**Date**: YYYY-MM-DD
+**Status**: proposed | accepted | superseded
+**Supersedes**: (link)
+**Superseded by**: (link)
+
+## Context
+
+## Options considered
+
+## Decision
+
+## Consequences
+```

project_init/templates/base/dot_claude/vault/design/README.md

@@ -0,0 +1,3 @@
+# design/
+
+Design notes, diagrams, spec drafts. Less formal than `decisions/` — a place for working through problems.

project_init/templates/base/dot_claude/vault/knowledge/README.md

@@ -0,0 +1,5 @@
+# knowledge/
+
+Domain notes, research, external references.
+
+Put API dumps, library notes, concept explainers here — the kind of things you'd want to re-read rather than re-derive.

project_init/templates/base/dot_claude/vault/sessions/README.md

@@ -0,0 +1,5 @@
+# sessions/
+
+Session logs. Append-only. The `/session_summary` skill writes one file per session: `YYYY-MM-DD-HHMM.md`.
+
+Manually editable if you want to add notes the agent missed.

project_init/templates/base/dot_devcontainer/devcontainer.json.tmpl

@@ -0,0 +1,17 @@
+{{#if devcontainer}}{
+  "name": "{{project_name}}",
+  "image": "mcr.microsoft.com/devcontainers/base:ubuntu-24.04",
+{{#if go}}  "features": {
+    "ghcr.io/devcontainers/features/go:1": {}
+  },
+{{/if go}}  "postCreateCommand": "bash .devcontainer/post-create.sh",
+  "remoteEnv": {
+    "PATH": "${containerEnv:HOME}/.local/bin:${containerEnv:HOME}/.bun/bin:${containerEnv:PATH}"
+  },
+  "customizations": {
+    "vscode": {
+      "extensions": ["anthropic.claude-code"]
+    }
+  }
+}
+{{/if devcontainer}}

project_init/templates/base/dot_devcontainer/post-create.sh.tmpl

@@ -0,0 +1,31 @@
+{{#if devcontainer}}#!/bin/bash
+# Devcontainer bootstrap (scaffolded by project-init): install the toolchain
+# the scaffolded workflow expects, then sync dependencies through the same
+# path the SessionStart hook uses. Idempotent — safe to re-run.
+set -euo pipefail
+
+mkdir -p "$HOME/.local/bin"
+export PATH="$HOME/.local/bin:$PATH"
+
+# just — the canonical command surface (`just --list`)
+if ! command -v just >/dev/null 2>&1; then
+  curl --proto '=https' --tlsv1.2 -sSf https://just.systems/install.sh \
+    | bash -s -- --to "$HOME/.local/bin"
+fi
+{{#if python}}
+# uv — Python toolchain and dependency manager
+if ! command -v uv >/dev/null 2>&1; then
+  curl -LsSf https://astral.sh/uv/install.sh | sh
+fi
+{{/if python}}{{#if node}}
+# bun — Node runtime and package manager
+if ! command -v bun >/dev/null 2>&1; then
+  curl -fsSL https://bun.sh/install | bash
+  export PATH="$HOME/.bun/bin:$PATH"
+fi
+{{/if node}}
+# Sync dependencies. With --no-plugin scaffolds the SessionStart script is
+# local; plugin-mode containers bootstrap via just (the plugin hook stamps
+# the environment once a session opens).
+{{#if no_plugin}}bash .claude/hooks/session_setup.sh{{/if no_plugin}}{{#if plugin_mode}}command -v just >/dev/null 2>&1 && [ -f justfile ] && just setup || true{{/if plugin_mode}}
+{{/if devcontainer}}

project_init/templates/base/dot_env.example.tmpl

@@ -0,0 +1,13 @@
+# .env.example — template for local environment (scaffolded by project-init).
+#
+# Copy to .env (gitignored) and fill in real values: cp .env.example .env
+#
+# Loading order (first match wins):
+#   1. variables already exported in your shell
+#   2. .env, loaded by the tool itself — `uv run --env-file .env`, bun
+#      auto-loads .env, or direnv if your team uses it
+# Nothing here is loaded implicitly by the scaffold; tools opt in.
+#
+# Never commit .env: the pre-commit gitleaks scan and CI both enforce this.
+# For team secrets, see .claude/docs/guides/secrets.md (escalation paths).
+# EXAMPLE_API_KEY=

project_init/templates/base/dot_github/CODEOWNERS.tmpl

@@ -0,0 +1,12 @@
+# CODEOWNERS — reviewers auto-requested for matching paths (scaffolded by project-init).
+# Order matters: the last matching pattern wins.
+# Owners must be GitHub usernames (@user) or teams (@org/team) with write access.
+{{#if project_owner}}
+# Default owner for everything in the repository.
+*       {{project_owner}}
+{{/if project_owner}}
+# Per-area examples — uncomment and adjust:
+# /src/             @your-org/backend
+# /docs/            @your-org/docs
+# /.github/         @your-org/platform
+# /.claude/         @your-org/platform

project_init/templates/base/dot_github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,98 @@
+name: Bug
+description: Something is broken
+labels: [bug]
+body:
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      options: [high, medium, low]
+    validations:
+      required: true
+  - type: input
+    id: area
+    attributes:
+      label: Area
+      placeholder: frontend, backend, docs, devops, product
+    validations:
+      required: true
+  - type: dropdown
+    id: size
+    attributes:
+      label: Size
+      options: [XS, S, M, L, XL]
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: What happened?
+      placeholder: Describe the bug
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to reproduce
+      placeholder: |
+        1. ...
+        2. See error
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behaviour
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      placeholder: "OS, runtime version, dependency versions"
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Related issues, PRs, ADRs, docs, designs, logs, or external links.
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies
+      description: Blocked-by, parent, or follow-up relationships.
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      placeholder: |
+        - [ ] ...
+    validations:
+      required: true
+  - type: dropdown
+    id: agent_ready
+    attributes:
+      label: Agent ready
+      description: Can an AI agent implement this without human clarification?
+      options: ["Yes", "No"]
+      default: 1
+  - type: dropdown
+    id: confidence
+    attributes:
+      label: Confidence
+      description: How well-understood is the scope and approach?
+      options: [high, medium, low, unknown]
+      default: 3
+  - type: textarea
+    id: ready
+    attributes:
+      label: Definition of Ready
+      placeholder: What must be true before implementation starts?
+    validations:
+      required: true
+  - type: textarea
+    id: done
+    attributes:
+      label: Definition of Done
+      placeholder: What must be true before this can close?
+    validations:
+      required: true

project_init/templates/base/dot_github/ISSUE_TEMPLATE/chore.yml

@@ -0,0 +1,82 @@
+name: Chore
+description: Maintenance, refactor, dependency update, or CI change
+labels: [chore]
+body:
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      options: [high, medium, low]
+    validations:
+      required: true
+  - type: input
+    id: area
+    attributes:
+      label: Area
+      placeholder: frontend, backend, docs, devops, product
+    validations:
+      required: true
+  - type: dropdown
+    id: size
+    attributes:
+      label: Size
+      options: [XS, S, M, L, XL]
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: What needs doing?
+    validations:
+      required: true
+  - type: textarea
+    id: why
+    attributes:
+      label: Why now?
+      description: What breaks or degrades if this is skipped?
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Related issues, PRs, ADRs, docs, designs, or external links.
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies
+      description: Blocked-by, parent, or follow-up relationships.
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      placeholder: |
+        - [ ] ...
+    validations:
+      required: true
+  - type: dropdown
+    id: agent_ready
+    attributes:
+      label: Agent ready
+      description: Can an AI agent implement this without human clarification?
+      options: ["Yes", "No"]
+      default: 1
+  - type: dropdown
+    id: confidence
+    attributes:
+      label: Confidence
+      description: How well-understood is the scope and approach?
+      options: [high, medium, low, unknown]
+      default: 3
+  - type: textarea
+    id: ready
+    attributes:
+      label: Definition of Ready
+      placeholder: What must be true before implementation starts?
+    validations:
+      required: true
+  - type: textarea
+    id: done
+    attributes:
+      label: Definition of Done
+      placeholder: What must be true before this can close?
+    validations:
+      required: true

project_init/templates/base/dot_github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Planning discussion
+    url: https://github.com
+    about: Use discussions for exploratory ideas that are not ready for issue tracking.

project_init/templates/base/dot_github/ISSUE_TEMPLATE/docs.yml

@@ -0,0 +1,84 @@
+name: Docs
+description: Documentation addition or correction
+labels: [documentation]
+body:
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      options: [high, medium, low]
+    validations:
+      required: true
+  - type: input
+    id: area
+    attributes:
+      label: Area
+      placeholder: docs, product, devops, frontend, backend
+    validations:
+      required: true
+  - type: dropdown
+    id: size
+    attributes:
+      label: Size
+      options: [XS, S, M, L, XL]
+    validations:
+      required: true
+  - type: textarea
+    id: scope
+    attributes:
+      label: What needs documenting?
+      description: Which behavior, workflow, or decision needs clearer documentation?
+    validations:
+      required: true
+  - type: textarea
+    id: audience
+    attributes:
+      label: Audience
+      description: Who needs this documentation?
+      placeholder: "Users, maintainers, agents, contributors, operators..."
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Related issues, PRs, ADRs, files, or external links
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies
+      description: Blocked-by, parent, or follow-up relationships.
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      placeholder: |
+        - [ ] ...
+    validations:
+      required: true
+  - type: dropdown
+    id: agent_ready
+    attributes:
+      label: Agent ready
+      description: Can an AI agent implement this without human clarification?
+      options: ["Yes", "No"]
+      default: 1
+  - type: dropdown
+    id: confidence
+    attributes:
+      label: Confidence
+      description: How well-understood is the scope and approach?
+      options: [high, medium, low, unknown]
+      default: 3
+  - type: textarea
+    id: ready
+    attributes:
+      label: Definition of Ready
+      placeholder: What must be true before implementation starts?
+    validations:
+      required: true
+  - type: textarea
+    id: done
+    attributes:
+      label: Definition of Done
+      placeholder: What must be true before this can close?
+    validations:
+      required: true

project_init/templates/base/dot_github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,87 @@
+name: Feature
+description: New feature or enhancement
+labels: [feature]
+body:
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      options: [high, medium, low]
+    validations:
+      required: true
+  - type: input
+    id: area
+    attributes:
+      label: Area
+      placeholder: frontend, backend, docs, devops, product
+    validations:
+      required: true
+  - type: dropdown
+    id: size
+    attributes:
+      label: Size
+      options: [XS, S, M, L, XL]
+    validations:
+      required: true
+  - type: input
+    id: title
+    attributes:
+      label: What should this do?
+      placeholder: "Add X / Support Y / Allow Z"
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What changes and why
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance criteria
+      description: Bullet list of conditions that define "done"
+      placeholder: |
+        - [ ] Criterion 1
+        - [ ] Criterion 2
+    validations:
+      required: true
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Related issues, PRs, ADRs, docs, designs, or external links.
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies
+      description: Blocked-by, parent, or follow-up relationships.
+  - type: dropdown
+    id: agent_ready
+    attributes:
+      label: Agent ready
+      description: Can an AI agent implement this without human clarification?
+      options: ["Yes", "No"]
+      default: 1
+  - type: dropdown
+    id: confidence
+    attributes:
+      label: Confidence
+      description: How well-understood is the scope and approach?
+      options: [high, medium, low, unknown]
+      default: 3
+  - type: textarea
+    id: ready
+    attributes:
+      label: Definition of Ready
+      placeholder: What must be true before implementation starts?
+    validations:
+      required: true
+  - type: textarea
+    id: done
+    attributes:
+      label: Definition of Done
+      placeholder: What must be true before this can close?
+    validations:
+      required: true