Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
One sentence that describes WHEN to invoke this skill. Write it as a trigger phrase, not a summary — include the words a user would say ("fix bug", "add feature", "review diff"). The agent routes on this field.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Without this skill, the agent tends to <failure mode>. This skill enforces <the alternative>.
| Thought | Reality |
|---|---|
| "I've done this before, I don't need the checklist" | Skills evolve; re-read the current SKILL.md. |
| "This case is simple" | Simple cases become complex mid-task. |
| "The user didn't ask for this rigor" | The user asked for a working result. Rigor is how you get one. |
Every skill ships with a real before/after pair proving it changes agent behaviour on a concrete task. Without this, the skill is a claim, not a tool.
evidence/before.md — a verbatim snippet of what the agent does on a
representative task WITHOUT this skill loaded. Include the prompt, the
agent's response, and what went wrong (or what got skipped).evidence/after.md — the same prompt with this skill loaded. Show the
changed behaviour and why it is better.If you cannot produce a before/after pair, the skill is not ready to ship. Land it as a draft in a branch, gather the evidence, then merge.
references/<topic>.md (only if needed; keep the body lightweight)아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt at session start — prose is for humans, JSON is for the loop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything else. Kills the "looks shipped, isn't shipped" bug across sessions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.