robsonrung
- 60 skills
- 0 followers
- 6 hours ago last updated
- ▌ Shared · robsonrung bundleShared references, schemas, and scripts used by the other skills. This directory is a library dependency, not an executable workflow.
- ▌ Cmux CLI · robsonrung bundleControl cmux workspaces, panels, terminal input, notifications, and sidebar state through its CLI. Use when the user asks to inspect or manage cmux, create or target a workspace or panel, send text or keys, or report task status in cmux.
- ▌ Review Gate · robsonrung bundleReturn a machine-readable review verdict for a PR or branch. Use when a workflow needs a merge gate with structured evidence; use full-review for a human-facing review.
- ▌ Diverse Plan · robsonrung bundleCompare independent implementation approaches and produce one reviewed plan. Use when the user explicitly requests a diverse plan or several model-generated approaches; it does not implement the plan.
- ▌ Skill Expert · robsonrung bundleCreate, audit, improve, or package SKILL.md workflows and their supporting resources. Use for skill authoring, discovery problems, or workflow simplification. For project instruction files, use agents-md-craft.
- ▌ Browser Smoke · robsonrung bundleSmoke-test the routes a branch or PR changes in a real browser. Use when the user asks to smoke-test a branch or PR, test affected pages, or run a diff-scoped browser test. It tests changed routes, not whole-product release QA.
- ▌ Fable Mindset · robsonrung bundleApply the Fable engineering posture to intake, diagnosis, decisions, implementation, and reports. Use when the user requests this mindset or an assessment of that work process; it does not select a model.
- ▌ Peer Sessions · robsonrung bundleCoordinate peer sessions through native delegation or a durable mailbox. Use for a requested peer fleet, cross-session handoffs, or resumable replies; use models-consensus for a requested opinion council.
- ▌ Verify Changes · robsonrung bundleRun a repository's deterministic checks from its own command surface. Use when the user asks to verify a branch, run repository checks, or prove that build and tests pass. It captures command evidence, does not repair code, and does not replace browser testing.
- ▌ Agents Md Craft · robsonrung bundleCreate, audit, or simplify project instruction files such as AGENTS.md and CLAUDE.md. Use to fix instruction drift or separate conditional guidance; use skill-expert for SKILL.md files.
- ▌ Dynamic Harness · robsonrung bundlePlan and run a bounded worker fleet for a complex task. Use when the user explicitly requests delegation, parallel work, a tournament, or a managed mission.
- ▌ Knowledge Graph · robsonrung bundleBuild and query a document knowledge graph with traceable evidence. Use for multi-hop answers, corpus-wide themes, or shared graph memory; use direct retrieval for single-document or single-hop questions.
- ▌ Tdd · robsonrungImplement behavior through the red-green-refactor loop. Use when test-first execution is requested or selected by the coding workflow; use safe-incremental-coding first for untested legacy code.
- ▌ Open Pr · robsonrung bundleCommit scoped changes, push a branch, and open or update a GitHub pull request. Use when the user asks to open a pull request, commit and push work, or write or update a pull request description. Do not use to implement work or merge a pull request.
- ▌ Worktree · robsonrungSet up an isolated git worktree for new work or an existing ref. Use when the user requests isolation or an implementation plan requires separate workspaces; reuse suitable existing isolation.
- ▌ Pi Runner · robsonrung bundleExecute an external Pi CLI prompt with a provider and model pinned per call. Use only for an explicit Pi CLI request, a selected Pi provider route unavailable as native host delegation, or an approved external fallback, including Kimi, GLM, Qwen, and Gemma seats.
- ▌ To Prd · robsonrung bundleTurn a settled decision record into a PRD for user approval. Use after interview-me or a settled product discussion; to-tasks consumes the approved PRD.
- ▌ HTML Explainer · robsonrung bundleCreate a self-contained HTML walkthrough of a subsystem or flow, with diagrams and expandable source evidence. Use for detailed interactive code explanations; use explain-architecture for a short orientation.
- ▌ Summarize · robsonrungCreate a concise continuity summary from the active session. Use when the user asks to summarize current work, prepare a handoff, or compact session context. Do not use to summarize an unrelated document or to store a handoff.
- ▌ Design Gate · robsonrungSelect relevant design lenses for a planned slice and return a proceed-or-revise verdict. Use during task planning or when a design boundary changes; invoke a named lens directly for a single-lens review.
- ▌ Diagnose · robsonrungFind and prove the cause of a bug, failing test, or unexpected behavior. Use for unexplained failures, including pipeline verification failures; an understood failure within a TDD loop stays with tdd.
- ▌ Grok Runner · robsonrung bundleExecute an external Grok CLI prompt in headless print mode. Use only for an explicit Grok CLI request, a selected Grok route unavailable as native host delegation, or an approved external fallback.
- ▌ To Tasks · robsonrungBreak an approved PRD into reviewable vertical slices and publish the approved task queue. Use when planning implementation tasks; implement-tasks handles model approval and execution.
- ▌ Collaborative Delivery · robsonrung bundleDeliver an approved task through an auditable multi-model panel with test, review, and verification evidence. Use when the user requires a recorded panel trail for implementation. For the normal fast path, use implement-and-review or implement-tasks.
- ▌ Test Lens · robsonrung bundleJudge test value and choose what to test or mock. Use for brittle tests, test reviews, and unit or integration test design; use tdd for the test-first execution loop.
- ▌ Full Review · robsonrung bundleReview code changes or requirements with evidence-backed findings. Use for integration seams, public contracts, security, migrations, or a requested deep review; keep local task reviews scoped.
- ▌ Cline Runner · robsonrung bundleExecute an external Cline CLI prompt with structured output. Use only for an explicit Cline CLI request, a selected Cline provider route unavailable as native host delegation, or an approved external fallback, including Muse and Minimax seats.
- ▌ Codex Runner · robsonrung bundleExecute an external Codex CLI prompt in non-interactive exec mode. Use only for an explicit Codex CLI request, a selected Astra, Sol, Terra, or Luna route unavailable as native host delegation, or an approved external fallback.
- ▌ Dcode Runner · robsonrung bundleExecute an external DeepAgents CLI (`dcode`) prompt with the user's configured model and credentials. Use only for an explicit dcode or DeepAgents CLI request. It is not an approved implementation or review route.
- ▌ Security Gate · robsonrungIdentify security decisions during an interview and classify slices for deep or standard review. Use when defining an exposed security surface or planning its review; full-review performs the code review.
- ▌ Clean Code · robsonrungRefactor existing code with behavior-preserving Clean Code practices. Use for local naming, readability, duplication, or structure problems; use architecture-lens for module boundary decisions.
- ▌ Claude Runner · robsonrung bundleExecute an external Claude CLI prompt in headless print mode. Use only for an explicit Claude CLI request, a selected Claude route unavailable as native host delegation, or an approved external fallback.
- ▌ Gemini Runner · robsonrung bundleExecute an external Antigravity CLI (`agy`) prompt for a Gemini route. Use only for an explicit Gemini or Antigravity CLI request, a selected external route, or an approved fallback when native delegation cannot meet the route.
- ▌ Brainstorm · robsonrung bundleExplore an uncertain idea and recommend whether to build, defer, reduce scope, or reject it. Use for brainstorming or a build decision; use interview-me next to settle requirements.
- ▌ UI UX Pro Max · robsonrung bundleChoose a reusable UI design system or review cross-screen UX using a design database. Use for visual systems, interaction rules, or UI quality; use frontend-design for bespoke visual implementation.
- ▌ Advanced React · robsonrung bundlePlan, implement, or review React component structure, state placement, re-renders, and async behavior using composition first. Use for component design or behavior problems; use react for compiler setup and version-specific APIs.
- ▌ Opencode Runner · robsonrung bundleGuide an external OpenCode CLI run through the host approval flow. Use only when users explicitly request OpenCode or approve an OpenCode comparison without a bundled runner script.
- ▌ Interview Me · robsonrung bundleSettle feature and design choices through interview rounds of up to five questions. Use --auto for a bounded two-role evidence-based interview; otherwise ask the user before a PRD.
- ▌ To Prototype · robsonrung bundleBuild a throwaway experiment to answer a design question that reading cannot settle. Use for technical spikes, state-model demos, or visual alternatives; use a tracer bullet when the code must ship.
- ▌ Decide About Disagreements · robsonrung bundleHelp the user resolve material disagreements in an existing models-consensus result. Present recorded opinions, distinct options, and a recommendation for each open decision without rerunning the council or implementing it.
- ▌ Design Patterns · robsonrung bundleChoose or review a Gang-of-Four pattern when recurring code structure creates a concrete design problem. Use to compare a named pattern with a simpler design; use architecture lenses for system boundaries.
- ▌ Explain Architecture · robsonrung bundleCreate a self-contained HTML orientation page explaining a codebase or subsystem with a map and one traced flow. Use for onboarding or architecture overviews; use html-explainer for a detailed code walkthrough.
- ▌ Session Handoff · robsonrungCreate an immutable session handoff or orient from a selected handoff. Use when the user asks to hand off current work, save continuity notes, resume from a handoff, or inspect available handoffs. Do not use for an ordinary session summary.
- ▌ Capture Learning · robsonrung bundleCapture a verified, reusable solution in docs/solutions. Use when asked to document a solved problem or when a delivery workflow selects learning capture; use session-handoff for work continuity.
- ▌ Architecture Lens · robsonrung bundleReview code-level coupling, cohesion, dependency direction, and module boundaries. Use when deciding where code belongs or whether to split, merge, or refactor a module; use macro-architecture for system shape.
- ▌ Frontend Design · robsonrung bundleBuild a custom frontend interface from a chosen visual direction. Use for a bespoke page, component, or site; use ui-ux-pro-max for reusable design systems and advanced-react for React behavior.
- ▌ Implement Tasks · robsonrung bundleExecute an approved task queue with exact model approval, native-first role sessions, dependency scheduling, and integration review. Use when the user asks to implement approved tasks; implement-and-review handles each task.
- ▌ Consensus Summary HTML · robsonrung bundleRender an existing models-consensus result as a self-contained HTML decision brief. Use when asked to visualize a council report; preserve its opinions and evidence without running a new council.
- ▌ Coding Design Plan · robsonrungPlan the implementation shape of one approved coding task. Use when a module, data, API, component, or deployment boundary still needs a design decision; use to-tasks for task decomposition.
- ▌ Macro Architecture · robsonrung bundleChoose a system architecture style or assess service decomposition and data ownership. Use for monolith, service, event-driven, or distributed-system boundaries; use architecture-lens for code-level structure.
- ▌ Models Consensus · robsonrung bundleRun a read-only council of model opinions after the user approves its model plan. Use only when the user invokes this skill or explicitly asks for extra model opinions; never use as an automatic escalation.
- ▌ Resolve Pr Feedback · robsonrung bundleEvaluate pull request feedback against the code, apply valid fixes, and reply to or resolve the addressed threads. Use only when the user asks to address pull request feedback or review threads. Do not use to find new issues in a diff.
- ▌ Implement And Review · robsonrung bundleImplement and review one approved coding task through exact model routes and persistent role contexts. Use for a scoped task with an acceptance contract; use implement-tasks to coordinate a queue.
- ▌ Domain Driven Design · robsonrung bundleReview domain boundaries, business language, aggregates, and domain events. Use when a change crosses bounded contexts or restructures business rules within one context.
- ▌ Coding Review Simplify · robsonrung bundleReview a completed code change for behavior-preserving simplification, local correctness, and maintainability. Use after implementing a scoped task or when the user asks to simplify a concrete diff. Do not use as a full feature review or to choose the delivery reviewer plan.
- ▌ Agent Architecture Lens · robsonrung bundleReview agent control flow, durable state, retries, and recovery. Use when choosing a loop or state graph, or when a tool-calling workflow must survive failures and resume safely.
- ▌ Data Systems Coding Lens · robsonrung bundleReview implementation risks in persistent state and asynchronous data paths. Use for schemas, migrations, queues, caches, retries, or concurrent writes; use macro-architecture to decide service and data ownership.
- ▌ Safe Incremental Coding · robsonrungBuild characterization tests before a risky change to untested legacy code. Use to preserve existing behavior while making the affected code testable, then hand behavior changes to tdd.
- ▌ Software Design Philosophy · robsonrung bundleReduce design complexity through deep modules, information hiding, and coherent interfaces. Use when a module or API is hard to understand or change; use clean-code for local cleanup.
- ▌ Distributed Systems Patterns · robsonrung bundleChoose or review distributed topology and event-stream patterns. Use for replicas, shards, container helpers, queues, or event-driven adoption and migration; use macro-architecture for overall system style.