{# Static "How to fix" guidance rendered below content-quality findings. Shown when either the inline content check or the LLM content-quality verdict reports issues. Holds the pattern cheatsheet and the "what good enough means" copy so the same guidance is visible from both rejection tiers. #}
How to fix — write a strong description
Each component description doubles as the trigger the model reads to decide whether to invoke it. Vague descriptions block routing more often than they block security — that's why this is enforced.
Pattern cheatsheet
What "good enough" means
Re-upload as new version → See submission examples ↗ Read full guidelines