Develop FastGen
Resolve the user's FastGen checkout separately from the installed skill. Use the requested revision, or the current checkout, as the authority for linked policies and interfaces. Read Design and Maintenance for the shared coding rules and the owning component's README and interface docstrings. Use the requested scope and information already provided before asking for missing inputs. For review-only requests, inspect and verify within scope, then report findings without editing.
- Trace. Follow the affected callers and consumers before editing. For changes across
data and model boundaries, inspect loader decoding in
datasets,
FastGenModel.prepare_batchin model.py,FastGenNetwork.build_conditioningin network.py andTrainer.train_stepin trainer.py as relevant; place the change with the component that owns the behavior. - Change. Apply the shared rules to the implementation and affected callers, tests and documentation together. For new capabilities, also use fastgen-add-network, fastgen-add-method or fastgen-add-modality.
- Verify. Follow the contributor guide's formatting and checks. Exercise changed behavior and requested boundary cases through real FastGen components and affected call sites; distinguish static checks from runtime tests. For patch deliverables, generate the diff from complete target files and check it against clean files at the selected revision. If a failure crosses interfaces, trace the producer and consumer contracts before adding another check or workaround.
Report source-backed findings or changed behavior, affected interfaces and documentation, checks actually run and any unverified paths.