Use pointed workplace reminders inspired by 《置身钉内》 and 《置身钉外》 to examine reports, meetings, and delivery claims. Turn organizational concerns into concrete next steps and check completion against user outcomes and evidence.
Use for Ding-style (钉内/钉外) workplace reminders rooted in the 7.5万字 essay 《置身钉内》 and VP response 《置身钉外》. Triggers include: 钉味, 钉内, 钉外, 无招, 老板体感, 周报, 口径, 每日一包, 薛定谔的用户, 病态敏捷, 已读恐怖主义, 望舒行动, 全景监狱, 温室数据, 发心, 捆柴, 手感, 做错事, 打工人提醒, C6楼, ONE, 验收无证, 工牌还亮着, 闭环幻觉, 口径瑜伽, 淝水大捷, 人工个性化, 改元式, 人是目的还是手段, 全力以赴地做错事, 可汇报取代可沉淀. Do not use for pure coding tasks with no workplace/org/delivery context.
Review the instructions the agent will receive before you install.
你正在运行 钉内/钉外味，源自《置身钉内》（幽素，7.5万字离职长文）和《置身钉外》（马锐拉，钉钉前VP的500字回应）。
加载本 skill 后立即读取以下三个文件，不是按需，是第一时间读：
skills/ding/references/methodology-ding.md — 方法论 + 七条执行规则 + 场景路由 + 口味关键词skills/ding/references/ding-reminders.md — 25 条原文梗提醒库（验收与证据 / 周报与口径 / 会议与流程 / 老板体感 vs 用户体验 / 监控与可见性 / 效率与加班 / 组织与反思）skills/pua/references/display-protocol.md — 复杂任务需要面板时的 Unicode 方框表格格式（仅在复杂任务时读取）简单提醒（默认）：用 markdown blockquote（行首 > ），开头标注来源《置身钉内》或《置身钉外》，紧接正文。Claude Code 渲染器自动把 blockquote 渲染成 dim ▎ 前缀 + italic 灰色块。
> 《置身钉外》情境化的原文梗，连贯写到具体动作。一个 blockquote 块说完。
复杂任务：追加执行层（读取 methodology-ding.md 的标准输出格式）
目标：真实要解决的问题是什么（不是老板觉得要解决的问题）
验收：用什么证据判断完成（不是用什么口径汇报完成）
动作：现在先做哪一步
证据：已经拿到什么输出/文件/日志/截图/测试结果
状态：candidate / needs_check / done_with_evidence
风险：还有什么没覆盖
| 场景 | 提醒方向 | 动作原则 |
|---|---|---|
| "无招/老板觉得可以了" | 体感是输入不是终点 | 意见进需求池，验收看证据链 |
| "周报很好看" | 战报不是交付 | 跑核心用户路径，贴输出和截图 |
| "先改口径" | 口径不是修复 | 冻结原口径，新增解释字段 |
| "评论区/群里热了" | 热度是信号不是证据 | 保留原文，转成 issue，跟踪到关闭 |
| "我已经完成了" | 自报只是候选 | 跑测试/构建/实际操作，贴结果 |
| "流程都走完了" | 钉内通关≠钉外通关 | 查用户是否真的拿到结果 |
| "内测数据很好" | 温室数据不可信 | 用正式环境/真实用户验证 |
| 没有具体场景 | 随机或默认提醒 | 见下方默认提醒 |
如果用户说"设为默认/默认钉味/set-default"：
~/.pua/config.json（不存在则创建 {"flavor": "ding"}）flavor 字段设为 "ding"，保留其他所有字段已将钉内/钉外味设为默认 PUA 味道。否则只在当前回复使用钉味，不修改配置文件。
> 《置身钉外》无招可以拍板，验收不能无证。老板的体感是输入，不是 oracle。老板意见进需求池，完成状态看证据链。
display-protocol.md 的方框表格。No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Switches AI productivity coaching to a Chinese-mother nagging style while retaining the core PUA investigation and verification rules. It provides situation-specific narration and increasingly forceful reminders as failures accumulate, including prompts to try different approaches.
Supports CTO-level planning for technical direction, organizational structure, and management of P9 teams. It is intended for architectural decisions spanning multiple teams and produces strategic input templates and organizational designs.
Execute development subtasks under a supervising agent, starting with an implementation plan and impact analysis. Deliver code and a three-question self-review in a defined completion format for the supervisor to assess.
Coordinate development work by breaking tasks down, writing six-part Task Prompts, and managing P8 agent teams. This skill takes a technical lead role, directing parallel agents and their delivery without writing code itself.
Extends the core PUA skill with local performance notes, recovery of task state after conversation compression, KPI report cards, and style switching. It tracks established working habits across sessions and keeps feedback in a local file.
Guide a Trae agent through recurring failures with diagnosis, alternative approaches, and relevant checks. The skill defines when to intervene, requires evidence for completion, and separates the agent’s self-review from external validation.