EnglandTong
- 6 skills
- 0 followers
- 16 hours ago last updated
- ▌ AI Workflow Os · englandtong bundleRoute complex AI-assisted work across project lifecycle guidance, formal project governance, coding execution, session memory, web-research intake, and cross-source synthesis without creating competing state. Use when a request spans two or more of these surfaces, the user is unsure which workflow skill applies, or a combined research-to-project-to-handoff flow needs clear authority and ordering. Typical triggers include 我这个需求该用哪个 skill, which skill should handle this, 研究和开发一起做, research then implement then hand off, 这个项目该怎么管, orchestrate this across skills, 从头到尾帮我跑一遍, and end-to-end AI workflow. Delegates to specialized skills when installed and uses bundled modules only as reduced-fidelity fallbacks. Applies a subtraction-first guard so a combined request does not silently become new scope.
- ▌ Daily Workflow · englandtong bundleSay 开工啦 or 收工啦 and get a resumable project note written for you, so tomorrow you or another AI can pick up without re-reading everything. Use when a user asks to resume a project, save progress, record a checkpoint, end a work session, prepare a handoff, switch to a new AI session, or reconcile stale working notes. Typical triggers include 开工啦, 中段检查, 吃饭啦, 收工啦, 交接, 记一下进度, 存个档, 明天接着做, 换个 AI 继续, 上下文快满了, start work, checkpoint, wrap up, handoff, save progress, resume tomorrow, and switch to a new agent session. Reads existing project authority first, preserves dirty worktrees and governance evidence, avoids competing state files, archives rather than deletes history, and records commands, final outcomes, blockers, risks, and exact next actions without claiming unverified completion or QA acceptance.
- ▌ Web Search Rules · englandtong bundleSearch the web and save findings into your knowledge base with a source URL, date and quote attached to every claim. Works with Obsidian, NotebookLM, IMA, Feishu Docs and Tencent Docs. Use when a user asks to search the web, verify a current claim, evaluate sources, deduplicate results, manage source allow/deny rules, stage research for review, archive approved findings, or migrate research notes between local and cloud knowledge bases. Typical triggers include 帮我查一下, 这个说法现在还成立吗, verify this claim, find authoritative sources, 查最新政策/价格/版本, fact check, 整理搜索结果, 放进知识库, archive these sources, deduplicate my research, and check whether this AI summary is accurate. Covers provenance, freshness, claim-level evidence, untrusted metadata, single-source cross-checking, prompt-injection resistance, confirmations, and audit logs; it does not make a source trustworthy merely because its domain is allowed, and it does not treat a snippet, a search engine summary, or a file's embedded metadata as an opened and verified sourc
- ▌ Agent Loop Engineering · englandtong bundleExecute an authorized software goal through low-context, bounded-autonomous AI coding loops with persistent state, proactive repair, automatic and functional evidence, layered stage review, independent final acceptance, safe workspace boundaries, and resumable handoffs. Use when a target and acceptance criteria are clear and the user asks to implement, debug, verify, continue autonomously, follow Controller-Developer-QC cycles, resume after context loss, or reduce repeated context and documentation. Typical triggers include keep going, continue where we left off, run it autonomously and fix what breaks, 接着跑 / 继续做 / 自动修 / 断点续跑 / 别再问我每一步, we are stuck on the same failure, 卡在同一个错误上, resume after compaction, 上下文快满了, stop burning tokens on repeated context, run the regression after this repair, and make a flaky test deterministic. Also use for bounded-autopilot, single-writer loop state, failure-signature stop rules, delivery-class-aware evidence, and anti-doc-bloat execution. For vague goals, legacy-state conflic
- ▌ Cms Project Governance · englandtong bundleKeep a drifting or half-finished project under control with one compact, conflict-checked delivery state, right-sized scope, bounded autonomy, and independent QA acceptance. Use for non-technical requirement guidance, Legacy Bootstrap, Small/Medium/Large sizing, Lite/Standard/Full governance, Controller-Developer-QC routing, Milestones, Work Orders, QA acceptance, drift recovery, target rebaseline, roadmap review, or reducing token and document overhead. Typical triggers include 项目做了一半 / 不知道该不该继续 / 范围蔓延 / 想加新方向 / 想重开一个项目, scope creep, we keep adding features, too many documents and no working code, docs outweigh code, governance overhead is too high, 治理内卷, which project should I kill, should I archive this, redefine done, change the target, rebaseline, is this really accepted, and we accepted it but never shipped. Also use for anti-involution doc budgets, archive discipline, stop-loss rules, Active Packet bootstrap, and accepted-but-never-released risk. For already-authorized ordinary coding loops, use agent-
- ▌ Project Lifecycle Navigator · englandtong bundleAudit a project you are unsure about and get a go, narrow, pivot, archive or stop recommendation, without writing code or changing governance state. Use when a non-technical user needs structured project guidance, a project is drifting, existing code needs a read-only audit, a recent delivery needs comparison with its current target, or new requirements may change scope. Typical triggers include 项目做了一半要不要继续, 我是不是该重开一个, 范围蔓延, 想加个新功能, I have too many projects, should I kill this one, 帮我看看这个仓库还能不能救, audit my codebase, is this project over-engineered, 定义一下 MVP, 怎样算做完, 止损, 归档, 这个项目还有价值吗, define MVP scope, scope creep, project drift, startup checklist, go or no-go, portfolio cleanup, and repository health audit. Also use for duplicate-copy detection, missing version control, hardcoded secrets in shipped artifacts, god-module and entrypoint-sprawl findings, and pre-commitment stop-loss rules. Produces bounded recommendations and handoffs without coding, self-authorizing work, changing governance state, or claiming Q