원클릭으로
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.