dotfiles

Routing skill for engineering workflow methods (two upstream packs: addyosmani/agent-skills and mattpocock/skills). Covers intent grilling, specs/PRDs, task breakdown, implementation strategy, TDD, debugging, code review, API/interface design, codebase architecture, domain modeling, security, performance, CI/CD, migration, documentation, release readiness. Use for non-trivial software engineering process decisions — not for trivial edits, casual chat, or pure tool usage. When triggered, read this file's index, then open the most relevant referenced SKILL.md before acting.

中文写作、改写和审校指南。写文章、报告、说明、邮件、文案、总结等面向读者的中文成稿时使用；用户要求润色、压缩、去套话、提高信息密度、减少 AI 味或检查表达质量时也使用。普通问答、代码和命令操作不使用。

Prefer Jujutsu (`jj`) for VCS operations whenever `jj` is installed. The `jj.ts` extension warns when `git` is used directly. Working copy is auto-tracked. Run `jj <cmd> --help` or `jj help -k <topic>` for exact syntax — this skill stays at the concept/workflow layer on purpose.

Use when the user wants to: spawn, stop, or monitor agents; send messages or follow-ups; run agents in parallel; collect results; schedule recurring work with triggers; or diagnose daemon issues. Trigger on any mention of 'agentd', and also on multi-agent patterns like 'run these in parallel', 'spawn a child agent', 'set a timed wakeup', or 'route a webhook into an agent'. Do NOT trigger for generic subprocess/asyncio, Celery/task-queue, or systemd/launchd questions unrelated to agentd.

Use when you are a channel-facing agent coordinating background work via spawned child agents. Trigger on requests like 'kick off X and Y in parallel and report back', 'dispatch a researcher', 'check on the workers', 'how's the migration going', or any pattern where the user expects you to manage subordinates without doing the work yourself. Do NOT trigger when the user wants to do the work directly, or when there is no parent-child relationship to manage.

Use when interacting with a user through Telegram, or when sending messages, files, and notifications via Telegram Bot API. Triggers on Telegram channel context, 'send to TG', 'notify via bot'. Do NOT use for bot development (webhooks, inline keyboards, handling updates).

Operate and troubleshoot Surge via surge-cli, including command discovery, runtime diagnostics, state inspection (dump/watch/test), and environment mutation with set key-paths. Use when a task asks to control Surge behavior, inspect live status, adjust policy/runtime switches, or automate Surge operations from CLI.