oimiragieo
- 991 skills
- 0 followers
- 3 weeks ago last updated
- ▌ Tensor Grep Config And Flags · oimiragieoUse when adding, changing, or auditing a tg environment variable, CLI flag, or provider mode (native/lsp/hybrid); when a search flag silently leaks to ripgrep or a command misroutes; when deciding whether a config axis (GPU, LSP, classify, semantic) is production or EXPERIMENTAL default-OFF; when adding a new `SearchConfig` field and needing to know whether it must be forwarded/refused/KNOWN_GAP'd for native delegation; or before registering a new `tg search --flag` or `tg COMMAND` (including `tg inventory`'s `--max-repo-files`/`--deadline`). Catalogs the load-bearing TG_*/TENSOR_GREP_* env vars (routing, timeouts, GPU, classify, session, MCP security, LSP) with their default and guard, the 2-front-door / 4-site registration checklist, and the native-delegation field-coverage ratchet.
- ▌ Tensor Grep Docs And Writing · oimiragieoUse when writing or editing any tensor-grep doc of record (AGENTS.md, CLAUDE.md, root SKILL.md, docs/SESSION_HANDOFF.md, docs/CONTRACTS.md, docs/CONTINUATION_PLAN.md, docs/PAPER.md, README.md, docs/benchmarks.md, docs/gpu_crossover.md, mkdocs.yml, or any .claude/skills/*/SKILL.md) — before adding a capability claim, syncing a release-line note, touching a version-stamped line, adding a new governed doc, or a docs-only pytest fails and you don't know which fragment broke it. Covers which doc owns which contract, the two governance layers (semantic-release version_variables + scripts/stamp_release_assets.py auto-stamping vs pytest content-pinning), the cross-doc fragment discipline, mkdocs --strict, and house style.
- ▌ Use N8n · oimiragieoUse whenever you need to create, modify, execute, or debug n8n workflows — whether the n8n instance is self-hosted on Fly/Docker, n8n Cloud, or local. Triggers on intent phrases — "build an n8n workflow", "add a Telegram approve-gate", "ingest from Reddit/arXiv/HN via n8n", "import a workflow template", "n8n REST API", "n8n MCP", "self-host n8n on Fly", "n8n.fly.dev", or any task involving the n8n automation platform. Encodes the three operational tiers (n8n-mcp MCP server for best programmatic control / public REST API at /api/v1/ for direct curl / UI browser-automation as last resort), the workflow-template archive sources (Zie619 4,343-template repo + n8n.io/workflows official library), and the bug-class catalog of pitfalls (HTTP body double-stringify, /rest vs /api/v1, executeManually payload shape, code node language v2 quirk, session cookie 401, code node "metadata" reserved attr, etc.) that cost real session time when discovered through trial-and-error.
- ▌ Use Codex · oimiragieoUse when delegating bounded coding, audit, or review work to codex-cli (OpenAI Codex) for an independent SECOND-OPINION pass that doesn't share Claude's blind spots, or to conserve Claude tokens on heavy content-writing. Codex picker (2026-07-01): gpt-5.5 (frontier/current default), gpt-5.4, gpt-5.4-mini, gpt-5.3-codex-spark (ultra-fast); gpt-5.3-codex and gpt-5.2 dropped from picker. Spec-driven, diff-first audit pattern — best for peer review of non-trivial diffs (money/auth/webhooks/migrations), bulk audits, multi-file content writes to spec. Skip for small edits or live step-through debugging. Sibling skill of use-cursor.
- ▌ Use Droid · oimiragieoUse when delegating bounded coding, audit, multi-agent mission, or review work to Factory's Droid CLI (droid exec, --mission mode with worker+validator subagent orchestration). Droid runs Claude Opus 4.8 by default (also carries Fable 5, Sonnet 5, GLM-5.2, Kimi K2.7, MiniMax M3, nemotron-3-ultra) on one Factory subscription across Anthropic/OpenAI/Google. Sibling skill of use-codex / use-gemini / use-cursor / use-copilot. Invoke from PowerShell (droid.ps1), NOT WSL — WSL's droid lacks auth (FACTORY_API_KEY error). Use -m to switch model, --cwd (Windows path) for target dir, -w/--worktree for isolated edits, -r/--resume or --fork for session memory. NOT for small targeted edits or live mid-flight debugging.
- ▌ Use Cursor · oimiragieoUse when delegating bounded coding work to cursor-agent (in WSL, auto-mode, unlimited tokens) to conserve Claude tokens for orchestration + audit — multi-file edits over an explicit task spec where the work is bounded, auditable diff-first, and an Agent-tool subagent's tokens would otherwise be wasted on writing-out-content.
- ▌ Use Gemini · oimiragieo bundleUse when delegating bounded coding, audit, or review work to Antigravity CLI (agy binary, post-2026-06-18 successor to gemini-cli) for a THIRD-OPINION pass alongside Claude + codex (3-way cross-validation), OR when work needs Gemini 3.1 Pro reasoning OR Gemini 3.5 Flash speed. Native Windows + WSL tmux wrapper for headless dispatch. Sibling skill of the other CLI-delegation skills.
- ▌ Use Copilot · oimiragieoUse when delegating bounded coding, audit, or review work to GitHub Copilot CLI. Copilot's edge is GitHub-native MCP integration (issues, PRs, code search) on a GitHub Copilot subscription with no separate billing. Sibling skill of use-codex / use-gemini / use-cursor / use-droid.
- ▌ Rate Fix Loop · oimiragieoDrive a public web surface from baseline to ≥9.5/10 via iterated 3-seat thinktank council rounds. Each round: read verdicts → pick #1 highest-leverage actionable fix → ship → dispatch next round. Validated on 3 pages (news 9.77, benchmarks 8.0 stopped, knowledge-hub 9.73). Default: delegate to a general-purpose subagent.
- ▌ Codebase Audit · oimiragieoUse when asked to investigate, deep-dive, audit, review, or assess a codebase/repo/project for bugs, issues, security gaps, infrastructure risks, optimization opportunities, or unwired/dead/partially-implemented code. Triggers on "investigate the X codebase", "audit/review the repo", "find bugs/security issues", "what's broken/risky in X", "dead code", "infra risks", "deep-dive the code". READ-ONLY: produces a structured report, makes NO edits. This is the code/security/infra analog of frontend-audit (which is visual-only).
- ▌ Use Gotcontext · oimiragieoRoute large context through gotcontext.ai MCP compression before sending to a model — pre-flight, ingest, skeleton reads, PR diffs, remote docs. Use when about to paste a large file, verbose CLI output, git diff, or remote URL into context. Pair with tg for local code reads. Triggers include "compress this", "shrink context", "gc_pre_flight", "ingest_context", "gotcontext MCP", "token savings".
- ▌ Deliver Durably · oimiragieoUse when building any fire-and-forget async delivery or dispatch (send a message, notify, post, trigger a pipeline, enqueue a task) that must survive a process crash or restart — or when a delivery "succeeded" in-session but never arrived.
- ▌ Workflow Ledger · oimiragieoSave and recall runs of the capital-W `Workflow` orchestration tool (and notable `Agent` fan-outs) across sessions and projects. NOT for colloquial "workflows", CI pipelines, or git flow. Invoke AFTER a substantial Workflow/fan-out to record what worked — structure, agentType, model, concurrency, gotchas — so future sessions reuse proven recipes instead of re-deriving them. Invoke BEFORE designing a new Workflow to check the ledger for a proven one. Triggers on "save this workflow", "check the workflow ledger", "reuse a proven workflow", "fan out N agents", "multi-agent orchestration", "have we run a workflow like this".
- ▌ Use Skill Review · oimiragieoUse when auditing, refreshing, or summarizing an existing SKILL.md — it exceeds ~5000 tokens or 500 lines, hasn't been refreshed in >14 days despite high usage, carries stale model/tool/CLI references, or skill summarization is about to be delegated to a sub-agent. Also use when a skill refresh dropped content or a condensed skill stopped triggering. Sibling of superpowers:writing-skills (that one CREATES new skills; this one refreshes existing ones).
- ▌ Chat Archeologist · oimiragieoUse when the user asks "what did we decide about X", "find the session where we discussed Y", "when did we first hit Z bug", "what was the rationale behind W", or any question that needs answers retrieved from prior Claude Code sessions across all projects. Also use proactively when the current session needs context that predates the loaded conversation thread — chat sessions are a queryable backup to long-term memory, and they hold reasoning traces (rejected alternatives, partial understandings, the why) that curated MEMORY.md / project_*.md entries don't capture. Searches the global ~/.claude/projects/*/*.jsonl archive via ripgrep + Python turn-pair extraction. NOT for current state queries (pod status, build status — read those directly), NOT for future plans (read paper §14 work queue or CLAUDE.md), NOT for questions already answered by MEMORY.md (check that first).
- ▌ Blog Post Template · oimiragieoUse when writing or auditing any blog post on your product's site (new post or existing). Enforces the BlogPostLayout container contract AND a Tier-1/Tier-2 anti-AI-slop checklist derived from 15-source Exa research (2026-05-14). Both checks are mandatory before any blog post merges.
- ▌ Common Sense Check · oimiragieoUse when about to call AskUserQuestion, write "want me to..." / "should I..." / "your call", draft an A/B/C/D option tree, or type a soft hedge ("worth doing...", "...or hold?", "no need to wait", "I'll just fire it" as a preface). Also use when a paid resource is idle/crashed, or when about to end a turn on a question instead of an action.
- ▌ Mengto UI Prompting · oimiragieo bundleUse when you need to prompt AI for UI like Meng To: design-first, spec-driven, skimmable. Covers prompt structure, constraints, variations, typography/spacing rules, and iteration workflow for consistent UI outputs.
- ▌ Agent Session Resume · oimiragieo bundleUse when continuing work from a previous AI coding-agent session, handoff transcript, chat log, exported conversation, saved artifact set, or session summary.
- ▌ Gh Release Ship Loop · oimiragieoUse whenever shipping a release on any GitHub-backed project with a CI + main-branch-merge pattern (Vercel, Fly, Render, Cloudflare Workers, or just GH Actions deploying somewhere). Encodes the 10-phase loop validated end-to-end on a multi-hop production ship train (several sequential hotfixes on the same feature) — the failure modes captured here cost real session time and CI cycles. Triggers on intent phrases — "ship a release", "push to main", "merge this PR", "deploy this", "release v1.X.Y", "hotfix", "rebase onto main and merge", "ship train", "land this fix in production", "open + merge a PR".
- ▌ Use Claude In Chrome · oimiragieoUse when an agent (Claude Code main session, cursor-agent, codex-cli, or gemini-cli) needs to drive a real Chrome browser via the claude-in-chrome MCP server — for live UI verification, OAuth flows, dashboard captures, paid-ad screenshots, OAuth secret rotation (e.g., Resend / Polar / Clerk dashboards), competitor recon, or any task that needs to interact with an authenticated web product the user is logged into. Inherits the user's Chrome session (cookies, OAuth, MFA-passed) — does NOT prompt for new logins. Sibling of `use-gemini` and other CLI-delegation skills.
- ▌ Standard Dev Workflow · oimiragieoThe 8-phase standard development pipeline locked-in by user 2026-05-24. Use WHEN starting any non-trivial implementation, planning, research, or debug task. Triggers on intent phrases — "let's build X", "implement X", "design X", "plan X", "research X", "fix this bug", "debug Y". The 8 phases (in order): (1) rewrite the task into a well-scoped spec with Opus, (2) Opus plans using superpowers + lists relevant skills, (3) current web research + Gemini + Opus update the plan, (4) a peer-review council flags conflicts → update plan, (5) codex (preferred) or cursor (long/wiring jobs, unlimited tokens until Sept 2026) implements, (6) Opus + Sonnet review codex work via a code-review skill, (7) Gemini for architecture/deep-research review when needed, (8) Debug = Opus + codex pair. Use sub-agents wherever possible to conserve main-session context.
- ▌ Research Council Defer · oimiragieoUse when deciding whether to BUILD or DEFER a researched feature pre-revenue — the demand-signal-over-stated-interest, set-threshold-first, prereq-chain, written-defer-brief discipline (the build-now-vs-defer axis, distinct from an act-vs-ask common-sense-gate axis).
- ▌ Supply Chain Hardening · oimiragieoUse BEFORE writing any code that extracts an archive, downloads a binary/wheel/tarball, installs a dependency or tool, self-upgrades a running binary, or bootstraps a toolchain (rustup/uv/mise). Triggers on: 'extract a zip/tar', 'extractall', 'download the release asset', 'self-update/auto-upgrade helper', 'install script', 'pin the dependency', 'cargo/npm/pip install in CI', 'bootstrap the toolchain'. Encodes 6 production-shipped, citation-backed hardening checks: zip-slip guard before extractall; time-bound + byte-capped downloads; checksum-gated FAIL-CLOSED installs (incl. detached self-upgrade helpers, verify before os.replace); --locked + exact version pins for CI tools; fail-closed-with-explicit-opt-in for unverified toolchains; committed-checksum for platform installers whose native bootstrap skips binary verification (uv .ps1/.sh). Apply BEFORE writing the code, not after.
- ▌ Tensor Grep Code Audit · oimiragieoUse tensor-grep (tg) as the default code-audit path — callers/blast-radius/scan/doctor/map for fast AST-aware impact analysis before touching shared code. Carries the per-version CLI-contract re-verify rule.
- ▌ Channel Adapter Pattern · oimiragieoUse when an agent's response/formatting logic is (or will be) reachable from more than one delivery channel (chat, SMS, email, push, web). Triggers — before adding a second channel to a single-channel agent, before writing/editing a shared respond()/format_reply()/persona-selection helper, or when a multi-channel agent's voice output sounds like it was written for text (spelled digits, markdown symbols read aloud).
- ▌ Deliver Format Fallback · oimiragieoUse when sending markdown/rich-text formatted messages through a strict wire-format channel API (Telegram, Slack, Discord, SMS/WhatsApp). Triggers — hardening a bot reply path, a message that "sometimes doesn't arrive", or literal *asterisks*/backticks showing in delivered messages. On any parse/entity 4xx, retry with a degraded payload so a malformed render never silently drops a reply on a critical notification channel.
- ▌ Design To Code Pipeline · oimiragieoUse when going from "I want a beautiful page/section/component" to shipped React in <web-app>/src/ — picking a design engine (claude.ai/design vs aura.build vs Figma), wiring the generate → assets → build → audit → ship pipeline, or deciding which generate-path fits ("build a new page", "make our nav look like X", "clone this site", "get my Claude Design mockup into Figma", "this UI looks like AI slop"). Router/meta-skill that bundles the existing UI/UX skills; it selects + sequences them, it does not redefine them.
- ▌ System Prompt Hardening · oimiragieoUse when authoring or hardening an agent's system prompt, persona, or tool descriptions — the non-obvious safety-floor, anti-bluff, and tool-description patterns a generic safety section misses.
- ▌ Trustworthy Cuj Scoring · oimiragieo bundleUse when building or running an agent eval, CUJ score, benchmark, or automated-improvement loop — and especially when a whole lane fails uniformly, a score looks too good or too bad to be true, you're about to trust a new grader/oracle/judge, or a scored harness invokes pnpm / npm / tsc / any .cmd subprocess on Windows. Symptoms: "the agent can't do X" reads as a capability gap, exit-127 / exit 127, a lane scores 0% or 100%, judge and oracle scores blended into one number, write-only-at-end eval crashed and lost work, ≥2 different failure modes on one harness, hill-climbing against a contaminated signal. Keywords: oracle, grader, LLM-as-judge, position bias, Cohen kappa, sealed holdout, decontamination, SNR, MDE, noise floor, checkpoint, status.jsonl, broken oracle, reward hacking, blind relaunch.
- ▌ Use Chrome Devtools MCP · oimiragieoUse when driving Chrome for navigation, form-filling, scraping, or front-end debugging via the chrome-devtools CDP MCP — especially when you need DOM/accessibility-tree access instead of screenshots, or when the official Claude-in-Chrome extension is unavailable because the CLI is on a different Claude account.
- ▌ Web CSS Border Gradient · oimiragieoCreate and apply CSS gradient borders using a pseudo-element mask (the .border-gradient::before technique), including Tailwind-friendly usage and customization of angle, colors, border thickness, and radius. Use when asked for gradient borders, border glow, or the specific mask-composite border gradient snippet.
- ▌ Verify Completion Signal · oimiragieoUse after any long-running subprocess, eval driver, CI gate, or job pipeline run reports apparent success (exit 0 / phase=DONE / "all tests passed") — before accepting the result. Catches the silent-success trap: a process can exit 0 without completing its intended work, and inference from "no error" to "success" is wrong. Require an explicit positive completion artifact (an output file, pass-count line, verdict.json with a status field, non-empty results directory).
- ▌ Verify Plan Against Code · oimiragieoUse BEFORE dispatching any AI/subagent-drafted implementation plan to a build agent (codex, cursor, droid, a fresh Claude). Triggers on: 'dispatch this plan', 'implement this plan', 'send to codex/cursor', 'phase N of the build', any plan an LLM drafted (including the orchestrating Claude, from memory/CLAUDE.md/a summary) for a multi-file or multi-seam change. Run a citation-enforced ADVERSARIAL verification of every seam claim — file paths, function/flag/command names, routing/dispatch logic, test entry points — against the REAL codebase BEFORE coding begins. A claim with no file:line citation is unverified. Bake corrections into the plan before dispatch. This is the PRE-DISPATCH gate, complementary to a POST-DISPATCH verification pass on the agent's actual output.
- ▌ Baseline Dev Architecture · oimiragieoUse when starting or restructuring any software project in ANY language — deciding folder/module layout, dependency direction, public API boundaries, where logic vs entrypoint lives, the testing tiers, smoke tests, or CI gates — when no language-specific architecture skill applies. Language-agnostic parent of typescript-cli-architecture and rust-workspace-architecture. Triggers — "how should I structure this", "where does this file/module go", "feature vs layer", "set up tests and CI", "smoke test", "new package or module?", "structure my Go/Python project", "project layout for <language>".
- ▌ Cost Tiered Orchestration · oimiragieoUse when about to spawn Agent/Workflow subagents, fan out parallel work, or pick a model for delegated work — especially before any multi-agent fan-out, or whenever a task might run on a cheaper model tier than the default.
- ▌ Ultrathink Deep Dive Loop · oimiragieoFull deep-dive audit loop — bugs, edge cases, backlog, current competitive web research, TDD fix waves, council-reviewed plans, re-audit until clean. Use for ultrathink mandates, /deep-dive, security audits, complete backlog, competitive analysis. Routes orchestrator by provider (Claude Opus vs Fable, Codex gpt-5.5, Cursor Auto vs Opus, agy Gemini 3.5/3.1). Spawns workflows + subagents; a peer-review council audits plans.
- ▌ Ground Actions To Registry · oimiragieoUse when an agent will name a domain entity it does not control — a repo, channel, tool, agent, skill, model alias, team — and act on it; or when an agent reports an action on an entity that may not exist.
- ▌ Authoring Dynamic Workflows · oimiragieoUse when a task is too big for a handful of subagents or needs cross-verification — codebase audits, multi-file migrations, cross-checked research, plan-from-N-angles, multi-source sweeps. Codifies the built-in Workflow tool (dynamic workflows), the authoring API, quality patterns, the framework-decision rule, what to download, and this project's reusable templates + house constraints.
- ▌ Rust Workspace Architecture · oimiragieoUse when creating, structuring, or adding a crate/module to a Rust Cargo workspace (CLI, agent, or backend) — deciding workspace layout, when to make a new crate vs a module, dependency direction, error types, where tests live, snapshot/property tests, the test runner (nextest), smoke tests, clippy/rustfmt gates, or CI. Triggers — "new crate or module?", "set up the workspace", "where do integration tests go", "insta snapshot", "cargo nextest", "smoke test the binary", "thiserror vs anyhow", "workspace.dependencies".
- ▌ Typescript CLI Architecture · oimiragieoUse when creating, structuring, or adding a feature to a TypeScript/Node/Bun CLI, agent, or backend project — deciding folder layout, where a new tool/command/module goes, naming, module boundaries, the test framework (Vitest), where tests live, smoke tests, or CI gates. Triggers — "where should this file go", "new feature folder", "set up tests", "vitest config", "smoke test the CLI", "structure this TS project", "feature vs layer folders".
- ▌ Arch Driven Release Workflow · oimiragieoUse when the user asks for a 'full' or 'end-to-end' release driven by an architecture document — typically a multi-track release landing a substantial product slice (new product line, multi-surface refactor, feature bundle). Triggers: 'design a doc for this system, then plan it, then ship it', 'ultrathink this through to ship', 'do all 10 phases', 'architecture refresh', 'convergence loop the doc, then implement, then push', or any prompt naming 4+ sequential phases ending in push/merge. Meta-skill bundling writing-plans, a peer-review council / codex peer-review, subagent-driven-development, verification-before-completion, gh-release-ship-loop, and blog-post-template.
- ▌ Dogfood The Shipped Artifact · oimiragieoUse AFTER publishing any CLI, tool, or service package — and BEFORE declaring a release good. Triggers on: 'release shipped', 'published to PyPI/npm', 'v1.X.Y is live', 'the tests all pass', 'CliRunner passes', 'TestClient passes'. Never trust an in-process test runner as proof the REAL shipped binary works: CliRunner (Click/Typer) and FastAPI TestClient invoke the app object DIRECTLY, bypassing the entry-point / front-door bootstrap layer. Install the PUBLISHED artifact in a clean env (Docker or fresh venv) and invoke the REAL binary across every feature flag combination before declaring the release good.
- ▌ Design Then Apply Loadbearing · oimiragieoUse when changing LOAD-BEARING code (a transport/driver path, a money-path or safety gate, the eval runner, a reload/merge contract, a release script) with help from subagents — ESPECIALLY when the working tree is concurrently dirty with another agent's in-flight lanes so worktree isolation cannot protect the human-owned mainline. Triggers on "have a subagent fix the transport/driver/money-path", "multi-gap hardening of one file", "an agent edit broke a contract test in another file", "a concurrent-agent git-add swept my change", "apply-then-verify the agent's patch", or any time an agent EDIT would be a hypothesis you must not land blind. NOT for greenfield/throwaway code or large parallel refactors with no shared mainline — those want worktree-isolated editor agents instead.
- ▌ Verify The Claim Not The Label · oimiragieoUse when a status label (DONE / RESOLVED / PASSING / CACHED / READY / SUCCESS / "it completes") is the only evidence that something works. Triggers on: "the gate is green", "that bug is resolved", "the cache is ready", "I ran it and it passed", "the test completed", "a generated report exists but is empty", "CI shard 1 passed but shards 2-3 never ran", "a cache said READY but was corrupt". The discipline: a SUCCESS label is a HYPOTHESIS until the bytes / per-sample data / real code confirm it. Extends SILENT-SUCCESS REFLEX (already in CLAUDE.md) to the agent's OWN claims and OWN live checks, not just external signals.
- ▌ Verify Claims Against Execution · oimiragieoUse when about to mark work complete/fixed/passing, accept a subagent's self-reported success or score, or trust any grader/oracle/judge/auto-rater — especially before running a scored batch.
- ▌ Worktree Fanout Verification Gate · oimiragieoUse when an orchestrator fans work out to worktree-isolated subagents (isolation:'worktree') and is about to integrate or PR the returned branches — especially when an agent reports "tests pass" / "N green" / "ruff clean". Worktree checkouts CANNOT self-test (no project venv), so their results are unverified hypotheses. Symptoms: parallel fan-out of code edits, "branch already used by worktree", Formatting/Linting CI failure after a green local run, scoped tests green but full CI red.
- ▌ Creation Feasibility Gate · oimiragieo bundleValidate whether a proposed new artifact is feasible in the current stack before creator workflows run.
- ▌ Error Recovery Escalation · oimiragieo bundle5-level error recovery escalation: retry, nudge, replan, fallback, force-done — each with entry criteria and timeout before escalating
- ▌ Mobile First Design Rules · oimiragieo bundleFocuses on rules and best practices for mobile-first design and responsive typography using tailwind.
- ▌ Service Class Conventions · oimiragieo bundleDefines the structure and implementation of service classes, enforcing the use of interfaces, ServiceImpl classes, DTOs for data transfer, and transactional management.
- ▌ Agent Enhancement Worker · oimiragieoAgent frontmatter enhancements — disallowedTools, mcpServers scoping, fork_eligible field
- ▌ Memory Discipline Worker · oimiragieoMemory index discipline — cap enforcement, pruning, archival, health reporting
- ▌ Routing Architect Worker · oimiragieoImplements hierarchical routing architecture (sub-routers, routing tables, hook updates)
- ▌ Context Driven Development · oimiragieo bundleContext-Driven Development methodology - treating project context as managed artifacts alongside code for consistent AI interactions and team alignment.
- ▌ Convex Development General · oimiragieo bundleApplies general rules for Convex development, emphasizing schema design, validator usage, index-first query patterns, function registration, and correct handling of system fields.
- ▌ Incident Runbook Templates · oimiragieo bundleCreate structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.
- ▌ Mobile UI Development Rule · oimiragieo bundleGeneral rules pertaining to Mobile UI development. Covers UI/UX best practices, state management, and navigation patterns.
- ▌ Pyqt6 UI Development Rules · oimiragieo bundlePyQt6 desktop GUI development rules -- signal/slot architecture, QSS theming, QThread concurrency, layout management, and cross-platform rendering. Enforces MVC separation and responsive UI patterns.
- ▌ React Native Skills Vercel · oimiragieo bundleReact Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
- ▌ Restcontroller Conventions · oimiragieo bundleSpecifies standards for RestController classes, including API route mappings, HTTP method annotations, dependency injection, and error handling with ApiResponse and GlobalExceptionHandler.
- ▌ Tauri Svelte UI Components · oimiragieo bundleRules specific to Svelte UI component development in Tauri applications.
- ▌ Token Saver Adaptive Ratio · oimiragieo bundleHelper skill that exposes adaptive token-saver compression ratios for large context corpora.
- ▌ Troubleshooting Regression · oimiragieo bundleRegression troubleshooting workflow for hook/router/memory/search failures with enforced evidence and fix validation
- ▌ Dispatching Parallel Agents · oimiragieo bundleConcurrent investigation of independent failures. Use when multiple unrelated issues need parallel resolution.
- ▌ Ecosystem Integrity Scanner · oimiragieo bundleDeeply analyzes Agent Studio framework structural health: catching phantom require() references, wrong module depth paths, missing skill/agent dependencies, bloated configurations, archived references in active code, stale catalog counts, and empty tool/skill directories.
- ▌ Kafka Development Practices · oimiragieo bundleApplies general coding standards and best practices for Kafka development with Scala.
- ▌ React Best Practices Vercel · oimiragieo bundleReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
- ▌ Property Based Testing · oimiragieo bundlefast-check patterns for JS/TS — 6 canonical property categories with worked examples targeting agent-studio utilities (path normalization, safe-json, glob-to-regex, routing logic)
- ▌ Requesting Code Review · oimiragieo bundleDispatch code-reviewer agent for two-stage review. Use after completing implementation tasks.
- ▌ Compliance Fix Worker · oimiragieoFixes test failures, compliance gaps, and validation issues in the agent-studio ecosystem
- ▌ Mission Engine Worker · oimiragieoBuilds mission engine modules, orchestration wiring, plugin system, headless execution, and code review infrastructure
- ▌ Compliance Policy Check · oimiragieo bundleValidate planned changes against local framework rules and policy guardrails before implementation or creation.
- ▌ Dynamic API Integration · oimiragieo bundleDiscover, parse, and call external HTTP APIs at runtime using OpenAPI specs, tool templates, and iterative chaining. Adapted from UTCP (Universal Tool Calling Protocol) patterns for Node.js and Claude Code agents.
- ▌ Feature Flag Management · oimiragieo bundleFeature flag lifecycle management -- safe feature toggling, gradual rollouts, A/B testing patterns, flag cleanup strategies, and technical debt prevention. Covers LaunchDarkly, Unleash, OpenFeature, and custom implementations.
- ▌ Project Stage Detection · oimiragieo bundleDetect project maturity stage (new/early/mid/mature) from file structure and route to appropriate onboarding workflow
- ▌ Spec To Code Compliance · oimiragieo bundleVerify that implementation code faithfully implements its specification — checks function contracts, API contracts, and protocol compliance against source specifications
- ▌ State Management Expert · oimiragieo bundleState management expert including MobX, Redux, Zustand, and reactive patterns
- ▌ Binary Analysis Patterns · oimiragieo bundleMaster binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.
- ▌ Form Validation With Zod · oimiragieo bundleEnforces the use of Zod for form validation throughout the project.
- ▌ Implementation Readiness · oimiragieo bundleGate for HIGH/EPIC tasks that validates plan completeness and architecture compliance before implementation begins
- ▌ On Call Handoff Patterns · oimiragieo bundleMaster on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.
- ▌ Task Management Protocol · oimiragieo bundleProtocol for task synchronization, context handoff, and cross-session coordination using Claude Code task tools. Ensures agents properly update tasks with findings and enables seamless work continuation.
- ▌ Token Saver Memory Dedup · oimiragieo bundleHelper skill that deduplicates token-saver memory records before persistence.
- ▌ Integration Test Worker · oimiragieoBuilds cross-area integration tests for the mission engine module system
- ▌ Authentication Flow Rules · oimiragieo bundleOAuth 2.1 compliant authentication flows (MANDATORY Q2 2026). PKCE required for ALL clients, Implicit Flow removed, modern token security.
- ▌ Behavioral Loop Detection · oimiragieo bundleDetect when agents are stuck in repetitive action loops using a rolling 20-action window with escalating nudges — replan after 3 similar actions, explore after 5, force-done after 8.
- ▌ Best Practices Guidelines · oimiragieo bundleSpecifies best practices, including following RESTful API design principles, implementing responsive design, using Zod for data validation, and regularly updating dependencies. This skill promotes modern coding standards and helps developers write consistent, maintainable code.
- ▌ Building Secure Contracts · oimiragieo bundleSmart contract and secure API contract security analysis — invariant checking, access control, reentrancy, and integer overflow patterns. Implements Checks-Effects-Interactions pattern, formal invariant verification, and OpenSCV vulnerability taxonomy for Solidity/EVM and Rust/Solana contracts.
- ▌ CI CD Implementation Rule · oimiragieo bundleUses GitHub Actions or GitLab CI for CI/CD implementation.
- ▌ Skills Repair Worker · oimiragieoFixes skill tests, catalog mismatches, missing workflows, and improves ecosystem gate scores
- ▌ API Development Expert · oimiragieo bundleAPI development expert including REST design, OpenAPI, and documentation
- ▌ Audit Context Building · oimiragieo bundleUltra-granular code analysis for deep architectural context building. Line-by-line and block-by-block analysis using First Principles, 5 Whys, 5 Hows methodology at micro scale. Builds mental models, tracks invariants and assumptions, and maps cross-function call flows for security audit preparation.
- ▌
- ▌
- ▌ Helm Chart Scaffolding · oimiragieo bundleDesign, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments.
- ▌ K8S Manifest Generator · oimiragieo bundleCreate production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.
- ▌ Memory Quality Auditor · oimiragieo bundleAudit memory retrieval quality (drift, staleness, citation-groundedness) and produce remediation backlog.
- ▌ Pipeline Reflection UX · oimiragieo bundleImprove router-facing pipeline and reflection narration to reduce noisy status churn and make Step 0/Reflection outcomes explicit. Use when updating Router output contract, reflection reminder wording, or post-pipeline notification batching.
- ▌ Content Security Scan · oimiragieo bundleAutomated security scanner for external skill/agent content fetched from GitHub or web sources. Runs a 7-step PASS/FAIL security gate against fetched markdown/text content.