What problem does it solve? When writing Intent Architect templates or factory extensions, developers often fall back to raw string-based stereotype and property lookups, which are brittle, error-prone, and break when metadata changes. This Skill enforces the use of generated typed extension methods so template logic that branches on stereotypes, properties, or model values stays type-safe and maintainable. ## Core Features & Use Cases - Typed Stereotype Access: Enforces use of generated *StereotypeExtensions.cs accessors (Has/Get/TryGet tiers) instead of GetStereotype("Name") string calls. - Safe Property Consumption: Requires null guards, .AsEnum() and .IsX() enum helpers, and TypeCheckExtensions primitive checks instead of raw string comparisons. - Fallback Guidance: Provides a GUID (DefinitionId)-based lookup pattern and a recipe for promoting it to a full typed extension when no generated accessor exists. - Use Case: While writing a template that conditionally adds a DisallowConcurrentExecution attribute, use this Skill to read the Scheduling stereotype via model.GetScheduling().DisallowConcurrentExecution() rather than string lookups. ## Quick Start Ask the assistant to read a stereotype or property value inside an Intent Architect template using the generated typed extension methods to drive the generated output.
