factory-experimental-steering-examples

Records architectural and implementation decisions. Use when a significant technical decision is made, a spec is modified, or an approach changes during implementation. Creates numbered decision records in .factory/decisions/.

Generates structured requirements using EARS (Easy Approach to Requirements Syntax) notation. Use when the user is planning a feature, entering spec mode, or asking for requirements. Produces user stories with testable acceptance criteria.

Technology stack constraints and approved libraries. Auto-loaded when Droid is making technology choices, adding dependencies, or proposing architectural changes. Defines what frameworks, libraries, and patterns are allowed.

Guardrails for debugging and troubleshooting. Auto-loaded when Droid encounters errors, test failures, or build issues. Prevents context drift and tech stack swaps during error recovery.