Update to Slop Curator

{
  "description": "Review or plan presentations, reports, brochures, documents, visual briefs, and Arabic RTL layouts for AI-design clichés, fake data, decorative copy, asset misuse, weak hierarchy, and Arabic rendering risks. Use when the requested deliverable has a visual or document-design component.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 347
    }
  ],
  "name": "visual-content-anti-slop",
  "skill_md_contents": "---\nname: visual-content-anti-slop\ndescription: Review or plan presentations, reports, brochures, documents, visual briefs, and Arabic RTL layouts for AI-design clichés, fake data, decorative copy, asset misuse, weak hierarchy, and Arabic rendering risks. Use when the requested deliverable has a visual or document-design component.\n---\n\n# Visual Content Anti-Slop\n\nThis Skill governs **content and art-direction constraints** for visual deliverables. It does not claim the host can render or edit an image unless a compatible tool is actually available.\n\n## One job per page or slide\n\nFor presentations, reports, proposals, brochures, and client files:\n\n- give each page or slide one primary communication job\n- build a clear reading sequence\n- preserve approved meaning and exact facts\n- do not repeat the title as body copy\n- do not add decorative copy to fill empty space\n- do not invent quotations, case studies, charts, statistics, screenshots, or portfolio work\n- use tables only when comparison is actually needed\n- keep labels short and body text readable\n- label genuine placeholders clearly\n\n## Anti-slop visual filter\n\nDo not default to generic AI-decoration patterns such as:\n\n- random gradients, neon, purple glow, glassmorphism, floating translucent cards\n- excessive rounding, shadows, icons, pills, badges, section numbers, or type sizes\n- random 3D/chrome/liquid objects, abstract blobs, decorative waves, unexplained dots or lines\n- robots, glowing brains, circuit-filled heads, futuristic tunnels, space, cyberpunk\n- fake dashboards, fake app screens, fake analytics, fake charts\n- stock teams pointing at screens, handshakes, rockets, light bulbs, targets, puzzle pieces, chess pieces, labyrinths, megaphones, magnifying glasses\n- floating social logos, purposeless laptop/device mockups, oversized quotation marks, decorative English labels\n- arbitrary diagonal layouts, busy-image text overlays, center-aligned long paragraphs\n\nEvery visual element should support comprehension, hierarchy, brand recognition, navigation, comparison, or explanation. Whitespace is allowed.\n\n## Structure\n\nPrefer a clear grid, consistent margins, controlled spacing, hierarchy, readable typography, sufficient contrast, purposeful whitespace, consistent alignment, limited color roles, limited type roles, and real supplied assets.\n\nUse diagrams only when relationships need explanation, charts only when verified data exists, mockups only for real application/context, photography only when relevant, and icons only when they improve recognition or scanning.\n\n## Arabic visual work\n\nFor Arabic presentations, graphics, documents, interfaces, or visuals:\n\n- use true RTL layout\n- use fonts that support Arabic shaping\n- render connected Arabic letters correctly\n- never reverse, mirror, or separate Arabic letters\n- verify similar forms and hamza/ligature behavior\n- check numeral and punctuation direction\n- inspect mixed Arabic-English lines\n- keep Latin brand names and logos in their original direction\n\nIf the available tool cannot guarantee correct Arabic rendering, state that limitation rather than pretending the render is correct.\n\n## Asset control\n\nWhen the user supplies real assets:\n\n- use approved assets\n- do not replace real assets with generated substitutes\n- do not alter logos, packaging, or approved artwork unless requested\n- do not add watermarked stock images or fabricate event/client photos\n- if an asset is missing, use a clearly labelled neutral placeholder or redesign around the gap\n\n## Routed specialists\n\nUse `strict-human-output` for exact format and house-style constraints, `arabic-style-curator` for Arabic copy and RTL-language logic, and `slop-quality-gate` for final content fidelity.\n"
}