메뉴
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.
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".
Verify Studio site is fully in sync with schemas. Build, test, check for hardcoded values. Trigger on "/sync-studio".
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").
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 | add-event-field |
| description | 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. |
Add a new field across the entire stack.
Field name (e.g. priority, category, version)
Schema — add to schema/events.schema.json → $defs.event.properties
type, title, description, default (if any), examplesDart model — add to lib/src/models/analytics_event.dart
Dart parser — update lib/src/parser/event_parser.dart
Dart renderer — update lib/src/generator/renderers/ if field affects generated code
Templates — add example to templates/events.yaml
Tests — add/update tests in test/parser/ and test/models/
Studio — nothing needed (reads from schema dynamically)
Verify — dart analyze, dart test, cd analytics-gen-studio && npm run build