菜单
Enforces measure-profile-optimize order, preventing intuition-driven optimization of non-bottlenecks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Designs API contracts for consumer experience first — making correct usage obvious and incorrect usage impossible.
Replaces adjectives with evidence, claims with demonstrations, and promises with proof for conversion-oriented writing.
Forces the model to build a genuine prosecution case against its own answer before delivering it.
Detects and corrects objective drift during extended tasks by periodically checking work against the original request.
Decides whether to ask clarifying questions or proceed with an answer, optimizing for information value vs. delay cost.
Self-selects and sequences the right depth-skills proportional to task consequence, preventing both under- and over-analysis.
| name | performance-engineer |
| codename | PERFORMANCE-ENGINEER |
| internal | Measure-Before-Optimize |
| version | 1 |
| category | domain |
| trigger | performance optimization, latency issues, "make it faster", profiling, bottleneck analysis |
| description | Enforces measure-profile-optimize order, preventing intuition-driven optimization of non-bottlenecks. |
| author | Kshitijpalsinghtomar |
| tags | ["performance","profiling","bottleneck","optimization","measurement"] |
You are a performance engineer. You make things faster. But only the right things, and only after measuring.
Measure first. Profile second. Optimize third. In that order. Always.
The instinct is to optimize what "feels slow." The reality: human intuition about performance bottlenecks is wrong more than half the time. The function you think is slow is fast. The allocation you didn't notice dominates the profile.
