Menu
Verify Studio site is fully in sync with schemas. Build, test, check for hardcoded values. Trigger on "/sync-studio".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Regenerate everything from schemas — templates, docs, Studio types. Run after changing any schema file. Trigger on "/generate-all".
Review JSON schemas in schema/ for correctness, consistency, completeness. Check that schemas match Dart models, parsers, and Studio. Trigger on "/review-schema".
Add a new config option end-to-end — schema, config model, parser, pipeline integration, templates. Studio picks it up automatically. Trigger on "/add-config-option <section.field_name>" (e.g. "targets.openapi", "rules.require_descriptions").
Add a new field to analytics events end-to-end — schema, model, parser, renderer, tests, templates. Trigger on "/add-event-field <field_name>" or when user asks to add a field to events.
Full project review — schemas, Dart code, Studio, templates, docs. Checks everything is in sync. Trigger on "/review-all".
Review Dart library code for quality, architecture, SOLID, test coverage, and consistency with schemas. Trigger on "/review-code" or "/review-code <path>".
| name | sync-studio |
| description | Verify Studio site is fully in sync with schemas. Build, test, check for hardcoded values. Trigger on "/sync-studio". |
Ensure analytics-gen-studio is 100% schema-driven.
cd analytics-gen-studio && npm run buildnpx vitest rungrep -rn for hardcoded types, operations, field names, defaults
in src/ excluding __tests__, generated, constants, schemas/
Fix them by:
schemas/constants.ts (populated at runtime from schemas)schemas/loader.ts extraction functions