SeamStressDev
UserTraining wheels for AI assisted coding. Seam aware protocols that make coding agents investigate first, gate irreversible actions, and prove their claims.
Categories
Indexed Skills (5)
fixture-immutability
Use this protocol whenever a test fails after a change, whenever editing test files, test fixtures, expected outputs, snapshots, or scoring criteria, and whenever the temptation exists to make a red check green by touching the check instead of the code.
irreversible-gate
Use this protocol before executing any action that cannot be cheaply undone: pushing to a shared branch, deploying, running a database migration, deleting data or resources, sending an email or message, spending money or calling a paid API in bulk, publishing anything public, or rotating or revoking secrets. Load BEFORE the action, not after.
seam-change-protocol
Use this protocol whenever an edit will touch a file listed in .seamstress/seam-map.md, or, if no seam map exists, whenever an edit touches code that moves money, decides authorization, crosses tenant or user data boundaries, or deletes data. Load BEFORE writing any change to such a file.
session-continuity
Use this protocol at the start of every session in a scaffolded repository, before making any change, and again at the end of the session or before context is lost. Applies to resumed work, handoffs between sessions, and any moment where the agent is acting on a codebase it did not just finish reading.
verification-discipline
Use this protocol whenever making a claim about what code does, did, or will do: describing behavior, confirming a fix, reporting test results, or asserting that something is safe, handled, or working. Applies to the agent's own statements throughout a session.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.