agentsclimarketplace
Sign in

Amadeus infrastructure design

Skill amadeus-dlc/amadeus/dist/codex/.agents/skills/amadeus-infrastructure-design

Run the AI-DLC `infrastructure-design` stage (construction phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage infrastructure-design --single`: the engine emits one run-stage directive for infrastructure-design and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.From its SKILL.md

Install
npx -y skills add amadeus-dlc/amadeus --skill amadeus-infrastructure-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 282 tokens by cl100k_base, as published. Nobody here has run it

AI-DLC Stage Runner — infrastructure-design

Run the infrastructure-design stage on its own. This is opt-in packaging over /amadeus --stage infrastructure-design --single; the same stage is always reachable via that flag without this skill.

Steps

  1. Ask the engine for the single-stage directive:

    bun .codex/tools/amadeus-orchestrate.ts next --stage infrastructure-design --single

    The engine emits one run-stage directive for infrastructure-design (carrying the lead agent, the resolved consumes/produces paths, the rules and sensors in context, and — on this first directive — the conductor persona). Run the stage exactly as the directive describes; do not load the conductor persona by hand, the engine delivers it.

  2. When the stage's work is done, commit the single-stage record:

    bun .codex/tools/amadeus-orchestrate.ts report --single --stage infrastructure-design --result completed

    This records a STAGE_STARTED / STAGE_COMPLETED pair under a synthetic workflow id and stops. It NEVER writes the main workflow's Current Stage — a single-stage run is isolated by design (the tool refuses to advance the main workflow).

Gives 0 of the 12 instructions most design frontend skills give in 282 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • Ask engine for single-stage nfr-design directive
  • Run the stage exactly as directive describes
  • Commit the single-stage record after stage completion

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,764. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.