docs: add missing design system integrations to llms.txt

[chanwukim]

Description

Add the four design system integration guides that are present in the documentation navigation but missing from docs/public/llms.txt.

Related Issue: None (minimal documentation-only update)

Changes

• Add shadcn/ui to the design system integration index.
• Add Radix UI to the design system integration index.
• Add Mantine to the design system integration index.
• Add Headless UI to the design system integration index.

Motivation and Context

The published documentation includes these integration guides, but the LLM-facing index currently lists only Material UI, Chakra UI, and Ant Design. Adding the missing links keeps the index aligned with the documentation navigation.

How Has This Been Tested?

• Compared each entry with its corresponding English MDX guide.
• Confirmed the branch differs from main by four additions in docs/public/llms.txt only.

Screenshots (if appropriate):

Not applicable.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have performed a self-review of my own code.
• My code is commented, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

Further Comments

No source code or generated documentation content was changed.

[vercel]

@chanwukim is attempting to deploy a commit to the Toss Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4042ec7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR