using-cohesive

What problem does it solve?

This Skill eliminates the confusion of being misrouted between Cohesive and Superpowers when working on substrate-first engineering tasks, ensuring you land in the right workflow immediately for work involving system invariants, specs, and codebase cohesion.

Core Features & Use Cases

• Substrate trigger detection: Identifies when your request relates to substrate-first work such as designing features that touch named invariants, reviewing code or PRs for cohesion, auditing missing system memory, rewriting specs or behavior matrices, implementing approved rewrites, or extending existing system concepts.
• Clean Superpowers deferral: Automatically defers implementation-discipline tasks (writing tests, executing existing plans, debugging specific issues, general code exploration) to Superpowers without sending unnecessary orientation messages.
• Use case example: If you ask to "review the PR for cohesion" or "rewrite the behavior matrix for the auth flow", this skill routes you directly to the Cohesive router instead of sending you to generic exploration or implementation workflows.

Quick Start

Request a substrate cohesion review of your current codebase or a rewrite of the existing behavior matrix for the user authentication flow to activate the correct Cohesive workflow.