メニュー
Use when adding emulator-backed e2e coverage for a provider — wiring an env-gated emulator seam, a compose.test.yaml service, a mise e2e-<provider> task, and a closed-network CI job. Covers emulator-vs-SDK divergences and coverage upload.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when restructuring the README or the GitHub Pages site generated from it — the left-nav/left-pane, section reorg, or per-provider command docs. Covers the build-docs-site.py split + literate-nav SUMMARY pipeline, its HTML-comment directives and site-only transforms (nav-group, site:skip, hero <h1>, asset ../ prefix, DOC_NAV grouping), the python-markdown gotchas GitHub hides, and the `mise docs-build` strict gate.
Use when authoring or backfilling the "## Highlights" section of a GitHub release — the human-written summary that prepends the auto-generated notes. Covers when a release earns highlights, the fixed format (bold lead + breaking-change note, `###` subsections, PR-referenced bullets), and the prepend-in-place mechanics.
Use when re-recording the CLI, TUI, or GUI demo GIFs after a UI change or a user-visible output change. Covers the record scripts, robust Playwright selectors, output-drift triggers, frame verification, and Git LFS.
Load when writing or reviewing Go that builds or transforms slices/maps. Prefer samber/lo, samber/lo/it, and stdlib slices/maps callback & iterator utilities over hand-rolled make + range + append; keep an explicit loop only where side effects or control flow are genuinely complex.
Load when you need the per-provider capability, versioning, and alias matrix for suve's CLI without reading the full docs/{aws,azure,gcloud}.md option tables. A one-page orientation; link out for per-command detail.
Load when adding or modifying a provider adapter, or when touching internal/provider/** or internal/domain/**. Captures the invariants that keep the provider-neutral seam honest: the neutral domain model, opaque version refs, the typed write/delete option pattern, interface segregation, and SDK confinement.
| name | add-e2e-emulator |
| description | Use when adding emulator-backed e2e coverage for a provider — wiring an env-gated emulator seam, a compose.test.yaml service, a mise e2e-<provider> task, and a closed-network CI job. Covers emulator-vs-SDK divergences and coverage upload. |
suve runs provider e2e against local emulators: Google Cloud (PR #256), Azure App Configuration (PR #258), and Azure Key Vault (PR #259).
SUVE_AZURE_APPCONFIG_CONNECTION_STRING,
SUVE_AZURE_KEYVAULT_ENDPOINT. Document in the code that the variable is for
emulator use and must never be pointed at production.compose.test.yaml service under the provider's compose profile.mise e2e-<provider> task (AWS is mise e2e-aws; Google Cloud is
mise e2e-gcloud; Azure is mise e2e-azure-appconfig / mise e2e-azure-keyvault).Upstream emulators break real SDKs — vet with the official SDK, not curl:
ghcr.io/mpyw/azure-app-configuration-emulator fixes: HMAC auth-header
parsing, RFC3339 timestamp offset handling, and a missing Sync-Token
response header.Document each quirk next to the code that routes around it.
SUVE_STAGING_KEY, or leave those paths to CI.