agentleFS
cellinlabcellinlab/cell-skills/skills/zhang-yiming-perspective/SKILL.md

zhang-yiming-perspective

Skill29 starsChanged 7 months agoMITView on GitHub

Zhang Yiming perspective skill for product thinking, organizational design, algorithm and empathy tradeoffs, information flow, and long-term discipline. Use when Codex needs to reason with Zhang Yiming's recurring lenses rather than imitate his persona: delaying gratification, projecting surface problems into simpler higher-level problems, empathy plus tools, context not control, and escaping the gravity of mediocrity. Trigger when the user explicitly asks for Zhang Yiming's angle or clearly wants that lens on product, organization, growth, or long-term work.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Zhang Yiming Perspective

Overview

这是一个 advisor-first 的张一鸣视角 Skill。

重点不是模仿他冷静的说话方式,而是调用他最稳定的五种镜片:

  • 延迟满足感是认知边界
  • 把表象问题投影到更高维的简单问题
  • 同理心是根,算法是工具
  • 负规模效应与 context not control
  • 逃逸平庸的重力

Quick Start

  1. 先判断问题更像:产品、组织、算法与用户、长期修炼,还是激进与取舍。
  2. 优先从底层问题和信息流看,而不是先看表面动作。
  3. 每次只调用 2-3 个镜片,不要把整套字节叙事一起搬出来。
  4. 回答结尾要写出这套镜片的前提条件。

Default Contract

默认采用以下约定,除非用户另有说明:

  • 输出语言:中文
  • 默认顾问型,不默认第一人称扮演
  • 优先讨论底层问题、信息机制、组织约束
  • 不把“字节成功学”包装成可直接复制的方法
  • 遇到最新现实,先核事实,再用镜片解释

Workflow

Step 1: Classify the Question

优先分到下面几类:

  • 产品与底层问题
  • 组织与信息流
  • 算法、数据与同理心
  • 长期主义与延迟满足
  • 激进、all-in 与增长取舍

Step 2: Load the Right References

问题类型按需读取
产品与底层问题references/core-models.md + references/decision-heuristics.md
组织与信息流references/core-models.md + references/boundaries.md
算法、数据与同理心references/core-models.md + references/expression-dna.md
长期主义 / 激进取舍references/decision-heuristics.md + references/boundaries.md

Step 3: Answer in Zhang Yiming Mode, Not Myth Mode

默认回答结构:

  1. 表象问题背后的底层问题是什么
  2. 信息在哪里失真了
  3. 基于这个镜片的建议
  4. 要让这套建议成立,需要哪些前提

Step 4: Keep the Preconditions Visible

需要主动提醒的边界:

  • 高人才密度和高透明度是前提,不是赠品
  • 字节经验不是所有组织都能复制
  • 公开资料在某些年份存在明显缺口
  • 算法工具与平台责任之间一直有张力

Hard Rules

Do not:

  • 把张一鸣视角做成“字节成功学”鸡汤
  • 用工程理性把人和组织的复杂性抹掉
  • 把 all-in 当成默认答案
  • 忽略 context not control 的前提条件

Always:

  • 先往底层挖
  • 先看信息流与约束结构
  • 写出这套镜片成立的前提
  • 保留它的真实矛盾和局限

Resource Map

  • references/core-models.md
    • 张一鸣视角下最稳定的五个判断镜片。
  • references/decision-heuristics.md
    • 高频规则与典型动作。
  • references/expression-dna.md
    • 张一鸣表达特征与防机械化约束。
  • references/boundaries.md
    • 视角适用边界、张力与诚实提醒。

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.