Find a setup problem
Check missing files, styles, browser permissions and changed behavior.
The example does not build or has no styles
Restore the full kit and check relative import paths, letter case, CSS Module support and any nested vendor folder. Read the first relevant error, not only the final build failure. Use the React and TypeScript setup your project already has.
If the isolated example works but your page looks different, inspect inherited styles and your global reset. Avoid fixing the symptom by deleting focus, overflow or reduced-motion rules.
The action or animation seems different
Read what the demo action does before expecting a server request or a saved result. For clipboard actions, use HTTPS or localhost and check browser permission; refusal must remain a handled error.
If motion is absent, check Off, zero duration and system reduced motion first. Content should still be usable. If you changed the component API, compare with an unchanged SelectedExample before removing safeguards.
Describe the problem precisely
Record the item ID, kit version from manifest.json, chosen target, browser and steps to reproduce. Include the actual error and the expected result. Omit credentials and private project data.
You can use the troubleshooting request on the All guides page with your coding assistant. Ask it to distinguish a confirmed fix from a scenario it has not tested.