Skip to content

chore: weekly CLAUDE.md improvements #484

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
cteyton merged 1 commit into from
Sep 14, 2026
Merged

chore: weekly CLAUDE.md improvements #484

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
8 changes: 4 additions & 4 deletions packages/CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ src/index.ts always — public barrel; nothing is imp
src/application/useCases/<useCaseName>/ most — `spaces` uses flat `src/application/usecases/<UseCaseName>.ts` files instead of one folder per use case
src/domain/repositories|useCases|errors/ most
src/domain/entities/ only accounts and standards
src/infra/schemas/ persistence packages only — <name>Schemas.ts barrel of TypeORM EntitySchemas
src/infra/schemas/ persistence packages only — index.ts barrel exporting a <name>Schemas array of TypeORM EntitySchemas
src/infra/repositories/ persistence packages, plus `coding-agent` (deployer implementations, not persisted entities)
src/application/jobs/ + src/domain/jobs/ only commands, deployments, git
test/ only the 7 packages listed below
Expand Down Expand Up @@ -116,9 +116,9 @@ plus one `<entity>Factory.ts` per entity), imported as `@packmind/<pkg>/test`
import one. (`packages/node-utils/test/` exists but holds shared test suites, not factories, and is
not exposed as a subpath.)

Only `commands`, `deployments`, `skills`, `spaces` (and the legacy `recipes`) have an explicit
`"@packmind/<pkg>/test"` entry in `tsconfig.base.json`; `accounts`, `git` and `standards` resolve
through the workspace package instead. If a new `/test` subpath fails to resolve under Jest, add the
Only `commands`, `deployments`, `skills`, `spaces`, `standards` (and the legacy `recipes`) have an
explicit `"@packmind/<pkg>/test"` entry in `tsconfig.base.json`; `accounts` and `git` resolve through
the workspace package instead. If a new `/test` subpath fails to resolve under Jest, add the
alias — `jest.config.ts` maps modules from those `paths`.

Spec files import factories from there; production code must not. For the split between these and the
Expand Down
Loading