dot-claude-code
dot-claude-code에는 mateusoliveirab에서 수집한 skills 9개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.
이 저장소의 skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
A relentless interview to sharpen a plan or design.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Reviews text for weasel words, vague language, and corporate jargon using Amazon's writing principles. Returns flagged issues and a polished version. Use when drafting Slack updates, PR descriptions, Jira tickets, or any professional communication that needs to be direct and concrete.
Captures high-value learnings from a skill execution and applies targeted improvements to the SKILL.md. Generic: works for any skill. Invoke right after running a skill when steps diverged from the documented flow, new techniques were discovered, or undocumented edge cases appeared. Synthesizes from conversation context automatically.
Audits and rewrites CLAUDE.md files. Use when the user asks to review, optimize, rewrite, standardize, or improve a CLAUDE.md file. Triggers include "audit claude.md", "otimiza o claude.md", "melhora o claude.md", "padroniza claude.md", "review CLAUDE.md". Also use when someone says "clean up my docs", "my claude context is messy", or asks to "initialize" context files in a project.
Pre-close session review. Scans for loose ends before ending a conversation — documentation gaps, unsaved memory, open checklist items, uncommitted git changes, and notification gaps. Reports findings grouped by category; never acts without confirmation. Invoke at the end of any work session before signing off.
Mid-session quality gate. Acts as a skeptical senior engineer arriving cold after the work is done. Auto-detects work domain (code, scripts, docs, communication), applies universal and domain-specific lenses, and outputs a READY / NEEDS WORK verdict. Use between finishing work and closing the session. Can be iterated: /validate → fix → /validate → conclude.
What this skill does and when to use it. Include keywords that help agents identify when to activate it.