timborovkov

Applies Tim's default project setup preferences when creating, initializing, or standardizing a repo. Covers repo shape, TypeScript/frontend defaults, optional Go/Python stacks, AI/model infrastructure, backend/data choices, product services, design quality,…

Refreshes every maintained documentation surface for a release or completed body of work, including Markdown, MDX, static HTML, generated docs, READMEs, changelogs, guides, and docs navigation. Use when the user says "document release," "release the docs,"…

End-of-session handoff and follow-up workflow after substantive work (step shipped, PR landing, or switching agents). Syncs with main/recent merged PRs, aligns docs/TODO markdown to the full merged state, writes self-contained prompts for one or more next…

Performs a read-only, high-signal review of changes in the current Git branch or worktree, defaulting to the effective working tree versus the merge base with the repository's main/master/default branch. Finds introduced bugs, regressions, security and data…

Safely syncs a feature branch with upstream/default branch using rebase or merge, resolves textual conflicts, preserves and implements the intent of upstream changes and current-branch changes, validates, tests, and ensures both sets of desired behavior…

Runs the general contribution workflow for shipping changes: follows AGENTS/CLAUDE and CONTRIBUTING guidance, writes meaningful tests, validates with `pnpm validate`, keeps docs/TODOs current, pushes changes, monitors GitHub CI, and responds to PR reviews or…

Testing strategy for adding, reviewing, and improving meaningful tests. Use when asked to increase coverage, add tests, review existing tests, set up test commands or GitHub Actions, design unit/integration/E2E/API/DB tests, or add evals for AI and agent…

Writes and maintains in-repo docs using Tim's conventions: HTML docs under `docs/`, markdown READMEs/TODOs, protected project files, visual-first docs, and safe markdown-to-HTML conversion. Use when creating docs, adding a package README, converting markdown…

List and mutate Posthouse calendar events via CLI, including ICS export. Use for agenda and CalDAV writes — not mail or connection setup.

Manage Posthouse connections via CLI (add, label, update, remove, probe, discover, doctor). Use for IMAP/SMTP/CalDAV setup — not mail or calendar work.

Read and send Posthouse mail via the local CLI (list, search, triage, unread, get, archive, send, reply, drafts). Use for message work — not connection setup or calendar.

Configure Posthouse MCP over stdio or HTTP /mcp. Use when the agent calls MCP tools instead of the local CLI.

Call a self-hosted Posthouse REST /v1 API. Use when posthouse serve is up and the agent should use HTTP instead of the CLI.

Use a connected Timeline workspace through timeline.* MCP tools. Apply only when the user explicitly mentions Timeline, asks to use its MCP tools, or the task explicitly depends on evidence stored in their Timeline workspace. Supports evidence-backed…