Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

wizard-prompt-supplement

Estrelas28

Forks0

Atualizado22 de maio de 2026 às 17:59

Long-form wizard contracts moved out of the always-on system commandments to keep per-turn prompts small. Load when wiring API keys, before confirm_event_plan, when writing the post-instrumentation events manifest or setup report, or when generating browser SDK init. Pre-staged at .claude/skills/wizard-prompt-supplement/ — use Read on the reference files listed below; do not skip relevant sections for your current phase.

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

amplitude

amplitude/wizard

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

7 arquivos

SKILL.md

readonly

name

wizard-prompt-supplement

description

Wizard prompt supplement

The static commandments block in the wizard stays intentionally short. This skill holds the relocated detail so you still follow the same rules — they are not optional.

When to read what

Phase	Read
Env vars, `.env`, client vs server keys	`references/api-keys-and-env.md`
Before `confirm_event_plan`, event naming, plan sizing, autocapture overlap	`references/confirm-event-plan-contract.md`
After `track()` calls, before dashboard	`references/post-instrumentation-events-and-dashboard.md`
`amplitude-setup-report.md`	`references/setup-report-requirements.md`
Browser / unified SDK init defaults (browser-targeting frameworks only)	`references/browser-sdk-init-defaults.md`
Why end-of-run lint must stay file-scoped	`references/lint-scoping.md`

Use the Read tool on each path relative to this skill directory (e.g. references/api-keys-and-env.md from .claude/skills/wizard-prompt-supplement/).

Mais deste repositório

mesmo repositório

discover-event-surfaces

amplitude/wizard

Given a change_brief YAML (output from diff-intake), generates an exhaustive list of candidate analytics events to instrument. Takes the perspective of an engineer with a PM mindset — surfaces everything worth considering so a PM can decide what actually matters. Use this as step 2 of the analytics instrumentation workflow, immediately after diff-intake produces a change_brief. Trigger whenever a user has a change_brief YAML and wants to know what analytics events to add, or asks "what should I track for this PR", "what events should I instrument", "generate event candidates", or any request to surface analytics coverage gaps for a code change.

2026-05-0628

instrument-events

amplitude/wizard

Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.

2026-05-0128

integration-android

amplitude/wizard

Amplitude integration for Android applications using the Kotlin SDK

2026-05-0128

integration-angular

amplitude/wizard

Amplitude integration for Angular applications

2026-05-0128

integration-astro-hybrid

amplitude/wizard

Amplitude integration for Astro hybrid rendering with both static and server-rendered pages

2026-05-0128

integration-astro-ssr

amplitude/wizard

Amplitude integration for server-rendered Astro applications with API routes

2026-05-0128

name

wizard-prompt-supplement

description

Wizard prompt supplement

The static commandments block in the wizard stays intentionally short. This skill holds the relocated detail so you still follow the same rules — they are not optional.

When to read what

Phase	Read
Env vars, `.env`, client vs server keys	`references/api-keys-and-env.md`
Before `confirm_event_plan`, event naming, plan sizing, autocapture overlap	`references/confirm-event-plan-contract.md`
After `track()` calls, before dashboard	`references/post-instrumentation-events-and-dashboard.md`
`amplitude-setup-report.md`	`references/setup-report-requirements.md`
Browser / unified SDK init defaults (browser-targeting frameworks only)	`references/browser-sdk-init-defaults.md`
Why end-of-run lint must stay file-scoped	`references/lint-scoping.md`

Use the Read tool on each path relative to this skill directory (e.g. references/api-keys-and-env.md from .claude/skills/wizard-prompt-supplement/).