sergekostenchuk/ui-ux-agent-skill-system

infra-launch-orchestrator

Use when a project needs launch/infrastructure coordination across domains, registrars, servers, DNS, deploy, SSL, webmaster tools, monitoring, and launch readiness.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/sergekostenchuk/ui-ux-agent-skill-system --skill infra-launch-orchestrator

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Infra Launch Orchestrator

This skill coordinates the infra/launch layer. It is not the central UI/UX chair and does not execute irreversible actions by default.

Operating Modes

  • plan: map launch scope, owners, approvals, rollback, and dependencies.
  • dry-run: prepare commands/checklists without applying them.
  • handoff: route to specialist infra skills.
  • launch-gate: collect readiness evidence before any production action.

Required Workflow

  1. Identify requested action: advisory, dry-run, or production execution.
  2. Route specialists:
  • domain ideas: domain-name-generator;
  • registrar choice: domain-registrar-advisor;
  • hosting choice: server-selector;
  • provisioning plan: server-provisioner;
  • deploy plan: deploy-orchestrator;
  • DNS plan: domain-dns-configurator;
  • SSL/security: ssl-and-security-hardener;
  • webmaster tools: webmaster-registrar;
  • final gate: launch-readiness-auditor.
  1. Keep all irreversible or paid steps Planned until explicit production approval is recorded.
  2. Require rollback and monitoring before launch.

Safety Rules

  • Do not buy domains, change DNS, provision paid servers, deploy production, issue destructive commands, submit webmaster changes, or store credentials without explicit approval.
  • Do not print API tokens, provider credentials, SSH keys, DNS tokens, cookies, or .env values.
  • If approval is missing, provide a dry-run plan only.

Validation

bash
python3 $CODEX_HOME/skills/.system/skill-creator/scripts/quick_validate.py $CODEX_HOME/skills/infra-launch-orchestrator
python3 $CODEX_HOME/skills/senior-skill-architect/scripts/lint_production_skill.py $CODEX_HOME/skills/infra-launch-orchestrator
python3 -m json.tool $CODEX_HOME/skills/infra-launch-orchestrator/evals/evals.json >/dev/null

Related by task

from this repository

More skills

All skills
sergekostenchuk
Community

admin-ui-builder

Use when admin/CMS/back-office screens need to be built or specified after admin-ui-orchestrator defines roles, permissions, workflows, and safety gates. Covers tables, forms, editors, moderation queues, dashboards, CRUD surfaces, and state coverage without production destructive actions.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

admin-ui-orchestrator

Use when a project needs admin/CMS/back-office UI architecture: roles, permissions, content workflows, AI assistant boundaries, audit logs, destructive-action confirmations, and builder handoff. Planning only; do not perform production admin actions or expose secrets.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

analytics-setup-architect

Use when a website or web app needs privacy-aware analytics architecture: GA4, Yandex Metrica, self-hosted analytics, consent, UTM, event taxonomy, funnels, dashboards, and launch verification. Do not mutate real analytics accounts or store credentials without explicit approval.

installs
1
GitHub stars
32
Updated
Sep 13
sergekostenchuk
Community

figma-canvas-editor

Create and edit native Figma canvas objects with MCP when explicitly scoped. Use this skill when the user asks to add or change frames, sections, components, instances, auto layout, variables, styles, FigJam objects, connectors, Slides objects, or selected nodes in Figma, and when the task requires mutation evidence, rollback-aware scope, and design-system consistency.

installs
1
GitHub stars
32
Updated
Sep 13