Creates Chronicle projections that populate read models from events in Cratis applications.
npx skills add https://github.com/Cratis/Screenplay --skill add-projection-cratis
Please help me install this Agent Skill. Skill: add-projection Source: https://github.com/Cratis/Screenplay/tree/main/.github Command: npx skills add https://github.com/Cratis/Screenplay --skill add-projection-cratis
High-intent search queries and answers about installing and using this skill.
Prefer a model-bound projection: put [ReadModel] and [FromEvent<T>] attributes directly on the read model record, marking the primary key with [Key]. Matching property names auto-map from the event, so no separate projection class is needed.
Use the fluent IProjectionFor<T> builder only when the projection logic is too complex for attributes or would become less clear if forced into attributes. AutoMap is on by default, so call .From<T>() directly without .AutoMap().
No. Joins in Chronicle projections must be on Chronicle events only, never on a read model type. Use [Join<T>(on: ..., eventPropertyName: ...)] with an event type, or the fluent builder equivalent.
Chronicle projections have no Identifier or ProjectionId property, so adding one causes errors. The read model key is declared with the [Key] attribute or via UsingKey in the fluent builder instead.
Projections select input through event types, joins, and event sequence configuration; they do not filter by appended tags. For metadata-based filtering, pair the projection with a reducer or reactor using [FilterEventsByTag], [EventSourceType], or [EventStreamType].
semicolon-devteamGenerate TypeScript event envelope types and Zod schemas from event contracts.
afel6Store and query embeddings with metadata filtering for semantic search.
reactor-teamBuild real-time video AI apps using Reactor SDKs over WebRTC.
ecotoneframeworkModels domain state as a sequence of events using Ecotone's event store and projections.
