docs: add link to visual style guide at uistyleguide.com

[LukeL99]

Hey guys,

I love your skill, and it makes a massive difference in the output of beautiful sites. I'm not a designer, so I find myself going through the list of styles that can be applied, googling them, going back, trying again, etc. It was a bit tedious so I made myself a visual reference guide, and then I thought it could be useful for others as well so I put it online.

You can check it out here. I would love to get a link in your docs so others can benefit from what I've built as well.

[patricksevat]

@LukeL99 thx for this! I'm also not a designer and I super appreciate this site so I can get a better feel for the styles supported by this skill. Hope the maintainers add it, cause it's super useful for engineers who lack design depth

[mrgoonie]

@claude review

[claude]

Claude finished @mrgoonie's task in 1m 13s —— View job

---

PR Review: docs: add link to visual style guide at uistyleguide.com

• Read the changed files
• Analyze the PR changes
• Post review feedback

---

Summary

This PR adds 2 lines to README.md linking to a community-built visual reference guide at uistyleguide.com. The change is purely documentation — no code, data, or scripts are modified.

---

Feedback

Positive aspects:

• Addresses a real pain point: the skill lists 67+ UI styles by name, but non-designers benefit from seeing them visually
• Community validation from @patricksevat confirms the utility
• Minimal, focused change with zero risk of breaking anything

Concerns to consider:

1. External dependency / link rot — The README would link to a third-party domain that maintainers have no control over. If uistyleguide.com goes down, changes ownership, or shifts content, the link becomes a liability. Consider whether adding a note like "community resource, not officially maintained" would set appropriate expectations.

2. Placement not visible in review — Since this PR is branched from a fork's main, I cannot inspect the actual diff locally. The placement of the link within the README matters. Ideally it should sit near the "Available Styles (67)" section (around line 161) or in a dedicated "Resources" / "Community" section — not tucked in an unrelated area. Maintainers should verify this before merging.

3. Branch convention — Per the project's CLAUDE.md, contributors should never push directly to main but instead use a feature branch (feat/...). This PR is submitted from the fork's main. It won't cause issues here since it's a fork, but it's worth noting for future contributions from @LukeL99.

4. No content vetting — Maintainers should briefly visit the site to confirm it accurately represents the styles in this skill and aligns with the project's quality bar before merging.

---

Verdict

✅ Looks good to merge (pending maintainer verification of link placement and site content)

The change is low-risk and fills a genuine documentation gap. The two concerns above (link placement and external dependency disclaimer) are minor and can be addressed in a follow-up if needed. A quick visit to the site and a look at where exactly in the README the link lands is all that's needed before merging.

---