메뉴
Log repeated or systemic workflow friction to FRICTION.md at the workspace root. Use only when explicitly invoked to capture avoidable backtracking, repeated manual workarounds, tool failures, or documentation gaps that should become automation, docs, or workflow fixes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Draft a GitHub pull request from the current conversation, branch diff, and repository PR template. Use when the user wants to review PR text before creating the PR with pr-create.
Provides the local command contract for HADL database credentials and tunnels. Use when an agent needs to inspect, traverse, or query HADL, Aquasense, Backoffice, staging, production, or windmill databases.
Restate the previous response in plain, concise language without jargon.
Manages project work with the Backlog.md CLI while preserving task metadata. Use when creating, viewing, searching, editing, implementing, or closing Backlog.md tasks, docs, decisions, acceptance criteria, Definition of Done checklists, or board workflows.
Builds portable TanStack Form composition for React apps. Use when adding, migrating, or reviewing composed form hooks, reusable field components, form options, validation, submit buttons, or form sections.
Creates cold-start-ready Backlog.md tasks through task shaping, codebase exploration, and focused questioning. Use when creating Backlog.md tasks, scoping feature work, capturing bugs, or preparing work for another agent.
| name | logging-friction |
| description | Log repeated or systemic workflow friction to FRICTION.md at the workspace root. Use only when explicitly invoked to capture avoidable backtracking, repeated manual workarounds, tool failures, or documentation gaps that should become automation, docs, or workflow fixes. |
| disable-model-invocation | true |
Append useful friction notes to FRICTION.md at the workspace or repository root unless the user explicitly names another path.
If the user provides enough detail, append an entry immediately.
If the user provides no detail, ask:
What friction should I log? Include the repeated trigger, workaround, and what would prevent it next time.
If the user provides vague detail, ask one clarifying question before writing.
Log repeated or systemic workflow friction:
Do not log one-off lint errors, ordinary coding mistakes, venting without a preventable cause, secrets, tokens, private keys, credentials, or full sensitive command output.
Create FRICTION.md lazily if it does not exist:
# Friction Log
Repeated or systemic workflow friction that should become automation, docs, or workflow fixes.
Preserve existing content and append new entries at the end. Omit the trigger suffix if no concise trigger is obvious.
## YYYY-MM-DD HH:mm - short trigger
- Trigger: What repeatedly caused friction.
- Workaround: What had to be done manually.
- Prevention: What automation, docs, or workflow change would prevent it.
Use the current local time. Keep entries factual and specific.