sdd-steering-custom

Custom steering documents are generated by analyzing codebase patterns and utilizing predefined templates to produce focused project memory for specialized areas like API standards. This process grounds the generated documentation in actual project patterns and best practices.

Project memory documentation for specialized contexts captures domain-specific standards, such as testing strategies and security protocols, beyond core technical steering. It creates actionable reference material tailored to a project's unique architectural patterns and requirements.

Yes, custom steering documents can be generated by integrating codebase analysis to inform the output. This ensures the resulting security documentation, including authentication flows and input validation rules, is grounded in your actual project patterns.

You can document testing strategies by utilizing predefined templates and analyzing your codebase to generate a tailored steering document. This creates consistent, actionable project memory detailing specific testing approaches for your architectural context.

The best way to ensure consistency is by leveraging predefined templates for common specialized areas during steering document generation. This approach standardizes the documentation structure while allowing domain-specific details to be populated through codebase analysis.

The main limitation is that custom steering documents rely on available templates and existing codebase patterns to ground the output. If a project context is highly unique or lacks sufficient codebase patterns, the generated documentation may require manual refinement for full accuracy.