3 ms·
I could see that. I’ve found that the more specificity you add to your prompt and less freedom you give Claude Code to kind of just “do its own thing”, the bet
by vunderba 6mo ago
I could see that. I’ve found that the more specificity you add to your prompt and less freedom you give Claude Code to kind of just “do its own thing”, the better your results will be.
FWIW, there’s also an official frontend-design skill for CC [1]. A while back I incorporated some of the more relevant guidance from WCAG into it [2].
[1] - https://github.com/anthropics/claude-code/blob/main/plugins/frontend-design/skills/frontend-design/SKILL.md https://github.com/anthropics/claude-code/blob/main/plugins/...
[2] - https://www.w3.org/WAI/standards-guidelines/wcag https://www.w3.org/WAI/standards-guidelines/wcag
- satvikpendem 6mo agoThere are accessibility skills as well: https://github.com/airowe/claude-a11y-skill https://github.com/airowe/claude-a11y-skill https://mcpmarket.com/tools/skills/accessibility-checker https://mcpmarket.com/tools/skills/accessibility-checker
- conception 6mo agoNote guidance for 4.7 specifically calls out being more specific compared to 4.6. Though the system prompt seems to say the opposite. Tldr I would expect different outcomes with 4.7 with not being specific.
- vunderba 6mo agoHonestly I'd heard so much seemingly conflicting information about the quality of 4.7 that I've got an override in CC to stay on Opus 4.6 (1 million token context) for the time being. For reference, in the .claude/settings.local.json { "model": "claude-opus-4-6[1M]" }
- classified 6mo agoYes, you have to enjoy micromanaging a machine to get somewhat acceptable results.