Skip to content
Skills Library
DevOps & cloud · Planning

ideogram-reference-architecture

/ideogram-reference-architecture

Design an Ideogram service boundary with policy gateway, queue, async state, verified webhooks, polling, moderation, storage, and audit. Use when creating or reviewing a production architecture. Trigger with "architect Ideogram", "design an Ideogram service", or "review an Ideogram system diagram".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Design an Ideogram service boundary with policy gateway, queue, async state, verified webhooks, polling, moderation, storage, and audit. Use when creating or reviewing a production architecture. Trigger with "architect Ideogram", "design an Ideogram service", or "review an Ideogram system diagram".

Triggers from the description

architect Ideogramdesign an Ideogram servicereview an Ideogram system diagram

Arguments

/ideogram-reference-architecture <workload> <tenant-model> <slo>
Original author description

Design an Ideogram service boundary with policy gateway, queue, async state, verified webhooks, polling, moderation, storage, and audit. Use when creating or reviewing a production architecture. Trigger with "architect Ideogram", "design an Ideogram service", or "review an Ideogram system diagram".

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Error Handling
  9. Output
  10. Examples
Original SKILL.md headings · 63 lines, 520 words
SKILL.md preview
---
name: ideogram-reference-architecture
description: >-
  Design an Ideogram service boundary with policy gateway, queue, async state, verified webhooks, polling, moderation, storage, and audit. Use when creating or reviewing a production architecture. Trigger with "architect Ideogram", "design an Ideogram service", or "review an Ideogram system diagram".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<workload> <tenant-model> <slo>"
version: 1.11.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, ideogram, architecture]
model: inherit
effort: high
compatibility: "Designed for Claude Code; architecture work is evidence-led and deployment-neutral"
---
# Ideogram Reference Architecture

## Overview

Define ownership and data flow for a production Ideogram integration. Keep user authorization, paid vendor authority, request validation, async state, event verification, content review, durable media, and audit evidence as explicit components.

## Prerequisites

- Workload, tenant and identity model, data class, SLO, budget, region, and retention policy.
- Expected endpoint mix, input sizes, concurrency, publication destinations, and failure modes.
- Owners for billing, security, moderation, storage, operations, and vendor escalation.

## Current Contract

The API uses server-side `Api-Key`, endpoint-specific multipart requests, sync and async generation, item-level safety, signed async webhooks, polling, and temporary asset URLs. Default capacity is 10 in-flight requests. These contracts require stateful application orchestration even when the product experience is synchronous.

## Authentication

Place `IDEOGRAM_API_KEY` only in a private vendor adapter. The policy gateway authenticates application identities and authorizes tenant, use case, spend, input, output, and destination separately.

## Instructions

1. Define ingress and policy gateway boundaries for identity, tenant, rights, media validation, safety, copyright settings, budget, and admission.
2. Route accepted work to a durable queue and an account-level concurrency controller.
3. Use a vendor adapter that owns endpoint schemas, multipart, deadlines, typed errors, and content-free telemetry.
4. Persist request and `generation_id` state before async delivery, then reconcile verified webhooks with polling.
5. Pass safe outputs through a downloader that validates media and stores opaque tenant-scoped objects immediately.
6. Publish only from the application object store after required review; never authorize from a vendor URL.
7. Add outbox, audit, deletion, incident, canary, and rollback paths with explicit owners.

## Tool Discipline

Use Read, Glob, and Grep to ground the design in the actual repository and infrastructure. Use Write and Edit for approved architecture records or implementation. Do not provision services, create keys, or deploy from a design invocation.

## Approval Boundaries

Require accountable review for trust-boundary changes, public ingress, data residency, sensitive media, external publication, retention, spend, and production topology. Record unresolved assumptions as blockers.

## Error Handling

- Keep queue acceptance distinct from vendor acceptance and durable asset completion.
- Reconcile duplicate or missing events without duplicate paid submissions.
- Quarantine unsafe, malformed, oversized, or tenant-mismatched media before publication.

## Output

Return components, flows, trust boundaries, state model, endpoint choices, SLO and capacity model, data lifecycle, controls, owners, failure paths, open decisions, and rollback architecture. Exclude secret or content examples.

## Examples

- Flow: application client -> policy gateway -> queue -> vendor adapter -> state store -> verified webhook or poller -> safe downloader -> object store -> reviewer -> publisher.
- Keep audit records content-free while placing regulated media in its approved retention boundary.

## Validation

Walk happy, unsafe, throttled, duplicate, missing-webhook, expired-URL, storage-failure, and rollback scenarios. Verify every state and retained datum has one owner and deletion path.

## Resources

- [Current first-party evidence map](references/official-docs.md) — use the dated endpoint, webhook, billing, team, and training links as the contract index for this workflow.
- Recheck the endpoint-specific page and current OpenAPI description before relying on an enum, limit, beta feature, or lifecycle claim.
- Record live observations as environment-specific evidence, not as universal vendor guarantees.
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 2 KB

Versions

RepositoryScoreLicence
This page · jeremylongshore/tons-of-skills-marketplace100MIT
HelixDevelopment/agent100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version f932ce394b14 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ideogram-deploy-integration
    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".
  • 100ideogram-ci-integration
    Configure Ideogram CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Ideogram tests into your build process. Trigger with phrases like "ideogram CI", "ideogram GitHub Actions", "ideogram automated tests", "CI ideogram".
  • 100ideogram-observability
    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".
  • 100ideogram-observability
    Set up comprehensive observability for Ideogram integrations with metrics, traces, and alerts. Use when implementing monitoring for Ideogram operations, setting up dashboards, or configuring alerting for Ideogram integration health. Trigger with phrases like "ideogram…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.