@primereact/mcp 11.0.0-rc.2

package/data/llms/primitive/components/visuallyhidden.md

@@ -0,0 +1,87 @@
+# VisuallyHidden
+
+A utility component that hides content visually while keeping it accessible to screen readers.
+
+<DocPrimitiveIntro description="Build accessible interfaces by providing screen reader text for icon-only actions and decorative elements." />
+
+```tsx
+'use client';
+import { VisuallyHidden } from 'primereact/visuallyhidden';
+import styles from './basic-demo.module.css';
+
+export default function BasicDemo() {
+    return (
+        <div className={styles.wrapper}>
+            <button className={styles.button}>
+                <i className="pi pi-heart" />
+                <VisuallyHidden>Add to favorites</VisuallyHidden>
+            </button>
+
+            <button className={styles.button}>
+                <i className="pi pi-trash" />
+                <VisuallyHidden>Delete item</VisuallyHidden>
+            </button>
+
+            <button className={styles.button}>
+                <i className="pi pi-cog" />
+                <VisuallyHidden>Open settings</VisuallyHidden>
+            </button>
+        </div>
+    );
+}
+```
+
+<DocPrimitiveLinks name="VisuallyHidden" />
+
+## Features
+
+- Hides content from visual display using WAI-ARIA recommended CSS techniques
+- `focusable` prop enables the element to receive keyboard focus for focus trap boundaries
+- Used internally by [Drawer](/docs/primitive/components/drawer), Dialog, and FocusTrap for focus management
+
+## Usage
+
+```tsx
+import { VisuallyHidden } from 'primereact/visuallyhidden';
+```
+
+```tsx
+<button>
+    <i className="pi pi-trash" />
+    <VisuallyHidden></VisuallyHidden>
+</button>
+```
+
+## Behavior
+
+### Polymorphic Rendering
+
+Use `as` to change the rendered HTML element. Defaults to `span`.
+
+```tsx
+<VisuallyHidden as="label" htmlFor="search-input">
+    Search
+</VisuallyHidden>
+```
+
+### Render Function Children
+
+```tsx
+<VisuallyHidden>{(instance) => <span>Hidden text</span>}</VisuallyHidden>
+```
+
+## API
+
+### VisuallyHidden
+
+<DocTable name="VisuallyHidden" category="api" />
+
+## Accessibility
+
+### Screen Reader
+
+VisuallyHidden content is announced by screen readers as regular text within the document flow. The component applies CSS styles that remove the element from visual rendering while preserving its presence in the accessibility tree.
+
+### Keyboard Support
+
+When `focusable` is `true`, the element receives a `tabIndex` of `0` and can be reached via `tab` navigation. This is used internally by focus trap implementations to create invisible tab-stop boundaries.

package/data/llms/primitive/guides/ai/llms.md

@@ -0,0 +1,25 @@
+# LLMs.txt
+
+LLMs.txt is a file that contains the LLMs for the PrimeReact documentation.
+
+## /llms.txt
+
+The [llms.txt](https://llmstxt.org/) file is an industry standard that helps AI models better understand and navigate the PrimeReact documentation. It lists key pages in a structured format, making it easier for LLMs to retrieve relevant information.
+
+<Button as="a" href="/llms.txt" target="_blank">Open llms.txt</Button>
+
+&nbsp;
+
+## /llms-full.txt
+
+The `llms-full.txt` file is a complete list of all the pages in the PrimeReact documentation. It is used to help AI models understand the entire documentation set.
+
+<Button as="a" href="/llms-full.txt" target="_blank">Open llms-full.txt</Button>
+
+&nbsp;
+
+## .md extension
+
+Add a `.md` to a page’s URL to display a Markdown version of that page.
+
+<Button as="a" href="/docs/overview/llms.md" target="_blank">Open /docs/overview/llms.md</Button>

package/data/llms/primitive/guides/icons/customicons.md

@@ -0,0 +1,47 @@
+# Custom Icons
+
+PrimeReact components can be used with any icon library using the templating features.
+
+## Material
+
+[Material icons](https://fonts.google.com/icons) is the official icon library based on Google Material Design.
+
+```tsx
+<Button>
+    <span className="material-icons">arrow_drop_down</span>
+</Button>
+```
+
+## FontAwesome
+
+[Font Awesome](https://fontawesome.com/) is a popular icon library with a wide range of icons.
+
+```tsx
+<Button>
+    <i className="fa-light fa-chevron-down"></i>
+</Button>
+```
+
+## SVG
+
+Inline SVGs are embedded inside the dom.
+
+```tsx
+<Button>
+    <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
+        <g id="chevron-down">
+            <path d="M12,15.25a.74.74,0,0,1-.53-.22l-5-5A.75.75,0,0,1,7.53,9L12,13.44,16.47,9A.75.75,0,0,1,17.53,10l-5,5A.74.74,0,0,1,12,15.25Z" />
+        </g>
+    </svg>
+</Button>
+```
+
+## Image
+
+Any type of image can be used as an icon.
+
+```tsx
+<Button>
+    <img alt="dropdown icon" src="/assets/icons/arrow_down.png">
+</Button>
+```

package/data/llms/primitive/guides/icons/primeicons.md

@@ -0,0 +1,112 @@
+# Prime Icons
+
+PrimeIcons is the default icon library of PrimeReact with over 250 open source icons developed by PrimeTek. PrimeIcons library is optional as PrimeReact components can use any icon with templating.
+
+<DocNotification>
+    Browse all 250+ icons on <a href="https://primeicons.dev" target="_blank" rel="noopener noreferrer">primeicons.dev</a>.
+</DocNotification>
+
+## Download
+
+`@primeicons/react` is available on npm. Each icon is a standalone React component, so only the icons you import are included in your bundle.
+
+```bash
+npm install @primeicons/react
+```
+
+## Import
+
+Import icons individually from their own entry point.
+
+```tsx
+import { Check } from '@primeicons/react/check';
+import { Search } from '@primeicons/react/search';
+```
+
+## Figma
+
+PrimeIcons library is now available on [Figma Community](https://www.figma.com/community/file/1354343849355792252/primeicons). By adding them as a library, you can easily use these icons in your designs.
+
+## Basic
+
+Each icon is an SVG React component. Import and render it directly — no additional configuration needed.
+
+```tsx
+import { Check } from '@primeicons/react/check';
+import { Search } from '@primeicons/react/search';
+import { Times } from '@primeicons/react/times';
+import { User } from '@primeicons/react/user';
+
+export default function BasicDemo() {
+    return (
+        <div className="flex justify-center gap-4">
+            <Check />
+            <Times />
+            <Search />
+            <User />
+        </div>
+    );
+}
+```
+
+## Size
+
+Icon size is controlled with the `size` prop, which sets both the width and height in pixels.
+
+```tsx
+import { Check } from '@primeicons/react/check';
+import { Search } from '@primeicons/react/search';
+import { Times } from '@primeicons/react/times';
+import { User } from '@primeicons/react/user';
+
+export default function SizeDemo() {
+    return (
+        <div className="flex justify-center items-center gap-4">
+            <Check size={16} />
+            <Times size={24} />
+            <Search size={32} />
+            <User size={40} />
+        </div>
+    );
+}
+```
+
+## Color
+
+Icon color is set with the `color` prop and is inherited from the parent element by default.
+
+```tsx
+import { Check } from '@primeicons/react/check';
+import { Search } from '@primeicons/react/search';
+import { Times } from '@primeicons/react/times';
+import { User } from '@primeicons/react/user';
+
+export default function ColorDemo() {
+    return (
+        <div className="flex justify-center items-center gap-4">
+            <Check color="#22c55e" />
+            <Times color="#ef4444" />
+            <Search color="#3b82f6" />
+            <User color="#a855f7" />
+        </div>
+    );
+}
+```
+
+## Spin
+
+Use a spin animation utility like `animate-spin` from Tailwind apply rotation.
+
+```tsx
+import { Cog } from '@primeicons/react/cog';
+import { Spinner } from '@primeicons/react/spinner';
+
+export default function SpinDemo() {
+    return (
+        <div className="flex justify-center gap-4">
+            <Spinner className="animate-spin" size={32} />
+            <Cog className="animate-spin" size={32} />
+        </div>
+    );
+}
+```

package/data/llms/primitive/guides/installation.md

@@ -0,0 +1,115 @@
+# Installation
+
+Install PrimeReact and compose unstyled primitive components in your React project.
+
+<DocMessage>
+Start from our <a href="https://github.com/primefaces/primereact-examples/tree/main/nextjs-primitive-quickstart" target="_blank" rel="noopener noreferrer">Next.js template</a>, pre-configured with PrimeReact.
+</DocMessage>
+
+Primitive components ship **unstyled** — you compose the behavior and bring your own styles. They work in any React setup; the steps below show a Next.js example you can adapt to your own framework.
+
+<DocStepper>
+    <DocStep>
+
+### Install Packages
+
+Install PrimeReact using your favorite package manager:
+
+```bash
+npm install primereact@11.0.0-rc.2
+```
+
+    </DocStep>
+    <DocStep>
+
+### PrimeReactProvider
+
+Wrap your app with `PrimeReactProvider` so the primitives' shared context is available everywhere. No theme or preset is needed — you style everything yourself:
+
+```tsx showLineNumbers title="components/prime-provider.tsx"
+'use client';
+import { PrimeReactProvider } from '@primereact/core';
+
+export function PrimeProvider({ children }: { children: React.ReactNode }) {
+    return <PrimeReactProvider>{children}</PrimeReactProvider>;
+}
+```
+
+Then wrap your app with it in `app/layout.tsx`:
+
+```tsx showLineNumbers title="app/layout.tsx" {1,6}
+import { PrimeProvider } from '@/components/prime-provider';
+
+export default function RootLayout({ children }: { children: React.ReactNode }) {
+    return (
+        <html lang="en">
+            <body>
+                <PrimeProvider>{children}</PrimeProvider>
+            </body>
+        </html>
+    );
+}
+```
+
+    </DocStep>
+    <DocStep>
+
+### Add a `cn` Helper (optional)
+
+If you style with Tailwind, a `cn` helper makes merging class names easier. Install `tailwind-merge` and create `lib/utils.ts`:
+
+```bash
+npm install tailwind-merge
+```
+
+```ts showLineNumbers title="lib/utils.ts"
+import { cn as _cn } from '@primeuix/utils';
+import { twMerge } from 'tailwind-merge';
+
+export function cn(...inputs: unknown[]) {
+    return twMerge(_cn(...inputs));
+}
+```
+
+    </DocStep>
+    <DocStep>
+
+### Verify
+
+Render the unstyled `Button` primitive, styled with your `cn` helper, to confirm everything is wired up:
+
+```tsx
+import { cn } from '@primeuix/utils';
+import { Button } from 'primereact/button';
+
+export default function VerifyDemo() {
+    return (
+        <div className="flex justify-center">
+            <Button
+                className={cn(
+                    'inline-flex items-center justify-center rounded-md bg-neutral-900 px-4 py-2 text-sm font-medium text-white transition-colors hover:bg-neutral-800'
+                )}
+            >
+                Verify
+            </Button>
+        </div>
+    );
+}
+```
+
+```tsx showLineNumbers {1}
+import { Button } from 'primereact/button';
+import { cn } from '@/lib/utils';
+
+export default function VerifyInstallation() {
+    return <Button className={cn('inline-flex items-center justify-center rounded-md bg-neutral-900 px-4 py-2 text-sm font-medium text-white transition-colors hover:bg-neutral-800')}>Verify</Button>;
+}
+```
+
+    </DocStep>
+
+</DocStepper>
+
+## Next Steps
+
+[Browse the components](/docs/primitive/components/autocomplete) and compose the unstyled primitives you need, styling them with any CSS solution.

package/data/llms/primitive/guides/introduction.md

@@ -0,0 +1,20 @@
+# Primitive
+
+Unstyled React components with composable subcomponents. Behavior included, styling up to you.
+
+## Overview
+
+Primitives are low-level React components built on top of our headless hooks. Unlike hooks, they provide a compound component API, `Dialog.Root`, `Dialog.Trigger`, `Dialog.Content`, so you compose pieces without wiring up hook props manually.
+
+Use primitives when you want the ergonomics of a component API but full freedom over styles. They're what our Styled and Tailwind layers are built on.
+
+## What you get
+
+- 70+ components with a compound API
+- No styles, use any CSS solution you like
+- Data attributes for state-based styling (`data-state`, `data-disabled`)
+- Full accessibility and keyboard navigation
+
+## Next steps
+
+Open any component in the sidebar to see its subcomponents and composition examples.

package/data/llms/primitive/guides/misc/accessibility.md

@@ -0,0 +1,215 @@
+# Accessibility
+
+PrimeReact has WCAG level compliance, refer to the accessibility documentation of each component for detailed information.
+
+import { CheckCircle } from '@primeicons/react/check-circle'
+import { TimesCircle } from '@primeicons/react/times-circle'
+
+## Introduction
+
+According to the World Health Organization, 15% of the world population has a disability to some degree. As a result, accessibility features in any context such as a ramp for wheelchair users or a multimedia with captions are crucial to ensure content can be consumed by anyone.
+
+Types of disabilities are diverse so you need to know your audience well and how they interact with the content created. There four main categories;
+
+### Visual Impairments
+
+Blindness, low-level vision or color blindness are the common types of visual impairments. Screen magnifiers and the color blind mode are usually built-in features of the browsers whereas for people who rely on screen readers, page developers are required to make sure content is readable by the readers. Popular readers are NVDA , JAWS and ChromeVox .
+
+### Hearing Impairments
+
+Deafness or hearing loss refers to the inability to hear sounds totally or partially. People with hearing impairments use assistive devices however it may not be enough when interacting with a web page. Common implementation is providing textual alternatives, transcripts and captions for content with audio.
+
+### Mobility Impairments
+
+People with mobility impairments have disabilities related to movement due to loss of a limb, paralysis or other varying reasons. Assistive technologies like a head pointer is a device to interact with a screen whereas keyboard or a trackpad remain as solutions for people who are not able to utilize a mouse.
+
+### Cognitive Impairments
+
+Cognitive impairments have a wider range that includes people with learning disabilities, depression and dyslexia. A well designed content also leads to better user experience for people without disabilities so designing for cognitive impairments result in better design for any user.
+
+## WCAG
+
+Correct page structure with the aid of assistive technologies are the core ingridients for an accessible web content. HTML is based on an accessible foundation, form controls can be used by keyboard by default and semantic HTML is easier to be processed by a screen reader.
+
+[WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/) refers to **Web Content Accessibility Guideline**, a standard managed by the WAI (Web Accessibility Initiative) of W3C (World Wide Web Consortium). WCAG consists of recommendations for making the web content more accessible. PrimeReact components aim high level of WCAG compliancy in the near future.
+
+Various countries around the globe have governmental policies regarding web accessibility as well. Most well known of these are Section 508 in the US and [Web Accessibility Directive](https://digital-strategy.ec.europa.eu/en/policies/web-accessibility) of the European Union.
+
+## Form Controls
+
+Native form elements should be preferred instead of elements that are meant for other purposes like presentation. As an example, button below is rendered as a form control by the browser, can receive focus via tabbing and can be used with space key as well to trigger.
+
+```tsx
+<button onClick={(event) => onButtonClick(event)}>Click</button>
+```
+
+On the other hand, a fancy css based button using a div has no keyboard or screen reader support.
+
+```tsx
+<div className="fancy-button" onClick={(event) => onButtonClick(event)}>
+    Click
+</div>
+```
+
+`tabIndex` is required to make a div element accessible in addition to use a keydown to bring the keyboard support back. To avoid the overload and implementing functionality that is already provided by the browser, native form controls should be preferred.
+
+```tsx
+<div className="fancy-button" onClick={(event) => onClick(event)} onKeyDown={(event) => onKeyDown(event)} tabIndex="0">
+    Click
+</div>
+```
+
+Form components must be related to another element that describes what the form element is used for. This is usually achieved with the `label` element.
+
+```tsx
+<label htmlFor="myinput">Username:</label>
+<input id="myinput" type="text" name="username" />
+```
+
+## Semantic HTML
+
+HTML offers various element to organize content on a web page that screen readers are aware of. Preferring Semantic HTML for good semantics provide out of the box support for reader which is not possible when regular `div` elements with classes are used. Consider the following example that do not mean too much for readers.
+
+```tsx
+<div className="header">
+    <div className="header-text">Header</div>
+</div>
+
+<div className="nav"></div>
+
+<div className="main">
+    <div className="content">
+    </div>
+
+    <div className="sidebar">
+    </div>
+</div>
+
+<div className="footer"></div>
+```
+
+Same layout can be achieved using the semantic elements with screen reader support built-in.
+
+```tsx
+<header>
+    <h1>Header</h1>
+</header>
+
+<nav></nav>
+
+<main>
+    <article></article>
+
+    <aside></aside>
+
+</main>
+
+<footer></footer>
+```
+
+## WAI ARIA
+
+ARIA refers to "Accessible Rich Internet Applications" is a suite to fill the gap where semantic HTML is inadequate. These cases are mainly related to rich UI components/widgets. Although browser support for rich UI components such as a datepicker or inputcolor has been improved over the past years many web developers still utilize UI components derived from standard HTML elements created by them or by other projects like PrimeReact. These types of components must provide keyboard and screen reader support, the latter case is where the WAI-ARIA is utilized.
+
+ARIA consists of roles, properties and attributes. **Roles** define what the element is mainly used for e.g. `checkbox`, `dialog`, `tablist` whereas **States** and **Properties** define the metadata of the element like `aria-checked`, `aria-disabled`.
+
+Consider the following case of a native checkbox. It has built-in keyboard and screen reader support.
+
+```tsx
+<input type="checkbox" value="Prime" name="ui" checked />
+```
+
+A fancy checkbox with css animations might look more appealing but accessibility might be lacking. Checkbox below may display a checked font icon with animations however it is not tabbable, cannot be checked with space key and cannot be read by a reader.
+
+```tsx
+<div className="fancy-checkbox">{checked && <i className="checked-icon" />}</div>
+```
+
+One alternative is using ARIA roles for readers and use javascript for keyboard support. Notice the usage of `aria-labelledby` as a replacement of the `label` tag with `htmlFor`.
+
+```tsx
+<span id="chk-label">Remember Me</span>
+<div className="fancy-checkbox" role="checkbox" aria-checked="false" tabIndex="0" aria-labelledby="chk-label"
+    onClick={toggle} onKeyDown={(event) => onKeyDown(event)}>
+    {checked && <i className="checked-icon" />}
+</div>
+```
+
+However the best practice is combining semantic HTML for accessibility while keeping the design for UX. This approach involves hiding a native checkbox for accessibility and using javascript events to update its state. Notice the usage of `p-hidden-accessible` that hides the elements from the user but not from the screen reader.
+
+```tsx
+<label htmlFor="chkbox">Remember Me</label>
+<div className="fancy-checkbox" onClick={toggle}>
+    <input className="p-hidden-accessible" type="checkbox" id="chkbox" onFocus={updateParentVisuals} onBlur={updateParentVisuals}
+        onKeyDown={(event) => onKeyDown(event)} />
+    {checked && <i className="checked-icon" />}
+</div>
+```
+
+A working sample is the PrimeReact checkbox that is tabbable, keyboard accessible and is compliant with a screen reader. Instead of ARIA roles it relies on a hidden native checkbox.
+
+```tsx
+'use client';
+import { Check } from '@primeicons/react/check';
+import { Checkbox } from 'primereact/checkbox';
+import styles from './accessibility-checkbox-demo.module.css';
+
+export default function AccessibilityCheckboxDemo() {
+    return (
+        <div className={styles.wrapper}>
+            <Checkbox.Root inputId="chkbox" className={styles.root} inputClassName={styles.input}>
+                <Checkbox.Box className={styles.box}>
+                    <Checkbox.Indicator match="checked" className={styles.indicator}>
+                        <Check className="w-3 h-3" />
+                    </Checkbox.Indicator>
+                </Checkbox.Box>
+            </Checkbox.Root>
+            <label htmlFor="chkbox" className={styles.label}>
+                Remember Me
+            </label>
+        </div>
+    );
+}
+```
+
+## Colors
+
+Colors on a web page should aim a contrast ratio of at least 4.5:1 and consider a selection of colors that do not cause vibration.
+
+### Good Contrast
+
+Color contrast between the background and the foreground content should be sufficient enough to ensure readability. Example below displays two cases with good and bad samples.
+
+<div className="flex">
+    <div className="h-32 w-32 flex justify-center items-center mr-8 font-bold bg-blue-600 rounded-lg">
+        <span className="text-white">GOOD</span>
+    </div>
+    <div className="h-32 w-32 flex justify-center items-center mr-8 font-bold bg-blue-400 rounded-lg">
+        <span className="text-white">BAD</span>
+    </div>
+</div>
+
+### Vibration
+
+Color vibration is leads to an illusion of motion due to choosing colors that have low visibility against each other. Color combinations need to be picked with caution to avoid vibration.
+
+<div className="flex">
+    <div className="h-32 w-32 flex justify-center items-center mr-8 font-bold bg-pink-500 rounded-lg">
+        <span className="text-blue-500">VIBRATE</span>
+    </div>
+</div>
+
+### Dark Mode
+
+Highly saturated colors should be avoided when used within a dark design scheme as they cause eye strain. Instead desaturated colors should be preferred.
+
+<div className="flex">
+    <div className="h-32 w-32 flex flex-col justify-center items-center mr-8 font-bold bg-gray-900 rounded-lg">
+        <span className="text-indigo-500">Indigo 500</span>
+        <TimesCircle className="text-indigo-500 mt-4 text-xl" />
+    </div>
+    <div className="h-32 w-32 flex flex-col justify-center items-center mr-8 font-bold bg-gray-900 rounded-lg">
+        <span className="text-indigo-200">Indigo 200</span>
+        <CheckCircle className="text-indigo-200 mt-4 text-xl" />
+    </div>
+</div>