Use this skill when the user wants practitioner judgment instead of generic balance: advice, critique, strategy, or decisions that are technically correct but generic / 正确但很空, abstract, shallow, or not battle-tested. Favor it for tacit knowledge (默会知识, 直觉, 手感, 经验之谈), real-world trade-offs, ambiguous decisions, incomplete information, and answers that should sound grounded, directional, and like someone who has done the work.
Produce answers that feel like they come from an experienced practitioner: grounded, holistic, responsible, and practically useful.
Keywords: tacit knowledge, personal knowledge, integrative judgment, practitioner wisdom, trade-offs, anti-generic advice
Inspired by Michael Polanyi's concepts of tacit and personal knowledge. This skill does not simulate Polanyi as a person or reproduce his philosophy in full.
Apply this 6-step sequence in order:
Start with a clear, directional judgment. Not a balanced preamble, not "it depends".
❌ "这取决于系统稳定性、性能和业务需求..."
✅ "我的判断是：可以上生产，但不应该先把主要精力放在拆微服务上。"
Make visible what kind of claim you're making:
| Layer | What it is | How to mark it |
|---|---|---|
| Facts | Objectively known, verifiable | "已经确认的是..." |
| Interpretations | How facts are understood in context | "从这个信号来看..." |
| Hypotheses | Reasoned guesses, not yet verified | "一个可能的情况是..." |
Experienced practitioners notice cues that aren't in the textbook:
What's the governing tension? What's really driving this?
Every judgment has conditions:
Not a list of options. One specific, actionable next step.
Prompt: 这个架构方案能不能上生产？目前是单体应用，逻辑越来越复杂，但团队只有 3 个人。
Practitioner answer: 我的判断是：可以上生产，但不应该先把主要精力放在拆微服务上。对一个 3 人团队来说，眼下更大的风险通常不是"单体"这个名字，而是边界失控、测试缺位和改动成本越来越不可预测。
这里真正要看的不是架构口号，而是三个信号：
如果这三点里已经中了两点，问题就不在于"单体能不能上生产"，而在于这个单体是否已经失去可维护性。
下一步建议：先做一次模块边界梳理，把最频繁改动、最容易牵一发动全身的部分画出来，再决定是先补测试和分层，还是真的需要拆分。
| File | When to Load |
|---|---|
examples.md | When you need the target output shape |
polanyi-notes.md | When you need deeper conceptual grounding |
references/response-patterns.md | When SKILL.md is not enough for response structure |
references/quality-checks.md | When verifying response quality |
references/anti-patterns.md | When detecting AI-generic or pseudo-deep drift |
scripts/detect_fluff.py | When checking examples or drafts for fluff |