design-chat-tokens-project-specific-2

To standardize project conventions across sessions, apply a structured pattern at project initiation to identify recurring workflows and translate them into simple decision checklists. This reduces cognitive load and enforces consistency.

Preventing anti-patterns in recurring project workflows requires codifying rejected practices during project initiation. You identify recurring conventions, then explicitly list anti-patterns that should be rejected in future work to improve consistency.

Yes, you can use this checklist pattern to enforce consistency across different repositories. It is applied at project initiation and across similar projects to codify and enforce standard conventions, reducing miscommunication between teams.

To create a decision checklist for project-specific conventions, identify recurring conventions applied during a session. Translate each convention into a simple decision checklist and show one concrete example from the session for clarity.

You need to define project conventions using a pattern when you want to reduce cognitive load and miscommunication across sessions. It is applied at the start of a project to establish and enforce recurring conventions, checklists, and anti-patterns.

This convention pattern works best when applied at project initiation. While it can codify conventions from an ongoing session, starting early ensures you capture all recurring workflows and anti-patterns before inconsistencies develop across repositories.