cocosil-domain

To enforce UX sequence rules for product prompts and UI copy, reference domain guardrails that mandate the non-negotiable empathy-to-action order. This ensures design decisions consistently follow the required empathy, reassurance, analysis, and action phases.

Anti-pattern constraints in language rules prevent inappropriate content generation in chat and diagnosis features. They enforce domain philosophy by restricting specific outputs, such as prohibiting fortune-telling phrasing, ensuring behavior remains consistent with product guidelines.

To check if your report generation flow violates domain guardrails, verify that the specification does not skip the empathy phase. You must implement constraints that prevent action plans from appearing before user input and analysis are complete.

Yes, you can use role-based responsibility boundaries to manage file modification routes. These boundaries clarify meaning design, visual design, and structural design responsibilities, ensuring each role only touches its permitted file boundaries during implementation.

You need domain philosophy alignment for API implementation decisions whenever product features require consistent behavior across phases and roles. This applies to chat, diagnosis, report, and UX flow designs where specific behavioral standards must be enforced.

The best way to maintain consistent product philosophy across UX flows is to reference mission guidelines, anti-pattern constraints, and role-based file boundary rules. This approach guides prompt, UI copy, and API implementation without deviation.