'artifacts' 검색 결과

Design one-off HTML artifacts (landing, deck, prototype).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Continuous production path for deployless repositories. Use after mainline governance and release controls exist, when a repo needs CI/CD changes to automatically deploy, publish, or promote artifacts from main across any language, runtime, or hosting platform.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Incrementally studies git history across tagged or pattern-matched intervals (e.g., creation of planning artifacts like EXECUTION_PLAN_N.md, release tags, or milestone commits). Extracts commit diffs, file churn, and subsystem shifts to track feature evolution and architectural convergence, providing structured feeds for ADR distillation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Establish build performance baselines and apply systematic optimization techniques. Only activate in MSBuild/.NET build context. USE FOR: diagnosing slow builds, establishing before/after measurements (cold, warm, no-op scenarios), applying optimization strategies like MSBuild Server, static graph builds, artifacts output, and dependency graph trimming. Start here before diving into build-perf-diagnostics, incremental-build, or build-parallelism. DO NOT USE FOR: non-MSBuild build systems, detailed bottleneck analysis (use build-perf-diagnostics after baselining).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide developers through capturing diagnostic artifacts to diagnose production .NET performance issues. Use when the user needs help choosing diagnostic tools, collecting performance data, or understanding tool trade-offs across different environments (Windows/Linux, .NET Framework/modern .NET, container/non-container).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Develops an implementation plan ready for wave-orchestration to execute. Takes the user's goal or rough plan as input, mines the codebase for facts, grills the user one question at a time for the decisions, drafts the planning/ artifacts (task DAG, wave table, worker prompt template, state file), then reviews its own plan on two axes before seeking approval. Use when the user wants to turn a feature idea, master plan, or backlog into a wave-orchestration execution plan.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interactive Domain-Driven Design modeling sessions based on DDD Distilled (Vaughn Vernon) and Domain Modeling Made Functional (Scott Wlaschin). Guides users through strategic and tactical design via 13 phases: discover, storming, contexts, mapping, aggregates, events, validate, glossary, workflows, types, simulate, publish, sync. Phase 13 (sync) reconciles divergences found by --analyze between the domain model and the implementation — judging whether the model or the code is authoritative, then planning and implementing the fix and re-aligning the model. Phases 9-11 take the conceptual model from phases 1-8 and produce workflow pipeline designs, compilable type definitions (TypeScript, Kotlin, Scala, Rust, C#, F#), workflow verification via type-level tests, and automatic UI field enumeration from the domain model. Phase 12 (publish) renders all docs/domain artifacts into one self-contained, cross-linked HTML site (separate files joined by a shared nav). Each phase is an interactive dialogue where AI acts as facilitator and domain expert challenger. Use when: "DDD", "ドメイン設計", "ドメインモデリング", "Event Storming", "Bounded Context", "集約設計", "ユビキタス言語", "コンテキストマップ", "ワークフロー設計", "パイプライン設計", "ステップ分割", "中間型", "型駆動フロー", "型駆動設計", "Domain Modeling Made Functional", "Railway Oriented Programming", "入力画面項目", "フォーム項目洗い出し", "UI 項目抽出", "HTMLにまとめる", "ドキュメントサイト化", "成果物を1つのHTMLに", "publish", "モデルと実装の差異", "差異解消", "実装との乖離", "モデルとコードを一致", "差異の実装計画", "sync", "複数フェーズを逐次実行", "フェーズをまとめて実行", "/ddd run", "サブコマンド一覧", "/ddd list", "/ddd", "ドメイン分析したい", "モデリングしたい", or any domain design / type modeling activity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures GitHub Actions CI/CD workflows for Flutter projects. Use when creating or editing `.github/workflows/` YAML files for Flutter, integrating subosito/flutter-action, automating `flutter test`, `flutter analyze`, or `dart format` on push or pull_request events, running build_runner in CI, building Android AAB or iOS IPA artifacts, managing keystore or signing secrets in GitHub Secrets, or combining GitHub Actions with Fastlane or Codemagic for the deployment stage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepares mobile releases across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including separate Android/iOS artifacts from a shared KMP revision. Covers versions, signing, symbols, store readiness, rollout, release notes and CI/CD. Use for release audits, store submission, build pipelines or rollout planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run automated repo documentation alignment: discover source truth, audit public/internal docs, refresh generated artifacts, coordinate subagent research, and verify docs in one pass.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide GitHub Actions workflow authoring. Use for CI, release, scheduled jobs, permissions, caching, matrices, artifacts, and secure workflow design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Opt-in agent heartbeat harness for target repositories: initialize config, run transaction-safe checks, preserve artifacts, and wire cron only after explicit activation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Azure Container Registry SDK for Python. Use for managing container images, artifacts, and repositories.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for Nauthilus configuration loading, config schema and defaults, Viper-backed config formats, config dump behavior, vim syntax generation, template validation, prompt guideline sync, documentation under README/IDP/server docs, config converters, and generated documentation or syntax artifacts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when running the dev Grafana stack and/or the Playwright e2e suite against a *packaged* plugin zip (a release/RC artifact like `hydrolix-hydrolix-datasource-<ver>.zip`) rather than the working-tree `dist/`. Unpacks the package into a timestamped `dist_<timestamp>/dist` sandbox alongside copies of the compose artifacts, so the run is reproducible and the folder stays available to experiment with afterwards. Delegates stack bring-up to `stack-run` (frozen mode: read-only mount + `DEV=false` so the mage-watcher can't rebuild the packaged Go binary), verifies signature/version, runs the suite, and treats cleanup as optional — the sandbox is deleted only with the user's approval. Apply whenever the task is "test this plugin package / zip" or "run e2e against the built artifact".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when starting, stopping, or inspecting the dev stack for this Hydrolix Grafana datasource plugin — Grafana (with the plugin bind-mounted), ClickHouse, Keycloak (OAuth), and the on-demand playwright runner. Covers `docker compose up` semantics, the `dist/` prerequisite, serving plugin artifacts from an alternate folder (any path, live or frozen, via an ephemeral compose override), switching Grafana versions, hot-reload behaviour, delve attach, log streaming, OAuth/anonymous auth, and ClickHouse fixture access. Apply whenever a task needs the plugin running locally, needs to reset the stack, or needs to debug why Grafana won't come up.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Derive slices from specs, order by dependencies, write acceptance criteria with citations, and finalize phase/progress artifacts

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create Kotlin Compose design tokens from one of three supported sources — Google Stitch (MCP), Figma (MCP or JSON), or Claude Design (kta-design-spec output, Claude HTML/markdown artifacts). Three-layer architecture (Primitive/Semantic/Component) with code generation. Use when user asks to "generate design tokens", "create theme from Figma/Stitch/Claude design", "build Compose tokens from design spec", or "convert design source to tokens". Refuses any other input source and asks user for correct seed data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create Kotlin Compose design tokens from one of three supported sources — Google Stitch (MCP), Figma (MCP or JSON), or Codex Design (kta-design-spec output, Codex HTML/markdown artifacts). Three-layer architecture (Primitive/Semantic/Component) with code generation. Use when user asks to "generate design tokens", "create theme from Figma/Stitch/Codex design", "build Compose tokens from design spec", or "convert design source to tokens". Refuses any other input source and asks user for correct seed data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Per-screen design spec generator for AI design tools (Stitch / Figma AI / Claude artifacts). Consumes per-feature PRDs from kta-prd-pipeline. Emits tool-agnostic markdown specs. Triggers — design spec, AI design prompt, screen mockup brief, Figma AI input, Stitch prompt, design system tokens, post-PRD design phase, generate design specs, design brief, mockup spec. DOES NOT generate Compose code, Kotlin code, or @Preview stubs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.