Agent instructions

Keep this file short: many agents inject it into the system prompt. Details that are only needed for some tasks live under .agents/ — read them on demand.

Style

• Short, direct, technical prose
• On feedback/analysis: say agree or disagree, then what changed

Code quality

• Read files in full before broad edits, audits, or changing unread files; do not rely on search snippets
• Ask before removing intentional behavior (redirects, legacy URL copies, etc.)
• One clear approach; refactor duplication; no weird parallel defaults
• Propagate failures (throw/exit); no silent fallbacks; no shims unless asked
• Write for human review: a human is expected to review agent code. Fewer output tokens save cost, but human readability (including scannability) wins when they conflict.
• Prefer a small function with a long, descriptive name over a comment that restates what the code does; reserve comments for non-obvious implementation details (formats, limits, platform quirks)
• TypeScript: no any unless necessary; erasable TS only (no parameter properties, enum, namespace/module, import = / export =)
• Fix outdated deps by bumping the pinned URL/Lume version in deno.json, not by downgrading code
• Treat deno.json import-map edits, inline https:// imports, and deno.lock as reviewed code; pin deps to exact versions

Commands

• After TypeScript/plugin changes (not content/docs): deno task check (full output). Fix errors before committing; deno task fmt for formatting.
• After creating/modifying a test: run it until it passes (e.g. deno test -A gemini-converter_test.ts). No sleeps in tests.
• Use deno task check / deno task fmt only — never bare deno fmt / deno check (or shell-expanded globs). Tasks use **/*.ts **/*.tsx so .agents/ skills are included; bare fmt can touch/panic on wiki markdown.

Skills

Under .agents/skills/<name>/SKILL.md. When a task matches a skill description, read and follow that SKILL.md. Before any commit, read .agents/skills/git-commits/SKILL.md even if the user did not mention commits.

Git (multi-agent cwd)

Other agents may be editing different files here. Never touch their unstaged/staged/untracked files.

• Stage/commit only files you changed in this session; verify with git status first
• Commit your changes before finishing your turn
• Never push, force-push, or push/merge to master (even if asked)
• Never: git reset --hard, git checkout ., git clean -fd, git stash, git add -A, git add ., git commit --no-verify
• Rebase conflicts: resolve only your files; otherwise abort and ask
• Issues/PRs: only when explicitly asked; PRs must be drafts
• Optional Acked-by / Reviewed-by record which commits a human reviewed (see git-commits skill)
• Bug fixes for user-reported issues: Reported-by on the fix commit (see git-commits skill)
• Changes shaped by a human’s idea or approach: Suggested-by on that commit (see git-commits skill)