메뉴
This skill should be used when the user wants to write a daily journal entry, record what happened today, or reflect on the day. Triggers on '日記を書く', '今日の記録', '日記', 'daily note', 'write diary', '今日あったこと', '1日の振り返り', '日報', 'journal'.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | daily |
| description | This skill should be used when the user wants to write a daily journal entry, record what happened today, or reflect on the day. Triggers on '日記を書く', '今日の記録', '日記', 'daily note', 'write diary', '今日あったこと', '1日の振り返り', '日報', 'journal'. |
Obsidian Vault に日記を書く。Zettelkasten のノートとは独立した時系列の記録。
~/Documents/Zettelkasten
04-Daily/
日記の中に知見が含まれる場合は、その知見を Fleeting Note として切り出すことを提案する。日記本体には知見を残さない。
YYYY-MM-DD.md（例: 2026-06-21.md）
---
date: 2026-06-21
tags:
- daily
---
本文は自由記述。ユーザーが話した内容をそのまま自然な日本語で記録する。箇条書き・散文どちらでもユーザーの話し方に合わせる。
当日に作成された Zettelkasten ノートがあれば、末尾の「今日書いたノート」セクションに wikilink で列挙する。
## 今日書いたノート
- [[ノート名1]]
- [[ノート名2]]
04-Daily/ ディレクトリの存在を確認する。なければ ${CLAUDE_PLUGIN_DIR}/assets/note-format.md の「Vault セットアップ」に従って初期化する（pre-commit hook のセットアップを含む）${CLAUDE_PLUGIN_DIR}/assets/note-format.md の「Pre-commit Hook セットアップ」に従って設置するgit log で検出し、「今日書いたノート」セクションに追記する[[wikilink]] が Vault 内の既存ノートに解決できることを確認する。解決できないリンクがある場合は、リンク先のノートを作成するか wikilink を修正する