All authors

Claude Skills by uzysjung
github.com/uzysjung24 skills1 installs2 views
- Audit Harness FitImprove agent instructions and skills for autonomous, productive delivery with verifiable quality. Resolve needless questions, repeated checks, conflicting decisions, missing actionable context, and low-value procedures; adapt guidance to demonstrated model and tool capabilities. Also fill or refresh AGENTS.md / CLAUDE.md project context from repository evidence. Use for harness review, cleanup, rule conflicts, or context scaffolding, not ordinary feature implementation.Votes: 0GitHub stars: 3
- Audit Service GapsAudits the observable gaps between a service as it is today and an explicit target state, then researches how reference services actually solved each high-ranked gap before proposing a fix. DETECT scans through three independent lenses — north-star alignment, correctness (bugs), and user-perspective (UX) — and enumerates concrete, severity-ranked gaps; BENCHMARK verifies how a reference service closes each one and PROPOSES a differentiated close. VERIFY, CHANGE-IMPACT, DRIFT and FULL extend t...Votes: 0GitHub stars: 3
- Compaction HandoffCreate a compact, reconstructible checkpoint immediately before context compaction. Persist only durable facts and decisions, overwrite one current resume anchor, verify Git and open-PR state, and emit one concrete next action plus a short /compact line. Use for "컴팩션 준비해줘", "컴팩션하고 이어서 진행할 수 있게 준비해줘", "핸드오프 준비해줘", or "prepare for compaction", or equivalent. Repeated execution must be idempotent and must not grow state files without bound.Votes: 0GitHub stars: 3
- External Model ConsultConsult a second, non-Claude model through a bundled wrapper for four things: (1) natural, native-sounding KOREAN phrasing via Google Gemini — copy, UI microcopy, marketing text; (2) a MULTI-PERSONA / second-opinion review of a design, plan or spec; (3) CONCISE, well-STRUCTURED writing via OpenAI Codex — tightening prose, restructuring a doc; and (4) IMAGE GENERATION as real image files on disk (not labeled diagrams — use Mermaid). Fire it when Korean reads translated, or when you would other...Votes: 0GitHub stars: 3
- Gh Issue WorkflowRuns work through GitHub Issues so the user and the agent can see the same backlog: normalize an incoming request into an issue before building, group tasks under a parent (epic) issue, order them with milestones and priority labels, read every comment before starting, and promote decisions out of comments into the issue body so they survive. Enforces the body template (배경/문제/근거/레퍼런스/제안/전제/방향성/AC/후속) so issues become reusable agent context, and keeps read-only, draft, remote-write, implement,...Votes: 0GitHub stars: 3
- Model OrchestrationSelect models, reasoning effort, and delegation boundaries for a task. Use when choosing direct execution versus subagents, allocating parallel work or independent review, or reducing multi-agent token and context overhead. Favor context reuse and add model calls or workers when their expected contribution justifies the cost.Votes: 0GitHub stars: 3
- Multi Persona ReviewA panel-review skill that critiques ONE artifact (launch post, README, doc, markdown, plan, design) via 3-5 disjoint user-perspective personas running in parallel, then synthesizes deduped, severity-ranked improvement points (P0/P1/P2). Use when the user says "작성글을 사용자 관점의 페르소나를 여러명 만들어서 (손넷 모델정도로) 피드백 받아바", "다면 리뷰 해볼까", "페르소나로 리뷰", "여러 관점으로 피드백", or in English "multi-persona review", "review this from different user perspectives", "get persona feedback on this post/README/doc", "panel review...Votes: 0GitHub stars: 3
- North StarDefines and enforces a project's long-term direction (North Star Statement, metric-as-proxy NSM, strategic Pillars with a module↔pillar map, Will/Won't, 4-gate + priority-order decision heuristics), then turns that direction into a ranked, persisted roadmap so the plan survives /compact and new sessions. Use when starting a new project, when scope creep is suspected, when a non-obvious feature request needs prioritization, or when the user asks where the project should go next. Sits one layer...Votes: 0GitHub stars: 3
- Objective BriefRewrite work about to be delegated, designed, or run over several steps into the canonical XML brief — objective, inputs, invariants, success_criteria, boundaries, autonomy, verification, communication, output_format — so the worker receives one judgeable definition of done instead of prose. Runs in two directions: INBOUND reshapes a sprawling or half-formed request into that shape, filling each field from context already on screen and dropping sections that do not apply; OUTBOUND writes the ...Votes: 0GitHub stars: 3
- Recurrence PreventionWhen the same defect, mistake, or incident happens AGAIN — a recurrence, not a one-off — verify it against prior evidence (memory, rule 근거 links, git/CHANGELOG history), classify it as a simple slip vs a complex harness problem, then re-evaluate the countermeasure that failed: repair or replace it, choosing a record, a one-line criterion, a code fix, or a structural gate (test, hook, derive) by evidence — more deterministic when prose has demonstrably failed, nothing new when repair suffices....Votes: 0GitHub stars: 3
- User Centered Explanation개발 중 문제·변경안·선택지를 사용자 행동과 결과의 관점에서, 사용자의 언어로 설명한다. 맥락·원인·대안·추천 이유를 연결하고, UI/UX 변경은 필요한 화면·문구·동작의 전후 차이를 보여준다. 사용자가 "뭔 소리야", "쉽게 설명해줘", "왜 문제야", "사용자에게 뭐가 달라져?", "화면으로 보여줘", "선택지와 추천을 정리해줘"라고 하거나 중요한 선택·승인의 차이와 근거를 설명할 때 사용한다. 이 스킬만 호출하면 현재 대화의 미해결 문제나 직전 선택 요청을 사용자 관점으로 재정리한다.Votes: 0GitHub stars: 3
- Decisions- Status: Accepted - Date: 2026-07-18 - PR: #216 - Context: 사용자 지시(2026-07-17, Lean 큐 ⑤): "장애나 결함, 하네스 진행하면서 동일 이슈가 여러 번 발생하면 — 재발방지 대책이 깜박한 것 같이 단순 실수면 기록하거나 룰을 강제해서 등록하게 하고, 복잡한 하네스 문제이면 다면 페르소나로 해결책을 만드는 스킬을 만들자." 본 repo 는 이 관행을 이미 반복 실행해 왔으나(no-false-ship: 3회 재발 후 rule 신설 + 사례표 / CHANGELOG 7릴리즈 drift → same-commit 테스트 게이트 / 하드코딩 목록 drift 2회 → "주석 경고 ≠ 차단 수단, derive 단일화"), 문서화된 자산이 없어 사용자 프로젝트에 전달되지 않았고, 에스컬레이션의 판단 기준(언제 기록으로 충분하고 언제 게이트가 필요한가)이 세션 기억에만 있었다. - Decision: 1. **`recurrence-pr...Votes: 0GitHub stars: 3
- Decisions- Status: Accepted - Date: 2026-08-02 - PR: #273 - Amended by: ADR-084 (2026-09-13) — Decision 1·2(5단계 · 3근거 판정 프레임)는 대체됐다. 3·4(전 트랙 기본 · 임의 프로젝트 동작)는 현행 - Context: 사용자 제안(2026-08-02) — "공식 문서 2편(prompting-claude-opus-5 · claude-code-power-user-tips)의 CLAUDE.md·rule·hook 관점을 기반으로 하네스 정리 스킬". 두 문서는 반대 방향의 루프 한 쌍이다: power-user-tips 는 축적 루프(실수→CLAUDE.md 추가, 강제는 hooks·permissions 로), opus-5 프롬프팅 문서는 감량 루프(검증·재확인 지시 제거 — "legacy harness scaffolding" 명시, 부정문→긍정 예시, 심각도 억제 지시의 문자적 순종 함정). 축적 루프만 있으면...Votes: 0GitHub stars: 3
- Audit Service GapsFinds and prioritizes observable service gaps against an explicit target across north-star alignment, correctness, and UX, then verifies reference solutions before proposing fixes for high-ranked gaps. Use for "갭분석", "북극성 기준으로 부족한 점", reference-service benchmarking, post-fix verification, changed-baseline impact, doc-code drift, or full-service audits. Product direction belongs to north-star; single-artifact critique to multi-persona-review. Keep unverified benchmark claims labeled.Votes: 0GitHub stars: 3
- Compaction HandoffCreates a reconstructible checkpoint before manual or automatic context compaction or a session handoff. Use for "컴팩션 준비해줘", "핸드오프 준비해줘", or prepare-for-compaction requests. Preserves durable facts and decisions, verifies Git/PR state, and overwrites one bounded resume anchor with one concrete next action and a short /compact pointer. Repeated runs are idempotent.Votes: 0GitHub stars: 3
- External Model ConsultUses bundled CLI wrappers for Gemini Korean copywriting/polishing and different-model critiques of designs, plans, or specs; Codex prose tightening/restructuring; and image-file generation (Codex default; Gemini for Gemini/Nano Banana requests). Use for polished user-facing Korean, translated-sounding text, substantive concision/structure work, image requests, or asking Gemini/Codex: "자연스럽게 다듬어줘", "제3자 관점", "간결하게 정리해줘", "이미지 만들어줘". Returns candidates or image files; never auto-applies. Not fo...Votes: 0GitHub stars: 3
- Gh Issue WorkflowOrganizes work through GitHub Issues: drafts, epics/sub-issues, milestones, priorities, implementation, verification, and status. Use when work outlives the chat turn, needs ordering for user review, or requests issue/backlog work ("이슈로 등록해줘", "에픽으로 묶어줘", "#42 작업해줘", "우선순위 다시 잡자"). Normalize requests before building, read all comments, and preserve decisions in issue bodies. Remote issue or project-board changes require the user's request; reading and drafting do not authorize writes.Votes: 0GitHub stars: 3
- Multi Persona ReviewReviews one artifact (post, README, document, plan, or design) through 3-5 distinct target-user personas in independent parallel reviews, then deduplicates and prioritizes concrete improvement candidates. Use for "다면 리뷰", "페르소나로 리뷰", "여러 관점으로 피드백", or multi-persona/panel review requests. Not for whole-service/codebase audits or gap-versus-benchmark analysis; those belong to audit-service-gaps.Votes: 0GitHub stars: 3
- Natural Korean한국어 답변·글쓰기·번역·퇴고에 사용한다. 뜻과 말투를 살리면서 번역투·불필요한 영어·상투구·기계적 반복을 줄인다. "자연스럽게 다듬어줘", "AI 티 없애줘", "번역투 고쳐줘", "문체 진단" 요청에도 적용한다.Votes: 0GitHub stars: 3
- North StarDefines long-term product direction, a North Star metric, strategic boundaries, and alignment criteria, then applies them to a prioritized, persisted roadmap. Use at new-project startup, suspected scope creep, non-obvious feature-priority decisions, direction reviews, or "앞으로 어떤 방향으로 발전시킬까", "북극성 정렬 로드맵", and roadmap/feature requests based on NORTH.md or NORTH_STAR. Answers why and where to go above SPEC/PRD; consumes audit findings rather than detecting current bugs, gaps, or regressions.Votes: 0GitHub stars: 3
- Objective BriefStructures requests and worker prompts into the canonical XML task brief, using existing context to state the objective, constraints, and verifiable completion criteria. Use for "브리프로 정리", "작업 지시서로 만들어", "프롬프트 구조화", or task-brief requests. Apply proactively before multi-part delegation to subagents, workflow workers, or parallel lanes, and before feature- or project-scale design or multi-step execution. Omit inapplicable fields; skip one-line questions, lookups, single edits, and routine chan...Votes: 0GitHub stars: 3
- Recurrence PreventionVerifies reported or detected recurrence against prior evidence and repairs or replaces the failed countermeasure, choosing a proportionate record, rule, code fix, or structural gate. Use for "재발했어", "같은 실수 또 했네", "재발방지 대책 등록해줘", "재발방지 룰 만들어", recurring failures, failed safeguards, or recurrence-focused postmortems. Complex cases use multi-persona countermeasure design. Not for ordinary first-time defects or general harness audits; do not create a standing rule from an unverified first occurr...Votes: 0GitHub stars: 3
- Self Hosted Github RunnerGitHub 호스티드 러너의 결제·사용량·쿼터·장애 문제로 CI가 막혔을 때, 기존 워크플로를 복제하지 않고 Docker self-hosted runner에서 실행하도록 돕는다. "CI를 로컬에서 돌리자", "self-hosted runner", "act로 돌릴까", "CI가 멈췄는데 머지·배포는?" 또는 CI 스텝을 로컬 스크립트로 옮기자는 제안에도 사용한다. PR·배포 게이트 복구와 로컬 실행 목적을 구분해 runner 또는 act를 선택한다.Votes: 0GitHub stars: 3
- Ui Visual ReviewCaptures and compares key UI-flow screenshots after E2E tests pass on UI tracks (csr-*, ssr-*, full), flags visual regressions and console errors, and prepares findings for user approval. Also owns browser-launch rules: read before opening any browser via Playwright, chrome-devtools MCP, or a launcher. Use for manual E2E checks, reference-product UX/fidelity comparisons, OAuth login, automated capture, or reported browser lag.Votes: 0GitHub stars: 3