Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

aspire-deploy-pipeline

Estrelas0

Forks0

Atualizado24 de maio de 2026 às 21:13

Reference for adding and ordering Aspire deploy pipeline steps, tagging steps, parameterizing deployment with AddParameter, configuring per-environment values with WithEnvironment, and using PipelineStepContext services. Use when asked to add a pipeline step, order deploy steps, set up infrastructure provisioning, configure deployment, or wire up aspire deploy.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

sliekens

sliekens/agentic

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

9 arquivos

SKILL.md

readonly

name	aspire-deploy-pipeline
description	Reference for adding and ordering Aspire deploy pipeline steps, tagging steps, parameterizing deployment with AddParameter, configuring per-environment values with WithEnvironment, and using PipelineStepContext services. Use when asked to add a pipeline step, order deploy steps, set up infrastructure provisioning, configure deployment, or wire up aspire deploy.

Pipeline APIs live under Aspire.Hosting.Pipelines. All files that reference them need #pragma warning disable ASPIREPIPELINES001.

References

Adding steps — WithPipelineStepFactory, PipelineStepAnnotation, direct PipelineStep construction
Well-known steps — the 14 WellKnownPipelineSteps constants, deploy order, Docker Compose dynamic step names, common placement patterns
Ordering steps — WithPipelineConfiguration, DependsOn, removing built-in steps, tag-based selection
Tagging steps — WellKnownPipelineTags, custom tags, context.GetSteps(tag)
Parameters and config — AddParameter, GetValueAsync, publish vs run mode, per-environment values
Pipeline services — IPipelineOutputService, IDeploymentStateManager, IHostEnvironment, context.Summary
Multi-step factory and keyed DI — returning multiple steps from one factory, resource-scoped DI
Gotchas — validation rules, concurrency traps, pragma requirements, env file patching

Mais deste repositório

mesmo repositório

technical-debt-audit

sliekens/agentic

Identify structural problems in a codebase and write them up as technical debt documentation — one file per issue in a subfolder, plus an index. Use this skill when the user asks about structural problems, code smells, maintainability issues, architectural concerns, god classes, tight coupling, or "what's wrong with this code at a high level." Also use it when the user says things like "what should we clean up", "where is this hard to change", "what are the pain points", or "document our tech debt." The skill produces actionable write-ups, not vague observations.

2026-06-280

release

sliekens/agentic

Release a new version of a plugin in this repo. Handles the full release workflow — bumps both plugin.json files, writes the changelog entry, updates the Skills or Agents section of the plugin README when something new was added, and runs the sync scripts. Invoke with /release or whenever the user says "bump version", "release plugin", "add changelog", "run sync", or asks to publish or version a plugin after making any kind of change.

2026-06-270

operator-setup

sliekens/agentic

Create or update .agents/OPERATOR.md in the current workspace — a personal profile that tells AI models who you are, your skill levels, and how you like to collaborate. Only invoke when the user explicitly runs /operator-setup. Do not auto-trigger based on context.

2026-06-200

scenario-design

sliekens/agentic

Use this skill for systematic scenario analysis — whenever a problem involves multiple variables, states, conditions, or failure modes and the user needs to enumerate the scenario space to find gaps, validate assumptions, or ensure coverage. Activate eagerly when the user asks "what cases should I handle?", "what could go wrong?", "am I missing any scenarios?", "how do I systematically test/model this?", or when they describe a decision table, state machine, input space, feature flag combination, risk matrix, or any artifact where multiple interacting variables might produce unexpected outcomes. Also use for non-testing contexts: config-flag interactions, requirement gap-finding, risk registers, design tradeoffs, business rule validation. This skill selects the right systematic technique, explains its reasoning, confirms with the user, and produces a structured markdown output for gap detection in code, requirements, design docs, or business rules.

2026-06-060

blind-spot-coverage

sliekens/agentic

Use this skill when the user wants to add test coverage targeting blind spots in a specific method — uncovered branches, edge cases, or unusual inputs. Activate on explicit requests to cover blind spots or when the user asks "what should I test here?" about a particular method. This is not about achieving 100% line coverage, but about ensuring the method behaves correctly in scenarios that are easy to miss.

2026-06-060

orient

sliekens/agentic

Help the user fill a specific gap in their mental model of a system. Use this skill when the user asks "why doesn't X happen", "how does Y work here", "why is this method not called", "why does this text get clipped", or any question where they clearly understand most of the system but are stuck on one specific behavior or mechanism. They have most of the picture — one piece is missing or wrong. This skill always reads back an interpretation of the gap before answering, so misunderstandings get caught early. Activate eagerly on "why" or "how does this work" questions about specific behaviors.

2026-05-230

name	aspire-deploy-pipeline
description	Reference for adding and ordering Aspire deploy pipeline steps, tagging steps, parameterizing deployment with AddParameter, configuring per-environment values with WithEnvironment, and using PipelineStepContext services. Use when asked to add a pipeline step, order deploy steps, set up infrastructure provisioning, configure deployment, or wire up aspire deploy.

Pipeline APIs live under Aspire.Hosting.Pipelines. All files that reference them need #pragma warning disable ASPIREPIPELINES001.

References

Adding steps — WithPipelineStepFactory, PipelineStepAnnotation, direct PipelineStep construction
Well-known steps — the 14 WellKnownPipelineSteps constants, deploy order, Docker Compose dynamic step names, common placement patterns
Ordering steps — WithPipelineConfiguration, DependsOn, removing built-in steps, tag-based selection
Tagging steps — WellKnownPipelineTags, custom tags, context.GetSteps(tag)
Parameters and config — AddParameter, GetValueAsync, publish vs run mode, per-environment values
Pipeline services — IPipelineOutputService, IDeploymentStateManager, IHostEnvironment, context.Summary
Multi-step factory and keyed DI — returning multiple steps from one factory, resource-scoped DI
Gotchas — validation rules, concurrency traps, pragma requirements, env file patching