team-attention
- 100 skills
- 0 followers
- 173 repo stars
- last month last updated
- ▌ Spets 3 · team-attentionSDD workflow executor - orchestrator-controlled spec-driven development. Activate when the user wants to run spets, SDD workflows, or spec-driven development tasks.
- ▌ QA 2 · team-attention bundleSystematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen. Three modes: browser (agent-browser/Playwright, fast, DOM-level), computer (MCP computer-use, screenshot + pixel clicks, any app), and cli (tmux, send-keys + capture-pane for interactive terminals). Auto-selects mode or accepts --browser / --computer / --cli override. Use when asked to "qa", "QA", "test this site", "test this app", "find bugs", "test and fix", "fix what's broken", "dogfood", "exploratory test", "bug hunt", "QA this app", "사이트 테스트", "앱 테스트", "브라우저 QA", "화면 보고 테스트해줘", "네이티브 앱 테스트", "screen test". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.
- ▌ Specify 2 · team-attention bundleTurn a goal into an implementation plan (spec.md). Simplified layer chain: L0:Goal → L1:Context → L2:Decisions → L3:Requirements → L4:Tasks. Evidence-based clarity scoring at L2. User approves at L2, L3, L4. Output is a single spec.md file written with the Write tool. Use when: "/specify", "specify", "plan this"
- ▌ Scaffold 2 · team-attention bundleDesign and optionally build a new project's architecture and AI work environment. Select a stack and dependencies, plan a working reference flow, and configure project instructions, verification, and useful skills/hooks. Use for "/scaffold", "new project setup", "프로젝트 세팅", or "초기 구조". Existing projects require an explicit adaptation scope, not automatic reinitialization.
- ▌ Clarify Vague 2 · team-attentionThis skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "뭘 원하는 건지", "make this clearer", "spec this out", "scope this", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.
- ▌ Clarify Unknown 2 · team-attention bundleThis skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4분면 분석", "blind spots", "뭘 놓치고 있지", "뭘 모르는지 모르겠어", "전략 점검", "전략 분석", "assumption check", "가정 점검", "quadrant analysis", "what am I missing". Strategy-level blind spot analysis with hypothesis-driven questioning. For requirement clarification use vague; for content-vs-form reframing use metamedium.
- ▌
- ▌ Clarify Metamedium 2 · team-attention bundleThis skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "관점 전환", "perspective shift", "다른 방법 없을까", "같은 방식이 안 먹혀", "diminishing returns". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use vague; for strategy blind spots use unknown.
- ▌ Spets 2 · team-attentionSDD workflow executor - orchestrator-controlled spec-driven development. Activate when the user wants to run spets, SDD workflows, or spec-driven development tasks.
- ▌ D2sf Printer Setup · team-attentionThis skill should be used when the user asks to "프린터 설치", "복합기 설치", "신도리코 설치", "프린터 연결", "프린터 세팅", "프린터가 안 돼요", "인쇄가 안 돼요", "출력이 안 돼요", "복사기 설치", "프린트 설치", "printer setup", "sindoh setup", "D451 설치", "프린터 추가", "복합기 드라이버", or needs help installing a Sindoh D451 multifunction printer on macOS.
- ▌
- ▌ Shape Goal · team-attentionUse when the user wants to run a long-horizon Codex `/goal` (or any persistence-loop agent) against a Ralph-style repo and needs the goal *shaped* — stop condition pinned, qualitative outcome turned into a verifiable checklist, proxy fidelity declared, and durable memory files seeded. Trigger on "shape my goal", "set up /goal", "make this a /goal", "/goal from RALPH.md", "long-running goal", "ralph goal", "goal prompt", "stop condition", or whenever a user asks to convert a vague long-running task into a Codex `/goal` prompt. Reads `RALPH.md` when present, fills the four shape checks (Outcome / Stop / Proxy / Memory), refuses to emit a goal that would loop forever, and writes seed `PLAN.md` / `EXPERIMENTS.md` / `EXPERIMENT_NOTES.md` next to `RALPH.md` so the loop has a place to remember.
- ▌ Clarify Image · team-attention bundleUse in Codex Plan mode when the user wants to clarify, shape, explore, visualize, or expand an idea through request_user_input choice questions and AI-generated image previews. Trigger on "clarify-image", "visualize my idea", "turn my idea into an image", "help me think through this visually", visual brainstorming, image-first ideation, or when the user wants Codex to ask structured multiple-choice questions, turn the answers into image previews, and use those images to make the idea clearer and stronger. This is a Plan-mode, request_user_input-based skill for Socratic idea clarification plus image generation, not for software implementation requirements.
- ▌ Openclone · team-attention bundleCreate, manage, or talk to an openclone "clone" — a named AI persona with one or more categories (vc, tech, founder, expert, influencer, politician, celebrity) and attached knowledge. Triggers on phrases like "create a clone", "make a persona", "talk as <name>", "switch to <name>", "feed knowledge to", "ingest url for <clone>", "update <name> with latest info", "<name> 클론 최신 정보로 업데이트", "ask all VCs", "stop being <name>", or any mention of `/openclone`. Renders the home panel with no args; name/number activates a clone; sub-actions `stop`, `new`, `ingest`, `update`, `room`, `panel`.
- ▌ Openclone CLI · team-attention bundleUse when the user wants to consult an AI persona "clone" for advice, strategy, analysis, or domain expertise—especially in startup, VC, tech, growth, HR, or business contexts. Available official clones include: 장동욱(Brian, VC), 김철우(VC/founder), 권도균(Douglas, founder/VC), 조여준(Ethan, VC), 정구봉(tech/founder), 김동현(iid, HR), 신재명(Jay, founder), 조쉬(founder/expert), 이경훈(founder/VC), 김용훈(Levi, growth/CMO). Also use when users ask how to install openclone via npm, run openclone outside Claude Code, choose a provider (OpenAI-compatible API, Codex OAuth, Claude Code subscription OAuth, or local Ollama), pick a model, list or resume saved conversation sessions (openclone history, --resume, --resume=<id>), use --no-persist, understand interactive chat mode, knowledge lookup, conversation persistence under ~/.openclone/conversations, or fix CLI errors.
- ▌ 08 Wrap · team-attention bundle작업을 마무리하는 스킬. 테스트 확인, 커밋/PR, worktree 정리와 함께 5개의 전문 에이전트로 세션 인사이트를 추출합니다.
- ▌ Doc Drift · team-attentionUse this skill when the user wants to audit the memory and documents Claude Code loads into context — CLAUDE.md (user global + project + nested), MEMORY.md, @imports, .claude/skills, .claude/agents, .claude/commands, installed plugins — and detect three kinds of issues: outdated claims, mutually contradictory statements, and risky-or-ambiguous wording. Produces a prioritized improvement list at `.drift-reports/`. Zero config. Trigger phrases: "doc drift", "memory drift", "memory audit", "context drift", "docs audit", "문서 점검", "문서 감사", "메모리 감사", "메모리 점검", "outdated 문서", "문서 충돌".
- ▌ Check Harness · team-attention bundleAudit a Claude Code project's development readiness: runtime and LSP, context, permissions, hooks, tests/CI, skills and independent verification. Distinguish configured, observed working, missing and unverified capabilities. Use for /check-harness, 하네스 점검, LSP 설치 확인, or 개발 환경 종합 점검.
- ▌ Deep Interview · team-attention"/deep-interview", "deep interview", "interview me", "clarify requirements", "요구사항 정리", "인터뷰", "딥 인터뷰", "뭘 만들어야 할지 모르겠어", "요구사항이 불명확", "아이디어 구체화"
- ▌ Agent Orchestrate · team-attentionAnalyze the user's task and propose the optimal orchestration pattern, then execute it. 4 patterns: Sequential Pipeline, Parallel Subagent, Team Mode, Ralph Loop. Situation-aware pattern selection with user confirmation before execution. Use when: "/agent-orchestrate", "agent-orchestrate", "오케스트레이션", "어떤 패턴으로", "병렬로 할까", "순차로 할까", "팀 모드", "에이전트 패턴", "작업 방식 제안", "how should we run this", "pick a pattern". Also trigger when the user describes a complex multi-step task that would clearly benefit from agent coordination — e.g., "A사 B사 C사 분석해줘", "설계하고 구현하고 리뷰까지", "이거 순서대로 해줘", "3개 동시에 돌려", or any task with 3+ subtasks where choosing the right execution pattern matters for efficiency.
- ▌ Auto Research · team-attention bundleUse when preparing Ralphthon research specifications or 연구 명세, automated experiments, a Track 1 short paper or 논문, a Track 2 review agent or 리뷰, or an evidence-backed submission under the event deadline.
- ▌ Wandb Onboarding · team-attention bundleUse when signing up or 가입 for W&B Cloud, configuring a personal API key, checking authentication, or creating a first experiment-tracking run or 실험 추적 project.
- ▌ Hello Ralphthon Icml · team-attentionWelcome and orient Ralphthon @ICML attendees, operators, sponsors, and QR/POP traffic. Use when the user asks for Ralphthon ICML onboarding, attendee welcome copy, event orientation, QR or POP copy, guestbook engagement, hackathon context, or Codex skill surface framing.
- ▌ World Model Ideation · team-attention bundleTurn a world-model, 월드모델, simulation, predictive-state, embodied-agent, or intervention-model idea into ranked falsifiable research questions and a compact experiment handoff. Use when selecting a world-model research direction, deciding whether an idea needs a world model, defining an action-conditioned or counterfactual comparison, or preparing Ralphthon work for Auto Research Track 1 or Track 2.
- ▌ Vessl Cloud Onboarding · team-attention bundleUse when signing up or 가입 for current VESSL Cloud, installing or authenticating vesslctl, checking organizations and teams, or preparing a first billable GPU Workspace, Job, or 기본 세팅.
- ▌ Weave Add Tracing · team-attention bundleAdd W&B Weave tracing to an existing LLM, agent, RAG, or tool-using application with minimal behavioral change. Use when the user asks to integrate Weave, instrument code with @weave.op, trace model or tool calls, choose trace boundaries, account for framework auto-patching, protect sensitive trace data, debug missing traces, or verify a real trace tree. Keep this skill focused on tracing; route evaluations, assets, and general W&B documentation elsewhere.
- ▌ Wandb Project Analyst · team-attention bundleAnalyze live W&B Models and Weave project data using the W&B MCP server, including runs, histories, configs, traces, evaluations, artifacts, registries, comparisons, diagnoses, and reports. Use when the user asks what happened in a W&B project, which run or model is best, why a run or trace failed, how evaluations performed, what changed between versions, or to save an evidence-backed analysis as a W&B Report.
- ▌ Wandb Track Experiment · team-attention bundleAdd W&B Models experiment tracking and guarded alerts to iterative experiment workflows, including Codex or Ralph-loop autoresearch. Use when the user asks to instrument experiments, create one W&B run per candidate, group related runs, record hypotheses and code provenance, log metrics and summaries, detect failed or stalled experiments, or validate that runs are comparable and reproducible. Use wandb-project-analyst for analysis of data already stored in W&B.
- ▌ Yc 5 Launching · team-attention bundleThis skill should be used when the user asks about "론칭", "첫 고객", "launching", "first customers", "cold email", "콜드 이메일", "/yc-5", "스타트업 출시", "고객 확보", "do things that don't scale", "launch strategy", "how to launch". YC Startup School Module 5: Launching — Kat Mañalac on launching repeatedly, Gustaf Alströmer on first customer acquisition, and PG's "Do Things That Don't Scale" essay.
- ▌ Guru Paul Graham · team-attention bundleThis skill should be used when the user mentions "폴 그레이엄", "Paul Graham", "PG 조언", "guru", "PG한테 물어봐", "/pg", "PG 에세이", "YC 철학", or asks for startup advice in the style of Paul Graham. Channels Paul Graham's philosophy to evaluate the user's startup, answer startup questions with PG's direct and contrarian voice, and applies his specific frameworks (schlep filter, unsexy filter, do things that don't scale, default alive/dead, etc.) to the user's actual situation. PG essays are also referenced individually by the module skills (/yc-1 through /yc-5).
- ▌ AI Startup School · team-attention bundleThis skill should be used when the user mentions "AI Native Company", "AI-native company", "AI 스타트업", "AI startup school", "AI 트렌드", "소프트웨어 3.0", "/yc-ai", "AI 창업", "AI 산업 트렌드", "AI 빌더", "agentic company", "self-improving company", "company brain", "skillify", "resolver", "Garry Tan", "Diana Hu", "Karpathy", "Sam Altman", "AGI", "vibe coding", or asks about insights from top AI leaders. Synthesizes knowledge from 17 AI Startup School / AI Native Company transcripts — including Karpathy, Altman, Musk, Nadella, Garry Tan, Diana Hu, Fei-Fei Li, Chollet, Ng, Srinivas, Jumper, Finn, Kaplan, Field, Truell, Masad, and the founder panel — and applies them to the user's current AI work, startup design, or company operating model.
- ▌ Yc 4 Planning An Mvp · team-attention bundleThis skill should be used when the user asks about "MVP", "유저 인터뷰", "talk to users", "사용자 대화", "제품 개발", "프로토타입", "MVP 만들기", "/yc-4", "product development", "user research", "사용자 인터뷰", or any questions about user research, building an MVP, or product-market fit iteration. YC Startup School Module 4: Planning an MVP — Gustaf Alströmer on talking to users, Michael Seibel on building MVP, and Diana Hu on technical founder principles.
- ▌ Yc 6 Growing And Monetizing · team-attention bundleThis skill should be used when the user asks about "성장", "수익화", "KPI", "비즈니스 모델", "PMF", "메트릭", "코호트", "retention", "pricing", "/yc-6", "지표 설정", "가격 책정", "리텐션", "product market fit 측정", "growth", "monetizing", "business model". YC Startup School Module 6: Growing and Monetizing — KPI setting, startup metrics, and business models from Divya Bhat, Tom Blomfield, and Aaron Epstein.
- ▌ Yc 1 Deciding To Start A Startup · team-attention bundleThis skill should be used when the user asks about "창업 시작", "스타트업 시작해야 할까", "should I start a startup", "should I start", "창업할 준비가 됐는지", "/yc-1", "창업 결정", "FAANG 그만둬야 하나", or questions about founder resilience, worst-case analysis, and when to make the leap. YC Startup School Module 1: Deciding to Start a Startup — Harj Taggar's decision framework and Paul Graham's foundational essays on why to start.
- ▌ Yc 3 Building Your Founding Team · team-attention bundleThis skill should be used when the user asks about "공동창업자", "co-founder", "지분", "equity", "equity split", "vesting", "창업팀", "공동창업자 찾기", "공동창업자 관계", "/yc-3", "co-founder breakup", "지분 배분", or any questions about co-founder selection, equity distribution, or founding team dynamics. YC Startup School Module 3: Building Your Founding Team — the #1 reason startups fail at YC is co-founder breakups.
- ▌ Yc 8 Stories From Great Founders · team-attentionThis skill should be used when the user asks about "창업자 스토리", "Facebook 창업", "23andMe", "founder stories", "/yc-8", "Mark Zuckerberg", "Anne Wojcicki", "great founders", "창업 스토리", "how Facebook started", "how 23andMe started". YC Startup School Module 8: Stories from Great Founders — Mark Zuckerberg on Facebook and Anne Wojcicki on 23andMe. No transcripts available; provides YouTube links and key themes.
- ▌ Yc 7 Fundraising And Company Building · team-attention bundleThis skill should be used when the user asks about "펀딩", "투자", "fundraising", "YC 지원", "YC 합격", "SAFE", "투자 용어", "엔젤 투자", "/yc-7", "어떻게 투자받나", "how fundraising works", "YC application", "startup legal terms", "cap table", "equity dilution". YC Startup School Module 7: Fundraising and Company Building — Brad Flora on how startup fundraising works and Dalton Caldwell on how to apply and succeed at YC.
- ▌ Yc 2 Getting And Evaluating Startup Ideas · team-attention bundleThis skill should be used when the user asks about "아이디어 검증", "스타트업 아이디어", "startup ideas", "tarpit", "아이디어 찾는 방법", "좋은 아이디어인지", "/yc-2", "피벗", "아이디어 평가", "idea evaluation", or any question about generating, evaluating, or pivoting startup ideas. YC Startup School Module 2: Getting and Evaluating Startup Ideas — Jared Friedman's systematic framework backed by patterns from thousands of YC companies, plus PG's canonical essay.
- ▌ Part Extra · team-attention bundleHeum 3시간 강의 Part Extra — Agent Teams, Hook, Plugin. 3시간 강의에서 다 못 다룬 심화 개념(에이전트 팀, 훅, 플러그인)을 선택적으로 다룬다. "파트엑스트라", "Part Extra", "extra", "agent-teams", "hook", "plugin" 요청에 사용.
- ▌ Part1 Sync · team-attention bundleHeum 3시간 강의 Part 1 — MCP & Context Sync. MCP가 뭔지 배우고, Slack을 연결해 나만의 Context Sync 스킬을 만들기 시작한다. "파트1", "Part 1", "sync", "MCP" 요청에 사용.
- ▌ Part3 Wrap · team-attention bundleHeum 3시간 강의 Part 3 — Wrap. wrap-session 스킬을 직접 만들고, 만든 스킬을 실행하고, wrap-history로 세션을 분석한다. "파트3", "Part 3", "wrap", "세션 래핑", "session wrap" 요청에 사용.
- ▌ Wrap History · team-attention bundleThis skill should be used when user wants to access, capture, or reference Claude Code session history. Trigger when user says "capture session", "save session history", "/wrap-history", or references past/current conversation as a source - whether for saving, extracting, summarizing, or reviewing. This includes any mention of "what we discussed", "today's work", "session history", or when user treats the conversation itself as source material (e.g., "from our conversation").
- ▌ Wrap Session · team-attention bundleThis skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "/wrap-session", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.
- ▌ Clarify Vague · team-attentionThis skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "요구사항 명확히", "요구사항 정리", "뭘 원하는 건지", "make this clearer", "spec this out", "scope this", "/clarify-vague", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use clarify-unknown; for content-vs-form reframing use clarify-metamedium.
- ▌ Part2 Clarify · team-attention bundleHeum 3시간 강의 Part 2 — Clarify. AskUserQuestion과 Clarify 플러그인으로 모호한 요구사항을 명확하게 만들고, 나만의 Clarify 스킬을 작성한다. "파트2", "Part 2", "clarify", "클래리파이" 요청에 사용.
- ▌ Wrap Analyzer · team-attention bundleThis skill should be used when the user asks to "analyze session", "세션 분석", "evaluate skill execution", "스킬 실행 검증", "check session logs", "로그 분석", "/wrap-analyzer", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session. Post-hoc analysis of Claude Code sessions to validate skill/agent/hook behavior against SKILL.md specifications.
- ▌ Clarify Unknown · team-attention bundleThis skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4분면 분석", "blind spots", "뭘 놓치고 있지", "뭘 모르는지 모르겠어", "전략 점검", "전략 분석", "assumption check", "가정 점검", "quadrant analysis", "what am I missing", "/clarify-unknown". Strategy-level blind spot analysis with hypothesis-driven questioning. For requirement clarification use clarify-vague; for content-vs-form reframing use clarify-metamedium.
- ▌ Clarify Metamedium · team-attention bundleThis skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "내용 vs 형식", "content vs form", "metamedium", "형식을 바꿔볼까", "새로운 포맷", "관점 전환", "perspective shift", "다른 방법 없을까", "같은 방식이 안 먹혀", "diminishing returns", "/clarify-metamedium". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use clarify-vague; for strategy blind spots use clarify-unknown.
- ▌ Wrap · team-attention세션 종료 시 자동 정리를 수행합니다. CLAUDE.md 업데이트 제안, 반복 패턴 자동화 기회 탐지, 배운 것 정리, 미완성 작업 정리. 사용자가 /wrap 또는 세션 마무리 요청 시 사용.
- ▌ Commit · team-attention코드 수정 완료 후 conventional commit 형식의 커밋 메시지를 자동 생성하고 사용자 확인 후 커밋합니다. 사용자가 커밋해줘 또는 /commit 요청 시 사용.
- ▌
- ▌ Nanobanana · team-attentionReading 원문에서 나노바나나 프로용 치트시트 프롬프트를 생성합니다. 3단계 에이전트 파이프라인(분석→구조설계→프롬프트생성)으로 콘텐츠 유형에 맞는 프롬프트 생성. 사용: /nanobanana week1/slug
- ▌ Eval Summary · team-attentionreadings.ts의 요약 필드가 원본 kr 마크다운과 비교하여 잘 작성되었는지 평가합니다. 이슈별로 개선사항을 제안하고 사용자 컨펌 후 readings.ts를 수정합니다. 사용: /eval-summary week1 또는 /eval-summary week1/slug
- ▌
- ▌ Improve Prompt · team-attention나노바나나 프롬프트의 정확성을 한글 번역본과 비교하여 검증하고, WebSearch로 팩트체크한 후 이슈별로 사용자 확인을 거쳐 수정합니다. 사용: /improve-prompt week1/deep-dive-llms/tokenization
- ▌ Upload Reading · team-attention번역된 한국어 마크다운 파일을 readings.ts에 추가하여 웹에 게시합니다. 마크다운 파싱 → ReadingContent 객체 생성 → readings.ts/syllabus.ts 업데이트. YouTube 콘텐츠의 경우 요약(tldr, chapterSummaries) 필드도 파싱. 사용: /upload-reading week1/slug 또는 /upload-reading week1/parent/child
- ▌
- ▌ Review Cheatsheet · team-attention나노바나나 치트시트 이미지를 Gemini Vision으로 분석하여 해당 kr md 파일의 내용과 일치하는지 검증합니다. 기술적/문맥적 오류, 잘못된 텍스트/그래프/그림을 찾아냅니다. 사용: /review-cheatsheet week1/slug/chapter
- ▌ Translate Reading · team-attention원본 reading을 한국어로 번역하여 마크다운 파일로 저장합니다. 다단계 에이전트 파이프라인(용어검색→번역→정제→검증→QA→요약)으로 고품질 번역 생성. YouTube 콘텐츠의 경우 챕터별 요약도 자동 생성. 사용: /translate-reading week1/slug 또는 /translate-reading week1/parent/child
- ▌ Publish Cheatsheet · team-attention나노바나나에서 생성된 치트시트 이미지를 public에 복사하고 readings.ts에 cheatsheetImage 필드를 추가합니다. 사용: /publish-cheatsheet week1/slug
- ▌ Review Translation · team-attention번역된 한국어 콘텐츠의 품질을 AI로 검증합니다. 원문과 번역본을 비교하여 정확성, 완전성, 자연스러움, 용어 일관성을 평가합니다. Claude, Codex, Gemini CLI 3개 AI로 교차 검증하여 합의된 이슈를 우선 표시합니다. 사용: /review-translation week1/slug
- ▌ Split Youtube Chapters · team-attentionYouTube 콘텐츠의 챕터별 하위페이지 구조를 readings.ts에 생성하고, 전체 번역 파일에서 챕터별 번역 파일을 자동 생성합니다. 사용: /split-youtube-chapters week1/deep-dive-llms
- ▌ QA · team-attention bundleSystematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen. Three modes: browser (chromux/CDP, fast, DOM-level), computer (MCP computer-use, screenshot + pixel clicks, any app), and cli (tmux, send-keys + capture-pane for interactive terminals). Auto-selects mode or accepts --browser / --computer / --cli override. Use when asked to "qa", "QA", "test this site", "test this app", "find bugs", "test and fix", "fix what's broken", "dogfood", "exploratory test", "bug hunt", "QA this app", "사이트 테스트", "앱 테스트", "브라우저 QA", "화면 보고 테스트해줘", "네이티브 앱 테스트", "screen test". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.
- ▌ Check · team-attention bundleThis skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists. Phase 1: validate changed files against .hoyeon/rules/ checklists and report PASS/WARN. Phase 2 (conditional): propose rule additions when unmatched patterns are detected. Essential before git push. Trigger phrases: "check", "checklist", "verify changes", "what did I miss", "pre-push check", "cascading changes", "any more changes needed", "update checklist", "update rules", "rules update", "체크", "체크리스트", "변경 확인", "빠뜨린 거 없나", "push 전 확인", "뭐 더 건드려야 해?", "연쇄 변경 확인", "규칙 갱신".
- ▌ Issue · team-attentionGitHub issue creation skill. Analyzes the entire codebase impact based on user request, then creates a structured issue with AI-verified/human-judgment-needed/caution sections. /issue "issue description" Trigger: "/issue", "이슈 만들어", "issue 만들자", "깃헙 이슈"
- ▌ Ralph · team-attentionIterative task completion loop with Definition of Done verification. Combines the Ralph Wiggum technique (prompt re-injection via Stop hook) with DoD-based independent verification. Claude proposes DoD criteria, user confirms, then Claude works autonomously. Stop hook re-injects the original prompt and blocks exit until all DoD items are independently verified. "/ralph", "ralph loop", "ralph 루프", "반복 작업", "DoD 루프", "완료 검증 루프", "task loop", "keep going until done"
- ▌ Rulph · team-attentionIterative rubric-based evaluation and self-improvement loop. Builds a scoring rubric interactively, evaluates an artifact with multiple models in parallel (Codex, Gemini, Claude), then autonomously improves the artifact one criterion at a time until a score threshold is met or circuit breaker fires. "/rulph", "rubric evaluate", "rubric score", "multi-model evaluate", "score and improve", "evaluate and iterate", "grade this", "루브릭 루프", "채점 루프", "자율 개선", "개선 루프", "루브릭 평가"
- ▌ Bugfix · team-attentionRoot cause based one-shot bug fix. debugger diagnosis → requirements.md generation → /execute. /bugfix "error description" Full investigation pipeline: debugger + gap-analyzer + standard verify. QA suggestion after successful fix.
- ▌ Mirror · team-attention"/mirror", "mirror back", "echo back", "다시 설명해줘", "이해한 거 맞아?", "내가 뭘 원하는지 말해봐", "확인해줘", "paraphrase this", "너가 이해한 거 설명해봘", "what did I ask?"
- ▌ Verify · team-attentionRun a full implementation verification pass after code or data changes. Use when the user asks to verify, QA, smoke test, run checks, validate a feature, inspect a local app in the browser, capture screenshots, or turn discovered QA issues into regression tests/checklists with user approval.
- ▌ Clarify · team-attention bundle"/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변 기록", "요구사항 명확화", "설계 명확화". Relentless ambiguity-resolution interview that records Q&A under .hoyeon/clarify/<topic>/ and hands off to specify/blueprint/docs when clear.
- ▌ Council · team-attentionThis skill should be used when the user says "/council", "council", "deliberate", "multi-perspective decision", "트레이드오프 분석", "위원회 소집", "여러 관점으로 검토", or wants deep multi-perspective deliberation with tradeoff mapping. Combines tribunal (structured adversarial review), agent-council (external LLM opinions), dev-scan (community sentiment), and step-back (meta-level review) into a unified decision-making committee. Uses Agent Teams for real peer-to-peer debate with iterative step-back moderation loop.
- ▌ Discuss · team-attention"/discuss", "discuss this", "think with me", "is this a good idea?", "what do you think about", "problem definition", "explore this idea", "/discuss --scored", "interview me", "clarify requirements", "요구사항 정리", "인터뷰", "딥 인터뷰", "뭘 만들어야 할지 모르겠어", Korean triggers: "같이 생각해보자", "이거 어떻게 생각해?", "문제 정의", "이게 좋은 아이디어야?", "이거 맞아?", "요구사항이 불명확", "아이디어 구체화"
- ▌ Execute · team-attention bundlePlan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan 실행", "blueprint 실행"
- ▌ Specify · team-attention bundle"/specify", "specify", "요구사항 정의", "requirements", "스펙 잡기", "뭘 만들어야 하는지", "기획 정리", "인터뷰해서 스펙" Turn a goal into structured requirements through systematic interview. Three phases: Interview → Extract → Cross-check. Writes requirements.md in the cli format (consumed by /blueprint).
- ▌ Compound · team-attention bundleThis skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR. Extracts knowledge from PR context and saves to docs/learnings/.
- ▌ Dev Scan · team-attention bundleCollect diverse opinions on technical topics from developer communities. Use for "developer reactions", "community opinions" requests. Aggregates Reddit, HN, Dev.to, Lobsters, ProductHunt, etc.
- ▌ Scaffold · team-attention bundleGreenfield project architecture + harness scaffolding for AI Agent productivity. Interview-driven decisions → requirements.md → execute. Produces: Code Structure (vertical slice exemplar), Test Infrastructure, Guard Rails, conditional extensions, AND Harness (CLAUDE.md with domain/team context, rules, skills, hooks). L2: architecture decisions, L3: harness setup, L4: requirements + harness decisions (tasks generated later by /execute into plan.json). Use when: "/scaffold", "scaffold", "new project", "set up project", "프로젝트 세팅", "초기 구조"
- ▌ Stepback · team-attentionOne-shot perspective reset that surfaces blind spots mid-work. Scans what the user has been doing, generates one abstract reframing question, and runs 3 quick checks (scope drift, side effects, better approach) in under 10 lines. No dialogue, no code. Trigger phrases: "/stepback", "step back", "한발 물러서", "넓은 관점", "놓치는 거 없나", "방향 맞나", "zoom out", "큰 그림", "방향이 맞는 거야", "잠깐 멈춰", "지금 뭘 하고 있는 거야", "blind spot", "재확인"
- ▌ Tribunal · team-attentionThis skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review. Also triggered by: "트리뷰널", "리뷰 해줘", "3관점 리뷰", "위험성 검토". Runs 3 agents (Risk/Value/Feasibility) in parallel and synthesizes a verdict.
- ▌ Blueprint · team-attention"/blueprint", "blueprint", "task graph", "contract derivation", "execution plan", "plan tasks from requirements", "contract-first planning" Turn requirements.md into an executable blueprint (plan.json + contracts.md). Five phases: Contracts → Tasks → Journeys → Verify Plan → Commit. Sits between /specify and /execute. Scope-adaptive (greenfield → bugfix). Uses hoyeon-cli (plan.json only; requirements.md is read as-is via Read tool).
- ▌ Ultrawork · team-attentionThis skill should be used when the user says "/ultrawork", "ultrawork", or wants to run the full specify → execute pipeline automatically with a single command. Automated end-to-end workflow that chains specify and execute skills.
- ▌ Analyze Oss · team-attentionAnalyze an open-source project from What/Why perspective (not how-it's-implemented). Use when the user says "/analyze-oss", "분석해줘 이 오픈소스", "이 레포 뭐하는거야", "analyze this repo", "what does X do", "이거 왜 쓰는거야", "이 라이브러리 분석", provides a GitHub URL and wants understanding, or asks to deeply understand an OSS project's purpose, value, target users, and usage flow. Clones the repo to ~/opensource-analysis/<repo-name>/ (git pull if already exists), dispatches parallel subagents per analysis lens, then synthesizes a What/Why-focused report in chat. Supports optional user-specific follow-up questions.
- ▌ Browser Work · team-attention bundleRecon-first browser automation. Orchestrator explores the site first via chromux, saves a guide file with insights, then delegates execution to browser-explorer agent. Use when: "/browser-work", "브라우저 작업", "사이트에서 해줘", "웹에서 해줘", "LinkedIn에서", "크롬으로", "browser task", "automate this site".
- ▌ Deep Research · team-attention bundleDeep web research skill using parallel subagents + chromux browser-explorer + Gemini. Spawns multiple WebSearch research agents AND browser-explorer agents (via chromux for JS-heavy/dynamic sites), plus a Gemini CLI deep research source, then synthesizes everything into a cited report. Uses WebSearch, WebFetch, chromux browser-explorer, and Gemini CLI. Invoke with /deep-research <topic>.
- ▌ Google Search · team-attention bundleGoogle search via real Chrome browser (chromux). Use when the user asks to "search Google", "구글 검색", "구글에서 찾아줘", "find articles about", "search the web for", or needs web search results with full page content. Also trigger when: searching a specific site ("search dev.to for..."), finding recent articles/posts about a topic, extracting content from search results, or when WebSearch results are insufficient and real browser rendering is needed. Prefer this over WebSearch when the user wants site-specific search, time-filtered results, or full article body/comments extraction.
- ▌ Tech Decision · team-attention bundleThis skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use", "tradeoffs", "tech selection", "implementation approach", or needs deep analysis for technical decisions. Provides systematic multi-source research and synthesized recommendations.
- ▌ Reference Seek · team-attentionThis skill should be used when the user asks to "find references", "참고할 만한 거", "similar implementation", "오픈소스 있나", "how others do this", "레퍼런스 찾아줘", or needs to find existing patterns (internal) and open-source examples (external) for implementing a feature.
- ▌ Hoyeon Clarify · team-attentionHoyeon ambiguity-resolution interview for Codex. Use when the user invokes "$hoyeon-clarify", "/clarify", asks to keep asking until clear, remove ambiguity, clarify requirements/design/domain/plan, or says Korean phrases like "모호한 게 없게", "명확해질 때까지", "질문 계속해", or "Q&A로 정리".
- ▌ Hoyeon Discuss · team-attentionHoyeon Socratic discussion workflow for Codex. Use when the user invokes "$hoyeon-discuss", "/discuss", asks to think through an idea, challenge assumptions, clarify requirements before planning, run a deep/scored discussion, or says Korean phrases like "같이 생각해보자", "문제 정의", "이거 어떻게 생각해?", "요구사항이 불명확", or "아이디어 구체화".
- ▌ Hoyeon Execute · team-attentionHoyeon execution workflow for Codex. Use when the user invokes "$hoyeon-execute" or wants to execute a Hoyeon plan.json through the Bash-first Codex adapter. This adapter loads the canonical execute skill and follows its Codex runtime surface.
- ▌ Hoyeon Specify · team-attentionHoyeon requirements workflow for Codex. Use when the user invokes "$hoyeon-specify" or wants to turn an unclear goal into structured requirements.md for Hoyeon. This adapter loads the canonical specify skill and follows its Codex runtime surface.
- ▌ Hoyeon Dev Scan · team-attentionHoyeon developer community scan workflow for Codex. Use when the user invokes "$hoyeon-dev-scan" or asks for developer reactions, community opinions, or cross-community sentiment on technical topics. This adapter loads the canonical dev-scan skill and follows its Codex runtime surface.
- ▌ Hoyeon Blueprint · team-attentionHoyeon blueprint workflow for Codex. Use when the user invokes "$hoyeon-blueprint" or wants to turn requirements.md into a validated plan.json and optional contracts.md. This adapter loads the canonical blueprint skill and follows its Codex runtime surface.
- ▌ Skill Session Analyzer · team-attention bundleThis skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed correctly in a past session. Post-hoc analysis of Claude Code sessions to validate skill/agent/hook behavior against SKILL.md specifications.
- ▌ Hoyeon Browser Work · team-attentionHoyeon browser automation workflow for Codex. Use when the user invokes "$hoyeon-browser-work" or asks Codex to perform a browser task through recon-first chromux automation. This adapter loads the canonical browser-work skill and follows its Codex runtime surface.
- ▌ Hoyeon Deep Research · team-attentionHoyeon deep research workflow for Codex. Use when the user invokes "$hoyeon-deep-research" or wants a multi-channel cited research report using web search, browser extraction, and optional Gemini. This adapter loads the canonical deep-research skill and follows its Codex runtime surface.
- ▌ Hoyeon Google Search · team-attentionHoyeon Google/chromux search workflow for Codex. Use when the user invokes "$hoyeon-google-search" or needs real-browser Google search, site-specific search, time filters, or body/comment enrichment. This adapter loads the canonical google-search skill and follows its Codex runtime surface.
- ▌ Hoyeon Reference Seek · team-attentionHoyeon implementation reference discovery workflow for Codex. Use when the user invokes "$hoyeon-reference-seek" or asks for internal patterns, open-source references, GitHub examples, official docs, or comparable implementations. This adapter loads the canonical reference-seek skill and follows its Codex runtime surface.
- ▌ Review · team-attentionInteractive markdown review with web UI. Use when: - User says "review this", "check this plan", "/review" - User wants to give feedback on a plan or document - User says "let me review", "피드백", "검토해줘" - User specifies a file path to review (e.g., "review /path/to/file.md")