mayatnikovandClaude Opus 4.7
fa0bbd8c59
The whole point of this project is that the agent's growth is shareable. If skills and extensions silently land in ~/.pi/ on the maintainer's laptop, every clone starts from zero and the repo becomes a fancy README. Fix that with an explicit hard rule and a contributor guide. - AGENTS.md: new "Artifact location — hard rule" subsection spelling out that skills/extensions/prompts/state/.pi-settings ALL live in this repo, never in ~/.pi/. Pi's own built-in skills (skill-creator, etc.) stay user-global; the agent may use them, but their *output* must land here. - README: new "Everything in the repo" subsection covering the same rule in user-facing language, plus a pointer to CONTRIBUTING.md. - CONTRIBUTING.md (new): skill/extension formats, server-agnostic and no-secrets requirements, smoke-test recipe, PR checklist. - .gitignore: switch from blanket `.pi/` ignore to `.pi/*` + explicit un-ignore of `.pi/settings.json`, so project Pi config is reproducible. - "Don't push without operator confirmation" → "without human confirmation via the repo" — consistent with the new control model. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
38 lines
641 B
Plaintext
38 lines
641 B
Plaintext
# Secrets — NEVER commit a populated .env
|
|
.env
|
|
.env.local
|
|
.env.*.local
|
|
|
|
# Node
|
|
node_modules/
|
|
npm-debug.log*
|
|
yarn-debug.log*
|
|
yarn-error.log*
|
|
pnpm-debug.log*
|
|
|
|
# Pi runtime state — sessions and cache are local-only.
|
|
.pi/*
|
|
# …but commit .pi/settings.json — it's the project's Pi config (installed
|
|
# extensions, model defaults, etc.) and must be reproducible across clones.
|
|
!.pi/settings.json
|
|
sessions/
|
|
*.session.json
|
|
|
|
# Bot runtime state — generated by skills (e.g. joined-before flag, inventory snapshots)
|
|
state/
|
|
logs/
|
|
*.log
|
|
|
|
# OS / editor
|
|
.DS_Store
|
|
Thumbs.db
|
|
.idea/
|
|
.vscode/
|
|
*.swp
|
|
*.swo
|
|
|
|
# Build artefacts
|
|
dist/
|
|
build/
|
|
*.tsbuildinfo
|