Results for “launcher”

Routes user requests to specialist skills for AEM 6.5 LTS workflow model design, custom step development, launcher configuration, triggering, debugging, and triaging.

Planning Product Launch

Build a launch checklist with owners, dates, dependencies, decision gates, and follow-through.

Launch Plan

Start or patch Dynamo router modes and run router endpoint smoke checks for round-robin, KV-aware, least-loaded, or device-aware routing.

Launch distributed Megatron-LM training jobs on a SLURM cluster with a minimal sbatch skeleton, environment-variable setup for torch.distributed.run, CUDA_DEVICE_MAX_CONNECTIONS rules, container conventions, monitoring, and per-rank failure diagnosis.

Scaffolds new Blazor web applications with the correct render mode, project structure, and authentication setup.

Mvp Pressure Launch

Implements deep linking, universal links (iOS), and app links (Android) in Flutter using go_router, including domain configuration, file association, and URL-based dynamic routing.

Launch a fixed-supply V3 token on Robinhood Chain (4663) via PonsLaunchFactory (pons.family), reverse-discover the factory from live PonsLauncherToken tokens, prepare launchToken txs, and verify TokenLaunched receipts. Use when the user says "launch on Pons", "pons.family launch", "PonsLaunchFactory", "launchToken", "PonsLauncherToken", "V3 launch on Robinhood", or wants agents to create a Pons token. Does NOT use RH bonding-curve createToken (rh-bonded-launch), does NOT mint Solana $CLAWD, and does NOT use NOXA Fun factories.

Startup skill router: maps any incoming request to the correct skill using Quick Lookup table and _manifest.json. Loaded automatically at session start. Triggers on: every new request — this is the dispatch layer, not a user-facing skill. NOT for: executing tasks directly — always routes to a domain-specific skill.

Use only for video game projects; plan Steam launch, festivals, creator outreach, demo timing, community, and wishlist targets

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.

Sets up internationalization by extracting hardcoded user-facing strings to locale files, auto-detecting the framework, configuring the appropriate i18n library, handling pluralization, formatting, and RTL support.

Harness Router

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.

Remix patterns including loaders, actions, nested routing, progressive enhancement, and deployment strategies.

Scaffolds a per-task verification skill for a repo, including a dev-local launcher, a browser driver, and a verification SOP that spawns a sub-agent to drive the app and produce proof.

Detect PowerShell Empire framework artifacts in Windows event logs by identifying Base64 encoded launcher patterns, default user agents, staging URL structures, stager IOCs, and known Empire module signatures in Script Block Logging events.