@phren/cli 0.0.1

package/starter/my-first-project/FINDINGS.md

@@ -0,0 +1,24 @@
+# my-first-project findings
+
+Fragments accumulated over time. Captured automatically during sessions and committed on exit.
+
+<!-- How findings work:
+
+Phren captures insights as you code. When Claude discovers something non-obvious
+(a pitfall, a pattern, a decision with context), it calls add_finding() and the
+insight lands here. The Stop hook auto-commits after every response.
+
+Entries are grouped by date. Old entries get confidence-decayed over time, so stale
+findings fade from retrieval naturally. You can remove wrong entries with
+remove_finding() or clean up bulk with `phren shell` > :find remove.
+
+Example entries (delete these once you have real ones):
+
+## 2026-03-06
+
+- The auth middleware runs before rate limiting, order matters in the middleware stack
+  <!-- phren:cite {"created_at":"2026-03-06T00:00:00.000Z"} -->
+- `npm run dev` needs PORT set or it defaults to 3001, not 3000
+  <!-- phren:cite {"created_at":"2026-03-06T00:00:00.000Z"} -->
+
+-->

package/starter/my-first-project/summary.md

@@ -0,0 +1,11 @@
+# my-first-project
+
+**What:** Replace this with one sentence about what the project does
+**Stack:** The key tech: language, framework, main deps
+**Status:** active
+**Run:** the command you use most (e.g. npm run dev)
+**Watch out:** the one thing that will bite you if you forget it
+
+<!-- This summary is the first thing phren shows Claude about your project.
+     Keep it short: 5 lines max. Think of it as the elevator pitch that helps
+     Claude understand what it's working on before reading any code. -->

package/starter/my-first-project/tasks.md

@@ -0,0 +1,25 @@
+# my-first-project tasks
+
+## Active
+
+### P0: Getting started
+
+- [ ] Fill in CLAUDE.md with your project's commands, architecture, and conventions
+- [ ] Update summary.md with a real description of your project
+
+## Queue
+
+### P1: Phren setup
+
+- [ ] Push this phren repo to a private GitHub repo for backup
+- [ ] Run `phren doctor` to verify everything is wired up
+- [ ] Add a second project with `phren-init <name>` or `phren shell`
+
+### P2: Nice to have
+
+- [ ] Set up profiles for work vs personal machines in profiles/
+- [ ] Add project-specific skills to the project `skills/` directory
+
+## Done
+
+- [x] Run `npx phren init` to set up phren

package/starter/my-frontend/.claude/skills/README.md

@@ -0,0 +1,7 @@
+# my-frontend skills
+
+| Skill | What it does |
+|-------|-------------|
+| `/verify` | Pre-commit gate |
+
+Add project-specific skills here.

package/starter/my-frontend/CLAUDE.md

@@ -0,0 +1,33 @@
+# CLAUDE.md
+
+## Project overview
+
+**Purpose**: Frontend app. Replace this with a real description of what it does.
+**Stack**: React, TypeScript, Vite (or whatever you're using)
+**Status**: active
+**Version**: 0.0.0
+
+## Commands
+
+```bash
+# Install:   npm install
+# Run:       npm run dev
+# Test:      npm test
+# Build:     npm run build
+```
+
+## Project skills
+
+Source skills live in the phren project `skills/` directory. Phren resolves global + project-local skills and mirrors the effective set into repo-local `.claude/skills/`.
+
+## Architecture
+
+<!-- Component structure, routing, state management approach -->
+
+## Key patterns
+
+<!-- Naming rules, component patterns, things to never do -->
+
+<!-- Tip: If this file grows past ~100 lines, split it using @import directives.
+     Example: @CLAUDE-architecture.md, @CLAUDE-commands.md, @CLAUDE-conventions.md
+     See phren README for details. -->

package/starter/my-frontend/FINDINGS.md

@@ -0,0 +1,9 @@
+# my-frontend findings
+
+Findings accumulated over time. Captured automatically during sessions and committed on exit.
+
+<!-- Example entry:
+## 2026-03-04
+- HMR breaks if you rename a component file without restarting the dev server
+- The API base URL in .env.local must not have a trailing slash
+-->

package/starter/my-frontend/summary.md

@@ -0,0 +1,7 @@
+# my-frontend
+
+**What:** Frontend app: replace with what yours actually does
+**Stack:** React, TypeScript, Vite (or whatever you're using)
+**Status:** active
+**Run:** npm run dev
+**Watch out:** API base URL set in .env.local: needs to match whatever port my-api runs on

package/starter/my-frontend/tasks.md

@@ -0,0 +1,7 @@
+# my-frontend tasks
+
+## Active
+
+## Queue
+
+- [ ] Add your tasks here

package/starter/profiles/default.yaml

@@ -0,0 +1,4 @@
+name: default
+description: Default profile
+projects:
+  - global

package/starter/profiles/personal.yaml

@@ -0,0 +1,4 @@
+name: personal
+description: "Personal machine defaults"
+projects:
+  - global

package/starter/profiles/work.yaml

@@ -0,0 +1,4 @@
+name: work
+description: "Work machine defaults"
+projects:
+  - global

package/starter/templates/README.md

@@ -0,0 +1,7 @@
+# starter/templates/
+
+Project templates bundled in the npm package, used by `npx phren init --template <name>`.
+
+Each subdirectory (frontend, library, monorepo, python-project) contains pre-filled project files with sensible defaults for that project type. When a user runs init with `--template`, these files are copied into their `~/.phren/<project>/` directory. For other project types, adaptive init infers topics and structure from repo content.
+
+Users interact with this directory indirectly through the `--template` flag during init. To add a new template type, create a subdirectory here with the standard project files.

package/starter/templates/frontend/CLAUDE.md

@@ -0,0 +1,23 @@
+# {{project}}
+
+Frontend application.
+
+## Commands
+
+```bash
+npm install
+npm run dev
+npm run build
+npm test
+```
+
+## Architecture
+
+<!-- Fill in: routing, state management, component structure -->
+
+## Conventions
+
+- Components in src/components/
+- Pages/routes in src/pages/ or src/routes/
+- Shared utilities in src/lib/
+- CSS modules or Tailwind for styling

package/starter/templates/frontend/FINDINGS.md

@@ -0,0 +1,7 @@
+# {{project}} Findings
+
+<!-- consolidated: 2024-01-01 -->
+
+## {{date}}
+
+- Example: component hot reload breaks when editing files imported by both client and server bundles. Move shared types to a separate module.

package/starter/templates/frontend/reference/README.md

@@ -0,0 +1,4 @@
+# {{project}} Reference
+
+Deep reference material: API details, data models, integration specs.
+Too long for CLAUDE.md? Put it here. Phren indexes these files automatically.

package/starter/templates/frontend/summary.md

@@ -0,0 +1,7 @@
+# {{project}}
+
+What: Frontend web application
+Stack: TypeScript, React
+Status: new
+Run: `npm run dev`
+Watch out: check node version matches .nvmrc

package/starter/templates/frontend/tasks.md

@@ -0,0 +1,11 @@
+# {{project}} tasks
+
+## Active
+
+## Queue
+
+- Set up routing
+- Add authentication flow
+- Configure deployment pipeline
+
+## Done

package/starter/templates/library/CLAUDE.md

@@ -0,0 +1,22 @@
+# {{project}}
+
+Reusable library published to a package registry.
+
+## Commands
+
+```bash
+npm install
+npm run build
+npm test
+npm publish
+```
+
+## Architecture
+
+<!-- Fill in: entry point, exports, module format -->
+
+## Conventions
+
+- Source in src/, tests in src/ alongside modules
+- Exports defined in package.json exports field
+- Semantic versioning, changelog on every release

package/starter/templates/library/FINDINGS.md

@@ -0,0 +1,7 @@
+# {{project}} Findings
+
+<!-- consolidated: 2024-01-01 -->
+
+## {{date}}
+
+- Example: dual CJS/ESM builds need separate tsconfig files. A single config with `module: "NodeNext"` only covers one output format.

package/starter/templates/library/reference/README.md

@@ -0,0 +1,4 @@
+# {{project}} Reference
+
+Deep reference material: API details, data models, integration specs.
+Too long for CLAUDE.md? Put it here. Phren indexes these files automatically.

package/starter/templates/library/summary.md

@@ -0,0 +1,7 @@
+# {{project}}
+
+What: Reusable library
+Stack: TypeScript, vitest
+Status: new
+Run: `npm test`
+Watch out: build before publish

package/starter/templates/library/tasks.md

@@ -0,0 +1,11 @@
+# {{project}} tasks
+
+## Active
+
+## Queue
+
+- Define public API surface
+- Add usage examples to README
+- Set up CI with automated publishing
+
+## Done

package/starter/templates/monorepo/CLAUDE.md

@@ -0,0 +1,21 @@
+# {{project}}
+
+Monorepo with multiple packages.
+
+## Commands
+
+```bash
+npm install
+npm run build --workspaces
+npm test --workspaces
+```
+
+## Architecture
+
+<!-- Fill in package layout and dependencies -->
+
+## Conventions
+
+- Each package in packages/ is independently versioned
+- Shared types in packages/shared
+- Use workspace references for inter-package deps

package/starter/templates/monorepo/FINDINGS.md

@@ -0,0 +1,7 @@
+# {{project}} Findings
+
+<!-- consolidated: 2024-01-01 -->
+
+## {{date}}
+
+- Example: workspace hoisting can shadow a package's own dependency version. Pin critical deps in each package.json, not just the root.

package/starter/templates/monorepo/reference/README.md

@@ -0,0 +1,4 @@
+# {{project}} Reference
+
+Deep reference material: API details, data models, integration specs.
+Too long for CLAUDE.md? Put it here. Phren indexes these files automatically.

package/starter/templates/monorepo/summary.md

@@ -0,0 +1,7 @@
+# {{project}}
+
+What: Monorepo with multiple packages
+Stack: TypeScript, npm workspaces
+Status: new
+Run: `npm run dev`
+Watch out: install from root, not inside individual packages

package/starter/templates/monorepo/tasks.md

@@ -0,0 +1,11 @@
+# {{project}} tasks
+
+## Active
+
+## Queue
+
+- Define package boundaries
+- Set up shared build pipeline
+- Add changeset for versioning
+
+## Done

package/starter/templates/python-project/CLAUDE.md

@@ -0,0 +1,21 @@
+# {{project}}
+
+Python project.
+
+## Commands
+
+```bash
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+pytest
+```
+
+## Architecture
+
+<!-- Fill in as the project grows -->
+
+## Conventions
+
+- Use pyproject.toml for packaging
+- Type hints on public APIs
+- Tests in tests/ directory

package/starter/templates/python-project/FINDINGS.md

@@ -0,0 +1,7 @@
+# {{project}} Findings
+
+<!-- consolidated: 2024-01-01 -->
+
+## {{date}}
+
+- Example: `pip install -e .` with pyproject.toml requires the build backend (setuptools/hatchling) listed in build-system.requires, not just in dev deps.

package/starter/templates/python-project/reference/README.md

@@ -0,0 +1,4 @@
+# {{project}} Reference
+
+Deep reference material: API details, data models, integration specs.
+Too long for CLAUDE.md? Put it here. Phren indexes these files automatically.

package/starter/templates/python-project/summary.md

@@ -0,0 +1,7 @@
+# {{project}}
+
+What: Python project
+Stack: Python, pytest
+Status: new
+Run: `pytest`
+Watch out: activate venv before running

package/starter/templates/python-project/tasks.md

@@ -0,0 +1,10 @@
+# {{project}} tasks
+
+## Active
+
+## Queue
+
+- Set up CI pipeline
+- Add type checking with mypy
+
+## Done