blueprint:bad-pattern

To document anti-patterns during code reviews, you log the bad practice and its remediation into patterns/bad/anti-patterns.md, creating the directory structure if needed to share knowledge across the codebase.

Maintaining a knowledge base of bad coding practices involves documenting anti-patterns with a standard template and updating patterns/bad/anti-patterns.md so teams have a clear reference of issues and recommended fixes.

Yes, you can record anti-patterns using a standard template. The skill applies a standard format to log bad practices and their recommended fixes into a dedicated markdown file within the repository.

Yes, the anti-pattern documentation workflow creates the directory structure automatically. It generates the patterns/bad/ directories if they are missing before updating the anti-patterns.md file.

Use a dedicated anti-pattern file instead of inline comments when capturing knowledge for ADR or audit workflows. It centralizes bad practices and remediation steps for broader team visibility and codebase consistency.