Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ __pycache__/
*.py[cod]
.pytest_cache/
.venv/
.agents/
dist/
build/
*.egg-info/
Expand Down
47 changes: 47 additions & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
# Agent Instructions

These instructions apply to the entire repository. See `CONTRIBUTING.md` for the
full development and release guidance.

## Working model

- Keep ordinary development correct with one primary agent. Use subagents only when
the user explicitly requests delegation.
- Preserve user changes and avoid unrelated formatting, generated-file churn, or
destructive Git operations.
- Use the Solodeveling workflow for project mutations and work that must survive a
session. Handle bounded read-only questions inline without creating lifecycle
artifacts.
- Keep reversible, well-understood Quick work ephemeral. Use `.solodeveling/` only
when work is tracked or a durable decision must be preserved.

## Skill sources and runtime copies

- Treat `skills/` as the canonical, Git-tracked skill suite.
- Treat `.agents/skills/` as a local managed runtime copy. Do not edit or commit it.
- After changing canonical skills, update runtime copies through the installer and
verify them instead of copying or rewriting files by hand.
- Keep detailed runtime and standards material in references or repository docs
rather than duplicating it across `SKILL.md` files.

## Verification

Run focused checks for the changed boundary. The main repository checks are:

```console
python -m pytest -q
python scripts/validate_skill_suite.py
python -m solodeveling_protocol.cli .
```

Do not claim work is complete, fixed, passing, secure, or ready without recent,
scoped evidence. Record unavailable checks and narrow the claim accordingly.

## Authority boundaries

- Do not add telemetry, credentials, automatic publication, force-delete behavior,
or required subagent delegation.
- Do not commit, push, merge, tag, publish, sign, attest, or change repository
metadata unless the user explicitly authorizes that action.
- Treat release and production-changing actions as separate decisions requiring
explicit authority.