一键导入
document
apply documentation philosophy — explain why, not what. use for jsdocs, READMEs, inline comments.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
apply documentation philosophy — explain why, not what. use for jsdocs, READMEs, inline comments.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Interact with local Chrome browser session (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome)
orchestrate multiple amp agents with bidirectional tmux communication. use for multi-hour autonomous runs with INDEPENDENT parallel tasks. NOT for review courts or generating opinions to reconcile.
systematic investigation and debugging methodology. hypothesis-driven analysis with verification agents. use for incident response, codebase archaeology, dependency mapping, root cause analysis, or any investigation requiring verified findings.
git workflows for agents: ship (stage → commit → push), worktree (parallel branches), hunks (selective staging). never force push, never git add -A, conventional commits. triggers on: commit, push, stage, ship, git add, worktree, hunks, selective staging.
structured investigation-to-PR workflow for linear issues. hypothesis-driven debugging with browser validation and counterfactual proof. use when investigating a linear ticket, fixing a UI bug, or shipping a fix with evidence. triggers on: investigate issue, fix bug, nexus-fix, AXM-, linear issue.
record context that would help in future sessions. use after learning something, discovering a gotcha, or making a decision worth preserving. test: would a future agent starting fresh benefit from knowing this?
| name | document |
| description | apply documentation philosophy — explain why, not what. use for jsdocs, READMEs, inline comments. |
apply documentation philosophy: explain why, not what.
delete this:
/** context provider that wraps children in a DisclosureProvider. */
keep this:
/**
* blocks CompositeContext so nested Lists create isolated focus loops.
* essential for "Simple API" goal — our List is "greedy" and would
* otherwise join parent's arrow-key navigation.
*/
/**
* one-line description of purpose or behavior.
*
* additional context if design rationale is complex (keep brief).
*
* @prop propName - what it does
* @example
* ```tsx
* <Component>content</Component>
* ```
*/
preserve @bdsqqq notes or similar when they explain non-obvious decisions:
/**
* @bdsqqq notes: alpha colors avoided for strokes due to compounding
* overlap issues at intersection points.
*/
jsdocs are source of truth. upon finishing a task, colocate valuable context as jsdocs — only notes that explain non-obvious why. delete everything else.