critic-comms-completeness

Check UI behaviors for missing communication states and actionable error messages.

3|Updated May 20, 2026

Search Tags:#UI validation #brand tone #communication states #error message review #notification checks

Ready to run

npx skills add https://github.com/iampawan/Manifest --skill critic-comms-completeness

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: critic-comms-completeness
Source: https://github.com/iampawan/Manifest/tree/main/skills/critic-comms-completeness
Command: npx skills add https://github.com/iampawan/Manifest --skill critic-comms-completeness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents "we forgot the error message" bugs by ensuring UI behaviors have comprehensive and actionable communication states.

Core Features & Use Cases

Verify UI States: Ensures UI behaviors have all required states (empty, loading, success, error).
Check Error Messages: Validates error messages are actionable and not vague or blaming.
Notify Through Channels: Validates notification channels and messages are correctly specified for each behavior.
Tone and Internationalization: Checks for brand tone consistency and internationalization readiness.

Quick Start

Run the critic-comms-completeness skill on your UI spec to verify the completeness of communication states.

Frequently Asked Questions about critic-comms-completeness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check for missing UI states and validate error messages in my software spec?▼

To check missing UI states and validate error messages, run a communication completeness review on your UI spec. This verifies empty, loading, success, and error states are present and ensures error messages are actionable rather than vague or blaming.

What is UI communication completeness and when do I need to check it?▼

UI communication completeness ensures every UI behavior specifies essential states, actionable error messages, notification channels, and brand tone consistency. You need this check during development workflows to prevent missing error message bugs and guarantee internationalization readiness.

How do I validate notification configurations and brand tone consistency for UI behaviors?▼

To validate notification configurations and brand tone consistency, review your UI spec to ensure notification channels and messages are correctly specified for each behavior. This process checks tone consistency and verifies internationalization readiness across all communication states.

Can I use this UI validation approach for internationalization readiness checks?▼

Yes, you can use this UI validation approach for internationalization readiness checks. It evaluates your UI behaviors to ensure communication states, error messages, and notification configurations are prepared for global audiences and brand tone consistency across languages.

What is the best way to prevent vague or blaming error messages in UI development?▼

The best way to prevent vague or blaming error messages is to run an error message review on your UI spec. This validates that all error messages are actionable, clearly specifying what went wrong and how the user can resolve the issue.

Why does my UI behavior validation fail when checking communication states?▼

UI behavior validation fails when checking communication states if your UI spec lacks required states like empty, loading, success, or error. It also fails when error messages are not actionable or notification channels are incorrectly specified for the behavior.