gamealgo-cli 0.3.0 → 0.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gamealgo-cli",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "GameAlgo command-line client for AI agents and game developers",
   "repository": {
     "type": "git",

package/skills/gamealgo/SKILL.md

@@ -27,7 +27,31 @@ When the user asks what GameAlgo can do, asks for ongoing iteration, or names a
 
 Do not run every catalog task in sequence. Complete the selected task and report unmet prerequisites instead of manufacturing missing data.
 
-## Integration Work
+## Route Work To Required Documentation
+
+Classify the requested work by the actions it requires, not only by the user's task title. Before implementation or interpreting results, load every applicable source below from the current Server:
+
+- SDK installation, identity, lifecycle, telemetry, attribution, advertising, or purchase work: run `gamealgo integration get-plan --environment <domestic|overseas> --platform <ios|android|maker|rest> --json`, then read `gamealgo docs sdk-integration`.
+- Calling or changing a concrete public SDK function: additionally run `gamealgo docs api <function> --platform <platform>` for each affected function. Never infer one platform's API from another.
+- Adding or changing events: additionally run `gamealgo events list --days 30 --json` before defining fields or names.
+- Reading, creating, changing, previewing, or publishing Report Packs, charts, report SQL, or business metrics: read `gamealgo docs reports` before interpreting data or editing definitions.
+- Creating or changing remote configuration, strategies, experiments, variants, objectives, rollout, or assessment: read `gamealgo docs experiments`; also load the integration plan and exact API documentation when client code changes.
+- Adjust or marketing attribution work: load the selected optimization task when one applies, read every topic in its `docs`, and load the integration plan and exact identifier/attribution APIs for the target platform.
+
+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.
+
+## Follow Mandatory Checkpoints
+
+1. Confirm project identity, environment, platform, requested outcome, and available permissions.
+2. Load the required live documents and task detail before making implementation decisions.
+3. Inspect existing code, configuration, event inventory, Report Pack, or experiment state before editing. Reuse established project patterns and preserve local fallback behavior.
+4. Make the smallest coherent change and run local validation, Report Pack validation, previews, or dry runs supported by the current workflow.
+5. Before publishing reports, remote configuration, scripts, strategies, experiments, rollout changes, or other externally visible mutations, show the relevant diff and impact unless the user has already explicitly authorized that exact operation.
+6. After execution, verify with real configuration retrieval, accepted non-debug events, report results, or experiment state as appropriate. A code diff or successful request alone is not business verification.
+
+Reading documentation does not grant permission to mutate production. CLI and Server validation, scopes, project binding, and explicit approval requirements still apply.
+
+## Integration Details
 
 For SDK integration or telemetry changes, determine the actual deployment environment and runtime platform, then run:
 
@@ -35,16 +59,13 @@ For SDK integration or telemetry changes, determine the actual deployment enviro
 gamealgo integration get-plan --environment <domestic|overseas> --platform <ios|android|maker|rest> --json
 ```
 
-Inspect the existing project before editing. Reuse existing SDK wrappers, user identity, lifecycle, event, advertising, purchase, and attribution flows. Use `gamealgo docs api <function> --platform <platform>` for exact public APIs; do not invent methods or infer support from another platform.
+Inspect the existing project before editing. Reuse existing SDK wrappers, user identity, lifecycle, event, advertising, purchase, and attribution flows.
 
-Before adding events, run `gamealgo events list --days 30 --json`. Reuse events with the same business meaning, register new fields with their real JSON types, and verify non-debug context and business events with real runtime traffic.
+Reuse events with the same business meaning, register new fields with their real JSON types, and verify non-debug context and business events with real runtime traffic.
 
 ## Changes And Verification
 
 - Make repository changes when the selected task requires them; keep unrelated files unchanged.
-- Preserve local fallback behavior when adding remote configuration, scripts, or experiments.
-- Validate Report Packs before preview or publication and compare results with real event counts.
-- Show the relevant diff and impact before publishing reports, remote configuration, scripts, or experiments unless the user has already explicitly authorized that exact operation.
 - Do not push directly to a protected primary branch. Follow the repository's branch and merge-request workflow.
 
-Finish with the changed files, checks executed, observed data evidence, unmet prerequisites, and any operation still awaiting developer approval. Only call initial integration activated after real configuration and event acceptance checks pass.
+Finish with the live documentation and task detail consulted, changed files, checks executed, observed data evidence, unmet prerequisites, and any operation still awaiting developer approval. Only call initial integration activated after real configuration and event acceptance checks pass.