uzysjung

@uzysjung source repo

21 skills
0 followers
9 hours ago last updated

▌
UI Visual Review 2 · uzysjung
Captures screenshots of key UI flows after E2E tests pass, runs an agent-side first-pass diff (regressions, console errors, layout shifts), then surfaces a checklist for the user's final approval. Also owns the browser-launch rules AND procedure — read it BEFORE opening a browser by any means (Playwright, chrome-devtools MCP, a launcher script), not after something feels slow: the prohibitions here exist because attaching to the user's live Chrome or using a throwaway context degrades the session in ways that are expensive to undo. Fire it for manual E2E checks, UX/fidelity comparison against a reference product, a one-time OAuth login, automated capture, and whenever the user reports the browser is laggy. Use after E2E tests pass on a UI track (csr-*, ssr-*, full).

0
installs
▌
North Star · uzysjung bundle
Defines 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 above SPEC/PRD — answers 'why and where to', not 'what and how'. Fires on the user's real phrasings: "앞으로 어떤 방향으로 개선·발전시킬지 고민해봐", "NORTH.md / NORTH_STAR 보고 나아갈 방향 + 기능 제안", "북극성 정렬 로드맵", and the English "what direction should we take next", "propose a roadmap from the north star". Do NOT use it to find what is broken right now — detecting bugs, gaps, or quality regressions belongs to the audit/gap skills; this skill consumes their findings and DIRECTS forward planning.

0
installs
▌
Task Brief · uzysjung
Rewrite a task request 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 deleting sections that do not apply; OUTBOUND writes the prompt that a spawned worker actually receives. Trigger on "브리프로 정리", "작업 지시서로 만들어", "프롬프트 구조화", and in English "turn this into a task brief", "structure this prompt". Fire unprompted the moment you are about to hand a multi-part task to a subagent, a workflow worker, or a parallel lane. Do NOT fire on a one-line question, a lookup, or an ordinary conversational exchange where you simply need one more piece of information — asking a clarifying question is not a brief, and wrapping a one-sentence ask in nine XML tags costs more than it buys.

0
installs
▌
Eval Harness · uzysjung bundle
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles

0
installs
▌
Spec Scaling · uzysjung
Detects when SPEC.md or PRD.md exceeds 300 lines and proposes feature-based splitting with a master route document. Use when SPEC.md grows too large to be effectively used as a single document.

0
installs
▌
Deep Research · uzysjung bundle
Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.

0
installs
▌
UI Visual Review · uzysjung
Captures screenshots of key UI flows after E2E tests pass, runs an agent-side first-pass diff (regressions, console errors, layout shifts), then surfaces a checklist for the user's final approval. Also owns the browser-launch procedure the `playwright-launch` rule delegates here: use it whenever a browser must be opened for a human to drive or for automated capture — manual E2E checks, UX/fidelity comparison against a reference product, or a one-time OAuth login. Use after E2E tests pass on a UI track (csr-*, ssr-*, full).

0
installs
▌
Audit Harness Fit · uzysjung bundle
Audits the resident steering layer — CLAUDE.md/AGENTS.md and its `@import` chain, `.claude/rules/`, hooks, permission rules, and the skill descriptors preloaded every session — against the published authoring checklist. INVENTORY measures what loads; EVIDENCE gathers block logs and correction history; VERDICT maps each section to the documented include categories and exclude list, then rules keep / rewrite / relocate / delete; RELOCATE moves procedures to skills, must-hold guarantees to hooks and permission rules, derivable facts back to code; APPLY proposes and waits for approval. Use when the user says any of "하네스 정리", "룰·훅이 밥값을 하는지", "CLAUDE.md 다이어트", "상주 컨텍스트 정리", "룰이 너무 많아", "훅이 실제로 뭘 막고 있는지" — or "harness audit", "trim my CLAUDE.md", "are my rules earning their keep", "prune the steering layer", "why does Claude ignore my rules". Do NOT use it after a specific defect recurred (that is recurrence-prevention), or for drift between the product's docs and its code (that is audit-service-gaps DRIFT).

0
installs
▌
Gh Issue Workflow · uzysjung bundle
Runs 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, verify, and status stages distinct. Use whenever a request will outlive the chat turn, whenever work needs an order the user can review, or when the user names issues ("이슈로 등록해줘", "에픽으로 묶어줘", "이슈 정리해줘", "#42 작업해줘", "우선순위 다시 잡자", "backlog this", "break this into sub-issues", "implement issue #N"). Read-only stages make no remote change; never create, edit, label, comment on, close, or re-parent a remote issue, and never touch a project board, without the user asking for that change.

0
installs
▌
Strategic Compact · uzysjung bundle
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

0
installs
▌
Verification Loop · uzysjung bundle
A comprehensive verification system. Selects and runs proportional verification tracks for UI, API/service, CLI/TUI, library/SDK, documents/configuration, and real user flows, then ends every run with a fixed verdict — PASS / PASS_WITH_NITS / FAIL — plus severity-labeled findings (CRITICAL/HIGH/MEDIUM/LOW) and the evidence each one rests on. Use after implementation, before a PR or handoff, after a refactor, or to verify a claimed fix. Do NOT use a green build, a passing type check, or file existence as proof of user-visible completion, and do NOT let the instance that wrote the change issue its own verdict.

0
installs
▌
Humanize Korean · uzysjung
한국어 글에서 실제로 어색한 문체 문제를 진단하고, 근거가 있는 부분만 최소 수정해 자연스럽게 다듬는다. 번역투, AI 상투구, 기계적 구조, 접속사·형식명사·완곡 표현의 반복, 불필요한 영어 장식 등을 다루며 의미·사실·수치·전문용어·말투는 보존한다. "AI 티 없애줘", "자연스럽게 다듬어줘", "번역투 고쳐줘", "사람이 쓴 글처럼", "문체 진단 후 고쳐줘" 같은 요청에 사용한다.

0
installs
▌
Audit Service Gaps · uzysjung bundle
Audits 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 the same loop to post-fix closure, baseline changes, doc-vs-code drift, and the whole-service sweep. Use when the user says any of: "북극성 기준으로 부족한 점", "갭분석", "다른 벤치마크 서비스는 이 부분을 어떻게 해결했는지", "레퍼런스 서비스랑 비교해서 부족한 점 찾아줘" — or the English "gap analysis", "benchmark against reference services", "audit this service". Do NOT use it to *define* product direction (that is north-star), to review ONE standalone artifact's prose (that is multi-persona-review), or to turn an unverified benchmark claim into a fact.

0
installs
▌
Compaction Handoff · uzysjung
Create 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.

0
installs
▌
Model Orchestration · uzysjung
Apply the fixed model-role and thinking-effort policy whenever work is delegated to subagents or a model/effort choice is made: the orchestrator (top-tier model, Fable) DIRECTLY owns 설계·기획·분배·리뷰 — sets direction, reviews plan/spec docs, improves shipped features, and hunts perf/security problems; core implementation, test authoring/execution (E2E included), and code verification/V&V go to Opus at xhigh or above; repetitive/simple implementation goes to Sonnet at high or above — Sonnet is never used for tests or verification; plan/spec drafts may be produced by Opus from a Fable direction brief, but the review/decision is always Fable's. Never delegate below the effort floors. Use whenever you are about to spawn an Agent/Task/Workflow worker, pick a model for a subtask, set a thinking/effort level, or assign verification. Trigger on "위임해", "오케스트레이션", "모델 역할분담", "어떤 모델로", "effort 얼마로", "서브에이전트", "delegate this", "which model should". Fire even when the user doesn't name the policy — any delegation is in scope.

0
installs
▌
Multi Persona Review · uzysjung bundle
A 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 this artifact". Lighter than a full service audit — point it at ONE artifact, not a whole codebase. Do NOT use it for a whole-service or whole-codebase audit, nor for a gap-vs-benchmark loop (both are audit-service-gaps), and do NOT simulate diversity by renaming reviewers that inspect the same evidence.

0
installs
▌
Recurrence Prevention · uzysjung bundle
When the same defect, mistake, or incident happens AGAIN — a recurrence, not a one-off — verify it against prior evidence (memory, rule case tables, git/CHANGELOG history), classify it as a simple slip vs a complex harness problem, then escalate the countermeasure one level up the ladder: record (1st) → forced rule with a case table (2nd) → structural gate — test, hook, or derive — once prose has failed (3rd+). Complex problems get countermeasure candidates designed by a multi-persona panel instead of a quick patch. Use for "재발했어", "같은 실수 또 했네", "이거 저번에도 그랬잖아", "재발방지 대책 등록해줘", "재발방지 룰 만들어", "this happened again", "same bug as last time", "add a recurrence countermeasure", "postmortem this failure". Do NOT use it for a first-time defect (fix it, record it, stop), do NOT create a standing rule from an unverified first occurrence, and do NOT use it as a general audit of the steering layer at rest.

0
installs
▌
External Model Consult · uzysjung bundle
Consult 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 otherwise hand-write polished Korean yourself. Triggers on "어색해", "자연스럽게 다듬어줘", "gemini 한테 물어봐", "nano banana", "제3자 관점", "codex한테 물어봐", "간결하게 정리해줘", "이미지 만들어줘", and in English "ask gemini", "ask codex", "generate an image". Returns candidates to choose from; never auto-applies. Do NOT use for deterministic transforms (rename, reformat, sort), labeled diagrams, internal logs or identifiers, anything needing repo secrets, a native subagent panel (`multi-persona-review`), or when the user explicitly wants YOUR answer.

0
installs
▌
Clear Korean Communication · uzysjung bundle
Make a technical explanation land, and turn the decision at the end of it into something the reader can approve in one pass. Two halves of one job: (1) EXPLAIN — fix the referent first (one name often points at two things), lead with who is affected and what changes, put file paths after the claim as evidence; (2) DECIDE — present approval/choice moments in the user's four-part format 전후맥락 (context) → 추천 + 이유 (recommendation) → UI/UX 형태 (a scannable table) → ASIS→TOBE contrast, led by the recommendation so the user can say yes fast. Run it whenever you explain a bug, a cause, or what your change did — especially the moment the reader says they don't follow ("뭔 소리야", "쉽게 설명해줘", "이해가 안 돼", "I don't follow") — and whenever you are about to ask "should I do this?" ("ASIS TOBE로 설명", "이거 진행할까요?", "should I do A or B"). Do NOT fire for pure information with no decision in it, for trivial reversible actions you would just do, or for context-free word/sentence translation — that is ordinary translation.

0
installs
▌
Self Hosted Github Runner · uzysjung
GitHub 호스티드 러너를 못 쓰게 됐을 때, 레포의 기존 워크플로를 **그대로** 자기 머신의 Docker self-hosted runner 에서 돌리게 만든다. 결제 실패·지출한도·분(minutes) 소진·조직 쿼터·Actions 장애로 CI 가 멈췄을 때, "CI 를 로컬에서 돌리자"·"self-hosted runner"·"act 로 돌릴까"·"CI 죽었는데 머지·배포 어떻게 하냐"는 말이 나올 때 쓴다. **누군가 "CI 스텝을 스크립트에 옮겨 적어 로컬에서 돌리자"고 제안할 때도 반드시 이 스킬을 켠다** — 그 안은 워크플로를 두 벌로 갈라놓고, 갈라진 순간부터 로컬 초록이 CI 초록을 뜻하지 않게 되기 때문이다.

0
installs
▌
Architecture Decision Record · uzysjung bundle
Use this skill when documenting significant architectural decisions. Provides ADR templates following the Nygard format with sections for context, decision, consequences, and alternatives. Use when writing ADRs, recording decisions, or evaluating options.

0
installs

21 published skills