Update to DXD Skills

{
  "name": "better-ai-design",
  "description": "Design distinctive, usable web and app interfaces when a brief calls for a strong visual direction, deliberate exploration, or visual critique beyond a routine implementation.",
  "included_files": [],
  "skill_md_contents": "---\nname: better-ai-design\ndescription: >-\n  Design distinctive, usable web and app interfaces when a brief calls for a\n  strong visual direction, deliberate exploration, or visual critique beyond a\n  routine implementation.\n---\n\n# Better AI Design\n\n## Goal\n\nHelp consequential interface work arrive at a clear visual point of view while\nremaining useful, coherent, and faithful to the product brief.\n\n## When to Use\n\nUse this when the user requests an ambitious or distinctive interface, asks to\nexplore directions before building, or wants a visual critique of a meaningful\nscreen or flow. For routine component work, use the project's existing design\nsystem and ordinary implementation judgment.\n\n## Workflow\n\n1. Establish the product purpose, audience, constraints, and feeling the\n   interface should create. Preserve explicit user references and existing\n   brand or design-system decisions.\n2. For work where the direction is genuinely open, compare a few materially\n   different concepts before committing. Use references, sketches, or small\n   experiments when they help make the choice concrete.\n3. Express the chosen direction through hierarchy, composition, typography,\n   color, imagery, and interaction, not merely a new palette on a familiar\n   layout.\n4. Remove decoration, containers, copy, and custom controls that do not improve\n   comprehension, task flow, or the chosen aesthetic.\n5. Inspect the rendered result. For visually important work, capture a\n   screenshot and seek an independent critique or compare it against suitable\n   references. Revise the highest-impact gaps, then stop when the result meets\n   the brief or further changes no longer improve it.\n\nGenerated imagery, animation, and separate critique contexts are tools for a\nspecific design problem, not a default process. Use them only when they add\nmeaningful character or confidence. Keep generated-media credentials out of\nshipped code. When using a fresh visual critic, provide screenshots and the brief\nwithout implementation details or a target score; start with one or two passes.\n\n## Guardrails\n\n- Never replace a clear user brief with an unrelated aesthetic experiment.\n- Never mistake novelty for usability, accessibility, or product fit.\n- Never run open-ended critique cycles; set a useful stopping condition.\n- Use inspiration to assess mood and craft; when the user requests faithful\n  implementation of a supplied design, preserve that reference and requested fidelity.\n- Never expose generation credentials or private assets.\n\n## Completion Checklist\n\n- [ ] The chosen direction serves the product and the user's brief.\n- [ ] Layout, type, color, and interaction reinforce the same direction.\n- [ ] Unnecessary visual and textual elements were removed.\n- [ ] The final rendered result was reviewed at an appropriate level of rigor.\n\n## Source\n\nAdapted from Anshu Chimala’s [“How to turn your AI into a world-class designer”](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world).\n"
}