tons-of-skills-marketplace

Hyperflow design phase. Use when designing a UI / visual system or making a screen look good — verbs like "design the UI", "make it look good", "design the screen", "visual design", "design system". Establishes or extends a domain-grounded design system, researches real-world prior art, and renders it slop-free. Thinking and taste, not building.

Hyperflow execution phase. Use when a task file exists in .hyperflow/tasks/ and the work needs building — verbs like build, implement, add, refactor, "wire up", "run the plan", "execute the task". Works batches sequentially with self-review and per-task commits. In Antigravity there is no sub-agent fan-out — the single agent does each batch itself.

Hyperflow planning phase. Use when a request needs shaping before code — a rough prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. Verbs like plan, design, brainstorm, explore, "should we", "what's the best way to", scope, decompose, "plan out", "break down", "enhance this prompt". Thinking, not building. Writes an optional spec to .hyperflow/specs/<slug>.md and a task file to .hyperflow/tasks/<slug>.md, then hands off to hyperflow-dispatch.

Build deterministic CI for Ideogram adapters with sanitized schemas, fixtures, secret isolation, and a trusted optional live lane. Use when adding or auditing automated integration tests. Trigger with "test Ideogram in CI", "build Ideogram contract tests", or "secure an Ideogram GitHub workflow".

Diagnose Ideogram authentication, validation, throttling, capacity, safety, and asset-expiry failures by evidence class. Use when a request fails or returns no usable image. Trigger with "debug Ideogram 422", "fix Ideogram 429", or "diagnose an empty Ideogram URL".

Select and operate the current Ideogram generation route across V4 sync, V4 async, transparency, and P-Image. Use when designing a text-to-image workflow with explicit latency and output contracts. Trigger with "generate with Ideogram V4", "choose an Ideogram model route", or "build transparent Ideogram images".

Choose among Ideogram edit, remix, describe, magic-prompt, upscale, background, reframe, and transformation tools. Use when modifying or analyzing an image under explicit rights and safety controls. Trigger with "edit with Ideogram", "describe an image for Ideogram", or "choose an Ideogram image tool".

Govern Ideogram prepaid spend through admission budgets, route choice, output bounds, useful-result accounting, and cleanup. Use when reducing cost or designing billing controls. Trigger with "cut Ideogram spend", "budget Ideogram generations", or "audit Ideogram API cost".

Govern Ideogram prompts, uploads, structured descriptions, generated assets, temporary URLs, metadata, and training datasets through deletion. Use when designing privacy or retention controls. Trigger with "map Ideogram data", "set Ideogram retention", or "audit Ideogram image storage".

Assemble a sanitized Ideogram support bundle with contract, status, queue, storage, and deployment evidence. Use when escalating an incident without exposing keys, prompts, images, or temporary URLs. Trigger with "build an Ideogram debug bundle", "sanitize Ideogram evidence", or "prepare an Ideogram support case".

Deploy an Ideogram server boundary with queues, storage, safety enforcement, observability, canaries, and rollback. Use when shipping a new runtime or changing production topology. Trigger with "deploy Ideogram", "ship an Ideogram worker", or "review Ideogram production architecture".

Map Ideogram Owner, Admin, and Member roles to application-owned tenant, budget, key, media, publishing, and audit permissions. Use when designing or reviewing enterprise access control. Trigger with "design Ideogram RBAC", "audit Ideogram team roles", or "separate Ideogram duties".

Generate and persist one bounded Ideogram V4 image through the current multipart endpoint. Use when testing a first server-side request or reviewing a minimal integration. Trigger with "first Ideogram image", "test Ideogram V4", or "build an Ideogram smoke test".

Analyze and contain Ideogram incidents involving credentials, billing, throttling, unsafe output, webhook loss, asset expiry, or storage failure. Use when coordinating production response and recovery. Trigger with "Ideogram incident", "contain an Ideogram outage", or "recover missing Ideogram images".

Configure Ideogram API access with prepaid billing, server-side credentials, and explicit team ownership. Use when installing or auditing a new Ideogram environment. Trigger with "set up Ideogram API", "configure an Ideogram key", or "audit Ideogram authentication".

Build a fixture-first local loop for Ideogram multipart requests, async states, safety outcomes, and expiring assets. Use when developing or testing without uncontrolled API spend. Trigger with "mock Ideogram locally", "test Ideogram fixtures", or "debug an Ideogram adapter".

Plan and execute a staged migration across Ideogram legacy, V3, V4, P-Image, and tool endpoints with semantic comparison and rollback. Use when modernizing a production image workflow. Trigger with "migrate Ideogram legacy API", "move Ideogram V3 to V4", or "redesign an Ideogram image pipeline".

Isolate Ideogram development, staging, and production across keys, budgets, webhook routes, storage, data, and promotion evidence. Use when designing or auditing environment separation. Trigger with "separate Ideogram environments", "configure Ideogram staging", or "audit Ideogram promotion".

Instrument Ideogram request, queue, async, safety, storage, latency, and spend signals without logging image content. Use when building dashboards, alerts, or SLO evidence. Trigger with "monitor Ideogram", "add Ideogram metrics", or "audit Ideogram telemetry".

Optimize Ideogram latency and throughput through route choice, bounded media, concurrency, async handling, and immediate storage. Use when improving an established workload without weakening quality or safety. Trigger with "speed up Ideogram", "profile Ideogram latency", or "optimize Ideogram throughput".