storybook/dist/_browser-chunks/chunk-KJ7GNWII.js

Storybook: Develop, document, and test UI components in isolation

import {
  getToolName
} from "./chunk-TYQWMAQX.js";

// src/shared/open-service/toolsets/docs/instructions.ts
function getDocsToolsetInstructions(transport) {
  let ref = getToolName({ transport });
  return `## Documentation Workflow

**CRITICAL: Never hallucinate component properties!** Before using ANY property on a component (even common-sounding ones like \`shadow\`), you MUST verify it is documented via these tools. If it is not documented, it does not exist \u2014 never assume props from naming conventions or other libraries; report it to the user instead.

1. Call **${ref("docs.list")}** once at the start of the task to discover available component and docs IDs.
2. Call **${ref("docs.show")}** with an \`id\` from that list to retrieve full component docs, props, usage examples, and stories.
3. Call **${ref("docs.showStory")}** for extra docs on a story variant not covered by the component docs.

Only use properties explicitly documented or shown in example stories. Only reference IDs returned by these tools; never guess IDs.

## Multi-Source Requests

- With multiple sources configured, **${ref("docs.list")}** returns entries from every source; pass \`storybookId\` to **${ref("docs.show")}** to scope one.
`;
}
var DOCS_TOOLSET_INSTRUCTIONS = getDocsToolsetInstructions("mcp");

export {
  getDocsToolsetInstructions,
  DOCS_TOOLSET_INSTRUCTIONS
};