菜单
Before making changes, verifies they match what was actually requested. Activates when about to modify files, add features, or refactor code. Catches scope creep before it happens - no "while I'm here" improvements.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | stay-in-lane |
| description | Before making changes, verifies they match what was actually requested. Activates when about to modify files, add features, or refactor code. Catches scope creep before it happens - no "while I'm here" improvements. |
| allowed-tools | file: read, edit |
Ask yourself:
## Scope Check
**User asked for:** [restate the request in one sentence]
**I'm about to:** [describe the change]
**Match?** [Yes / No / Adjacent]
| Match | Action |
|---|---|
| Yes | Proceed |
| No | Stop. Don't do it. |
| Adjacent | Ask first OR note it for later |
"Adjacent" means related but not requested:
For adjacent work:
The Helpful Refactor:
User: "Fix the typo in the error message" Claude: rewrites entire error handling system
The Preemptive Feature:
User: "Add a save button" Claude: adds save, autosave, save-as, and export
The Drive-By Cleanup:
User: "Update the API endpoint" Claude: also reformats file, adds types, updates imports
The Future-Proofing:
User: "Add user authentication" Claude: builds role-based permissions, audit logging, SSO
For significant changes, show scope alignment:
## Changes Made
**Requested:** [what user asked]
**Delivered:**
- [x] [matches request]
- [x] [matches request]
**Not done (out of scope):**
- [ ] [thing you resisted doing]
User: "Change the button color from blue to green"
Scope Check:
User asked for: Change button color blue → green I'm about to: Change the color value in the CSS Match? Yes
What to resist:
Correct response:
What DOESN'T work:Changed the button color from blue to green in
styles.css:47.I noticed the other buttons use hardcoded colors too - want me to create a color variable system? (separate change)
Generates Obsidian .base files from natural language descriptions. Translates requests like "show me all active project notes sorted by date" into valid .base YAML with filters, formulas, views, and summaries. Activates on "create base", "make a view", "show me all notes where", "dashboard", or when user wants structured views of their vault.
Generates Obsidian .canvas files from intent. Takes a description of what you want to visualise and produces valid JSON Canvas — mind maps, flowcharts, kanban boards, research canvases, project overviews. Activates on "create canvas", "make a board", "visualise", "map out", "mind map", or when spatial organisation of ideas is needed.
Manages daily notes workflow in Obsidian. Appends tasks, session logs, and learnings to today's daily note. Creates the daily note if it doesn't exist. Bridges Claude Code sessions to your daily note so nothing gets lost. Activates on "add to daily", "log this", "daily note", or end of session when daily notes are enabled.
Creates well-structured Obsidian notes with proper frontmatter, wikilinks, and template adherence. Detects available CLI (official, Yakitrak, or direct file write) and uses the best option. Reads vault conventions from CLAUDE.md before creating. Activates on "create note", "new note", "add to obsidian", or when creating markdown files in an Obsidian vault.
End-of-session ritual that syncs Claude Code session artifacts to an Obsidian vault. Chains breadcrumbs, retrospective, note creation, and daily driver into a single flow. Creates session notes, updates daily note, and leaves breadcrumbs. Activates on "sync to obsidian", "save session", "end session", or when user wraps up significant work in a vault-connected project.
Initialises an Obsidian vault for Claude Code workflows. Sets up folder structure, frontmatter conventions, templates, starter .base views, and a CLAUDE.md that describes the vault so future sessions understand it instantly. Activates on "set up obsidian", "init vault", "new vault", or first contact with an Obsidian project that has no CLAUDE.md.