family-experiment-tracking
Skill0 starsChanged 2 months agoMITView on GitHub
家庭成长实验的逐日记录、数据核算与判定日准备。触发:纸面实验/跟踪记录/孩子用卡/家庭实验复盘。
In this repository19 other files it gives its agents.
- cross-domain-borrowSkill
- daodejing-overviewSkill
- expert-panelSkill
- fact-check-claimSkill
- first-principlesSkill
- ian-xiaohei-illustrationsSkill
- jingang-dialogueSkill
- life-designerSkill
- macos-app-installSkill
- meeting-action-itemsSkill
- min-experiment-designSkill
- reverse-deconstructSkill
- skill-authoringSkill
- socratic-interviewSkill
- steelman-decisionSkill
- talent-diggerSkill
- third-party-handoverSkill
- two-layer-explainSkill
- weekly-review-planningSkill
The file
Files
家庭成长实验跟踪(纸面实验类)
一句话:师兄每天口述当天发生的事,Hermes 落档案、核算数据、提炼信号、维护预案——先记事实,写不写文等他拍板。
落档与命名
- 位置:
LifeOS/30-39 家庭成长/(隐私区,永不进 GitHub、不进任何远端,agent 只记位置不抄内容到报告); - 文件名守宪法格式
YYYY-MM-DD-HHMMSS-内容.md(先取机器时间再写); - 每天的事件追加进既有跟踪记录,不新开文件;判定日/总结再另开文档。
每日追加模板
用卡记录(谁 / 哪张卡 / 换掉或拒了什么 / 家长反应)→ 关键事件(原话优先)→ 家长侧破功计数 → 共学家庭进展 → 当日状态。师兄口述没提的项直接省略,不要补编状态。
硬规则
- 匿名代号:孩子用单名(无姓、无正脸、无学校小区);对外文章口径以师兄当期拍板为准,两套代号并存时以最新一次为准;
- 累计数据行是"替换"不是"追加":用卡次数/破功次数这类累计统计每次改写旧行;改写后回读校验,否则多版数据并存互相矛盾;
- 分歧原样并记、不裁决:两位家长立场不同时(如"自主性好" vs "被安排惯了"),两种解释都写进档案并标注为判定日议题——师兄认可这种诚实,不替他选边也不和稀泥;
- 区分"拒绝的对象"与"动机":孩子拒绝某活动时记清是拒绝被安排的感觉还是活动本身(判断依据:拒绝当天该活动的动机端是否在增强、孩子是否仍参与商量);
- 用卡后的去向才是数据:只记次数不足以判定,要跟"用卡后去做了什么"(做真实贡献 vs 纯消遣)——散漫与否的判据在这里。
预案分层(判定日前必须都写好)
- 预案 A 恐惧/拒绝型:改判词("先不弄了,谢谢你们说真话")+ 产品搁置,判定不是实验失败而是诊断成立;
- 预案 B 散漫不恢复型:先分两本账(自主性账 / 节律账)→ 给孩子的判词("权利永远有效,现在进入下一关:学会不只是拒绝,还要自己安排")→ 加"安排卡"(拒绝后须自提替代方案)→ 提前定死"无法恢复"的量化硬标准,避免判定日各说各话;卡永远不收回,它是信任的锚。
汇报与协作纪律
- 当天记完回复 3-5 句要点,不写长文;
- 有公众号素材价值时只记事实并问师兄是否成文(曾虚报"已写好"实际未落盘的教训);成文配方见 content-pipeline 的「实验/跟踪类连载文配方」;
- 要给师兄看全文时,先把文件复制到无空格路径再给预览指令,预览指令的引号必须是 ASCII 直引号(见 content-pipeline 预览三层坑);
- 判定日前主动与师兄确认现行判定标准、两本账口径与"无法恢复"硬标准,并给他备"第一句话"讲稿。
版本演进
(本节由每轮实验结束后追加一行:起止日期 / 参与人数 / 新增规则——保持一段话以内,别堆事故叙事。)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

