菜单
Optional workflow skill for Notion-style worklogs, Todo roadmaps, and meeting notes. Use only when the user keeps worklogs in Notion or a similar workspace and wants verbose entries condensed for scanning.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | worklog-note |
| description | Optional workflow skill for Notion-style worklogs, Todo roadmaps, and meeting notes. Use only when the user keeps worklogs in Notion or a similar workspace and wants verbose entries condensed for scanning. |
| metadata | {"source":"born-here","summary":"Optional Notion 업무일지 정리 workflow","routing":{"visibility":"contextual","risk_level":"low","task_types":["reporting","worklog"],"triggers":[{"kind":"keyword","values":["노션용","업무일지","Done/Todo","worklog"]},{"kind":"intent","values":["summarize_work_for_notion"]}],"keywords":{"ko":["노션","업무일지","오늘 한 거","정리"],"en":["notion","worklog","done","todo"]},"use_when":["Notion이나 유사한 개인 업무일지에 오늘 작업을 Done/Todo 형태로 정리해야 하는 경우"],"do_not_use_when":["회사 Slack 일일보고처럼 프로젝트별 진척률이 필요한 경우"],"requires":["today_session_context"]}} |
노션 업무일지를 한눈에 들어오게 쓴다. 각 항목은 굵은 성과/목적 1줄(headline) 이 먼저 눈에 박히고, 세부는 최소로. 첫 줄만 훑어도 "오늘 뭐 했는지" 잡혀야 한다.
before → after (실제 예):
before (장황 — 스캔 안 됨):
[Dual Write 스택 확정]
- 프로젝트 내 데이터 전수 조사를 통해 팀장님의 TimescaleDB 일괄 도입 초안의
오버엔지니어링 파악 및 데이터 특성별 '하이브리드 스택' 선회 확정.
- 상태 변경이 잦은 sms_request ➡️ Pure PG 파티셔닝으로 선회 (created_at 기반
1시간 윈도우 파티션 프루닝 가드 설계).
- 해시 기반 단건 조회가 메인인 sms_scanresult ➡️ Plain PG 일반 테이블로 단순화.
- ... (5줄)
after (headline 1줄 + 세부 1줄):
- **Dual Write 스택 확정** — TimescaleDB 일괄 도입(오버엔지니어링) 기각 → 데이터 특성별 하이브리드 선회
- sms_request→PG파티션 / sms_scanresult·stats→Plain PG / audit_log→hypertable
[ ]. 자동 생성된 과세부 항목(메트릭명까지 박힌 것)은 한 단계 추상화.基于 SOC 职业分类
Use when starting a new session on a codebase, resuming interrupted work from a previous session, after making an architectural or design decision, or before ending a session or creating a PR — to create, update, or hand off docs/context/ project context files.
Use when a tool, command, sandbox, permission, network, dependency, or approval operation fails or repeats the same infrastructure error — classify the failure, cap retries, choose one bounded fallback, and stop before recovery consumes excessive tokens or time.
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture, setting up dependency injection, refactoring tightly coupled code, managing singletons or service factories, or when the user asks about inversion of control, service containers, or wiring dependencies in Go.
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code.
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.
Kotlin Coroutines and Flow patterns for Android and KMP — structured concurrency, Flow operators, StateFlow, error handling, and testing.
