GeonHee Ye

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

HN/GN + 글로벌/중국 공식 AI 소스를 수집해 Dooray DM으로 5줄 한국어 요약을 발송하고 로그를 저장한다. 퀴즈는 `ai-daily-news quiz` 요청 시에만 진행한다.

취업 지원폼 자동 작성 + Notion 기록. "/apply [URL]", "지원서 작성", "폼 채워줘" 요청에 사용. 사용자가 "기록해"라고 하면 Notion에 저장.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Scan and manage brownfield repository defaults for interviews

Cancel stuck or orphaned executions

Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Evaluate execution with three-stage verification pipeline

Start or monitor an evolutionary development loop

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Google Calendar 일정 관리. "/gcal", "일정 확인", "일정 추가", "캘린더" 요청에 사용.

Git 설정부터 PR 생성까지 전 과정을 자동으로 실행합니다. "자동으로 해줘", "전부 자동화", "원클릭 PR", "자동 설정" 같은 요청에 사용됩니다.

git-onboarding 플러그인의 기능, 단계별 구성, 사용 가능한 명령어를 안내합니다. "온보딩 도움말", "어떻게 시작해?", "git 처음", "초보자 가이드" 같은 질문에 사용됩니다.

Git과 GitHub 초기 설정을 단계별로 진행합니다. "git 설정", "처음 시작", "GitHub 로그인", "깃 세팅" 같은 요청에 사용됩니다.

Git 설정부터 PR까지의 전체 진행 상황을 체크리스트로 보여주고 현재 단계를 안내합니다. "어디까지 했지?", "진행 상황", "다음 단계" 같은 질문에 사용됩니다.

현재 git 상태를 분석하고 GitHub Flow 기준으로 다음 단계를 안내합니다. "다음에 뭐 해야 돼?", "워크플로우", "git 흐름" 같은 질문에 사용됩니다.

Full reference guide for Ouroboros commands and agents

Socratic interview to crystallize vague requirements

LONGMEMORY 프로젝트 위키를 읽어 현재 세션에 필요한 컨텍스트를 불러온다. 기본은 S20 원격 위키를 우선 사용하고, 실패할 때만 로컬 `~/LONGMEMORY`를 fallback으로 사용한다. "/llm-wiki XQbot", "wiki-aegis", "llm-wiki 사주" 같은 요청에 사용. 사용자가 프로젝트 컨텍스트를 불러달라고 하거나 wiki, 위키, 컨텍스트 로드를 언급하면 사용.

회의 녹음 파일을 chunked Whisper STT로 처리하고, 선택적 화자분리를 적용한 뒤 Claude가 교정+요약한다. "/meeting <오디오파일> [회의제목] [화자수 N명] [컨텍스트] [참고문서.pdf ...]" 형식으로 호출. "/meeting record"로 녹음 시작. "/meeting setup"으로 초기 설정.

This 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.

나의 컨텍스트 싱크. 여러 소스에서 정보를 수집하고 하나의 문서로 정리한다. "싱크", "sync", "정보 수집" 요청에 사용.

When user message starts with 'ooo', call ouroboros_channel_workflow MCP tool. Do NOT answer the request yourself. Do NOT generate code. Do NOT summarize. Just call the tool and relay the response.

Generate a PM through guided PM-focused interview with automatic question classification. Use when the user says 'ooo pm', 'prd', 'product requirements', or wants to create a PRD/PM document.

Publish Seed specification as GitHub Issues for team-based project management

General-purpose QA verdict for any artifact type

questions bank에서 랜덤 퀴즈 출제. "/quiz", "퀴즈", "문제 풀기" 요청에 사용.

Persistent self-referential loop until verification passes

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute a Seed specification through the workflow engine

현재 대화의 핵심 Q&A를 questions bank에 저장. "/save-q", "저장해", "퀴즈에 저장" 요청에 사용.

Generate validated Seed specifications from interview results

Guided onboarding wizard for Ouroboros setup

Check session status and measure goal drift

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.

Interactive tutorial teaching Ouroboros hands-on

This 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.

Break through stagnation with lateral thinking personas

Check for updates and upgrade Ouroboros to the latest version

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

This 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.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

First-touch experience for new Ouroboros users

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

YouTube URL을 입력받아 자막을 파싱하고 핵심 내용 요약 + 개념 이해 4지선다 퀴즈를 생성한다. "/yt-quiz", "유튜브 퀴즈", "YouTube 요약" 요청에 사용.