gamealgo-cli 0.3.1 → 0.3.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/gamealgo/SKILL.md +2 -0
package/package.json
CHANGED
package/skills/gamealgo/SKILL.md
CHANGED
|
@@ -40,6 +40,8 @@ Classify the requested work by the actions it requires, not only by the user's t
|
|
|
40
40
|
|
|
41
41
|
If work crosses domains, combine their requirements. For example, an advertising event used by an experiment report requires the integration plan, event inventory, SDK API documentation, report documentation, and experiment documentation. Read a topic once per turn unless the task expands or the Server documentation version changes.
|
|
42
42
|
|
|
43
|
+
For initial integration or business dashboard work, standard dashboards are only the baseline. During the initial integration, inspect the actual game loop and define a separate game-specific new-user flow dashboard with meaningful milestones and drop-off diagnostics. Add required milestone telemetry and event catalog fields in the same integration instead of waiting for production volume. Validate the pipeline with test data; label business conclusions as awaiting data when production samples are immature, but do not omit the dashboard design.
|
|
44
|
+
|
|
43
45
|
## Follow Mandatory Checkpoints
|
|
44
46
|
|
|
45
47
|
1. Confirm project identity, environment, platform, requested outcome, and available permissions.
|