flowcore-io/flowcore
Connects coding agents to the Flowcore event platform and teaches them to operate it: the resource hierarchy, IAM policies that actually match, virtual and managed Data Pathways, and building apps with the @flowcore/pathways SDK.
Operate Flowcore Data Pathways — the control-plane resources that deliver events from a data core to a consumer. Covers virtual vs managed pathways, create, pause, resume, restart/replay, disable, delete and delivery troubleshooting through the Flowcore MCP tools. Use when the user asks to deliver events somewhere, replay events, hold or resume delivery, or why a consumer is behind. For writing app code with the @flowcore/pathways SDK use flowcore-pathways.
Flowcore access control — users, API keys, roles, policies, FRN resource names and actions. Use when the user asks to give or remove access, create an API key for a service, write or fix a policy, or debug a "forbidden" error on Flowcore. Contains the only valid policy statement format; named resource ids silently never match.
Use when building or changing a TypeScript app that writes or consumes Flowcore events with the @flowcore/pathways library, including registering event types, handlers, pathways.write, the data pump, cluster mode, auto-provisioning, virtual pathways, encryption, chunking and transformers. This is the SDK and build skill. Operating Data Pathways in the control plane (pause, restart, inspect, delete) belongs to the flowcore-data-pathways skill.
Core model of the Flowcore event platform — tenants, data cores, flow types, event types, events and time buckets — plus the safety rules for every Flowcore MCP operation. Use before any Flowcore MCP call, when modeling events, or when the user asks how Flowcore is structured. For access control use flowcore-iam; for delivery use flowcore-data-pathways; for app code use flowcore-pathways.