Menu
SkillsMP has collected 37 skills from team-attention/hoyeon. Open a skill to review its source and details.
Showing 37 of 37 collected skills.
Run 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โฆ
Hoyeon 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.
Plan-driven orchestrator. Reads plan.json (from /blueprint) or requirements.md, then dispatches workers to build the system. Use when: "/execute", "execute", "plan ์คํ", "blueprint ์คํ"
Recon-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โฆ
Deep 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โฆ
Systematically 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โฆ
Hoyeon 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.
Hoyeon 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โฆ
Hoyeon 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 "๋ชจํธํ ๊ฒ ์๊ฒ", "๋ช ํํด์ง ๋๊น์ง", "์ง๋ฌธ ๊ณ์ํด",โฆ
Hoyeon 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โฆ
Hoyeon 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โฆ
Hoyeon 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 "๊ฐ์ดโฆ
Hoyeon 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โฆ
Hoyeon 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โฆ
Hoyeon 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.
"/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โฆ
"/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "์ง๋ฌธ ๊ณ์ํด", "๋ชจํธํ ๊ฒ ์๊ฒ", "๋ช ํํด์ง ๋๊น์ง", "๊ณ์ ๋ฌผ์ด๋ด", "Q&A๋ก ์ ๋ฆฌ", "์ง๋ฌธ๋ต๋ณ ๊ธฐ๋ก", "์๊ตฌ์ฌํญ ๋ช ํํ", "์ค๊ณ ๋ช ํํ". Relentless ambiguity-resolutionโฆ
Collect diverse opinions on technical topics from developer communities. Use for "developer reactions", "community opinions" requests. Aggregates Reddit, HN, Dev.to, Lobsters, ProductHunt, etc.
Google 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โฆ
This 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.
"/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โฆ
Root 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.
Greenfield 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โฆ
"/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โฆ
This 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 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โฆ
This 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โฆ
This 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/.
This 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โฆ
This 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โฆ
This 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โฆ
GitHub 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 ๋ง๋ค์", "๊นํ ์ด์"
One-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โฆ
Iterative 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.โฆ
Iterative 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โฆ
"/mirror", "mirror back", "echo back", "๋ค์ ์ค๋ช ํด์ค", "์ดํดํ ๊ฑฐ ๋ง์?", "๋ด๊ฐ ๋ญ ์ํ๋์ง ๋งํด๋ด", "ํ์ธํด์ค", "paraphrase this", "๋๊ฐ ์ดํดํ ๊ฑฐ ์ค๋ช ํด๋ด", "what did I ask?"
This 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โฆ