This is a non-executable architecture guide, but it uses very broad mandatory activation rules that can steer many unrelated coding tasks without clear user opt-in.
Install this only for projects where you explicitly want all business-logic changes to follow this pipeline architecture. Be cautious in general-purpose workspaces because the broad trigger terms may cause the agent to apply this pattern during normal refactors or tests. For real file, device, or external API mutations, add project-specific allowlists, authorization checks, idempotency safeguards, and rollback or compensation rules before using the generated pattern in production.