design-chat-tokens-project-specific

Design tokens are codified project conventions that ensure repeatability by translating recurring workflows into a reusable pattern with decision checklists, concrete examples, and anti-pattern guidance for consistent sessions.

To codify project conventions, identify recurring workflows applied during a session and translate each into a simple decision checklist, showing one concrete example and listing anti-patterns to reject in future work.

You need project-specific token conventions when managing ongoing projects in teams that require consistent workflows across sessions, repositories, and handoffs to maintain repeatable practices and avoid convention drift.

The best way to document project patterns for handoffs is specifying enforced steps and artifacts like decision checklists, concrete session examples, and anti-pattern guidance to ensure repeatable practice across different repositories.

Yes, applying the project-specific convention pattern identifies anti-patterns that should be rejected in future work by evaluating existing workflows against the codified decision checklist and concrete session examples.

Yes, the convention pattern applies specifically to ongoing projects in teams that require consistent workflows across multiple repositories and handoffs, enforcing repeatable practice through artifacts like checklists and anti-pattern guidance.