Claude Skills by islee23520

Read Claude Code plugins, skills, project auto-memory, and the durable Grok↔Claude message bridge. Use when the user asks what Claude plugins/skills are installed, to inspect Claude MEMORY.md / project memory, or to send/read messages between Grok/lfg and Claude Code (mailbox or live `claude -p` ask). Triggers: claude plugins, claude skills, claude memory, Claude Code inventory, read claude skill, marketplace plugins, message claude, talk to claude, claude bridge, lfg claude ask.

MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, OpenCode, Senpi/pi, OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, or unknown local agent logs. Covers transcripts, session IDs, rollout JSONL, state SQLite, Claude projects/pre-compact histories, OpenCode messages/parts, child/subagent linkage, cwd/model/time/token filters, archives, and cost ...

Use when GrokBuild needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook (lfg native hook).

Drive a native macOS app via the cua-driver CLI (default) or MCP server — snapshot its AX tree, click/type/scroll by element_index, verify via re-snapshot. Use when the user (or an agent persona) asks to operate, drive, automate, or perform a GUI task in a real macOS application on the host (e.g. "open a file in TextEdit", "navigate to /Applications in Finder", "click the Save button in Numbers", control creative tools, etc.).

Persistent code-mode kernels (JS/Python) for incremental computation — omp/senpi eval analog on GrokBuild via lfg MCP. Use when multi-step code execution, data exploration, or stateful REPL beats one-shot bash.

MUST USE for frontend/web UI/UX/visual work: building, styling, redesigning pages/components, React setup, performance audits, visual QA, taste, and polish. Routes four rulesets: design taste router and brand references; perfection for Playwright/Chromium Lighthouse/Core Web Vitals; ui-ux-db palettes/fonts/guidelines; designpowers personas/accessibility/critique/handoff; plus curl-only lazyweb real-app-screen research for design direction. Triggers: frontend, UI, UX, design, redesign, styling...

(builtin) Initialize hierarchical AGENTS.md knowledge base

Contribute a verified bug fix for lfg or its GrokBuild adapter payload. Use when the user asks to debug and fix an lfg setup, skill sync, hook, MCP, agent, config, package, or GrokBuild integration defect.

Diagnose lfg GrokBuild adapter installation health against the latest lfg source. Use when lfg setup, the installed ~/.grok/plugins/lfg payload, hooks, skills, agents, model config, or GrokBuild integration behaves oddly after install or update.

Create a high-signal bug report for lfg or its GrokBuild adapter payload. Use when the user asks to report, file, open, or triage an lfg setup, skill sync, hook, MCP, agent, config, package, or GrokBuild integration bug.

@islee23520/lfg — OpenCode OmO/lazycodex GrokBuild port 설치 CLI. 용도와 setup 명령 안내.

Use when GrokBuild needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace (lfg MCP lsp surface).

MUST USE for ANY work on .py .pyi .rs .ts .tsx .mts .cts .go files. One philosophy: strict types, modern stacks (Pydantic v2 / serde+thiserror / Zod / gin+sqlc+pgx+slog), modern toolchains (uv+basedpyright+ruff / cargo+clippy+miri / Bun+Biome+tsc / gofumpt+golangci-lint v2+nilaway+go-race), parse-don't-validate, exhaustive match, typed errors, no any/unwrap/panic, 250 LOC ceiling, TDD, consumer-routed logging. Routes to references/{python,rust,typescript,rust-ub,go}/ + references/logging.md. ...

Intelligent refactor command. Triggers: refactor, refactoring, cleanup, restructure, extract, simplify, modernize.

Remove AI-generated code smells (slop) from branch changes or an explicit file list. Locks behavior with regression tests FIRST, then runs categorized cleanup via parallel `deep` agents in batches of 5, then verifies with quality gates. Covers 10 slop categories including performance equivalences, excessive complexity (object annotations, if/elif variant chains), and oversized modules (250+ pure LOC with mandatory modular refactoring). MUST USE when the user asks to \"remove slop\", \"clean A...

Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE after completing any significant implementation work. Triggers: 'review work', 'review my work', 'review changes', 'QA my work', 'verify implementation', 'check my work', 'validate ch...

Use when the user asks about lfg/GrokBuild rules injection, project rules files, matching, or environment configuration.

Execute a Prometheus work plan in GrokBuild with `/goal` state, Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and explicit continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.

GrokBuild + Codex team orchestration: run a named team of cooperating workers with durable script-managed state under .omo/teams. MUST USE when the user asks to create, run, coordinate, inspect, archive, or delete a team of agents/subagents/sessions, or to work as a team in parallel. On GrokBuild, FIRST select transport spawn_subagent (host spawn_subagent + bind-subagent). On Codex, select multi_agent_v2 or codex_app. The main session is always the leader; members are concrete part/ownership/...

Legacy alias for ulw-research. MUST USE when the user asks for ultraresearch, /ultraresearch, or /ultraresearch; immediately load and follow the ulw-research skill.

Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.

MUST USE for planning before coding: 5+ steps, ambiguous scope, multiple modules, architecture decisions, a vague 'just make it good / figure out what to build' brief, or any request to plan, interview, or break work down. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker exe...

Maximum-saturation research orchestration: parallel explore+librarian swarms across codebase, web, official docs, and OSS repos; a recursive EXPAND loop driven by leads workers return in message text; empirical verification by running code; cited synthesis and optional MD/HTML/PDF/PPTX reports. ACTIVATES ONLY on an explicit user demand for research — the word 'ulw-research' ('/ulw-research', '/ulw-research'), the legacy alias 'ultraresearch', any 'ulw' research wording, or an explicit request...

MUST USE after building/changing any UI or when asked whether a page, component, or TUI looks right. Rigorous visual QA across web/page and terminal UIs. Prefer browser:control-in-app-browser for unauthenticated browser/page QA in Codex, then Playwright/agent-browser/dev-browser. Captures screenshot/TUI evidence with bundled diff scripts, runs design-system/functional and visual-fidelity/CJK reviewer passes, then synthesizes a good/bad verdict. Triggers: visual QA, screenshot/pixel diff, UI l...

Use when the user asks to generate, draft, answer, rewrite, summarize, or reason with xAI/Grok text generation through the Grok-connected xAI text tool.

Use when the user asks to generate, create, make, or save images with xAI, Grok Imagine, or a Grok-connected xAI image generation tool.

Use when the user asks to generate speech, text-to-speech, audio narration, voice output, or TTS with xAI/Grok through a Grok-connected xAI TTS tool.

Use when the user asks to generate video, Grok Imagine video, text-to-video, image-to-video, or xAI video through a Grok-connected xAI video generation tool.

Use when the user asks xAI/Grok to search the web, find current information, answer with citations, or use server-side web_search from a Grok-connected xAI tool.

Use when the user asks to search X, Twitter, posts, handles, tweets, or real-time social signal through Grok-connected xAI server-side x_search.

Use for xAI/Grok API capabilities through the lfg xai_grok MCP — text generation, web search, X/Twitter search, image/video generation, and TTS. Load when the user wants Grok-connected xAI tools beyond built-in host tools, or when search_tool should target xai_* MCP tools.

Drive a native macOS app via the cua-driver CLI (default) or MCP server — snapshot its AX tree, click/type/scroll by element_index, verify via re-snapshot. Use when the user (or an agent persona) asks to operate, drive, automate, or perform a GUI task in a real macOS application on the host.

Read Claude Code plugins, skills, project auto-memory, and the durable Grok↔Claude message bridge. Use when the user asks what Claude plugins/skills are installed, to inspect Claude MEMORY.md / project memory, or to send/read messages between Grok/lfg and Claude Code (mailbox or live `claude -p` ask). Triggers: claude plugins, claude skills, claude memory, Claude Code inventory, read claude skill, marketplace plugins, message claude, talk to claude, claude bridge, lfg claude ask.

MUST USE when asked to find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across Codex, Claude Code/Desktop, OpenCode, Senpi/pi, OpenClaw, Factory Droid, Amp, Gemini/Kimi/Qwen CLIs, Codebuff, Roo/Kilo/Cline, Kodu, Cursor CLI, Aider, or unknown local agent logs. Covers transcripts, session IDs, rollout JSONL, state SQLite, Claude projects/pre-compact histories, OpenCode messages/parts, child/subagent linkage, cwd/model/time/token filters, archives, and cost ...

Use when GrokBuild needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook (lfg native hook).

Drive a native macOS app via the cua-driver CLI (default) or MCP server — snapshot its AX tree, click/type/scroll by element_index, verify via re-snapshot. Use when the user (or an agent persona) asks to operate, drive, automate, or perform a GUI task in a real macOS application on the host (e.g. "open a file in TextEdit", "navigate to /Applications in Finder", "click the Save button in Numbers", control creative tools, etc.).

Persistent code-mode kernels (JS/Python) for incremental computation — omp/senpi eval analog on GrokBuild via lfg MCP. Use when multi-step code execution, data exploration, or stateful REPL beats one-shot bash.

MUST USE for frontend/web UI/UX/visual work: building, styling, redesigning pages/components, React setup, performance audits, visual QA, taste, and polish. Routes four rulesets: design taste router and brand references; perfection for Playwright/Chromium Lighthouse/Core Web Vitals; ui-ux-db palettes/fonts/guidelines; designpowers personas/accessibility/critique/handoff; plus curl-only lazyweb real-app-screen research for design direction. Triggers: frontend, UI, UX, design, redesign, styling...

(builtin) Initialize hierarchical AGENTS.md knowledge base

Contribute a verified bug fix for lfg or its GrokBuild adapter payload. Use when the user asks to debug and fix an lfg setup, skill sync, hook, MCP, agent, config, package, or GrokBuild integration defect.

Diagnose lfg GrokBuild adapter installation health against the latest lfg source. Use when lfg setup, the installed ~/.grok/plugins/lfg payload, hooks, skills, agents, model config, or GrokBuild integration behaves oddly after install or update.

Create a high-signal bug report for lfg or its GrokBuild adapter payload. Use when the user asks to report, file, open, or triage an lfg setup, skill sync, hook, MCP, agent, config, package, or GrokBuild integration bug.

Use when GrokBuild needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace (lfg MCP lsp surface).

MUST USE for ANY work on .py .pyi .rs .ts .tsx .mts .cts .go files. One philosophy: strict types, modern stacks (Pydantic v2 / serde+thiserror / Zod / gin+sqlc+pgx+slog), modern toolchains (uv+basedpyright+ruff / cargo+clippy+miri / Bun+Biome+tsc / gofumpt+golangci-lint v2+nilaway+go-race), parse-don't-validate, exhaustive match, typed errors, no any/unwrap/panic, 250 LOC ceiling, TDD, consumer-routed logging. Routes to references/{python,rust,typescript,rust-ub,go}/ + references/logging.md. ...

Intelligent refactor command. Triggers: refactor, refactoring, cleanup, restructure, extract, simplify, modernize.

Remove AI-generated code smells (slop) from branch changes or an explicit file list. Locks behavior with regression tests FIRST, then runs categorized cleanup via parallel `deep` agents in batches of 5, then verifies with quality gates. Covers 10 slop categories including performance equivalences, excessive complexity (object annotations, if/elif variant chains), and oversized modules (250+ pure LOC with mandatory modular refactoring). MUST USE when the user asks to \"remove slop\", \"clean A...

Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE after completing any significant implementation work. Triggers: 'review work', 'review my work', 'review changes', 'QA my work', 'verify implementation', 'check my work', 'validate ch...

Use when the user asks about lfg/GrokBuild rules injection, project rules files, matching, or environment configuration.

Execute a Prometheus work plan in GrokBuild with `/goal` state, Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and explicit continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.

GrokBuild + Codex team orchestration: run a named team of cooperating workers with durable script-managed state under .omo/teams. MUST USE when the user asks to create, run, coordinate, inspect, archive, or delete a team of agents/subagents/sessions, or to work as a team in parallel. On GrokBuild, FIRST select transport spawn_subagent (host spawn_subagent + bind-subagent). On Codex, select multi_agent_v2 or codex_app. The main session is always the leader; members are concrete part/ownership/...