Reusable agent setup package, starting with Claude.
pasika stores portable agent setup assets that individual repos can apply or adapt. Today it focuses on Claude, with room for Codex and other agent-specific setup flows later.
This repo intentionally starts narrow:
- Claude first for v1
- reusable agent setup assets only
- shared docs at the repo root
- no project-specific rules, workflows, or business logic
claude/
settings.base.json
hooks/
status-line/
index.js
notification.sh
protect-files.sh
scripts/
render-settings.ts
docs/
claude/
hooks.md
scripts/
pasika.ts
dist/
...
vulyk.json
AGENTS.md
CLAUDE.md
- portable setup scripts
- base settings templates
- shared docs and generated
CLAUDE.md - shared naming and layout conventions
- final agent config folders in project repos
- project-specific rules, agents, and prompts
- repository-specific plugin choices
- scripts that depend on a specific app, CI setup, or codebase
The current entry point is:
npx pasika claudeOptional flags:
--target-dir <path>writes into another repo--forcereplaces an existing generated file instead of merging
The CLI source lives in TypeScript.
npm run lint
npm run typecheck
npm run buildnpm run build uses vulyk docs to emit root AGENTS.md and CLAUDE.md.
Hooks and helper executables should come from node_modules.
That gives us:
- versioned reusable scripts
- easy upgrades through the package manager
- no manual copying of hook files into every repo
settings.json is different. It still needs to exist in each project repo, because Claude Code does not give us a clean inheritance model for it.
So the recommended pattern is:
- install
pasikaas a dev dependency - run
npx pasika claude - generate or merge into
.claude/settings.jsonin the project - point hook commands at
./node_modules/pasika/claude/... - keep project-specific plugin, skill, and rule decisions in the project repo
npx pasika claude also copies the packaged Claude hooks docs into .claude/hooks/ in the target repo.