菜单
This skill should be used when the user explicitly asks to write a note, save a memo, or record something in the Zettelkasten vault. Triggers on 'これ書いて', 'メモして', 'ノートにして', 'Zettelkastenに保存', 'write this down', 'save this note', 'record this', 'これを記録して', 'ノートを作って'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | note |
| description | This skill should be used when the user explicitly asks to write a note, save a memo, or record something in the Zettelkasten vault. Triggers on 'これ書いて', 'メモして', 'ノートにして', 'Zettelkastenに保存', 'write this down', 'save this note', 'record this', 'これを記録して', 'ノートを作って'. |
ユーザーが明示的にノートの書き出しを指示した時のインターフェース。
${CLAUDE_PLUGIN_DIR}/assets/note-format.md に従ってノートファイルを作成する${CLAUDE_PLUGIN_DIR}/assets/note-format.md の「Vault セットアップ」に従って初期化する（pre-commit hook のセットアップを含む）${CLAUDE_PLUGIN_DIR}/assets/note-format.md の「Pre-commit Hook セットアップ」に従って設置する[[wikilink]] が Vault 内の既存ノートに解決できることを確認する。解決できないリンクがある場合は、リンク先のノートを作成するか wikilink を修正するAuto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
Internal project-context placement and consistency reference used by context refactoring and verification workflows.
This skill should be used when the user asks to "audit project standards", "check standards compliance", "devkit audit", "find standards violations", "are we following devkit standards", "what's not following standards", "compliance report", "規約チェック", "スタンダード監査", or "規約違反を探して". It actively scans code and reports violations. Do NOT use for project scaffolding (use init-project), single-CLI-tool checks (use cli-compliance), or looking up what the standards are (use standards).
This skill should be used when the user asks to "set up a project", "choose a tech stack", "establish coding standards", "configure linting", "set up tests", "pick a framework", "review code quality", "set up logging", "configure observability", "choose an ORM", "set up auth", "set up Storybook", "write stories", "visual testing", "CSF", "coverage threshold", or discusses any technology choices for a TypeScript project. Also use when starting a new project, setting up CI/CD, choosing between tools (oxlint vs ESLint, pnpm vs npm), configuring environment variables, or when any other devkit skill needs to reference project conventions. This is the central reference for all devkit technology decisions and coding principles.
Review whether the current code satisfies a GitHub issue, then update the issue status to match. Use when the user asks to 'review an issue', 'check if an issue is done', 'is this issue resolved', 'update issue status', 'issueの対応状況を確認', 'issueが完了しているかレビュー', or 'issueのステータスを更新'.
This skill should be used when the user asks to 'create a skill', 'add a new skill', 'make a skill', 'scaffold a skill', 'new skill', 'スキル化して', 'スキルを作成', 'スキルを追加', or wants to create a new Claude Code skill for a plugin or project. Provides a guided workflow with automated scaffolding, validation, and dynamic context injection.