Results for “fallback”

Create an Agent SKILL.md fallback for an existing find-XXXX finder that relies on a fragile discovery foundation — above all LLM_DECOMPILE (patterns C/D/E), which matches the decompiled shape of a predecessor function against a stored reference and breaks when a symbol is inlined or de-inlined in a way the reference does not cover. The generated fallback coexists with the preprocessor and runs only when it returns failure, recovering every target robustly by decompiling the predecessor and following the inline/de-inline boundary with semantic anchors. Use when a finder broke on a game update, or you want to durably backstop one before it does. The recipe generalizes to any finder foundation. Triggers: create agent skill fallback, add SKILL.md fallback, robust fallback for finder, backstop LLM_DECOMPILE finder, final guarantee skill

The English summary is being prepared. Showing the original description.

Review picture elements that select images by format or display conditions. Check fallback images, alternative text, dimensions, and source ordering, then provide corrected HTML with JPEG or PNG fallbacks for browsers that cannot use the selected formats.

• Checking fallback images for AVIF or WebP delivery
• Reviewing picture element order and attributes
• Fixing image markup with missing descriptions or dimensions

Fix test failures when adding retry/fallback logic causes mock call count mismatches. Use when: (1) Test fails with "Expected: <1>, Actual: <2>" or similar call count errors after adding retry or fallback mechanisms, (2) MissingStubError appears for methods in new fallback code paths, (3) Mockito verify().called(N) assertions fail after behavior changes. Applies to Dart/Flutter with Mockito, but pattern is universal.

The English summary is being prepared. Showing the original description.

Progressive WebGL fallback: production-level capability detection, static SVG fallback. Use when implementing, reviewing or testing progressive webgl fallback for React, Vite, Next.js or Perfect_AI projects.

The English summary is being prepared. Showing the original description.

Group AI providers and models behind one model ID in OmniRoute. Choose among 19 routing strategies, define fallback sequences for failures, simulate which provider will be selected, and inspect latency, success rates, and costs.

• Call multiple AI models through one model ID
• Configure fallback order for failures
• Simulate routing decisions before making API calls

Build a Claude Code mod, a plugin that extends behavior through event hooks, from ruflo’s template. Sets up function hooks with a classic fallback, user options, status reporting, validation, and tests.

• Creating a mod that extends Claude Code behavior
• Implementing function hooks with a classic fallback
• Adding user settings and mod status reporting

Create a custom offline page and configure a service worker, a browser background script, to cache it in advance. Show it when page navigation fails, and review resource dependencies and fallback conditions.

• Add an offline page to a PWA
• Guide users during connection loss
• Review offline page caching

Review HTML object elements and add meaningful fallback content for people who cannot load or view embedded material. Identify missing alternatives, suggest text or appropriate HTML elements, and explain how to verify accessibility.

• Find object elements with missing fallback content
• Add alternatives for embedded content that fails to load
• Review whether fallback content conveys equivalent information

Review contracts against your organization’s negotiation guidelines, flag departures from preferred terms, and explain business implications. Produce proposed clause revisions, fallback positions, and negotiation priorities, with findings intended for review by qualified legal professionals.

• Reviewing vendor or customer agreements
• Checking clauses against internal negotiation guidelines
• Preparing proposed revisions and fallback terms

Configure GKE ComputeClasses, which define preferred computing resources for workloads. Set fallback options between Spot and on-demand VMs, target GPUs or machine families, control class usage, and investigate pods waiting for suitable nodes.

• Configuring fallback from Spot VMs to on-demand capacity
• Selecting GPUs, TPUs, or machine families
• Restricting ComputeClass editing and workload usage

Retrieve Chinese medical guidelines, drug information, and regulatory documents when original sources are inaccessible. It checks document identity and version before using alternative copies, while keeping summaries and reposts separate from independent clinical evidence.

• Finding a guideline when its original page is inaccessible
• Checking whether an alternative PDF matches the original version
• Reviewing fallback rules for Chinese medical sources

Continue Python work when the code sandbox is unavailable by running scripts through run_shell. The workflow covers recognizing connection failures, installing required packages, reading and writing workspace files, and checking execution results.

• Continuing calculations during an e2b outage
• Running Python after a sandbox connection failure
• Processing and saving JSON through the shell

Recover document and PDF generation tasks when sandbox errors provide little detail. Checks Python libraries, runs generation through the shell, captures errors, and verifies output files, with alternative PDF tools and text output as fallback options.

• Recovering PDF generation after unclear sandbox errors
• Checking required PDF libraries before generation
• Capturing detailed document generation errors

Extract PDF text using a sequence of tools when one method fails. Validate downloaded files, check whether the extracted text is substantial, record the successful method, and investigate alternative sources if extraction remains unsuccessful.

• Extracting text from regulatory documents and handbooks
• Checking whether a PDF download returned an error page
• Trying another tool after empty or garbled text extraction

Recover from Pandoc PDF generation failures by checking installed PDF engines and retrying alternatives. The guide matches engines to Unicode text, simple Latin documents, or HTML-based layouts, and includes an automated fallback script.

• Retrying failed Pandoc PDF conversions
• Choosing an engine for Japanese or other Unicode text
• Automating PDF engine fallback in document pipelines

The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a website, a topic explainer, a GitHub PR, existing footage, a short motion graphic, or a Remotion port — prefer it (see /hyperframes); use this only as the general fallback when none fit.

The English summary is being prepared. Showing the original description.

Build AI fallback systems with model routing. TRIGGERS - Use when user needs help with ai-fallback-system related tasks.

The English summary is being prepared. Showing the original description.

Enforces error handling standards: silent error prohibition, custom error class hierarchy (AppError base with category never-fallback / transient / permanent, cause preservation, ValidationError / UnauthorizedError / UpstreamError etc. — canonical definitions in ERRORS.md), external-boundary normalization (normalizeExternalError), Result pattern (Result.ok/Result.fail), proper try-catch with error type checking, structured error logging with a single Logger contract, fallback prohibition categories (isNeverFallback), and HTTP status code mapping. Use when implementing error handling, reviewing catch blocks, or designing error responses.

The English summary is being prepared. Showing the original description.

Build AI fallback systems with model routing. TRIGGERS - Use when user needs help with ai-fallback-system related tasks.

The English summary is being prepared. Showing the original description.

Tiered web access router. TIER 1 insane-search: headless extraction plus WAF bypass via curl_cffi, yt-dlp, Jina Reader, public APIs, Playwright fallback for blocked/403/Cloudflare pages, articles, YouTube subtitles. TIER 1.5 agent-reach: platform-native readers for Chinese/social platforms: Xiaohongshu, Douyin, Weibo, Bilibili, V2EX, WeChat, plus Twitter/Reddit/LinkedIn/GitHub. TIER 2 aside-browser FIRST (user's real logged-in browser: aside exec agent, aside repl Playwright), then CloakBrowser + agent-browser as the stealth fallback: source-patched stealth Chromium (CloakBrowser) driven over CDP by the agent-browser CLI for clicks, forms, screenshots, video, cookie login, QA/dogfood, Electron apps. Triggers: browse, stealth browser, CloakBrowser, agent-browser, cloak launch, bypass bot detection, blocked site, scrape, fill form, screenshot, import cookies, play youtube, podcast transcript. NOT for simple searches (web-search), fetches (webfetch), or messaging/workspace platforms — Slack/Discord/Notion/Gmail have Tier-1 CLIs in external-communication; come here only as its fallback.

The English summary is being prepared. Showing the original description.

Prepare and inspect plans for opening interactive commands in a visible WezTerm window while keeping the executable and arguments separate. Check terminal availability, preview launches as JSON, and use fallback or recovery modes when needed.

• Opening an interactive CLI in a new terminal window
• Starting an SSH session or local development process
• Inspecting a launch plan without opening a window

Diagnose image export and download failures in browsers and Electron. Separate image data preparation from file saving, investigate empty files and blocked writes, and choose a suitable fallback save method.

• Investigating exported images saved as 0 KB files
• Fixing failures in Save As dialogs and file writes
• Troubleshooting image downloads in Electron

Research current public information by checking original sources, recording relevant passages, dates, and URLs, and using browser interaction when needed. Cross-check important claims and clearly separate supported facts from inference.

• Checking current information against official sources
• Comparing evidence across multiple web pages
• Researching pages that require browser interaction

Review pages for situations where JavaScript is disabled or unavailable. Check that important content appears in the initial HTML and that noscript elements offer useful alternatives, then suggest changes to keep core content and navigation accessible.

• Checking page content with JavaScript disabled
• Adding alternatives for JavaScript-dependent features
• Reviewing initial HTML for important content