using-pythia
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseUsing pythia — the pocket handbook
使用pythia——袖珍手册
Phase: Learn → Ask → Do — this page opens the right one
pythia is the main book; this is the small notebook clipped inside its cover.
Its one job is consistency: whether a session asks the right questions should
not depend on the agent's mood that day.
阶段: 学习 → 提问 → 执行 —— 本页面将为你打开正确的技能入口
pythia是主手册;本指南是夹在其封面内的小笔记本。
它的唯一职责是确保一致性:会话是否提出正确的问题,不应取决于Agent当日的状态。
The Rule
规则
If there is even a small chance a pythia skill applies, open it before
acting — before answering, before exploring, before clarifying questions.
Opened the wrong one? Close it, no harm done. Skipping the check is how
sessions drift: some ask, some silently decide.
只要存在适用pythia技能的微小可能性,就应在采取行动前打开它——在回答、探索、提出澄清问题之前。打开了错误的技能?关闭即可,不会造成任何损害。跳过检查是导致会话偏离正轨的原因:有些会话会提问,有些则默默做决定。
Route by what the developer said
根据开发者的请求进行路由
| The request sounds like | Open first | Then |
|---|---|---|
| "build / add / change X" — and any decision is open | | impact → write → apply |
| "explain X / why / how does it work" | | |
| "is it safe to touch X" | | |
| "review this" | | |
| "land / deploy / apply this" | | |
| "our standards / adopt this base's style" | | |
| "make a skill for how we do X" | | |
| setup, connection failures, privilege warnings | | |
| an ORA-/PLS- error to investigate | | |
Priority when several apply: process before construction — spec before
write, impact before apply. Announce the skill you opened ("Using
pythia-spec — ...") so the developer can see which page you are on.
| 请求听起来像 | 优先打开 | 后续步骤 |
|---|---|---|
| "build / add / change X" —— 且存在待决策事项 | | 影响评估 → 编写 → 应用 |
| "explain X / why / how does it work"(解释X/为什么/如何运作) | | |
| "is it safe to touch X"(修改X是否安全) | | |
| "review this"(审核此项) | | |
| "land / deploy / apply this"(部署/应用此项) | | |
| "our standards / adopt this base's style"(我们的标准/采用此基础风格) | | |
| "make a skill for how we do X"(为我们处理X的方式创建一个技能) | | |
| 设置、连接失败、权限警告 | | |
| 需要排查的ORA-/PLS-错误 | | |
当多个技能适用时的优先级:流程优先于构建——编写前先确认规格,应用前先评估影响。请告知开发者你打开的技能(例如“正在使用pythia-spec —— ...”),以便他们了解你当前所处的环节。
Working beside other packs
与其他工具包协同工作
This notebook assumes nothing else is installed. If a general process pack
(brainstorming, TDD, planning) is active in the session, let it own generic
process and keep pythia's Oracle gates — they compose. Never treat its
presence as a reason to skip , nor pythia's presence as a
reason to skip it.
pythia-spec本手册不依赖任何已安装的其他工具。如果会话中启用了通用流程工具包(头脑风暴、TDD、规划),则由其负责通用流程,同时保留pythia的Oracle相关规则——二者可以组合使用。绝不能以其他工具包的存在为理由跳过,也不能以pythia的存在为理由跳过其他工具包。
pythia-specRed flags — the exact thoughts behind "some sessions ask, some don't"
危险信号——“有些会话提问,有些则不”背后的真实想法
| Thought | Reality |
|---|---|
| "This task is simple" | Simple tasks hide spec. A forgot-password flow carried seven unasked decisions. |
| "I remember what that skill says" | Skills evolve. Open the current page. |
| "I'll just look around first" | |
| "Another pack will do the asking" | If it fires, good. If it does not, |
| "Asking would stall the developer" | Paying for an unasked decision stalls harder. |
| 想法 | 现实 |
|---|---|
| “这个任务很简单” | 简单任务往往隐藏着规格要求。一个找回密码的流程就包含七个未被询问的决策点。 |
| “我记得那个技能的内容” | 技能会不断演进。请打开当前最新的页面。 |
| “我先随便看看” | |
| “另一个工具包会负责提问” | 如果它生效了,那很好。如果没有, |
| “提问会耽误开发者时间” | 因未提问而做出错误决策,会造成更严重的延误。 |
No skill support on this platform?
本平台不支持技能功能?
pythia guidepythia guide --briefThe pattern — a router consulted before any action — is Jesse Vincent's
Superpowers, rebuilt from scratch for this kit.
pythia guidepythia guide --brief这种“在采取任何行动前先咨询路由”的模式,源自Jesse Vincent的Superpowers,针对本工具包进行了全新重构。