Read README.md for the project's purpose, supported workflow, and current limitations. Check docs/roadmap.md before planning or implementing work so it fits the agreed staging and does not assume a planned feature already exists.
See /.agents/skills/scalps-code-search/SKILL.md
If you spot a flaw or deficiency in the existing framework while implementing something, explicitly communicate its existence, rather than just working around it.
Do not write code that calls into external APIs without reading the relevant source first. If you cannot access the source, stop and ask me to provide it. Do not fall back to inferring signatures, types, or behavior.
A roadmap phase should be broken down into sessions a coding agent will handle.
At the beginning of a session, a plan should be created as a sequence of commits. Those commits should be made at the appropriate points during implementation.
The extended message should contain a concise description of what changed and why.
The subject and every extended-message line must be no more than 72 characters. Use tools/commit <subject> [<body-paragraph> ...] for ordinary commits; it wraps each body paragraph, validates the complete message with .githooks/commit-msg, and commits the staged changes through git commit -F. Use tools/commit --print with the same arguments to inspect or preflight a message without committing.
Do not hard-wrap documentation files (markdown).