@atlaskit/ads-mcp 1.12.11 → 1.12.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (25) hide show
  1. package/CHANGELOG.md +15 -0
  2. package/dist/cjs/tools/get-all-components/components.codegen.js +2 -2
  3. package/dist/cjs/tools/get-atlaskit-components/atlaskit-components.codegen.js +2 -2
  4. package/dist/cjs/tools/get-atlaskit-hooks/atlaskit-hooks.codegen.js +5 -5
  5. package/dist/cjs/tools/get-atlaskit-utilities/atlaskit-utilities.codegen.js +2 -2
  6. package/dist/cjs/tools/get-lint-rules/lint-rules-structured-content.codegen.js +41 -25
  7. package/dist/cjs/tools/migration-guides/migrations/onboarding-with-motion.js +5 -5
  8. package/dist/es2019/tools/get-all-components/components.codegen.js +2 -2
  9. package/dist/es2019/tools/get-atlaskit-components/atlaskit-components.codegen.js +2 -2
  10. package/dist/es2019/tools/get-atlaskit-hooks/atlaskit-hooks.codegen.js +5 -5
  11. package/dist/es2019/tools/get-atlaskit-utilities/atlaskit-utilities.codegen.js +2 -2
  12. package/dist/es2019/tools/get-lint-rules/lint-rules-structured-content.codegen.js +41 -25
  13. package/dist/es2019/tools/migration-guides/migrations/onboarding-with-motion.js +23 -30
  14. package/dist/esm/tools/get-all-components/components.codegen.js +2 -2
  15. package/dist/esm/tools/get-atlaskit-components/atlaskit-components.codegen.js +2 -2
  16. package/dist/esm/tools/get-atlaskit-hooks/atlaskit-hooks.codegen.js +5 -5
  17. package/dist/esm/tools/get-atlaskit-utilities/atlaskit-utilities.codegen.js +2 -2
  18. package/dist/esm/tools/get-lint-rules/lint-rules-structured-content.codegen.js +41 -25
  19. package/dist/esm/tools/migration-guides/migrations/onboarding-with-motion.js +5 -5
  20. package/dist/types/tools/get-all-components/components.codegen.d.ts +1 -1
  21. package/dist/types/tools/get-atlaskit-components/atlaskit-components.codegen.d.ts +1 -1
  22. package/dist/types/tools/get-atlaskit-hooks/atlaskit-hooks.codegen.d.ts +1 -1
  23. package/dist/types/tools/get-atlaskit-utilities/atlaskit-utilities.codegen.d.ts +1 -1
  24. package/dist/types/tools/get-lint-rules/lint-rules-structured-content.codegen.d.ts +1 -1
  25. package/package.json +3 -3
@@ -3,7 +3,7 @@
3
3
  *
4
4
  * Structured content for MCP (JSON) for ESLint rule docs from constellation.
5
5
  *
6
- * @codegen <<SignedSource::89a5a1c47b0a992cb611dc171b6eb82e>>
6
+ * @codegen <<SignedSource::b7233ec49872f0354cb5b2d7ff72ccad>>
7
7
  * @codegenCommand yarn build structured-docs
8
8
  */
9
9
  /* eslint-disable no-template-curly-in-string */
@@ -13,7 +13,7 @@ export var lintRulesMcpStructuredContent = [{
13
13
  ruleName: 'badge-appearance-semantic-migration',
14
14
  description: 'This rule enforces migration of Badge component `appearance` prop values to new semantic values.'
15
15
  }, {
16
- content: "{\"ruleName\":\"consistent-css-prop-usage\",\"description\":\"Ensures consistency with css prop usage.\",\"content\":\"# consistent-css-prop-usage\\n\\nEnsures consistency with css prop usage.\\n\\n## Rationale\\n\\nEvery app should be defining styles in the same way, using the same tools, enforced by the same\\nlinting rules, which we can then all evolve and scale together.\\n\\n## How the rule works\\n\\nThis rule checks for the following cases:\\n\\n- Styles should not be defined inline; it should instead be in a standalone variable.\\n - The exception for this is style composition (e.g. `<div css={[baseStyles, moreStyles]} />`),\\n which is a way to combine styles from two variables.\\n- Styles must be wrapped in a `css` function call.\\n- Styles must be defined in the same file as their usage, and not be imported.\\n- Styles should not contain spread operators (e.g. `css({ ...spreadStyles })`).\\n- Styles must all be defined at the top of the file, or at the bottom of the file.\\n\\nThis rule also has an autofixer that enforces and fixes the code (where practical) to meet the above\\nrequirements.\\n\\nAll the above can also work for custom `css` functions, such as `xcss`\\n(https://atlassian.design/components/primitives/xcss/).\\n\\nThis rule has several options - see below.\\n\\n## Examples\\n\\n### Incorrect\\n\\n**Calling a css/xcss function or direct objects inside the JSX attribute.**\\n\\n```js\\nfunction Button({ children }) {\\n return <div css={css({...})}>{children}</div>;\\n ^^^^^^^ css function call used inline (performance issue)\\n}\\n```\\n\\n**Inserting a non css-function based object identifier into a css JSX attribute.**\\n\\n```js\\nconst container = {\\n ^^^^^^^^^ should be a css function call\\n zIndex: 10,\\n};\\n\\nfunction Button({ children }) {\\n return <button css={container}>{children}</button>;\\n}\\n```\\n\\n**Importing styles from another file.**\\n\\n```js\\nimport { container } from './styles';\\n ^^^^^^^^^ styles should be local, not shared\\n\\nfunction Button({ children }) {\\n return <button css={container}>{children}</button>;\\n}\\n```\\n\\n**Nesting styles with objects instead of arrays.**\\n\\n```js\\nconst baseContainerStyles = css({\\n zIndex: 5,\\n});\\n\\nconst containerStyles = css({\\n ...baseContainerStyles,\\n ^^^^^^^^^^^^^^^^^^^^^^ compose styles by providing an array to the css call instead (see example below)\\n zIndex: 7,\\n});\\n\\nfunction Button({ children }) {\\n return <button css={containerStyles}>{children}</button>;\\n}\\n```\\n\\n### Correct\\n\\n**Using the css() function to create a style object and passing it as a variable into the\\n`css={...}` JSX attribute.**\\n\\nWith the following options turned on:\\n\\n- cssFunctions = ['css']\\n- stylesPlacement = 'top'\\n\\n```js\\nconst containerStyles = css({\\n\\tzIndex: 1,\\n});\\n\\nfunction Button({ children }) {\\n\\treturn <button css={containerStyles}>{children}</button>;\\n}\\n```\\n\\n**Technically correct usage of the cssMap function.**\\n\\nWith the following options turned on:\\n\\n- cssFunctions = ['css']\\n- stylesPlacement = 'top'\\n\\n```js\\nconst borderStyles = cssMap({\\n 'solid': '1px solid';\\n 'none': '0px';\\n})\\n\\nfunction Button({ children }) {\\n return <button css={borderStyles[solid]}>{children}</button>;\\n}\\n```\\n\\n**Create composite styles with arrays, not objects.**\\n\\nWith the following options turned on:\\n\\n- cssFunctions = ['css']\\n- stylesPlacement = 'bottom'\\n\\n```js\\nfunction Button({ children }) {\\n\\treturn <button css={[baseContainerStyles, containerStyles]}>{children}</button>;\\n}\\n\\nconst baseContainerStyles = css({\\n\\tzIndex: 5,\\n});\\n\\nconst containerStyles = css({\\n\\tzIndex: 7,\\n});\\n```\\n\\n**Ternaries can be used inline**\\n\\n```js\\nconst baseStyles = css({ color: token('color.text.primary') });\\nconst disabledStyles = css({ color: token('color.text.disabled') });\\n\\n<div css={props.disabled ? disabledStyles : baseStyles}></div>;\\n```\\n\\n## Options\\n\\nThis rule comes with options to support different repository configurations.\\n\\n### cssFunctions\\n\\nAn array of function names the linting rule should target. Defaults to `['css', 'xcss']`. The\\nfunctionality of `cssMap` will be linted regardless of the configuration of `cssFunctions`, as it\\ncan be used with either attribute.\\n\\n### stylesPlacement\\n\\nEither `top` or `bottom`.\\n\\nThe rule prevents inline styles from being created. This option defines what the error message\\nshould say: \\\"(...) styles at the top (...)\\\" or \\\"(...) styles at the bottom (...)\\\". Defaults to\\n`top`.\\n\\n### cssImportSource\\n\\nWhen auto-fixing the contents of the `css` attribute, this rule will wrap CSS styles in a `css(...)`\\nfunction call or ``css`...` `` template expression, and it will add an import declaration for the\\n`css` function. `cssImportSource` is a string that determines what package `css` should be imported\\nfrom.\\n\\nThis is `@compiled/react` by default.\\n\\n### xcssImportSource\\n\\nWhen auto-fixing the contents of the `xcss` attribute, this rule will wrap XCSS styles in a\\n`xcss(...)` function call, and it will add an import declaration for the `xcss` function.\\n`xcssImportSource` is a string that determines what package `xcss` should be imported from.\\n\\nThis is `@atlaskit/primitives` by default.\\n\\n### excludeReactComponents\\n\\nWhether to exclude `css` attributes of React components from being affected by this ESLint rule. We\\nassume that an element is a React component if its name starts with a capital letter, e.g.\\n`<Button />`.\\n\\nThis is `false` by default.\\n\\n### shouldAlwaysCheckXcss\\n\\nOverrides `excludeReactComponents` specifically for the `xcss` prop.\\n\\nThis means that even if `excludeReactComponents` is `true`, you can still lint the `xcss` prop by\\nsetting `shouldAlwaysCheckXcss` to `true`.\\n\\nThis is `false` by default.\\n\\n### autoFix\\n\\nWhen set to `true`, this rule will turn on the autofixer. Set this to `false` if you do not want the\\nautofixers to run.\\n\\nThis is `true` by default.\\n\"}",
16
+ content: "{\"ruleName\":\"consistent-css-prop-usage\",\"description\":\"Ensures consistency with css prop usage.\",\"content\":\"# consistent-css-prop-usage\\n\\nEnsures consistency with css prop usage.\\n\\n## Rationale\\n\\nEvery app should be defining styles in the same way, using the same tools, enforced by the same\\nlinting rules, which we can then all evolve and scale together.\\n\\n## How the rule works\\n\\nThis rule checks for the following cases:\\n\\n- Styles should not be defined inline; it should instead be in a standalone variable.\\n - The exception for this is style composition (e.g. `<div css={[baseStyles, moreStyles]} />`),\\n which is a way to combine styles from two variables.\\n- Styles must be wrapped in a `css` function call.\\n- Styles must be defined in the same file as their usage, and not be imported.\\n- Styles should not contain spread operators (e.g. `css({ ...spreadStyles })`).\\n- Styles must all be defined at the top of the file, or at the bottom of the file.\\n\\nThis rule also has an autofixer that enforces and fixes the code (where practical) to meet the above\\nrequirements.\\n\\nAll the above can also work for custom `css` functions, such as `xcss`\\n(https://atlassian.design/components/primitives/xcss/).\\n\\nThis rule has several options - see below.\\n\\n## Examples\\n\\n### Incorrect\\n\\n**Calling a css/xcss function or direct objects inside the JSX attribute.**\\n\\n```js\\nfunction Button({ children }) {\\n return <div css={css({...})}>{children}</div>;\\n ^^^^^^^ css function call used inline (performance issue)\\n}\\n```\\n\\n**Inserting a non css-function based object identifier into a css JSX attribute.**\\n\\n```js\\nconst container = {\\n ^^^^^^^^^ should be a css function call\\n zIndex: 10,\\n};\\n\\nfunction Button({ children }) {\\n return <button css={container}>{children}</button>;\\n}\\n```\\n\\n**Importing styles from another file.**\\n\\n```js\\nimport { container } from './styles';\\n ^^^^^^^^^ styles should be local, not shared\\n\\nfunction Button({ children }) {\\n return <button css={container}>{children}</button>;\\n}\\n```\\n\\n**Nesting styles with objects instead of arrays.**\\n\\n```js\\nconst baseContainerStyles = css({\\n zIndex: 5,\\n});\\n\\nconst containerStyles = css({\\n ...baseContainerStyles,\\n ^^^^^^^^^^^^^^^^^^^^^^ compose styles by providing an array to the css call instead (see example below)\\n zIndex: 7,\\n});\\n\\nfunction Button({ children }) {\\n return <button css={containerStyles}>{children}</button>;\\n}\\n```\\n\\n### Correct\\n\\n**Using the css() function to create a style object and passing it as a variable into the\\n`css={...}` JSX attribute.**\\n\\nWith the following options turned on:\\n\\n- cssFunctions = ['css']\\n- stylesPlacement = 'top'\\n\\n```js\\nconst containerStyles = css({\\n\\tzIndex: 1,\\n});\\n\\nfunction Button({ children }) {\\n\\treturn <button css={containerStyles}>{children}</button>;\\n}\\n```\\n\\n**Technically correct usage of the cssMap function.**\\n\\nWith the following options turned on:\\n\\n- cssFunctions = ['css']\\n- stylesPlacement = 'top'\\n\\n```js\\nimport { cssMap } from '@atlaskit/css';\\nimport { token } from '@atlaskit/tokens';\\n\\nconst borderStyles = cssMap({\\n\\tsolid: { borderStyle: 'solid', borderWidth: token('border.width') },\\n\\tnone: { borderStyle: 'none' },\\n});\\n\\nfunction Button({ children, isSolid }) {\\n\\treturn <button css={borderStyles[isSolid ? 'solid' : 'none']}>{children}</button>;\\n}\\n```\\n\\n**Create composite styles with arrays, not objects.**\\n\\nWith the following options turned on:\\n\\n- cssFunctions = ['css']\\n- stylesPlacement = 'bottom'\\n\\n```js\\nfunction Button({ children }) {\\n\\treturn <button css={[baseContainerStyles, containerStyles]}>{children}</button>;\\n}\\n\\nconst baseContainerStyles = css({\\n\\tzIndex: 5,\\n});\\n\\nconst containerStyles = css({\\n\\tzIndex: 7,\\n});\\n```\\n\\n**Ternaries can be used inline**\\n\\n```js\\nconst baseStyles = css({ color: token('color.text.primary') });\\nconst disabledStyles = css({ color: token('color.text.disabled') });\\n\\n<div css={props.disabled ? disabledStyles : baseStyles}></div>;\\n```\\n\\n## Options\\n\\nThis rule comes with options to support different repository configurations.\\n\\n### cssFunctions\\n\\nAn array of function names the linting rule should target. Defaults to `['css', 'xcss']`. The\\nfunctionality of `cssMap` will be linted regardless of the configuration of `cssFunctions`, as it\\ncan be used with either attribute.\\n\\n### stylesPlacement\\n\\nEither `top` or `bottom`.\\n\\nThe rule prevents inline styles from being created. This option defines what the error message\\nshould say: \\\"(...) styles at the top (...)\\\" or \\\"(...) styles at the bottom (...)\\\". Defaults to\\n`top`.\\n\\n### cssImportSource\\n\\nWhen auto-fixing the contents of the `css` attribute, this rule will wrap CSS styles in a `css(...)`\\nfunction call or ``css`...` `` template expression, and it will add an import declaration for the\\n`css` function. `cssImportSource` is a string that determines what package `css` should be imported\\nfrom.\\n\\nThis is `@compiled/react` by default.\\n\\n### xcssImportSource\\n\\nWhen auto-fixing the contents of the `xcss` attribute, this rule will wrap XCSS styles in a\\n`xcss(...)` function call, and it will add an import declaration for the `xcss` function.\\n`xcssImportSource` is a string that determines what package `xcss` should be imported from.\\n\\nThis is `@atlaskit/primitives` by default.\\n\\n### excludeReactComponents\\n\\nWhether to exclude `css` attributes of React components from being affected by this ESLint rule. We\\nassume that an element is a React component if its name starts with a capital letter, e.g.\\n`<Button />`.\\n\\nThis is `false` by default.\\n\\n### shouldAlwaysCheckXcss\\n\\nOverrides `excludeReactComponents` specifically for the `xcss` prop.\\n\\nThis means that even if `excludeReactComponents` is `true`, you can still lint the `xcss` prop by\\nsetting `shouldAlwaysCheckXcss` to `true`.\\n\\nThis is `false` by default.\\n\\n### autoFix\\n\\nWhen set to `true`, this rule will turn on the autofixer. Set this to `false` if you do not want the\\nautofixers to run.\\n\\nThis is `true` by default.\\n\"}",
17
17
  ruleName: 'consistent-css-prop-usage',
18
18
  description: 'Ensures consistency with css prop usage.'
19
19
  }, {
@@ -49,7 +49,7 @@ export var lintRulesMcpStructuredContent = [{
49
49
  ruleName: 'icon-label',
50
50
  description: 'Icon labels are used to describe what the icon is so the visually impaired can be described what the'
51
51
  }, {
52
- content: '{"ruleName":"index","description":"---","content":"---\\norder: 0\\n---\\n\\nThis plugin contains rules that should be used when working with the\\n[Atlassian Design System](https://atlassian.design).\\n\\n## Rules\\n\\n<!-- START_RULE_TABLE_CODEGEN -->\\n<!-- @codegenCommand afm workspace @atlaskit/eslint-plugin-design-system codegen -->\\n\\n| Rule | Description | Recommended | Fixable | Suggestions |\\n| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------- | ----------- |\\n| <a href=\\"/components/eslint-plugin-design-system/consistent-css-prop-usage/usage\\">consistent-css-prop-usage</a> | Ensures consistency with `css` and `xcss` prop usages | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/enforce-inline-styles-in-select/usage\\">enforce-inline-styles-in-select</a> | Disallow unsupported CSS selectors in styles prop for @atlaskit/select and require inline styles only | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-avatar-tag-avatar-props/usage\\">ensure-avatar-tag-avatar-props</a> | Ensures AvatarTag avatar prop does not include controlled props (size, borderColor, appearance) which are managed internally. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-design-token-usage/usage\\">ensure-design-token-usage</a> | Enforces usage of design tokens rather than hard-coded values. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-design-token-usage-preview/usage\\">ensure-design-token-usage/preview</a> | Enforces usage of pre-release design tokens rather than hard-coded values. | | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-icon-color/usage\\">ensure-icon-color</a> | Enforces that upcoming icon components have a color prop set, to enable a migration of the default value. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-proper-xcss-usage/usage\\">ensure-proper-xcss-usage</a> | Enforces proper xcss usage: migrate from xcss() to cssMap() and use cssMap objects with specific keys. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/expand-motion-shorthand/usage\\">expand-motion-shorthand</a> | Expands `transition` and `animation` CSS shorthand properties into their individual sub-properties, so individual values can be replaced with motion tokens. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/icon-label/usage\\">icon-label</a> | Enforces accessible usage of icon labels when composed with Atlassian Design System components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/lozenge-badge-tag-labelling-system-migration/usage\\">lozenge-badge-tag-labelling-system-migration</a> | Helps migrate Lozenge isBold prop, Badge appearance values, and SimpleTag/RemovableTag components as part of the Labelling System Phase 1 migration. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-banned-imports/usage\\">no-banned-imports</a> | Disallow importing banned modules. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-css-map-scoped/usage\\">no-css-map-scoped</a> | Disallows usage of the experimental `cssMapScoped` API from `@compiled/react`. This API is internal and is not part of the public Compiled CSS-in-JS interface. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-css-tagged-template-expression/usage\\">no-css-tagged-template-expression</a> | Disallows any `css` tagged template expressions that originate from Emotion, Styled Components or Compiled | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-dark-theme-vr-tests/usage\\">no-dark-theme-vr-tests</a> | Disallow using dark colorScheme in VR tests. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-deprecated-apis/usage\\">no-deprecated-apis</a> | Disallow using deprecated APIs. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-deprecated-design-token-usage/usage\\">no-deprecated-design-token-usage</a> | Disallow using deprecated design tokens. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-deprecated-imports/usage\\">no-deprecated-imports</a> | Disallow importing deprecated modules. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-direct-use-of-web-platform-drag-and-drop/usage\\">no-direct-use-of-web-platform-drag-and-drop</a> | Disallow using direct use of native drag and drop (please use Pragmatic drag and drop) | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-emotion-primitives/usage\\">no-emotion-primitives</a> | Ensures usage of Compiled Primitives import instead of Emotion entrypoint. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-empty-icon-button-label/usage\\">no-empty-icon-button-label</a> | Ensures icon-only Atlassian Design System buttons do not have an empty accessible name. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-empty-styled-expression/usage\\">no-empty-styled-expression</a> | Forbids any styled expression to be used when passing empty arguments to styled.div() (or other JSX elements). | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-exported-css/usage\\">no-exported-css</a> | Forbid exporting `css` function calls. Exporting `css` function calls can result in unexpected behaviour at runtime, and is not statically analysable. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-exported-keyframes/usage\\">no-exported-keyframes</a> | Forbid exporting `keyframes` function calls. Exporting `css` function calls can result in unexpected behaviour at runtime, and is not statically analysable. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-anchor/usage\\">no-html-anchor</a> | Discourage direct usage of HTML anchor elements in favor of Atlassian Design System link components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-button/usage\\">no-html-button</a> | Discourage direct usage of HTML button elements in favor of Atlassian Design System button components. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-checkbox/usage\\">no-html-checkbox</a> | Discourage direct usage of HTML checkbox elements in favor of the Atlassian Design System checkbox component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-code/usage\\">no-html-code</a> | Discourage direct usage of HTML code elements in favor of the Atlassian Design System code component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-heading/usage\\">no-html-heading</a> | Discourage direct usage of HTML heading elements in favor of Atlassian Design System heading components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-image/usage\\">no-html-image</a> | Discourage direct usage of HTML image elements in favor of the Atlassian Design System image component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-radio/usage\\">no-html-radio</a> | Discourage direct usage of HTML radio elements in favor of the Atlassian Design System radio component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-range/usage\\">no-html-range</a> | Discourage direct usage of HTML range elements in favor of the Atlassian Design System range component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-select/usage\\">no-html-select</a> | Discourage direct usage of HTML select elements in favor of the Atlassian Design System select component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-text-input/usage\\">no-html-text-input</a> | Discourage direct usage of HTML text input elements in favor of the Atlassian Design System textfield component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-textarea/usage\\">no-html-textarea</a> | Discourage direct usage of HTML textarea elements in favor of the Atlassian Design System textarea component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-icon-spacing-prop/usage\\">no-icon-spacing-prop</a> | Disallows usage of the deprecated spacing prop on new icons. Use Flex with cssMap for spacing instead. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-invalid-css-map/usage\\">no-invalid-css-map</a> | Checks the validity of a CSS map created through cssMap. This is intended to be used alongside TypeScript\'s type-checking. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-keyframes-tagged-template-expression/usage\\">no-keyframes-tagged-template-expression</a> | Disallows any `keyframe` tagged template expressions that originate from Emotion, Styled Components or Compiled | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-margin/usage\\">no-margin</a> | Disallow using the margin CSS property. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-modal-label/usage\\">no-modal-label</a> | Disallows usage of the `label` prop on Atlassian Design System modal dialog and modal entry-point triggers. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-nested-styles/usage\\">no-nested-styles</a> | Disallows use of nested styles in `css` functions. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-physical-properties/usage\\">no-physical-properties</a> | Disallow physical properties and values in `css` and `cssMap` function calls. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-placeholder/usage\\">no-placeholder</a> | Placeholders should not be used. If information should be given to the user about the proper type or formatting of a value, this should be included using a helper message that is associated to the input instead. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-readonly-or-disabled-inputs/usage\\">no-readonly-or-disabled-inputs</a> | Inputs should almost always be interactive. Disabled and read-only inputs can usually be replaced by a more user-friendly design pattern. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-separator-with-list-elements/usage\\">no-separator-with-list-elements</a> | Warn when the `separator` prop is used with `as=\\"li\\"`, `as=\\"ol\\"`, or `as=\\"dl\\"` in the Inline component. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-styled-tagged-template-expression/usage\\">no-styled-tagged-template-expression</a> | Disallows any `styled` tagged template expressions that originate from Emotion, Styled Components or Compiled | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-to-match-snapshot/usage\\">no-to-match-snapshot</a> | Disallow using toMatchSnapshot() and toMatchInlineSnapshot() in unit tests. Snapshot assertions should be replaced with explicit assertions. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unsafe-design-token-usage/usage\\">no-unsafe-design-token-usage</a> | Enforces design token usage is statically and locally analyzable. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unsafe-inline-snapshot/usage\\">no-unsafe-inline-snapshot</a> | Enforce guardrails on toMatchInlineSnapshot usage: snapshots must not exceed 100 lines and must not contain internal implementation details like className or style attributes. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unsafe-style-overrides/usage\\">no-unsafe-style-overrides</a> | Discourage usage of unsafe style overrides used against the Atlassian Design System. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unsupported-drag-and-drop-libraries/usage\\">no-unsupported-drag-and-drop-libraries</a> | Disallow importing unsupported drag and drop modules. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unused-css-map/usage\\">no-unused-css-map</a> | Detects unused styles in cssMap objects to help keep code clean. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/prefer-primitives/usage\\">prefer-primitives</a> | Increase awareness of primitive components via code hints. Strictly used for education purposes and discoverability. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-button-group-label/usage\\">use-button-group-label</a> | Ensures button groups are described to assistive technology by a direct label or by another element. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-character-counter-field/usage\\">use-character-counter-field</a> | Suggests using CharacterCounterField or CharacterCounter when Textfield or Textarea components have maxLength or minLength props. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-correct-field/usage\\">use-correct-field</a> | Ensure makers use appropriate field component for their respective form elements. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-cx-function-in-xcss/usage\\">use-cx-function-in-xcss</a> | Enforces cx function use to combine styles in xcss. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-datetime-picker-calendar-button/usage\\">use-datetime-picker-calendar-button</a> | Encourages makers to use calendar button in Atlassian Design System\'s date picker and datetime picker components. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-drawer-label/usage\\">use-drawer-label</a> | Encourages to provide accessible name for Atlassian Design System Drawer component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-field-message-wrapper/usage\\">use-field-message-wrapper</a> | Encourage use of message wrapper component when using form message components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-heading/usage\\">use-heading</a> | Encourage the usage of heading components. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-heading-level-in-section-message/usage\\">use-heading-level-in-section-message</a> | The `SectionMessage` component in `@atlaskit/section-message` needs to be the correct level within the document flow. This is not something that can be automated and requires contextual knowledge of what is present in the experience. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-heading-level-in-spotlight-card/usage\\">use-heading-level-in-spotlight-card</a> | Inform developers of eventual requirement of `headingLevel` prop in `SpotlightCard` component. The heading level should be the appropriate level according to the surrounding context. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-href-in-link-item/usage\\">use-href-in-link-item</a> | Inform developers of eventual requirement of `href` prop in `LinkItem` component. Elements with a `link` role require an `href` attribute for users to properly navigate, particularly those using assistive technologies. If no valid `href` is required for your use case, consider using a `ButtonItem` instead. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-latest-xcss-syntax/usage\\">use-latest-xcss-syntax</a> | Enforces usage of space design tokens rather than hard-coded values in xcss. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-latest-xcss-syntax-typography/usage\\">use-latest-xcss-syntax-typography</a> | Prohibits use of unsafe styling properties in xcss. Please use Text/Heading primitives instead. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-menu-section-title/usage\\">use-menu-section-title</a> | Encourages makers to provide accessible title for Atlassian Design System Menu Section component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-modal-dialog-close-button/usage\\">use-modal-dialog-close-button</a> | Encourages makers to use close button in Atlassian Design System\'s modal dialog component. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-modal-title/usage\\">use-modal-title</a> | Encourages makers to include `ModalTitle` within `ModalHeader` when using Atlassian Design System modal dialog. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-onboarding-spotlight-label/usage\\">use-onboarding-spotlight-label</a> | Ensures onboarding spotlight dialogs are described to assistive technology by a direct label or by another element. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-popup-label/usage\\">use-popup-label</a> | Encourages to provide accessible name for Atlassian Design System Popup component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-pressable-motion/usage\\">use-pressable-motion</a> | Suggests semantic motion tokens when Pressable or native buttons change interactive colours through local static styles. | | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-primitives-text/usage\\">use-primitives-text</a> | Encourage the usage of text components. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-should-render-to-parent/usage\\">use-should-render-to-parent</a> | Encourages makers to use the `shouldRenderToParent` where possible in Atlassian Design System `Popup` and `DropdownMenu` components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-simple-field/usage\\">use-simple-field</a> | Encourage use of simple field for better developer experience and accessibility. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-simple-form/usage\\">use-simple-form</a> | Encourage use of simple form for better developer experience and accessibility. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-spotlight-package/usage\\">use-spotlight-package</a> | Discourage the use of @atlaskit/onboarding in favor of @atlaskit/spotlight. | | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tag-group-label/usage\\">use-tag-group-label</a> | Ensures tag groups are described to assistive technology by a direct label or by another element. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-textfield-autocomplete/usage\\">use-textfield-autocomplete</a> | Enforce that Textfield components with type=\\"email\\", \\"tel\\", or \\"url\\" have an appropriate autocomplete value for WCAG 2.2 SC 1.3.5 compliance (Identify Input Purpose). | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tokens-motion/usage\\">use-tokens-motion</a> | Enforces usage of motion design tokens rather than hard-coded duration and easing values. | | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tokens-shape/usage\\">use-tokens-shape</a> | Enforces usage of shape design tokens rather than hard-coded values. | | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tokens-space/usage\\">use-tokens-space</a> | Enforces usage of space design tokens rather than hard-coded values. | | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tokens-typography/usage\\">use-tokens-typography</a> | Enforces usage of design tokens for typography properties rather than hard-coded values. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-visually-hidden/usage\\">use-visually-hidden</a> | Enforce usage of the visually hidden component. | Yes | Yes | |\\n\\n<!-- END_RULE_TABLE_CODEGEN -->\\n\\n\\n## Props\\n\\nUse the recommended config to get reasonable defaults recommended by the Atlassian Design System:\\n\\n```diff\\nmodule.exports = {\\n extends: [\\n+ \'plugin:@atlaskit/design-system/recommended\',\\n ],\\n};\\n```\\n\\nWe don\'t recommended maintaining your own configuration. If you do not use our config you will need\\nto specify individual rules and configuration. Add the plugin to your `eslint.config.cjs` file.\\n\\n```diff\\nmodule.exports = {\\n plugins: [\\n+ \'@atlaskit/design-system\',\\n ],\\n};\\n```\\n\\nEnable the rules that you would like to use.\\n\\n```diff\\nmodule.exports = {\\n rules: [\\n+ \'@atlaskit/design-system/no-deprecated-apis\': \'error\',\\n ],\\n};\\n```\\n"}',
52
+ content: '{"ruleName":"index","description":"---","content":"---\\norder: 0\\n---\\n\\nThis plugin contains rules that should be used when working with the\\n[Atlassian Design System](https://atlassian.design).\\n\\n## Rules\\n\\n{/* START_RULE_TABLE_CODEGEN */}\\n\\n{/* @codegenCommand afm workspace @atlaskit/eslint-plugin-design-system codegen */}\\n\\n| Rule | Description | Recommended | Fixable | Suggestions |\\n| ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------- | ----------- |\\n| <a href=\\"/components/eslint-plugin-design-system/consistent-css-prop-usage/usage\\">consistent-css-prop-usage</a> | Ensures consistency with `css` and `xcss` prop usages | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/enforce-inline-styles-in-select/usage\\">enforce-inline-styles-in-select</a> | Disallow unsupported CSS selectors in styles prop for @atlaskit/select and require inline styles only | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-avatar-tag-avatar-props/usage\\">ensure-avatar-tag-avatar-props</a> | Ensures AvatarTag avatar prop does not include controlled props (size, borderColor, appearance) which are managed internally. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-design-token-usage/usage\\">ensure-design-token-usage</a> | Enforces usage of design tokens rather than hard-coded values. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-design-token-usage-preview/usage\\">ensure-design-token-usage/preview</a> | Enforces usage of pre-release design tokens rather than hard-coded values. | | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-icon-color/usage\\">ensure-icon-color</a> | Enforces that upcoming icon components have a color prop set, to enable a migration of the default value. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/ensure-proper-xcss-usage/usage\\">ensure-proper-xcss-usage</a> | Enforces proper xcss usage: migrate from xcss() to cssMap() and use cssMap objects with specific keys. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/expand-motion-shorthand/usage\\">expand-motion-shorthand</a> | Expands `transition` and `animation` CSS shorthand properties into their individual sub-properties, so individual values can be replaced with motion tokens. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/icon-label/usage\\">icon-label</a> | Enforces accessible usage of icon labels when composed with Atlassian Design System components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/lozenge-badge-tag-labelling-system-migration/usage\\">lozenge-badge-tag-labelling-system-migration</a> | Migrates legacy Lozenge and Badge appearance values and guides SimpleTag/RemovableTag migrations to the supported Tag APIs. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-banned-imports/usage\\">no-banned-imports</a> | Disallow importing banned modules. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-css-map-scoped/usage\\">no-css-map-scoped</a> | Disallows usage of the experimental `cssMapScoped` API from `@compiled/react`. This API is internal and is not part of the public Compiled CSS-in-JS interface. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-css-tagged-template-expression/usage\\">no-css-tagged-template-expression</a> | Disallows any `css` tagged template expressions that originate from Emotion, Styled Components or Compiled | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-dark-theme-vr-tests/usage\\">no-dark-theme-vr-tests</a> | Disallow using dark colorScheme in VR tests. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-deprecated-apis/usage\\">no-deprecated-apis</a> | Disallow using deprecated APIs. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-deprecated-design-token-usage/usage\\">no-deprecated-design-token-usage</a> | Disallow using deprecated design tokens. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-deprecated-imports/usage\\">no-deprecated-imports</a> | Disallow importing deprecated modules. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-direct-use-of-web-platform-drag-and-drop/usage\\">no-direct-use-of-web-platform-drag-and-drop</a> | Disallow using direct use of native drag and drop (please use Pragmatic drag and drop) | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-emotion-primitives/usage\\">no-emotion-primitives</a> | Ensures usage of Compiled Primitives import instead of Emotion entrypoint. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-empty-icon-button-label/usage\\">no-empty-icon-button-label</a> | Ensures icon-only Atlassian Design System buttons do not have an empty accessible name. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-empty-styled-expression/usage\\">no-empty-styled-expression</a> | Forbids any styled expression to be used when passing empty arguments to styled.div() (or other JSX elements). | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-exported-css/usage\\">no-exported-css</a> | Forbid exporting `css` function calls. Exporting `css` function calls can result in unexpected behaviour at runtime, and is not statically analysable. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-exported-keyframes/usage\\">no-exported-keyframes</a> | Forbid exporting `keyframes` function calls. Exporting `css` function calls can result in unexpected behaviour at runtime, and is not statically analysable. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-global-z-index/usage\\">no-global-z-index</a> | Disallow `z-index` values above 10. Global layer ordering is handled by the browser top layer. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-anchor/usage\\">no-html-anchor</a> | Discourage direct usage of HTML anchor elements in favor of Atlassian Design System link components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-button/usage\\">no-html-button</a> | Discourage direct usage of HTML button elements in favor of Atlassian Design System button components. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-checkbox/usage\\">no-html-checkbox</a> | Discourage direct usage of HTML checkbox elements in favor of the Atlassian Design System checkbox component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-code/usage\\">no-html-code</a> | Discourage direct usage of HTML code elements in favor of the Atlassian Design System code component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-heading/usage\\">no-html-heading</a> | Discourage direct usage of HTML heading elements in favor of Atlassian Design System heading components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-image/usage\\">no-html-image</a> | Discourage direct usage of HTML image elements in favor of the Atlassian Design System image component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-radio/usage\\">no-html-radio</a> | Discourage direct usage of HTML radio elements in favor of the Atlassian Design System radio component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-range/usage\\">no-html-range</a> | Discourage direct usage of HTML range elements in favor of the Atlassian Design System range component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-select/usage\\">no-html-select</a> | Discourage direct usage of HTML select elements in favor of the Atlassian Design System select component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-text-input/usage\\">no-html-text-input</a> | Discourage direct usage of HTML text input elements in favor of the Atlassian Design System textfield component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-html-textarea/usage\\">no-html-textarea</a> | Discourage direct usage of HTML textarea elements in favor of the Atlassian Design System textarea component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-icon-spacing-prop/usage\\">no-icon-spacing-prop</a> | Disallows usage of the deprecated spacing prop on new icons. Use Flex with cssMap for spacing instead. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/no-invalid-css-map/usage\\">no-invalid-css-map</a> | Checks the validity of a CSS map created through cssMap. This is intended to be used alongside TypeScript\'s type-checking. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-keyframes-tagged-template-expression/usage\\">no-keyframes-tagged-template-expression</a> | Disallows any `keyframe` tagged template expressions that originate from Emotion, Styled Components or Compiled | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-margin/usage\\">no-margin</a> | Disallow using the margin CSS property. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-modal-label/usage\\">no-modal-label</a> | Disallows usage of the `label` prop on Atlassian Design System modal dialog and modal entry-point triggers. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-native-popover-or-dialog/usage\\">no-native-popover-or-dialog</a> | Disallow native `popover` and `<dialog>` elements. Use a Design System component, or `@atlaskit/top-layer` if no Design System component fits. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-nested-styles/usage\\">no-nested-styles</a> | Disallows use of nested styles in `css` functions. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-physical-properties/usage\\">no-physical-properties</a> | Disallow physical properties and values in `css` and `cssMap` function calls. | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-placeholder/usage\\">no-placeholder</a> | Placeholders should not be used. If information should be given to the user about the proper type or formatting of a value, this should be included using a helper message that is associated to the input instead. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-readonly-or-disabled-inputs/usage\\">no-readonly-or-disabled-inputs</a> | Inputs should almost always be interactive. Disabled and read-only inputs can usually be replaced by a more user-friendly design pattern. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-separator-with-list-elements/usage\\">no-separator-with-list-elements</a> | Warn when the `separator` prop is used with `as=\\"li\\"`, `as=\\"ol\\"`, or `as=\\"dl\\"` in the Inline component. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-styled-tagged-template-expression/usage\\">no-styled-tagged-template-expression</a> | Disallows any `styled` tagged template expressions that originate from Emotion, Styled Components or Compiled | | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-third-party-focus-traps/usage\\">no-third-party-focus-traps</a> | Disallow third-party focus trap libraries, such as `react-focus-lock` and `focus-trap`. Design System layering components manage focus. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-third-party-layering/usage\\">no-third-party-layering</a> | Disallow third-party layering libraries, such as Popper.js and Floating UI. Use a Design System layering component or `@atlaskit/top-layer`. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-to-match-snapshot/usage\\">no-to-match-snapshot</a> | Disallow using toMatchSnapshot() and toMatchInlineSnapshot() in unit tests. Snapshot assertions should be replaced with explicit assertions. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unsafe-design-token-usage/usage\\">no-unsafe-design-token-usage</a> | Enforces design token usage is statically and locally analyzable. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unsafe-inline-snapshot/usage\\">no-unsafe-inline-snapshot</a> | Enforce guardrails on toMatchInlineSnapshot usage: snapshots must not exceed 100 lines and must not contain internal implementation details like className or style attributes. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unsafe-style-overrides/usage\\">no-unsafe-style-overrides</a> | Discourage usage of unsafe style overrides used against the Atlassian Design System. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unsupported-drag-and-drop-libraries/usage\\">no-unsupported-drag-and-drop-libraries</a> | Disallow importing unsupported drag and drop modules. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/no-unused-css-map/usage\\">no-unused-css-map</a> | Detects unused styles in cssMap objects to help keep code clean. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/prefer-primitives/usage\\">prefer-primitives</a> | Increase awareness of primitive components via code hints. Strictly used for education purposes and discoverability. | | | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-button-group-label/usage\\">use-button-group-label</a> | Ensures button groups are described to assistive technology by a direct label or by another element. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-character-counter-field/usage\\">use-character-counter-field</a> | Suggests using CharacterCounterField or CharacterCounter when Textfield or Textarea components have maxLength or minLength props. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-correct-field/usage\\">use-correct-field</a> | Ensure makers use appropriate field component for their respective form elements. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-cx-function-in-xcss/usage\\">use-cx-function-in-xcss</a> | Enforces cx function use to combine styles in xcss. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-datetime-picker-calendar-button/usage\\">use-datetime-picker-calendar-button</a> | Encourages makers to use calendar button in Atlassian Design System\'s date picker and datetime picker components. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-drawer-label/usage\\">use-drawer-label</a> | Encourages to provide accessible name for Atlassian Design System Drawer component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-field-message-wrapper/usage\\">use-field-message-wrapper</a> | Encourage use of message wrapper component when using form message components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-heading/usage\\">use-heading</a> | Encourage the usage of heading components. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-heading-level-in-section-message/usage\\">use-heading-level-in-section-message</a> | The `SectionMessage` component in `@atlaskit/section-message` needs to be the correct level within the document flow. This is not something that can be automated and requires contextual knowledge of what is present in the experience. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-heading-level-in-spotlight-card/usage\\">use-heading-level-in-spotlight-card</a> | Inform developers of eventual requirement of `headingLevel` prop in `SpotlightCard` component. The heading level should be the appropriate level according to the surrounding context. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-href-in-link-item/usage\\">use-href-in-link-item</a> | Inform developers of eventual requirement of `href` prop in `LinkItem` component. Elements with a `link` role require an `href` attribute for users to properly navigate, particularly those using assistive technologies. If no valid `href` is required for your use case, consider using a `ButtonItem` instead. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-latest-xcss-syntax/usage\\">use-latest-xcss-syntax</a> | Enforces usage of space design tokens rather than hard-coded values in xcss. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-latest-xcss-syntax-typography/usage\\">use-latest-xcss-syntax-typography</a> | Prohibits use of unsafe styling properties in xcss. Please use Text/Heading primitives instead. | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-menu-section-title/usage\\">use-menu-section-title</a> | Encourages makers to provide accessible title for Atlassian Design System Menu Section component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-modal-dialog-close-button/usage\\">use-modal-dialog-close-button</a> | Encourages makers to use close button in Atlassian Design System\'s modal dialog component. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-modal-title/usage\\">use-modal-title</a> | Encourages makers to include `ModalTitle` within `ModalHeader` when using Atlassian Design System modal dialog. | Yes | | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-onboarding-spotlight-label/usage\\">use-onboarding-spotlight-label</a> | Ensures onboarding spotlight dialogs are described to assistive technology by a direct label or by another element. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-popup-label/usage\\">use-popup-label</a> | Encourages to provide accessible name for Atlassian Design System Popup component. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-pressable-motion/usage\\">use-pressable-motion</a> | Suggests semantic motion tokens when Pressable or native buttons change interactive colours through local static styles. | | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-primitives-text/usage\\">use-primitives-text</a> | Encourage the usage of text components. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-should-render-to-parent/usage\\">use-should-render-to-parent</a> | Encourages makers to use the `shouldRenderToParent` where possible in Atlassian Design System `Popup` and `DropdownMenu` components. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-simple-field/usage\\">use-simple-field</a> | Encourage use of simple field for better developer experience and accessibility. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-simple-form/usage\\">use-simple-form</a> | Encourage use of simple form for better developer experience and accessibility. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-spotlight-package/usage\\">use-spotlight-package</a> | Discourage the use of @atlaskit/onboarding in favor of @atlaskit/spotlight. | | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tag-group-label/usage\\">use-tag-group-label</a> | Ensures tag groups are described to assistive technology by a direct label or by another element. | Yes | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-textfield-autocomplete/usage\\">use-textfield-autocomplete</a> | Enforce that Textfield components with type=\\"email\\", \\"tel\\", or \\"url\\" have an appropriate autocomplete value for WCAG 2.2 SC 1.3.5 compliance (Identify Input Purpose). | Yes | Yes | |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tokens-motion/usage\\">use-tokens-motion</a> | Enforces usage of motion design tokens rather than hard-coded duration and easing values. | | | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tokens-shape/usage\\">use-tokens-shape</a> | Enforces usage of shape design tokens rather than hard-coded values. | | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tokens-space/usage\\">use-tokens-space</a> | Enforces usage of space design tokens rather than hard-coded values. | | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-tokens-typography/usage\\">use-tokens-typography</a> | Enforces usage of design tokens for typography properties rather than hard-coded values. | Yes | Yes | Yes |\\n| <a href=\\"/components/eslint-plugin-design-system/use-visually-hidden/usage\\">use-visually-hidden</a> | Enforce usage of the visually hidden component. | Yes | Yes | |\\n\\n{/* END_RULE_TABLE_CODEGEN */}\\n\\n\\n## Props\\n\\nUse the recommended config to get reasonable defaults recommended by the Atlassian Design System:\\n\\n```diff\\nmodule.exports = {\\n extends: [\\n+ \'plugin:@atlaskit/design-system/recommended\',\\n ],\\n};\\n```\\n\\nWe don\'t recommended maintaining your own configuration. If you do not use our config you will need\\nto specify individual rules and configuration. Add the plugin to your `eslint.config.cjs` file.\\n\\n```diff\\nmodule.exports = {\\n plugins: [\\n+ \'@atlaskit/design-system\',\\n ],\\n};\\n```\\n\\nEnable the rules that you would like to use.\\n\\n```diff\\nmodule.exports = {\\n rules: [\\n+ \'@atlaskit/design-system/no-deprecated-apis\': \'error\',\\n ],\\n};\\n```\\n"}',
53
53
  ruleName: 'index',
54
54
  description: '---'
55
55
  }, {
@@ -61,9 +61,9 @@ export var lintRulesMcpStructuredContent = [{
61
61
  ruleName: 'lozenge-badge-appearance-migration',
62
62
  description: 'This rule helps migrate deprecated `<Lozenge>` usages to the new API or `<Tag>` component, and'
63
63
  }, {
64
- content: '{"ruleName":"lozenge-badge-tag-labelling-system-migration","description":"This rule helps migrate deprecated `<Lozenge>` props and appearance values to the new API, migrate","content":"# lozenge-badge-tag-labelling-system-migration\\n\\nThis rule helps migrate deprecated `<Lozenge>` props and appearance values to the new API, migrate\\n`<Badge>` component appearance prop to new semantic values, and migrate `<SimpleTag>` and\\n`<RemovableTag>` components to the new `<Tag>` or `<AvatarTag>` components as part of the Labelling\\nSystem Phase 1 migration.\\n\\n## Examples\\n\\n### Incorrect\\n\\n```tsx\\n// Lozenge: isBold is deprecated — remove it regardless of value\\n<Lozenge isBold={false} appearance=\\"success\\" />\\n<Lozenge isBold={true} appearance=\\"success\\" />\\n<Lozenge isBold appearance=\\"success\\" />\\n<Lozenge isBold={someVariable} />\\n\\n// Lozenge: Old appearance values that need migration to new semantic values\\n<Lozenge appearance=\\"default\\">Default</Lozenge>\\n<Lozenge appearance=\\"inprogress\\">In Progress</Lozenge>\\n<Lozenge appearance=\\"moved\\">Moved</Lozenge>\\n<Lozenge appearance=\\"removed\\">Removed</Lozenge>\\n<Lozenge appearance=\\"new\\">New</Lozenge>\\n\\n// Badge: Old appearance values that need migration\\n<Badge appearance=\\"added\\">{5}</Badge>\\n<Badge appearance=\\"removed\\">{10}</Badge>\\n<Badge appearance=\\"default\\">{3}</Badge>\\n<Badge appearance=\\"primary\\">{7}</Badge>\\n<Badge appearance=\\"primaryInverted\\">{2}</Badge>\\n<Badge appearance=\\"important\\">{99}</Badge>\\n\\n// Badge: Dynamic appearance expressions require manual review\\n<Badge appearance={getStatus()}>{count}</Badge>\\n<Badge appearance={condition ? \'added\' : \'removed\'}>{num}</Badge>\\n\\n// SimpleTag/RemovableTag: Old tag components that need migration\\n<SimpleTag>Hello</SimpleTag>\\n<SimpleTag color=\\"blueLight\\">Hello</SimpleTag>\\n<SimpleTag elemBefore={<Avatar src=\\"x\\" />}>Hello</SimpleTag>\\n<RemovableTag color=\\"redLight\\">Hello</RemovableTag>\\n<RemovableTag elemBefore={<Avatar />}>Hello</RemovableTag>\\n\\n// SimpleTag/RemovableTag from subpaths: Also need migration\\nimport SimpleTag from \'@atlaskit/tag/simple-tag\';\\n<SimpleTag color=\\"blueLight\\">Hello</SimpleTag>\\n\\nimport RemovableTag from \'@atlaskit/tag/removable-tag\';\\n<RemovableTag color=\\"redLight\\">Hello</RemovableTag>\\n```\\n\\n### Correct\\n\\n```tsx\\n// Lozenge: Use new semantic appearance values (no isBold prop)\\n<Lozenge appearance=\\"success\\">Success</Lozenge>\\n<Lozenge appearance=\\"neutral\\">Default</Lozenge>\\n<Lozenge appearance=\\"information\\">In Progress</Lozenge>\\n<Lozenge appearance=\\"warning\\">Moved</Lozenge>\\n<Lozenge appearance=\\"danger\\">Removed</Lozenge>\\n<Lozenge appearance=\\"discovery\\">New</Lozenge>\\n\\n// Badge: New semantic appearance values\\n<Badge appearance=\\"success\\">{5}</Badge>\\n<Badge appearance=\\"danger\\">{10}</Badge>\\n<Badge appearance=\\"neutral\\">{3}</Badge>\\n<Badge appearance=\\"information\\">{7}</Badge>\\n<Badge appearance=\\"inverse\\">{2}</Badge>\\n<Badge appearance=\\"danger\\">{99}</Badge>\\n\\n// SimpleTag/RemovableTag: Migrate to Tag component\\nimport Tag from \'@atlaskit/tag\';\\n<Tag>Hello</Tag>\\n<Tag color=\\"blue\\" isRemovable={false}>Hello</Tag>\\n\\n// SimpleTag/RemovableTag: Migrate to AvatarTag with render props\\nimport { AvatarTag } from \'@atlaskit/tag\';\\nimport Avatar from \'@atlaskit/avatar\';\\n<AvatarTag avatar={(props) => <Avatar {...props} src=\\"x\\" />}>Hello</AvatarTag>\\n\\n// SimpleTag/RemovableTag from subpaths: Also migrate to main module\\nimport Tag from \'@atlaskit/tag\';\\nimport Avatar from \'@atlaskit/avatar\';\\n<Tag color=\\"blue\\" isRemovable={false}>Hello</Tag>\\n<AvatarTag avatar={(props) => <Avatar {...props} />}>Hello</AvatarTag>\\n```\\n\\n## Rule Details\\n\\nThis rule enforces multiple migration patterns:\\n\\n1. **Remove deprecated `isBold` prop from `<Lozenge>`**: The `isBold` prop is deprecated in the new\\n Lozenge API. The rule warns and auto-removes it regardless of value (true, false, or dynamic).\\n Both bold and subtle variants are now expressed via the `appearance` prop alone.\\n\\n2. **Migrate Lozenge appearance values to new semantic values**: Detects old appearance values\\n (`default`, `inprogress`, `moved`, `removed`, `new`) and auto-fixes them to new semantic values\\n (`neutral`, `information`, `warning`, `danger`, `discovery`). The value `success` is unchanged.\\n\\n3. **Migrate Badge appearance values**: Detects Badge components using old appearance values and\\n migrates them to new semantic values.\\n\\n4. **Warn on dynamic Badge appearance expressions**: Detects dynamic `appearance` props on Badge\\n components that cannot be safely auto-fixed and require manual review.\\n\\n5. **Migrate SimpleTag/RemovableTag to Tag**: Detects SimpleTag and RemovableTag components (from\\n named imports or subpaths) and migrates them to the new Tag component, updating imports and\\n handling color prop mapping.\\n\\n6. **Migrate SimpleTag/RemovableTag with Avatar to AvatarTag**: Detects SimpleTag and RemovableTag\\n components that use an Avatar component in the `elemBefore` prop and migrates them to the new\\n `AvatarTag` component with render props pattern: `avatar={(props) => <Avatar {...props} />}`.\\n Removes `appearance` and `color` props from AvatarTag migrations.\\n\\n7. **Handle subpath imports**: Detects default imports from `@atlaskit/tag/simple-tag` and\\n `@atlaskit/tag/removable-tag` and migrates them to the main `@atlaskit/tag` module with the\\n appropriate component (Tag or AvatarTag).\\n\\n8. **Handle default Tag imports**: Detects default imports from `@atlaskit/tag` (old RemovableTag)\\n and checks if they need migration. If nothing needs migration, treats them as the new Tag\\n component.\\n\\n## Flowcharts\\n\\n### Tag Migration Flowchart (SimpleTag/RemovableTag/Tag)\\n\\n```\\n┌─────────────────────────────────────────────────────────────┐\\n│ Tag Migration (SimpleTag/RemovableTag/Tag) │\\n└─────────────────────────────────────────────────────────────┘\\n │\\n ▼\\n ┌───────────────┐\\n │ Is default │\\n │ Tag import │\\n │ from │\\n │ @atlaskit/ │\\n │ tag? │\\n └───────┬───────┘\\n │\\n ┌───────────┴───┐\\n │ │\\n YES │ │ NO\\n │ │\\n ▼ │\\n ┌───────────────┐ │\\n │ Check if │ │\\n │ already new │ │\\n │ Tag (nothing │ │\\n │ to migrate) │ │\\n └───────┬───────┘ │\\n │ │\\n ┌───────┴───────┐ │\\n │ │ │\\n YES │ │ NO │\\n │ │ │\\n ▼ ▼ ▼\\n┌───────────────┐ ┌───────────────┐\\n│ SKIP │ │ Check │\\n│ (Already │ │ elemBefore │\\n│ migrated) │ │ for Avatar │\\n└───────────────┘ └───────┬───────┘\\n │\\n ┌───────┴───────┐\\n │ │\\n YES │ │ NO\\n │ │\\n ▼ ▼\\n ┌───────────────┐ ┌───────────────┐\\n │ Migrate to │ │ Migrate to │\\n │ AvatarTag │ │ Tag │\\n │ - Convert │ │ - Map colors │\\n │ elemBefore │ │ - Add │\\n │ to avatar │ │ isRemovable │\\n │ render prop │ │ ={false} │\\n │ - Remove │ │ (if │\\n │ appearance/ │ │ SimpleTag) │\\n │ color │ │ - Update │\\n │ │ │ imports │\\n └───────────────┘ └───────────────┘\\n```\\n\\n### Badge Migration Flowchart\\n\\n```\\n┌─────────────────────────────────────────────────────────────┐\\n│ Badge Migration │\\n└─────────────────────────────────────────────────────────────┘\\n │\\n ▼\\n ┌───────────────┐\\n │ Has │\\n │ appearance │\\n │ prop? │\\n └───────┬───────┘\\n │\\n ┌───────────┴───────────┐\\n │ │\\n YES │ │ NO\\n │ │\\n ▼ ▼\\n ┌───────────────┐ ┌───────────────┐\\n │ Is dynamic? │ │ SKIP │\\n │ (variable/ │ │ (no │\\n │ expression) │ │ migration │\\n └───────┬───────┘ │ needed) │\\n │ └───────────────┘\\n ┌───────┴───────┐\\n │ │\\n YES │ │ NO\\n │ │\\n ▼ ▼\\n┌───────────────┐ ┌───────────────┐\\n│ Report │ │ Map & fix │\\n│ warning │ │ appearance │\\n│ (manual │ │ value: │\\n│ review) │ │ - added → │\\n│ │ │ success │\\n│ │ │ - removed → │\\n│ │ │ danger │\\n│ │ │ - default → │\\n│ │ │ neutral │\\n│ │ │ - primary → │\\n│ │ │ information │\\n│ │ │ - primaryIn │\\n│ │ │ verted → │\\n│ │ │ inverse │\\n│ │ │ - important → │\\n│ │ │ danger │\\n└───────────────┘ └───────────────┘\\n```\\n\\n### Lozenge Migration Flowchart\\n\\n```\\n┌─────────────────────────────────────────────────────────────┐\\n│ Lozenge Migration │\\n└─────────────────────────────────────────────────────────────┘\\n │\\n ▼\\n ┌───────────────┐\\n │ Check isBold │\\n │ prop │\\n └───────┬───────┘\\n │\\n ┌───────────────────┼───────────────────┐\\n │ │ │\\n ▼ ▼ ▼\\n┌───────────────┐ ┌────────────────┐ ┌───────────────┐\\n│ isBold={false}│ │ No isBold prop │ │ isBold={true} │\\n│ │ │ (implicit │ │ OR │\\n│ │ │ false) │ │ isBold │\\n│ │ │ │ │ (implicit) │\\n└───────┬───────┘ └───────┬────────┘ └───────┬───────┘\\n │ │ │\\n │ │ │\\n ▼ ▼ ▼\\n┌────────────────────────────┐ ┌───────────────┐\\n│ Check if │ │ Stay as │\\n│ appearance is │ │ Lozenge │\\n│ dynamic | │ - Update │\\n└───────┬────────────────────┘ │ appearance │\\n │ │ if needed │\\n┌───────┴─────────────────┐ └───────────────┘\\n│ │\\n│ DYNAMIC │ NOT DYNAMIC\\n│ │\\n▼ ▼\\n┌───────────────┐ ┌───────────────┐\\n│ Report │ │ Migrate to │\\n│ warning │ │ Tag │\\n│ (manual │ │ - appearance │\\n│ review) │ │ → color │\\n│ │ │ - Map values: │\\n│ │ │ success → │\\n│ │ │ lime │\\n│ │ │ default → │\\n│ │ │ gray │\\n│ │ │ removed → │\\n│ │ │ red │\\n│ │ │ inprogress │\\n│ │ │ → blue │\\n│ │ │ new → │\\n│ │ │ purple │\\n│ │ │ moved → │\\n│ │ │ yellow │\\n│ │ │ - Remove │\\n│ │ │ isBold │\\n│ │ │ - Add │\\n│ │ │ isRemov │\\n│ │ │ able= │\\n│ │ │ {false} │\\n│ │ │ - Add │\\n│ │ │ migration_ │\\n│ │ │ fallback= │\\n│ │ │ \\"lozenge\\" │\\n└───────────────┘ └───────────────┘\\n```\\n\\n## Appearance Prop Handling\\n\\n### Lozenge Appearance Value Migration\\n\\nThe new Lozenge API uses semantic color names. Old legacy appearance values are auto-fixed in-place:\\n\\n| Old Appearance | New Appearance |\\n| -------------- | --------------------- |\\n| `default` | `neutral` |\\n| `inprogress` | `information` |\\n| `moved` | `warning` |\\n| `removed` | `danger` |\\n| `new` | `discovery` |\\n| `success` | `success` (unchanged) |\\n\\nThe `<Lozenge>` component stays as `<Lozenge>` — it no longer migrates to `<Tag>`.\\n\\n### isBold Prop\\n\\nThe `isBold` prop is **not flagged** by this rule. While the feature flag\\n`platform-dst-lozenge-tag-badge-visual-uplifts` is OFF, users still need `isBold` to render subtle\\nLozenges. Removing it prematurely would break subtle Lozenges in those environments.\\n\\nOnce the feature flag is fully rolled out and the new Lozenge (always bold) is the only variant,\\n`isBold` cleanup can be handled in a separate codemod pass.\\n\\n### Badge Appearance Value Mapping\\n\\nBadge components use the following appearance value mapping:\\n\\n| Old Appearance | New Appearance |\\n| ----------------- | -------------- |\\n| `added` | `success` |\\n| `removed` | `danger` |\\n| `default` | `neutral` |\\n| `primary` | `information` |\\n| `primaryInverted` | `inverse` |\\n| `important` | `danger` |\\n\\n### Tag Color Mapping\\n\\nSimpleTag and RemovableTag color props are mapped to new semantic color values when migrating to\\nTag:\\n\\n| Old Color | New Color |\\n| -------------- | --------- |\\n| `limeLight` | `lime` |\\n| `orangeLight` | `orange` |\\n| `magentaLight` | `magenta` |\\n| `greenLight` | `green` |\\n| `blueLight` | `blue` |\\n| `redLight` | `red` |\\n| `purpleLight` | `purple` |\\n| `greyLight` | `gray` |\\n| `tealLight` | `teal` |\\n| `yellowLight` | `yellow` |\\n| `grey` | `gray` |\\n\\n## Auto-fixes\\n\\n- ✅ Lozenge legacy appearance values migrated to new semantic values in-place (e.g.,\\n `appearance=\\"inprogress\\"` → `appearance=\\"information\\"`)\\n- ✅ Static Badge appearance prop values (e.g., `appearance=\\"added\\"` → `appearance=\\"success\\"`)\\n- ✅ SimpleTag/RemovableTag migration to `<Tag>` with color mapping and import updates\\n- ✅ SimpleTag/RemovableTag from subpaths (e.g., `@atlaskit/tag/simple-tag`) migration to main\\n module\\n- ✅ SimpleTag/RemovableTag with Avatar migration to `<AvatarTag>` with render props pattern\\n- ✅ Static Tag color prop mapping (e.g., `color=\\"blueLight\\"` → `color=\\"blue\\"`)\\n- ✅ SimpleTag `isRemovable={false}` prop addition when migrating to Tag\\n- ✅ Subpath import conversion to main `@atlaskit/tag` module\\n- ❌ Dynamic Lozenge `appearance` prop values (warning with FIXME comment only)\\n- ❌ Dynamic Badge appearance expressions (warning only - requires manual review)\\n"}',
64
+ content: '{"ruleName":"lozenge-badge-tag-labelling-system-migration","description":"Migrate legacy Lozenge and Badge appearance values and legacy SimpleTag/RemovableTag usage. The rule","content":"# lozenge-badge-tag-labelling-system-migration\\n\\nMigrate legacy Lozenge and Badge appearance values and legacy SimpleTag/RemovableTag usage. The rule\\nis opt-in and retains warnings when a safe automatic migration cannot be inferred.\\n\\n## Appearance values\\n\\nApply the autofix for these static values. The diagnostic names the old and replacement values.\\n\\n| Component | Legacy → semantic |\\n| --------- | ---------------------------------------------------------------------------------------------------------------- |\\n| Lozenge | default → neutral; inprogress → information; moved → warning; removed → danger; new → discovery |\\n| Badge | default → neutral; primary → information; primaryInverted → inverse; added → success; removed/important → danger |\\n\\nFor dynamic Badge appearance, inspect each possible value and update the value producer. A dynamic\\nexpression still requires manual review after its values are mapped; the rule cannot prove its type.\\nLozenge `isBold` cleanup is outside this rule. Check the installed Lozenge API separately; this rule\\nleaving a prop untouched does not establish that the prop is supported.\\n\\n## Plain Tag\\n\\nThe root default `@atlaskit/tag` export is the legacy RemovableTag. The supported new plain Tag is\\nthe default export from `@atlaskit/tag/tag-new`, with required `text: string | string[]`. It does\\nnot display children. For SimpleTag, preserve non-removability with `isRemovable={false}`.\\n\\n```tsx\\n// Before\\nimport { SimpleTag } from \'@atlaskit/tag\';\\n<SimpleTag text=\\"Design\\" color=\\"blueLight\\" />;\\n\\n// After\\nimport Tag from \'@atlaskit/tag/tag-new\';\\n<Tag text=\\"Design\\" color=\\"blue\\" isRemovable={false} />;\\n```\\n\\nThe autofix handles an isolated import with one JSX use, a static `text` prop or one plain text\\nchild, and supported props. It maps legacy Light colors and grey/greyLight, preserves a static\\nnon-Avatar `elemBefore`, and sets `isRemovable={false}` for SimpleTag. If `Tag` is already bound, it\\nchooses an unused `MigratedTag` name.\\n\\nFor mixed imports, multiple references, existing new Tag imports, spreads, callbacks, dynamic or\\nunsupported props, or children that are not one plain text node, follow the diagnostic and migrate\\nmanually. Preserve every remaining import and migrate all uses of a binding together. Review the\\ncurrent\\n[TagNewProps](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/src/master/platform/packages/design-system/tag/src/tag-new/types.tsx)\\nbefore transferring props. Existing root default imports named Tag/AvatarTag retain the rule\'s\\nprevious detection scope; a missing diagnostic is not evidence that they already use the new API.\\n\\n## AvatarTag\\n\\nWhen the old `elemBefore` contains an imported Atlaskit Avatar, migrate manually to the default\\n`@atlaskit/tag/avatar-tag` export. Supply `text: string`, an explicit entity `type` (`user`,\\n`other`, or `agent`), and an avatar renderer that forwards its provided props. The rule cannot infer\\nentity type from JSX. Preserve `isRemovable={false}` when migrating a SimpleTag.\\n\\n```tsx\\nimport Avatar from \'@atlaskit/avatar\';\\nimport AvatarTag from \'@atlaskit/tag/avatar-tag\';\\n\\n<AvatarTag text=\\"Alex\\" type=\\"user\\" avatar={(props) => <Avatar {...props} />} isRemovable={false} />;\\n```\\n\\nCheck\\n[AvatarTagProps](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/src/master/platform/packages/design-system/tag/src/tag-new/avatar-tag.tsx)\\nfor entity-specific props and removal callbacks. Keep the diagnostic visible until the migration is\\ncomplete; do not substitute a root Tag import or invent a named root Tag export.\\n"}',
65
65
  ruleName: 'lozenge-badge-tag-labelling-system-migration',
66
- description: 'This rule helps migrate deprecated `<Lozenge>` props and appearance values to the new API, migrate'
66
+ description: 'Migrate legacy Lozenge and Badge appearance values and legacy SimpleTag/RemovableTag usage. The rule'
67
67
  }, {
68
68
  content: '{"ruleName":"lozenge-isBold-and-lozenge-badge-appearance-migration","description":"This rule helps migrate deprecated `<Lozenge>` usages to the new API or `<Tag>` component, and","content":"# lozenge-isBold-and-lozenge-badge-appearance-migration\\n\\nThis rule helps migrate deprecated `<Lozenge>` usages to the new API or `<Tag>` component, and\\nmigrate `<Badge>` component appearance prop to new semantic values as part of the Labelling System\\nPhase 1 migration.\\n\\n## Examples\\n\\n### Incorrect\\n\\n```tsx\\n// Non-bold Lozenge variants should migrate to Tag\\n<Lozenge isBold={false} />\\n<Lozenge /> // no isBold means implicit false\\n\\n// Dynamic isBold expressions require manual review\\n<Lozenge isBold={someVariable} />\\n<Lozenge isBold={condition ? true : false} />\\n\\n// Badge: Old appearance values that need migration\\n<Badge appearance=\\"added\\">{5}</Badge>\\n<Badge appearance=\\"removed\\">{10}</Badge>\\n<Badge appearance=\\"default\\">{3}</Badge>\\n<Badge appearance=\\"primary\\">{7}</Badge>\\n<Badge appearance=\\"primaryInverted\\">{2}</Badge>\\n<Badge appearance=\\"important\\">{99}</Badge>\\n\\n// Badge: Dynamic appearance expressions require manual review\\n<Badge appearance={getStatus()}>{count}</Badge>\\n<Badge appearance={condition ? \'added\' : \'removed\'}>{num}</Badge>\\n```\\n\\n### Correct\\n\\n```tsx\\n// Non-bold variants should use Tag component with appearance prop\\n<Tag appearance=\\"success\\" />\\n<Tag appearance=\\"default\\" />\\n\\n// Bold Lozenge variants can stay as Lozenge\\n<Lozenge isBold />\\n<Lozenge isBold={true} />\\n<Lozenge appearance=\\"success\\" isBold />\\n\\n// Badge: New semantic appearance values\\n<Badge appearance=\\"success\\">{5}</Badge>\\n<Badge appearance=\\"danger\\">{10}</Badge>\\n<Badge appearance=\\"neutral\\">{3}</Badge>\\n<Badge appearance=\\"information\\">{7}</Badge>\\n<Badge appearance=\\"inverse\\">{2}</Badge>\\n<Badge appearance=\\"danger\\">{99}</Badge>\\n\\n// Badge: Already using semantic values\\n<Badge appearance=\\"success\\">{42}</Badge>\\n```\\n\\n## Rule Details\\n\\nThis rule enforces multiple migration patterns:\\n\\n1. **Migrate `isBold={false}` or missing `isBold` → `<Tag />`**: Detects non-bold Lozenge variants\\n and suggests migrating to the Tag component, preserving other props including the `appearance`\\n prop with its value.\\n\\n2. **Warn on dynamic `isBold` expressions**: Detects dynamic `isBold` props that cannot be safely\\n auto-fixed and require manual review.\\n\\n3. **Migrate Badge appearance values**: Detects Badge components using old appearance values and\\n migrates them to new semantic values.\\n\\n4. **Warn on dynamic Badge appearance expressions**: Detects dynamic `appearance` props on Badge\\n components that cannot be safely auto-fixed and require manual review.\\n\\n## Appearance Prop Handling\\n\\n### Lozenge and Tag\\n\\nBoth `<Lozenge>` and `<Tag>` now use the `appearance` prop with new semantic values. The rule will\\nautomatically map old appearance values to the new semantic values when they differ.\\n\\n### Appearance Value Mapping\\n\\nThe rule includes a mapping function that will update old appearance values to new semantic values:\\n\\n```tsx\\n// Example mappings (to be updated with actual semantic values)\\n\'success\' → \'success\' // or new semantic equivalent\\n\'default\' → \'default\' // or new semantic equivalent\\n\'removed\' → \'removed\' // or new semantic equivalent\\n\'inprogress\' → \'inprogress\' // or new semantic equivalent\\n\'new\' → \'new\' // or new semantic equivalent\\n\'moved\' → \'moved\' // or new semantic equivalent\\n```\\n\\n**Note**: The current implementation preserves existing values. The mapping will be updated once the\\nnew semantic values are finalized.\\n\\n### Badge Appearance Value Mapping\\n\\nBadge components use the following appearance value mapping:\\n\\n| Old Appearance | New Appearance |\\n| ----------------- | -------------- |\\n| `added` | `success` |\\n| `removed` | `danger` |\\n| `default` | `neutral` |\\n| `primary` | `information` |\\n| `primaryInverted` | `inverse` |\\n| `important` | `danger` |\\n\\n## Auto-fixes\\n\\n- ✅ `isBold={false}` and missing `isBold` migration to `<Tag>` with preserved `appearance` prop\\n- ✅ Static Badge appearance prop values (e.g., `appearance=\\"added\\"` → `appearance=\\"success\\"`)\\n- ❌ Dynamic `isBold` expressions (warning only)\\n- ❌ Dynamic Badge appearance expressions (warning only - requires manual review)\\n"}',
69
69
  ruleName: 'lozenge-isBold-and-lozenge-badge-appearance-migration',
@@ -121,47 +121,51 @@ export var lintRulesMcpStructuredContent = [{
121
121
  ruleName: 'no-exported-keyframes',
122
122
  description: 'Disallows `keyframes` export declarations that originate from a CSS-in-JS library, including'
123
123
  }, {
124
- content: '{"ruleName":"no-html-anchor","description":"Don\'t use native HTML anchors. The Atlassian Design System provides ready-made link components that","content":"# no-html-anchor\\n\\nDon\'t use native HTML anchors. The Atlassian Design System provides ready-made link components that\\ninclude event tracking, automatic router configuration, ensure accessible implementations, and\\nprovide access to ADS styling features like design tokens.\\n\\nUse Atlassian Design System components such as the [Link](/components/link) or\\n[LinkButton](/components/button/link-button) components when suitable. There may also be other\\ncomponents better-suited depending on the use case. If these components aren\'t suitable, use the\\n[Anchor primitive](/components/primitives/anchor) which helps you build custom links with Atlassian\\nDesign System styling.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML anchor elements.\\n\\n### Incorrect\\n\\n```jsx\\n<a href=\\"/\\">\\n ^ Using a native HTML `<a>`\\n Hello, World!\\n</a>\\n\\n<div role=\\"link\\" tabIndex=\\"0\\" data-href=\\"https://www.atlassian.com\\">\\n ^^^^^^^^^^^ Using `role=\\"link\\"` to create links\\n Hello, World!\\n</div>\\n\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Anchor from \'@atlaskit/primitives/anchor\';\\n\\n<Anchor href=\\"/\\">Hello, World!</Anchor>;\\n\\nimport Link from \'@atlaskit/link\';\\n\\n<Link href=\\"/\\">Hello, World!</Link>;\\n\\nimport LinkButton from \'@atlaskit/button/link\';\\n\\n<LinkButton href=\\"/\\">Hello, World!</LinkButton>;\\n```\\n"}',
124
+ content: '{"ruleName":"no-global-z-index","description":"Layers are moving to the browser","content":"# no-global-z-index\\n\\nLayers are moving to the browser\\n[top layer](https://developer.mozilla.org/en-US/docs/Glossary/Top_layer). The top layer orders\\nlayers by insertion (the layer shown last is on top) and ignores `z-index`. No element in the page,\\nat any `z-index`, can paint above a top layer element.\\n\\nLarge `z-index` values exist to win the global stack, which is the contest the top layer now\\nsettles. Code that relies on \\"my `9999` beats your `510`\\" breaks as soon as either layer moves to\\nthe top layer.\\n\\nSmall values (10 or less) are fine. They order siblings inside one component, such as a badge over\\nan avatar or a sticky table header, and the top layer does not change that.\\n\\nFor layered experiences, use a Design System layering component:\\n\\n- Overlays: [popup](https://atlassian.design/components/popup),\\n [tooltip](https://atlassian.design/components/tooltip),\\n [inline-dialog](https://atlassian.design/components/inline-dialog)\\n- Messaging: [modal-dialog](https://atlassian.design/components/modal-dialog),\\n [flag](https://atlassian.design/components/flag),\\n [spotlight](https://atlassian.design/components/spotlight)\\n- Forms and inputs: [dropdown-menu](https://atlassian.design/components/dropdown-menu),\\n [select](https://atlassian.design/components/select),\\n [datetime-picker](https://atlassian.design/components/datetime-picker)\\n\\nIf none of these fit, use `@atlaskit/top-layer`.\\n\\n## Examples\\n\\nThis rule marks `z-index` values above 10, and `calc(infinity)`, in:\\n\\n- object styles (`css`, `cssMap`, `xcss`, `styled`, inline `style`, `react-select` `styles`)\\n- tagged template styles (`` css`…` ``, `` styled.div`…` ``, `` createGlobalStyle`…` ``)\\n- `zIndex` JSX props\\n- `element.style.zIndex = …` assignments\\n- `style.setProperty(\'z-index\', …)` calls\\n\\nIt resolves numbers, numeric strings, ternaries, `??`, `||` and `&&`, and `const` values declared in\\nthe same file. It skips values it can\'t know from the file alone, such as imports, function calls,\\nand `calc()` other than `calc(infinity)`. It skips objects passed to `expect(…)` assertions, such as\\n`toHaveStyle({ zIndex: 700 })`, because they read a value rather than set one.\\n\\n### Not covered\\n\\n- `layers.*()` from `@atlaskit/theme`, such as `layers.modal()`. The rule can\'t know these values\\n from the file, and the\\n [`no-atlaskit-theme`](https://atlassian.design/components/eslint-plugin-ui-styling-standard/no-atlaskit-theme/usage)\\n rule already bans importing `@atlaskit/theme`.\\n- `element.style.cssText = \'z-index: 500\'` and `element.setAttribute(\'style\', \'z-index: 500\')`\\n- untagged template literals and plain strings, such as `` `z-index: 500;` ``\\n- functions inside `styled` templates, such as `` styled.div`z-index: ${(props) => props.z};` ``\\n\\n### Incorrect\\n\\n```tsx\\nconst styles = css({ zIndex: 500 });\\n ^^^\\n\\nconst Overlay = styled.div`\\n z-index: 9999;\\n ^^^^^^^^^^^^^\\n`;\\n\\nconst MODAL_Z_INDEX = 510;\\nconst styles = css({ zIndex: MODAL_Z_INDEX });\\n ^^^^^^^^^^^^^\\n\\n<Portal zIndex={700} />\\n ^^^\\n\\n<div style={{ zIndex: isOpen ? 1000 : 1 }} />\\n ^^^^\\n\\n<Iframe zIndex={options.zIndex ?? 1000} />\\n ^^^^\\n\\nelement.style.zIndex = \'2147483647\';\\n ^^^^^^^^^^^^\\n```\\n\\n### Correct\\n\\n```tsx\\n// Local ordering inside a component\\nconst badgeStyles = css({ zIndex: 1 });\\nconst stickyHeaderStyles = css({ zIndex: 10 });\\n\\n// A Design System layering component handles ordering for you\\n<Popup content={() => <Menu />} trigger={(props) => <Button {...props}>Open</Button>} />;\\n```\\n\\n## When not to use it\\n\\n- **Page chrome meant to sit under everything.** A sticky header, side navigation or in-page banner\\n can need a `z-index` to stay above scrolling page content. That ordering is all within the base\\n layer, and every top layer surface should still paint above it.\\n- **A base layer surface outside your control.** Rarely, code must order itself against something\\n you can\'t change, such as a third-party widget.\\n\\nAn `eslint-disable` comment silences this rule, but not the AFM-wide ratchet \\"No new z-index values\\nabove 10 (AFM-wide)\\", which counts `z-index` values in changed lines and ignores disable comments.\\nFor a real exception, add the file to the ratchet\'s `excluded` list in\\n`platform/monorepo.config/tasks/global-ratcheting/rules/no-global-z-index.ts` with an owner, a\\nreason and a removal condition, or get the ratchet increase accepted. Moving existing values into a\\nnew file also counts as new.\\n"}',
125
+ ruleName: 'no-global-z-index',
126
+ description: 'Layers are moving to the browser'
127
+ }, {
128
+ content: '{"ruleName":"no-html-anchor","description":"Don\'t use native HTML anchors. The Atlassian Design System provides ready-made link components that","content":"# no-html-anchor\\n\\nDon\'t use native HTML anchors. The Atlassian Design System provides ready-made link components that\\ninclude event tracking, automatic router configuration, ensure accessible implementations, and\\nprovide access to ADS styling features like design tokens.\\n\\nUse Atlassian Design System components such as the [Link](/components/link) or\\n[LinkButton](/components/button/link-button) components when suitable. There may also be other\\ncomponents better-suited depending on the use case. If these components aren\'t suitable, use the\\n[Anchor primitive](/components/primitives/anchor) which helps you build custom links with Atlassian\\nDesign System styling.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML anchor elements.\\n\\n### Incorrect\\n\\n```jsx\\n<a href=\\"/\\">\\n ^ Using a native HTML `<a>`\\n Hello, World!\\n</a>\\n\\n<div role=\\"link\\" tabIndex=\\"0\\" data-href=\\"https://www.atlassian.com\\">\\n ^^^^^^^^^^^ Using `role=\\"link\\"` to create links\\n Hello, World!\\n</div>\\n\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { Anchor } from \'@atlaskit/primitives/compiled/anchor\';\\n\\n<Anchor href=\\"/\\">Hello, World!</Anchor>;\\n\\nimport Link from \'@atlaskit/link/link\';\\n\\n<Link href=\\"/\\">Hello, World!</Link>;\\n\\nimport LinkButton from \'@atlaskit/button/link\';\\n\\n<LinkButton href=\\"/\\">Hello, World!</LinkButton>;\\n```\\n"}',
125
129
  ruleName: 'no-html-anchor',
126
130
  description: "Don't use native HTML anchors. The Atlassian Design System provides ready-made link components that"
127
131
  }, {
128
- content: '{"ruleName":"no-html-button","description":"Don\'t use native HTML buttons. The Atlassian Design System provides ready-made button components","content":"# no-html-button\\n\\nDon\'t use native HTML buttons. The Atlassian Design System provides ready-made button components\\nthat include event tracking, ensure accessible implementations, and provide access to ADS styling\\nfeatures like design tokens.\\n\\nUse Atlassian Design System components such as the [Button component](/components/button) when\\nsuitable. There may also be other components better-suited depending on the use case. If these\\ncomponents aren\'t suitable, use the [Pressable primitive](/components/primitives/pressable) which\\nhelps you build custom buttons with Atlassian Design System styling.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML button elements.\\n\\n### Incorrect\\n\\n```jsx\\n<button>\\n ^^^^^^ Using a native HTML `<button>`\\n Hello, World!\\n</button>\\n\\n<div role=\\"button\\" tabIndex=\\"0\\">\\n ^^^^^^^^^^^^^ Using `role=\\"button\\"` to create buttons\\n Hello, World!\\n</div>\\n\\n<input type=\\"button\\" value=\\"Button\\" />\\n ^^^^^^^^^^^^^ Using a `<input>` as a button\\n\\n<input type=\\"submit\\" value=\\"Submit\\" />\\n ^^^^^^^^^^^^^ Using a `<input>` as a button\\n\\n<input type=\\"reset\\" value=\\"Reset\\" />\\n ^^^^^^^^^^^^ Using a `<input>` as a button\\n\\n<input type=\\"image\\" alt=\\"Submit\\" src=\\"/submit-button.png\\" />\\n ^^^^^^^^^^^^ Using a `<input>` as a button\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Pressable from \'@atlaskit/primitives/pressable\';\\n\\n<Pressable>Hello, World!</Pressable>;\\n\\nimport Button from \'@atlaskit/button/default/button\';\\n\\n<Button>Hello, World!</Button>;\\n```\\n"}',
132
+ content: '{"ruleName":"no-html-button","description":"Don\'t use native HTML buttons. The Atlassian Design System provides ready-made button components","content":"# no-html-button\\n\\nDon\'t use native HTML buttons. The Atlassian Design System provides ready-made button components\\nthat include event tracking, ensure accessible implementations, and provide access to ADS styling\\nfeatures like design tokens.\\n\\nUse Atlassian Design System components such as the [Button component](/components/button) when\\nsuitable. There may also be other components better-suited depending on the use case. If these\\ncomponents aren\'t suitable, use the [Pressable primitive](/components/primitives/pressable) which\\nhelps you build custom buttons with Atlassian Design System styling.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML button elements.\\n\\n### Incorrect\\n\\n```jsx\\n<button>\\n ^^^^^^ Using a native HTML `<button>`\\n Hello, World!\\n</button>\\n\\n<div role=\\"button\\" tabIndex=\\"0\\">\\n ^^^^^^^^^^^^^ Using `role=\\"button\\"` to create buttons\\n Hello, World!\\n</div>\\n\\n<input type=\\"button\\" value=\\"Button\\" />\\n ^^^^^^^^^^^^^ Using a `<input>` as a button\\n\\n<input type=\\"submit\\" value=\\"Submit\\" />\\n ^^^^^^^^^^^^^ Using a `<input>` as a button\\n\\n<input type=\\"reset\\" value=\\"Reset\\" />\\n ^^^^^^^^^^^^ Using a `<input>` as a button\\n\\n<input type=\\"image\\" alt=\\"Submit\\" src=\\"/submit-button.png\\" />\\n ^^^^^^^^^^^^ Using a `<input>` as a button\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { Pressable } from \'@atlaskit/primitives/compiled/pressable\';\\n\\n<Pressable>Hello, World!</Pressable>;\\n\\nimport Button from \'@atlaskit/button/default/button\';\\n\\n<Button>Hello, World!</Button>;\\n```\\n"}',
129
133
  ruleName: 'no-html-button',
130
134
  description: "Don't use native HTML buttons. The Atlassian Design System provides ready-made button components"
131
135
  }, {
132
- content: '{"ruleName":"no-html-checkbox","description":"Don\'t use native HTML checkboxes. The Atlassian Design System provides a ready-made checkbox","content":"# no-html-checkbox\\n\\nDon\'t use native HTML checkboxes. The Atlassian Design System provides a ready-made checkbox\\ncomponent that includes event tracking, ensures accessible implementations, and provides access to\\nADS styling features like design tokens.\\n\\nUse the Atlassian Design System [Checkbox](https://atlassian.design/components/checkbox) component\\nwhen suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML checkbox elements.\\n\\n### Incorrect\\n\\n```jsx\\n<label>\\n\\tRemember me\\n\\t<input type=\\"checkbox\\" id=\\"remember-me\\" />\\n\\t^^^^^ Using a native checkbox input\\n</label>\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { Checkbox } from \'@atlaskit/checkbox\';\\n\\n<Checkbox value=\\"remember-me\\" label=\\"Remember me\\" name=\\"remember-me\\" />;\\n```\\n"}',
136
+ content: '{"ruleName":"no-html-checkbox","description":"Don\'t use native HTML checkboxes. The Atlassian Design System provides a ready-made checkbox","content":"# no-html-checkbox\\n\\nDon\'t use native HTML checkboxes. The Atlassian Design System provides a ready-made checkbox\\ncomponent that includes event tracking, ensures accessible implementations, and provides access to\\nADS styling features like design tokens.\\n\\nUse the Atlassian Design System [Checkbox](https://atlassian.design/components/checkbox) component\\nwhen suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML checkbox elements.\\n\\n### Incorrect\\n\\n```jsx\\n<label>\\n\\tRemember me\\n\\t<input type=\\"checkbox\\" id=\\"remember-me\\" />\\n\\t^^^^^ Using a native checkbox input\\n</label>\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Checkbox from \'@atlaskit/checkbox/checkbox\';\\n\\n<Checkbox value=\\"remember-me\\" label=\\"Remember me\\" name=\\"remember-me\\" />;\\n```\\n"}',
133
137
  ruleName: 'no-html-checkbox',
134
138
  description: "Don't use native HTML checkboxes. The Atlassian Design System provides a ready-made checkbox"
135
139
  }, {
136
- content: '{"ruleName":"no-html-code","description":"Don\'t use native HTML code element. The Atlassian Design System provides a ready-made code component","content":"# no-html-code\\n\\nDon\'t use native HTML code element. The Atlassian Design System provides a ready-made code component\\nthat ensures accessible implementations and consistent ADS styling.\\n\\nUse the Atlassian Design System [Code](/components/code) component when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML code elements.\\n\\n### Incorrect\\n\\n```jsx\\n<code>yarn changeset</code>\\n ^^^^ Using a native HTML `<code>`\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { Code } from \'@atlaskit/code\';\\n\\n<Code>yarn changeset</Code>;\\n```\\n"}',
140
+ content: '{"ruleName":"no-html-code","description":"Don\'t use native HTML code element. The Atlassian Design System provides a ready-made code component","content":"# no-html-code\\n\\nDon\'t use native HTML code element. The Atlassian Design System provides a ready-made code component\\nthat ensures accessible implementations and consistent ADS styling.\\n\\nUse the Atlassian Design System [Code](/components/code) component when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML code elements.\\n\\n### Incorrect\\n\\n```jsx\\n<code>yarn changeset</code>\\n ^^^^ Using a native HTML `<code>`\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Code from \'@atlaskit/code/code\';\\n\\n<Code>yarn changeset</Code>;\\n```\\n"}',
137
141
  ruleName: 'no-html-code',
138
142
  description: "Don't use native HTML code element. The Atlassian Design System provides a ready-made code component"
139
143
  }, {
140
- content: '{"ruleName":"no-html-heading","description":"Don\'t use native HTML headings. The Atlassian Design System provides a ready-made heading component","content":"# no-html-heading\\n\\nDon\'t use native HTML headings. The Atlassian Design System provides a ready-made heading component\\nthat ensures accessible implementations, and provides access to ADS styling features like design\\ntokens.\\n\\nUse the Atlassian Design System [Heading](/components/heading) component when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML heading elements.\\n\\n### Incorrect\\n\\n```jsx\\n<h1>Hello world!</h1>\\n ^^ Using a native HTML heading element\\n\\n<span role=\\"heading\\" aria-level=\\"1\\">Hello world!</span>\\n ^^^^ Using `role=\\"heading\\"` to create headings\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Heading from \'@atlaskit/heading\';\\n\\n<Heading as=\\"h1\\">Hello, World!</Heading>;\\n```\\n"}',
144
+ content: '{"ruleName":"no-html-heading","description":"Don\'t use native HTML headings. The Atlassian Design System provides a ready-made heading component","content":"# no-html-heading\\n\\nDon\'t use native HTML headings. The Atlassian Design System provides a ready-made heading component\\nthat ensures accessible implementations, and provides access to ADS styling features like design\\ntokens.\\n\\nUse the Atlassian Design System [Heading](/components/heading) component when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML heading elements.\\n\\n### Incorrect\\n\\n```jsx\\n<h1>Hello world!</h1>\\n ^^ Using a native HTML heading element\\n\\n<span role=\\"heading\\" aria-level=\\"1\\">Hello world!</span>\\n ^^^^ Using `role=\\"heading\\"` to create headings\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Heading from \'@atlaskit/heading/heading\';\\n\\n<Heading size=\\"large\\" as=\\"h1\\">\\n\\tHello, World!\\n</Heading>;\\n```\\n"}',
141
145
  ruleName: 'no-html-heading',
142
146
  description: "Don't use native HTML headings. The Atlassian Design System provides a ready-made heading component"
143
147
  }, {
144
- content: '{"ruleName":"no-html-image","description":"Don\'t use native HTML images. The Atlassian Design System provides a ready-made image component that","content":"# no-html-image\\n\\nDon\'t use native HTML images. The Atlassian Design System provides a ready-made image component that\\nensures accessible implementations and provides access to ADS styling features like design tokens.\\n\\nUse the Atlassian Design System [Image](/components/image) component when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML image elements.\\n\\n### Incorrect\\n\\n```jsx\\n<img src=\\"foo.jpg\\" alt=\\"The word \'foo\' written on a white background.\\" />\\n ^^^ Using a native HTML `<img>`\\n\\n<div role=\\"img\\" src=\\"foo.jpg\\" alt=\\"The word \'foo\' written on a white background.\\" />\\n ^^^ Using `role=\\"img\\"` to create images\\n\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Image from \'@atlaskit/image\';\\n\\n<Image src=\\"foo.jpg\\" alt=\\"The word \'foo\' written on a white background.\\" />;\\n```\\n"}',
148
+ content: '{"ruleName":"no-html-image","description":"Don\'t use native HTML images. The Atlassian Design System provides a ready-made image component that","content":"# no-html-image\\n\\nDon\'t use native HTML images. The Atlassian Design System provides a ready-made image component that\\nensures accessible implementations and provides access to ADS styling features like design tokens.\\n\\nUse the Atlassian Design System [Image](/components/image) component when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML image elements.\\n\\n### Incorrect\\n\\n```jsx\\n<img src=\\"foo.jpg\\" alt=\\"The word \'foo\' written on a white background.\\" />\\n ^^^ Using a native HTML `<img>`\\n\\n<div role=\\"img\\" src=\\"foo.jpg\\" alt=\\"The word \'foo\' written on a white background.\\" />\\n ^^^ Using `role=\\"img\\"` to create images\\n\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Image from \'@atlaskit/image/image\';\\n\\n<Image src=\\"foo.jpg\\" alt=\\"The word \'foo\' written on a white background.\\" />;\\n```\\n"}',
145
149
  ruleName: 'no-html-image',
146
150
  description: "Don't use native HTML images. The Atlassian Design System provides a ready-made image component that"
147
151
  }, {
148
- content: '{"ruleName":"no-html-radio","description":"Don\'t use native HTML radios. The Atlassian Design System provides a ready-made radio component that","content":"# no-html-radio\\n\\nDon\'t use native HTML radios. The Atlassian Design System provides a ready-made radio component that\\nincludes event tracking, ensures accessible implementations, and provides access to ADS styling\\nfeatures like design tokens.\\n\\nUse the Atlassian Design System [Radio](https://atlassian.design/components/radio) and\\n[RadioGroup](https://atlassian.design/components/radio/radio-group/examples) components when\\nsuitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML radio elements.\\n\\n### Incorrect\\n\\n```jsx\\n<fieldset>\\n\\t<legend>Preferred contact method</legend>\\n\\t<input type=\\"radio\\" id=\\"contact-method--email\\" name=\\"contact\\" value=\\"email\\" />\\n\\t^^^^^ Using a native radio input\\n\\t<label for=\\"contact-method--email\\">Email</label>\\n\\t<input type=\\"radio\\" id=\\"contact-method--phone\\" name=\\"contact\\" value=\\"phone\\" />\\n\\t^^^^^ Using a native radio input\\n\\t<label for=\\"contact-method--phone\\">Phone</label>\\n</fieldset>\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { ErrorMessage, Field } from \'@atlaskit/form\';\\nimport { RadioGroup } from \'@atlaskit/radio\';\\nimport { type OptionsPropType } from \'@atlaskit/radio/types\';\\n\\nconst options: OptionsPropType = [\\n\\t{ name: \'contact\', value: \'email\', label: \'Email\' },\\n\\t{ name: \'contact\', value: \'phone\', label: \'Phone\' },\\n];\\n\\n<Field label=\\"Preferred contact method\\" name=\\"contact\\" defaultValue=\\"email\\">\\n\\t{({ fieldProps }) => <RadioGroup {...fieldProps} options={options} />}\\n</Field>;\\n```\\n"}',
152
+ content: '{"ruleName":"no-html-radio","description":"Don\'t use native HTML radios. The Atlassian Design System provides a ready-made radio component that","content":"# no-html-radio\\n\\nDon\'t use native HTML radios. The Atlassian Design System provides a ready-made radio component that\\nincludes event tracking, ensures accessible implementations, and provides access to ADS styling\\nfeatures like design tokens.\\n\\nUse the Atlassian Design System [Radio](https://atlassian.design/components/radio) and\\n[RadioGroup](https://atlassian.design/components/radio/radio-group/examples) components when\\nsuitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML radio elements.\\n\\n### Incorrect\\n\\n```jsx\\n<fieldset>\\n\\t<legend>Preferred contact method</legend>\\n\\t<input type=\\"radio\\" id=\\"contact-method--email\\" name=\\"contact\\" value=\\"email\\" />\\n\\t^^^^^ Using a native radio input\\n\\t<label for=\\"contact-method--email\\">Email</label>\\n\\t<input type=\\"radio\\" id=\\"contact-method--phone\\" name=\\"contact\\" value=\\"phone\\" />\\n\\t^^^^^ Using a native radio input\\n\\t<label for=\\"contact-method--phone\\">Phone</label>\\n</fieldset>\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { Fieldset } from \'@atlaskit/form/fieldset\';\\nimport Radio from \'@atlaskit/radio/radio\';\\n\\n<Fieldset legend=\\"Preferred contact method\\">\\n\\t<Radio name=\\"contact\\" value=\\"email\\" label=\\"Email\\" defaultChecked />\\n\\t<Radio name=\\"contact\\" value=\\"phone\\" label=\\"Phone\\" />\\n</Fieldset>;\\n```\\n"}',
149
153
  ruleName: 'no-html-radio',
150
154
  description: "Don't use native HTML radios. The Atlassian Design System provides a ready-made radio component that"
151
155
  }, {
152
- content: '{"ruleName":"no-html-range","description":"Don\'t use native HTML ranges. The Atlassian Design System provides a ready-made range component that","content":"# no-html-range\\n\\nDon\'t use native HTML ranges. The Atlassian Design System provides a ready-made range component that\\nincludes event tracking, ensures accessible implementations, and provides access to ADS styling\\nfeatures like design tokens.\\n\\nUse the Atlassian Design System [Range](https://atlassian.design/components/range) component when\\nsuitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML range elements.\\n\\n### Incorrect\\n\\n```jsx\\n<label for=\\"volume\\">Volume</label>\\n<input type=\\"range\\" id=\\"volume\\" name=\\"volume\\" step=\\"1\\" min=\\"0\\" max=\\"10\\" />\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Range from \'@atlaskit/range\';\\n\\n<label for=\\"volume\\">Volume</label>\\n<Range id=\\"volume\\" step={1} min={0} max={10} />\\n```\\n"}',
156
+ content: '{"ruleName":"no-html-range","description":"Don\'t use native HTML ranges. The Atlassian Design System provides a ready-made range component that","content":"# no-html-range\\n\\nDon\'t use native HTML ranges. The Atlassian Design System provides a ready-made range component that\\nincludes event tracking, ensures accessible implementations, and provides access to ADS styling\\nfeatures like design tokens.\\n\\nUse the Atlassian Design System [Range](https://atlassian.design/components/range) component when\\nsuitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML range elements.\\n\\n### Incorrect\\n\\n```jsx\\n<label for=\\"volume\\">Volume</label>\\n<input type=\\"range\\" id=\\"volume\\" name=\\"volume\\" step=\\"1\\" min=\\"0\\" max=\\"10\\" />\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Range from \'@atlaskit/range/range\';\\n\\nexport default function Example() {\\n\\treturn (\\n\\t\\t<>\\n\\t\\t\\t<label htmlFor=\\"volume\\">Volume</label>\\n\\t\\t\\t<Range id=\\"volume\\" step={1} min={0} max={10} />\\n\\t\\t</>\\n\\t);\\n}\\n```\\n"}',
153
157
  ruleName: 'no-html-range',
154
158
  description: "Don't use native HTML ranges. The Atlassian Design System provides a ready-made range component that"
155
159
  }, {
156
- content: "{\"ruleName\":\"no-html-select\",\"description\":\"Don't use native HTML selects. The Atlassian Design System provides a ready-made select component\",\"content\":\"# no-html-select\\n\\nDon't use native HTML selects. The Atlassian Design System provides a ready-made select component\\nthat has event tracking, ensures accessible implementations, and provides access to ADS styling\\nfeatures like design tokens.\\n\\nUse one of the Atlassian Design System [Select](/components/select) components when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML select elements.\\n\\n### Incorrect\\n\\n```jsx\\n<select name=\\\"cities\\\" id=\\\"city-select\\\">\\n\\t<option value=\\\"adelaide\\\">Adelaide</option>\\n\\t<option value=\\\"brisbane\\\">Brisbane</option>\\n\\t<option value=\\\"canberra\\\">Canberra</option>\\n\\t<option value=\\\"darwin\\\">Darwin</option>\\n\\t<option value=\\\"hobart\\\">Hobart</option>\\n\\t<option value=\\\"melbourne\\\">Melbourne</option>\\n\\t<option value=\\\"perth\\\">Perth</option>\\n\\t<option value=\\\"sydney\\\">Sydney</option>\\n</select>\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Select from '@atlaskit/select';\\n\\nexport const cities: OptionsType = [\\n\\t{ label: 'Adelaide', value: 'adelaide', extra: 'extra' },\\n\\t{ label: 'Brisbane', value: 'brisbane' },\\n\\t{ label: 'Canberra', value: 'canberra' },\\n\\t{ label: 'Darwin', value: 'darwin' },\\n\\t{ label: 'Hobart', value: 'hobart' },\\n\\t{ label: 'Melbourne', value: 'melbourne' },\\n\\t{ label: 'Perth', value: 'perth' },\\n\\t{ label: 'Sydney', value: 'sydney' },\\n];\\n\\n<Select inputId=\\\"city-select\\\" options={cities} />\\n```\\n\"}",
160
+ content: '{"ruleName":"no-html-select","description":"Don\'t use native HTML selects. The Atlassian Design System provides a ready-made select component","content":"# no-html-select\\n\\nDon\'t use native HTML selects. The Atlassian Design System provides a ready-made select component\\nthat has event tracking, ensures accessible implementations, and provides access to ADS styling\\nfeatures like design tokens.\\n\\nUse one of the Atlassian Design System [Select](/components/select) components when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML select elements.\\n\\n### Incorrect\\n\\n```jsx\\n<select name=\\"cities\\" id=\\"city-select\\">\\n\\t<option value=\\"adelaide\\">Adelaide</option>\\n\\t<option value=\\"brisbane\\">Brisbane</option>\\n\\t<option value=\\"canberra\\">Canberra</option>\\n\\t<option value=\\"darwin\\">Darwin</option>\\n\\t<option value=\\"hobart\\">Hobart</option>\\n\\t<option value=\\"melbourne\\">Melbourne</option>\\n\\t<option value=\\"perth\\">Perth</option>\\n\\t<option value=\\"sydney\\">Sydney</option>\\n</select>\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Select from \'@atlaskit/select/default\';\\n\\nconst cities = [\\n\\t{ label: \'Adelaide\', value: \'adelaide\', extra: \'extra\' },\\n\\t{ label: \'Brisbane\', value: \'brisbane\' },\\n\\t{ label: \'Canberra\', value: \'canberra\' },\\n\\t{ label: \'Darwin\', value: \'darwin\' },\\n\\t{ label: \'Hobart\', value: \'hobart\' },\\n\\t{ label: \'Melbourne\', value: \'melbourne\' },\\n\\t{ label: \'Perth\', value: \'perth\' },\\n\\t{ label: \'Sydney\', value: \'sydney\' },\\n];\\n\\nexport default function Example() {\\n\\treturn (\\n\\t\\t<>\\n\\t\\t\\t<label htmlFor=\\"city-select\\">City</label>\\n\\t\\t\\t<Select name=\\"cities\\" inputId=\\"city-select\\" options={cities} defaultValue={cities[0]} />\\n\\t\\t</>\\n\\t);\\n}\\n```\\n"}',
157
161
  ruleName: 'no-html-select',
158
162
  description: "Don't use native HTML selects. The Atlassian Design System provides a ready-made select component"
159
163
  }, {
160
- content: '{"ruleName":"no-html-text-input","description":"Don\'t use native HTML text inputs. The Atlassian Design System provides a ready-made textfield","content":"# no-html-text-input\\n\\nDon\'t use native HTML text inputs. The Atlassian Design System provides a ready-made textfield\\ncomponent that includes event tracking, ensures accessible implementations, and provides access to\\nADS styling features like design tokens.\\n\\nUse the Atlassian Design System [Textfield](https://atlassian.design/components/textfield) component\\nwhen suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML text input elements.\\n\\n### Incorrect\\n\\n```jsx\\n<label for=\\"full-name\\">Full Name</label>\\n<input name=\\"full-name\\" id=\\"full-name\\" />\\n\\n<label for=\\"nickname\\">Nickname</label>\\n<input name=\\"nickname\\" id=\\"nickname\\" type=\\"text\\" />\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Textfield from \'@atlaskit/range\';\\n\\n<label for=\\"full-name\\">Full Name</label>\\n<Textfield name=\\"full-name\\" id=\\"full-name\\" />\\n\\n<label for=\\"nickname\\">Nickname</label>\\n<Textfield name=\\"nickname\\" id=\\"nickname\\" />\\n```\\n"}',
164
+ content: '{"ruleName":"no-html-text-input","description":"Don\'t use native HTML text inputs. The Atlassian Design System provides a ready-made textfield","content":"# no-html-text-input\\n\\nDon\'t use native HTML text inputs. The Atlassian Design System provides a ready-made textfield\\ncomponent that includes event tracking, ensures accessible implementations, and provides access to\\nADS styling features like design tokens.\\n\\nUse the Atlassian Design System [Textfield](https://atlassian.design/components/textfield) component\\nwhen suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML text input elements.\\n\\n### Incorrect\\n\\n```jsx\\n<label for=\\"full-name\\">Full Name</label>\\n<input name=\\"full-name\\" id=\\"full-name\\" />\\n\\n<label for=\\"nickname\\">Nickname</label>\\n<input name=\\"nickname\\" id=\\"nickname\\" type=\\"text\\" />\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Textfield from \'@atlaskit/textfield/text-field\';\\n\\nexport default function Example() {\\n\\treturn (\\n\\t\\t<>\\n\\t\\t\\t<label htmlFor=\\"full-name\\">Full Name</label>\\n\\t\\t\\t<Textfield name=\\"full-name\\" id=\\"full-name\\" />\\n\\t\\t\\t<label htmlFor=\\"nickname\\">Nickname</label>\\n\\t\\t\\t<Textfield name=\\"nickname\\" id=\\"nickname\\" />\\n\\t\\t</>\\n\\t);\\n}\\n```\\n"}',
161
165
  ruleName: 'no-html-text-input',
162
166
  description: "Don't use native HTML text inputs. The Atlassian Design System provides a ready-made textfield"
163
167
  }, {
164
- content: '{"ruleName":"no-html-textarea","description":"Don\'t use native HTML textarea elements. The Atlassian Design System provides a ready-made textarea","content":"# no-html-textarea\\n\\nDon\'t use native HTML textarea elements. The Atlassian Design System provides a ready-made textarea\\ncomponent that includes event tracking, ensures accessible implementations, and provides access to\\nADS styling features like design tokens.\\n\\nUse the Atlassian Design System [Textarea](/components/textarea) component when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML textarea elements.\\n\\n### Incorrect\\n\\n```jsx\\n<label htmlFor=\\"textarea\\">Share your feedback</label>\\n<textarea id=\\"textarea\\"></textarea>\\n ^^^^^^^^ Using a native HTML `<textarea>`\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Textarea from \'@atlaskit/textarea\';\\n\\n<label htmlFor=\\"textarea\\">Share your feedback</label>\\n<Textarea id=\\"textarea\\" />\\n```\\n"}',
168
+ content: '{"ruleName":"no-html-textarea","description":"Don\'t use native HTML textarea elements. The Atlassian Design System provides a ready-made textarea","content":"# no-html-textarea\\n\\nDon\'t use native HTML textarea elements. The Atlassian Design System provides a ready-made textarea\\ncomponent that includes event tracking, ensures accessible implementations, and provides access to\\nADS styling features like design tokens.\\n\\nUse the Atlassian Design System [Textarea](/components/textarea) component when suitable.\\n\\n## Examples\\n\\nThis rule marks code as violations when it finds native HTML textarea elements.\\n\\n### Incorrect\\n\\n```jsx\\n<label htmlFor=\\"textarea\\">Share your feedback</label>\\n<textarea id=\\"textarea\\"></textarea>\\n ^^^^^^^^ Using a native HTML `<textarea>`\\n```\\n\\n### Correct\\n\\n```jsx\\nimport Textarea from \'@atlaskit/textarea/text-area\';\\n\\nexport default function Example() {\\n\\treturn (\\n\\t\\t<>\\n\\t\\t\\t<label htmlFor=\\"textarea\\">Share your feedback</label>\\n\\t\\t\\t<Textarea id=\\"textarea\\" />\\n\\t\\t</>\\n\\t);\\n}\\n```\\n"}',
165
169
  ruleName: 'no-html-textarea',
166
170
  description: "Don't use native HTML textarea elements. The Atlassian Design System provides a ready-made textarea"
167
171
  }, {
@@ -184,6 +188,10 @@ export var lintRulesMcpStructuredContent = [{
184
188
  content: '{"ruleName":"no-modal-label","description":"Do not use the `label` prop on the Atlassian Design System modal dialog default import.","content":"# no-modal-label\\n\\nDo not use the `label` prop on the Atlassian Design System modal dialog default import.\\n\\nUse `ModalTitle` within `ModalHeader`, or another element with `titleId` applied from `useModal()`\\nto provide a clear, visible title for modal content. This content will be propagated to assistive\\ntechnology as well as serving visual users. It is very rare that a dialog title should differ\\nbetween the visible text and that shown to users of assistive technology.\\n\\n## Examples\\n\\nThis rule warns when `label` is used on:\\n\\n- the default import from `@atlaskit/modal-dialog` or `@atlaskit/modal-dialog/modal-dialog`\\n- `modalProps.label` on modal entry-point triggers from `@atlassian/entry-points`\\n\\n### Incorrect\\n\\n```tsx\\nimport ModalDialog from \'@atlaskit/modal-dialog\';\\n\\n<ModalDialog label=\\"Create issue\\" />;\\n```\\n\\n```tsx\\nimport Modal from \'@atlaskit/modal-dialog/modal-dialog\';\\n\\n<Modal label={modalLabel} />;\\n```\\n\\n```tsx\\nimport { ModalTrigger } from \'@atlassian/entry-points/modal-trigger\';\\n\\n<ModalTrigger entryPoint={entryPoint} modalProps={{ label: \'Create issue\' }}>\\n\\t{({ ref, ...triggerProps }) => (\\n\\t\\t<button ref={ref} {...triggerProps}>\\n\\t\\t\\tOpen\\n\\t\\t</button>\\n\\t)}\\n</ModalTrigger>;\\n```\\n\\n### Correct\\n\\n```tsx\\nimport ModalDialog, { ModalHeader, ModalTitle } from \'@atlaskit/modal-dialog\';\\n\\n<ModalDialog>\\n\\t<ModalHeader>\\n\\t\\t<ModalTitle>Create issue</ModalTitle>\\n\\t</ModalHeader>\\n</ModalDialog>;\\n```\\n\\n```tsx\\nimport ModalDialog, { ModalHeader, ModalTitle, useModal } from \'@atlaskit/modal-dialog\';\\nimport Heading from \'@atlaskit/heading\';\\n\\nconst CustomHeader = () => {\\n\\tconst { titleId } = useModal();\\n\\n\\treturn (\\n\\t\\t<ModalHeader>\\n\\t\\t\\t<Heading id={titleId}>Create issue</Heading>\\n\\t\\t</ModalHeader>\\n\\t);\\n};\\n\\n<ModalDialog>\\n\\t<CustomHeader />\\n</ModalDialog>;\\n```\\n\\n```tsx\\nimport { ModalIconButtonTrigger } from \'@atlassian/entry-points/modal-icon-button-trigger\';\\n\\n// Top-level `label` on icon button triggers is the trigger button name — allowed.\\n<ModalIconButtonTrigger entryPoint={entryPoint} label=\\"Create issue\\" icon={AddIcon} />;\\n```\\n"}',
185
189
  ruleName: 'no-modal-label',
186
190
  description: 'Do not use the `label` prop on the Atlassian Design System modal dialog default import.'
191
+ }, {
192
+ content: "{\"ruleName\":\"no-native-popover-or-dialog\",\"description\":\"Do not use a native `popover` or `<dialog>` element. Use a Design System component. If no Design\",\"content\":\"# no-native-popover-or-dialog\\n\\nDo not use a native `popover` or `<dialog>` element. Use a Design System component. If no Design\\nSystem component fits, use `@atlaskit/top-layer`.\\n\\nDesign System layers share one layer stack. A press of Escape closes the topmost layer, and only\\nthat layer. A native `popover` or `<dialog>` that you build yourself is not in that stack. For\\nexample, a `popover=\\\"manual\\\"` element that closes itself on Escape, inside a Modal dialog, closes\\ntogether with the dialog. Design System components also give you focus management, placement, a\\nfallback for browsers without the top layer, and testing utilities.\\n\\nUse, in this order:\\n\\n1. A Design System component:\\n - Overlays: [popup](https://atlassian.design/components/popup),\\n [tooltip](https://atlassian.design/components/tooltip),\\n [inline-dialog](https://atlassian.design/components/inline-dialog)\\n - Messaging: [modal-dialog](https://atlassian.design/components/modal-dialog),\\n [drawer](https://atlassian.design/components/drawer),\\n [flag](https://atlassian.design/components/flag),\\n [spotlight](https://atlassian.design/components/spotlight)\\n - Forms and inputs: [dropdown-menu](https://atlassian.design/components/dropdown-menu),\\n [select](https://atlassian.design/components/select),\\n [datetime-picker](https://atlassian.design/components/datetime-picker)\\n2. `@atlaskit/top-layer`, only if no Design System component fits:\\n - Render it behind the `platform-dst-top-layer` feature flag. The primitives do not check the\\n flag. While the flag is off, they paint above every layer that is not in the top layer.\\n - For a `popover=\\\"manual\\\"` element that closes on Escape or an outside press, use\\n `useManualLightDismiss`. Do not add your own listeners.\\n\\n## Examples\\n\\nThis rule marks:\\n\\n- `<dialog>` elements, wrappers such as `<motion.dialog>`, and `styled.dialog`\\n- `popover` attributes on HTML elements, such as `<div popover=\\\"auto\\\">`, and on wrappers such as\\n `<motion.div popover=\\\"auto\\\">`\\n- `popover` in spread props or `createElement` props, such as `<div {...{ popover: 'auto' }}>` and\\n `createElement('div', { popover })`\\n- `createElement('dialog')`\\n- `setAttribute('popover', …)` and `toggleAttribute('popover')`\\n- `element.popover = '…'`\\n\\nIt does not mark a `popover` prop on a component, because a component can define its own. It does\\nnot check props that are only known at runtime, such as `<div {...props}>`.\\n\\n### Incorrect\\n\\n```tsx\\n<dialog ref={ref}>{children}</dialog>\\n ^^^^^^\\n\\n<div popover=\\\"auto\\\">{children}</div>\\n ^^^^^^^^^^^^^^\\n\\ndocument.createElement('dialog');\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\nelement.setAttribute('popover', 'manual');\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\ntooltip.popover = 'hint';\\n^^^^^^^^^^^^^^^^^^^^^^^^\\n```\\n\\n### Correct\\n\\n```tsx\\nimport ModalDialog from '@atlaskit/modal-dialog';\\nimport Popup from '@atlaskit/popup';\\n\\n<ModalDialog onClose={onClose}>{children}</ModalDialog>;\\n\\n<Popup\\n\\tisOpen={isOpen}\\n\\tonClose={onClose}\\n\\tcontent={() => <Menu />}\\n\\ttrigger={(props) => <Button {...props}>Open</Button>}\\n/>;\\n```\\n\\n## When not to use it\\n\\n- **An element that is in the top layer but is not a layer for the user.** For example, a drag\\n preview that must paint above the page for one frame. It does not take Escape or close on an\\n outside press.\\n- **Code without React.** The `@atlaskit/top-layer` primitives are React components and hooks.\\n\\nAn `eslint-disable` comment silences this rule. In the Atlassian Frontend Monorepo, the ratchet \\\"Do\\nnot disable @atlaskit/design-system/no-native-popover-or-dialog (AFM-wide)\\\" counts these comments,\\nand `'off'` for this rule in an ESLint config, so a new one fails ratcheting. For a real exception,\\ngive a reason after `--` in the disable comment, and add the file to the ratchet's `excluded` list\\nin `platform/monorepo.config/tasks/global-ratcheting/rules/no-native-popover-or-dialog.ts` with an\\nowner and a reason.\\n\"}",
193
+ ruleName: 'no-native-popover-or-dialog',
194
+ description: 'Do not use a native `popover` or `<dialog>` element. Use a Design System component. If no Design'
187
195
  }, {
188
196
  content: "{\"ruleName\":\"no-nested-styles\",\"description\":\"Disallows using nested styles. Nested styles can change unexpectedly when child markup changes and\",\"content\":\"# no-nested-styles\\n\\nDisallows using nested styles. Nested styles can change unexpectedly when child markup changes and\\nresult in duplicates when extracting to CSS.\\n\\n## Examples\\n\\nThis rule checks for nested styles inside `css` objects. This rule has no options.\\n\\n### Incorrect\\n\\n```js\\ncss({\\n\\tdiv: {\\n\\t\\tcolor: 'red',\\n\\t},\\n});\\n```\\n\\n```js\\ncss({\\n\\t'@media (min-width: 480px)': {\\n\\t\\tcolor: 'red',\\n\\t},\\n});\\n```\\n\\n### Correct\\n\\n```js\\ncss({\\n\\tcolor: 'red',\\n\\t':hover': {\\n\\t\\tcolor: 'black',\\n\\t},\\n});\\n```\\n\\nUse canonical typed media-query keys:\\n\\n```tsx\\nimport { css } from '@atlaskit/css';\\nimport type MediaAboveXs from '@atlaskit/css/at-rules/media-above-xs';\\n\\ncss({\\n\\t['@media (min-width: 30rem)' satisfies MediaAboveXs]: {\\n\\t\\tcolor: 'red',\\n\\t},\\n});\\n```\\n\"}",
189
197
  ruleName: 'no-nested-styles',
@@ -193,9 +201,9 @@ export var lintRulesMcpStructuredContent = [{
193
201
  ruleName: 'no-physical-properties',
194
202
  description: 'Disallows using physical properties. Physical properties prevent correct support for different'
195
203
  }, {
196
- content: '{"ruleName":"no-placeholder","description":"Placeholders are inherently inaccessible and should not be used. Instead, information about the type","content":"# no-placeholder\\n\\nPlaceholders are inherently inaccessible and should not be used. Instead, information about the type\\nor formatting of a value should be included in a helper message that is associated to the input.\\nThis can be done natively in Atlaskit forms using the form\'s field and messaging components, like\\n[this example](https://atlassian.design/components/form/examples#building-a-form) in our form\'s\\ndocumentation.\\n\\nAn exception to this rule is that placeholder text can be used in search fields if it’s accompanied\\nby an icon and accessible label. This ensures that people using assistive technologies understand\\nwhat type of field it is.\\n\\n## Examples\\n\\nThis rule will find violations for when a placeholder is used on an input element.\\n\\n### Incorrect\\n\\n```jsx\\n<input id=\\"name\\" name=\\"username\\" type=\\"text\\" placeholder=\\"FooBarBaz\\" />\\n ^^^^^^^^^^^ `placeholder` prop should not be used\\n```\\n\\n```jsx\\nimport Textfield from \'@atlaskit/textfield\';\\n\\n<Textfield placeholder=\\"FooBarBaz\\">\\n ^^^^^^^^^^^ `placeholder` prop should not be used\\n```\\n\\n```jsx\\nimport Form, { Field, FormFooter } from \'@atlaskit/form\';\\nimport Textarea from \'@atlaskit/textarea\';\\n\\nexport default function Example(): React.JSX.Element {\\n return (\\n <Form onSubmit={(formState: unknown) => console.log(\'form submitted\', formState)}>\\n <Field label=\\"Comments\\" name=\\"comments\\">\\n {({ fieldProps }) => (\\n <Textfield\\n placeholder=\\"Include any thoughts you have about the above blog post.\\"\\n ^^^^^^^^^^^ `placeholder` prop should not be used\\n {...fieldProps}\\n />\\n )}\\n </Field>\\n <FormFooter>\\n <Button type=\\"submit\\" appearance=\\"primary\\">\\n Submit\\n </Button>\\n </FormFooter>\\n </Form>\\n );\\n}\\n```\\n\\n```jsx\\nimport Form, { Field, FormFooter } from \'@atlaskit/form\';\\nimport Textarea from \'@atlaskit/textarea\';\\n\\nexport default function Example(): React.JSX.Element {\\n return (\\n <Form onSubmit={(formState: unknown) => console.log(\'form submitted\', formState)}>\\n <Field\\n label=\\"Comments\\"\\n name=\\"comments\\"\\n component={({ fieldProps }) => (\\n <Textfield\\n placeholder=\\"Include any thoughts you have about the above blog post.\\"\\n ^^^^^^^^^^^ `placeholder` prop should not be used\\n {...fieldProps}\\n />\\n )}\\n />\\n <FormFooter>\\n <Button type=\\"submit\\" appearance=\\"primary\\">\\n Submit\\n </Button>\\n </FormFooter>\\n </Form>\\n );\\n}\\n```\\n\\n### Correct\\n\\n```jsx\\n<input id=\\"name\\" name=\\"username\\" type=\\"text\\" aria-describedby=\\"name__helper\\" />\\n<p id=\\"name__helper\\">Usernames should be over 8 characters and include upper- and lower-case characters. For example, \\"FooBarBaz\\"</p>\\n```\\n\\n```jsx\\nimport Textfield from \'@atlaskit/textfield\';\\n\\n<Textfield id=\\"name\\" name=\\"username\\" aria-describedby=\\"name__helper\\" />\\n<p id=\\"name__helper\\">Usernames should be over 8 characters and include upper- and lower-case characters. For example, \\"FooBarBaz\\"</p>\\n```\\n\\n```jsx\\nimport Form, { Field, FormFooter, HelperMessage, MessageWrapper } from \'@atlaskit/form\';\\nimport Textarea from \'@atlaskit/textarea\';\\n\\nexport default function Example(): React.JSX.Element {\\n return (\\n <Form onSubmit={(formState: unknown) => console.log(\'form submitted\', formState)}>\\n <Field label=\\"Comments\\" name=\\"comments\\">\\n {({ fieldProps }) => (\\n <Fragment>\\n <Textfield {...fieldProps} />\\n <MessageWrapper>\\n <HelperMessage>Include any thoughts you have about the above blog post.</HelperMessage>\\n </MessageWrapper>\\n </Fragment>\\n )}\\n </Field>\\n <FormFooter>\\n <Button type=\\"submit\\" appearance=\\"primary\\">\\n Submit\\n </Button>\\n </FormFooter>\\n </Form>\\n );\\n}\\n```\\n\\n```jsx\\nimport Form, { Field, FormFooter } from \'@atlaskit/form\';\\nimport Textarea from \'@atlaskit/textarea\';\\n\\nexport default function Example(): React.JSX.Element {\\n return (\\n <Form onSubmit={(formState: unknown) => console.log(\'form submitted\', formState)}>\\n <Field\\n label=\\"Comments\\"\\n name=\\"comments\\"\\n component={({ fieldProps }) => (\\n <Textfield {...fieldProps} />\\n )}\\n helperMessage=\\"Include any thoughts you have about the above blog post.\\"\\n />\\n <FormFooter>\\n <Button type=\\"submit\\" appearance=\\"primary\\">\\n Submit\\n </Button>\\n </FormFooter>\\n </Form>\\n );\\n}\\n```\\n"}',
204
+ content: '{"ruleName":"no-placeholder","description":"Move input instructions out of `placeholder` into persistent helper text. Keep the input\'s visible","content":"# no-placeholder\\n\\nMove input instructions out of `placeholder` into persistent helper text. Keep the input\'s visible\\nlabel and existing `aria-describedby` associations. Search fields can use a placeholder when they\\nalso have an icon and an accessible label; see the rule options before changing a search experience.\\n\\n## Incorrect\\n\\n```jsx\\n<input name=\\"username\\" placeholder=\\"At least eight characters\\" />\\n```\\n\\n## Correct\\n\\nFor a native input, give the helper an id and reference it alongside any existing description ids:\\n\\n```jsx\\n<>\\n\\t<label htmlFor=\\"username\\">Username</label>\\n\\t<input id=\\"username\\" name=\\"username\\" aria-describedby=\\"username-help\\" />\\n\\t<p id=\\"username-help\\">Use at least eight characters.</p>\\n</>\\n```\\n\\nFor Field\'s `component` API, use `helperMessage` and preserve the supplied `fieldProps`:\\n\\n```jsx\\nimport { Field } from \'@atlaskit/form\';\\nimport Textfield from \'@atlaskit/textfield\';\\n\\n<Field\\n\\tname=\\"username\\"\\n\\tlabel=\\"Username\\"\\n\\tcomponent={({ fieldProps }) => <Textfield {...fieldProps} />}\\n\\thelperMessage=\\"Use at least eight characters.\\"\\n/>;\\n```\\n\\nFor the render-prop API, keep HelperMessage within its Field context so its generated helper id\\nmatches the input\'s supplied description ids. Keep MessageWrapper around the messages:\\n\\n```jsx\\nimport { Field, HelperMessage, MessageWrapper } from \'@atlaskit/form\';\\nimport Textfield from \'@atlaskit/textfield\';\\n\\n<Field name=\\"username\\" label=\\"Username\\">\\n\\t{({ fieldProps }) => (\\n\\t\\t<>\\n\\t\\t\\t<Textfield {...fieldProps} />\\n\\t\\t\\t<MessageWrapper>\\n\\t\\t\\t\\t<HelperMessage>Use at least eight characters.</HelperMessage>\\n\\t\\t\\t</MessageWrapper>\\n\\t\\t</>\\n\\t)}\\n</Field>;\\n```\\n"}',
197
205
  ruleName: 'no-placeholder',
198
- description: 'Placeholders are inherently inaccessible and should not be used. Instead, information about the type'
206
+ description: "Move input instructions out of `placeholder` into persistent helper text. Keep the input's visible"
199
207
  }, {
200
208
  content: "{\"ruleName\":\"no-pseudo-class-in-select-styles\",\"description\":\"This ESLint rule disallows pseudo classes in the `styles` prop for `@atlaskit/select` component.\",\"content\":\"# no-pseudo-class-in-select-styles\\n\\nThis ESLint rule disallows pseudo classes in the `styles` prop for `@atlaskit/select` component.\\nInstead, developers should use the `components` API with `xcss` props for styling pseudo-states.\\n\\n### Incorrect\\n\\n```tsx\\nimport Select from '@atlaskit/select';\\n\\n// ❌ Inline styles with pseudo-class\\n<Select\\n\\tstyles={{\\n\\t\\tcontrol: (base) => ({\\n\\t\\t\\t...base,\\n\\t\\t\\t':hover': { backgroundColor: 'blue' },\\n\\t\\t}),\\n\\t}}\\n/>;\\n\\n// ❌ Variable-defined styles with pseudo-class\\nconst selectStyles = {\\n\\tcontrol: (base) => ({\\n\\t\\t...base,\\n\\t\\t':focus': { borderColor: 'red' },\\n\\t}),\\n};\\n<Select styles={selectStyles} />;\\n\\n// ❌ Pseudo class in spread operation\\nconst styles = {\\n\\t':hover': { backgroundColor: 'green' },\\n};\\n\\n<Select\\n\\tstyles={{\\n\\t\\toption: (base) => ({\\n\\t\\t\\t...base,\\n\\t\\t\\t...styles,\\n\\t\\t}),\\n\\t}}\\n/>;\\n```\\n\\n### Correct\\n\\n```tsx\\n// ✅ Use normal CSS properties without pseudo-classes\\nimport Select from '@atlaskit/select';\\n\\n<Select\\n\\tstyles={{\\n\\t\\tcontrol: (base) => ({\\n\\t\\t\\t...base,\\n\\t\\t\\tbackgroundColor: 'white',\\n\\t\\t\\tborderColor: 'gray',\\n\\t\\t}),\\n\\t}}\\n/>;\\n\\n// ✅ Use components API with xcss prop\\nimport { cssMap } from '@compiled/react';\\nimport Select, { components } from '@atlaskit/select';\\n\\nconst controlStyles = cssMap({\\n\\troot: {\\n\\t\\t'&:hover': {\\n\\t\\t\\tbackgroundColor: 'white',\\n\\t\\t},\\n\\t},\\n});\\n\\n<Select\\n\\tcomponents={{\\n\\t\\tControl: (props) => <components.Control {...props} xcss={controlStyles.root} />,\\n\\t}}\\n/>;\\n```\\n\"}",
201
209
  ruleName: 'no-pseudo-class-in-select-styles',
@@ -212,6 +220,14 @@ export var lintRulesMcpStructuredContent = [{
212
220
  content: "{\"ruleName\":\"no-styled-tagged-template-expression\",\"description\":\"Disallows any `styled` tagged template expressions that originate from a CSS-in-JS library,\",\"content\":\"# no-styled-tagged-template-expression\\n\\nDisallows any `styled` tagged template expressions that originate from a CSS-in-JS library,\\nincluding `@atlaskit/css`, `@compiled/react`, Emotion, and `styled-components`.\\n\\nTagged template expressions are difficult to parse correctly (which can lead to more frequent build\\nfailures or invalid CSS generation), have limited type safety, and lack syntax highlighting. These\\nproblems can be avoided by using the preferred call expression syntax instead.\\n\\nThe `--fix` option on the command line automatically fixes problems reported by this rule.\\n\\n## Examples\\n\\n### Incorrect\\n\\n```js\\nimport { styled } from '@compiled/react';\\n\\nconst InlinedStyles = styled.div`\\n\\tcolor: blue;\\n`;\\n\\nconst MultilineStyles = styled.div`\\n\\tcolor: blue;\\n\\tfont-weight: 500;\\n`;\\n\\nconst ComposedStyles = styled(InlinedStyles)`\\n\\tfont-weight: 500;\\n`;\\n\\nconst DynamicStyles = styled.div`\\n\\tcolor: ${(props) => props.color};\\n\\t${(props) => (props.disabled ? 'opacity: 0.8' : 'opacity: 1')}\\n`;\\n```\\n\\n### Correct\\n\\n```js\\nimport { styled } from '@compiled/react';\\n\\nconst InlinedStyles = styled.div({\\n\\tcolor: 'blue',\\n});\\n\\nconst MultilineStyles = styled.div({\\n\\tcolor: 'blue',\\n\\tfontWeight: 500,\\n});\\n\\nconst ComposedStyles = styled(InlinedStyles)({\\n\\tfontWeight: 500,\\n});\\n\\nconst DynamicStyles = styled.div(\\n\\t{\\n\\t\\tcolor: (props) => props.color,\\n\\t},\\n\\t(props) => (props.disabled ? 'opacity: 0.8' : 'opacity: 1'),\\n);\\n```\\n\\n## Options\\n\\n### importSources\\n\\nBy default, this rule will check `styled` usages from:\\n\\n- `@atlaskit/css`\\n- `@atlaskit/primitives`\\n- `@compiled/react`\\n- `@emotion/react`\\n- `@emotion/core`\\n- `@emotion/styled`\\n- `styled-components`\\n\\nTo change this list of libraries, you can define a custom set of `importSources`, which accepts an\\narray of package names (strings).\\n\\n```tsx\\n// [{ importSources: ['other-lib'] }]\\n\\nimport { styled } from 'other-lib';\\n\\n// Invalid!\\nexport const Component = styled.div``;\\n```\\n\\n## Limitations\\n\\n- Comments are not fixable.\\n- Component selectors are not fixable for `styled-components`.\\n\\nDo not migrate to this object syntax manually, it is invalid `styled-components`.\\n\\n```tsx\\nconst Button = styled.button``;\\nconst Wrapper = styled.div({\\n color: 'red',\\n [`${Button}`]: {\\n color: 'blue',\\n },\\n});\\n<Wrapper><Button /><Wrapper>\\n```\\n\\nInstead, style the button directly—make it clear that you're styling that button.\\n\\n```tsx\\nconst buttonStyles = css({ color: 'blue' });\\nconst Wrapper = styled.div({\\n\\tcolor: 'red',\\n});\\n\\n<Wrapper>\\n\\t<button css={buttonStyles} />\\n</Wrapper>;\\n```\\n\\nIf that's not feasible, you can use data attributes, but these will result in failing the UI Styling\\nStandard around nested styles, pushing the error down the road.\\n\\n```tsx\\nconst Wrapper = styled.div({\\n\\tcolor: 'red',\\n\\t'[data-component-selector=\\\"my.button\\\"]': {\\n\\t\\tcolor: 'blue',\\n\\t},\\n});\\n\\n<Wrapper>\\n\\t<button data-component-selector=\\\"my.button\\\" />\\n</Wrapper>;\\n```\\n\"}",
213
221
  ruleName: 'no-styled-tagged-template-expression',
214
222
  description: 'Disallows any `styled` tagged template expressions that originate from a CSS-in-JS library,'
223
+ }, {
224
+ content: "{\"ruleName\":\"no-third-party-focus-traps\",\"description\":\"Do not use a third-party focus trap library, such as `react-focus-lock` or `focus-trap`. Design\",\"content\":\"# no-third-party-focus-traps\\n\\nDo not use a third-party focus trap library, such as `react-focus-lock` or `focus-trap`. Design\\nSystem layering components manage focus for you. If no Design System component fits, use\\n`@atlaskit/top-layer`.\\n\\nLayers are moving to the browser\\n[top layer](https://developer.mozilla.org/en-US/docs/Glossary/Top_layer). A focus trap from another\\nlibrary does not know about layers in the top layer:\\n\\n- It can pull focus out of a Design System layer that opens outside the trap, such as a flag, or a\\n modal dialog that another part of the page opens.\\n- Around a layer that is not in the top layer, it does not contain the content that moves to the top\\n layer. Tab can move into or out of the trapped region.\\n- It repeats what a modal `<dialog>` already does. A modal dialog makes the rest of the page inert,\\n and the Design System keeps focus inside the dialog.\\n\\nDesign System layers own their focus:\\n\\n- `Dialog` from `@atlaskit/top-layer`, and components that use it such as\\n [modal-dialog](https://atlassian.design/components/modal-dialog), keep focus inside the dialog and\\n make the rest of the page inert.\\n- `Popover` with `role=\\\"dialog\\\"` keeps Tab and Shift+Tab inside the popover.\\n- Both put focus in the layer when it opens. When it closes, `Dialog` always gives focus back, and\\n `Popover` gives focus back unless the user pressed outside it.\\n\\nUse, in this order:\\n\\n1. A Design System component:\\n - Overlays: [popup](https://atlassian.design/components/popup),\\n [inline-dialog](https://atlassian.design/components/inline-dialog)\\n - Messaging: [modal-dialog](https://atlassian.design/components/modal-dialog),\\n [drawer](https://atlassian.design/components/drawer),\\n [spotlight](https://atlassian.design/components/spotlight)\\n - Forms and inputs: [dropdown-menu](https://atlassian.design/components/dropdown-menu),\\n [select](https://atlassian.design/components/select)\\n2. `@atlaskit/top-layer`, only if no Design System component fits: `Dialog`, or `Popover` with\\n `role=\\\"dialog\\\"`.\\n\\n## Examples\\n\\nThis rule marks each module that a file loads from a focus trap library, as a whole package or a\\nsubpath:\\n\\n- `import` and `import type` declarations, and `import 'module'`\\n- `export … from 'module'`\\n- `import('module')`\\n- `require('module')`\\n\\nThese libraries are marked: `focus-lock`, `focus-trap`, `focus-trap-react`, `react-focus-lock`,\\n`react-focus-on`, `react-focus-trap`.\\n\\n### Not covered\\n\\n- Focus traps that you write yourself, such as a `keydown` listener that moves focus.\\n- Code that makes the rest of the page inert with the `inert` attribute or `aria-hidden`.\\n- `jest.mock('module')` and `vi.mock('module')`. A mock does not trap focus.\\n- Specifiers that are only known at runtime, such as `import(name)`.\\n- TypeScript `import name = require('module')`.\\n\\n### Incorrect\\n\\n```tsx\\nimport FocusLock from 'react-focus-lock';\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\nimport { createFocusTrap } from 'focus-trap';\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\nimport type { ReactFocusLockProps } from 'react-focus-lock/interfaces';\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\nconst FocusTrap = require('focus-trap-react');\\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n```\\n\\n### Correct\\n\\n```tsx\\nimport ModalDialog, { ModalBody, ModalHeader, ModalTitle } from '@atlaskit/modal-dialog';\\n\\n<ModalDialog onClose={onClose}>\\n\\t<ModalHeader>\\n\\t\\t<ModalTitle>Settings</ModalTitle>\\n\\t</ModalHeader>\\n\\t<ModalBody>{children}</ModalBody>\\n</ModalDialog>;\\n```\\n\\n## When not to use it\\n\\n- **A focus region that is not a layer.** For example, a full screen presentation mode that is part\\n of the page. Make sure that no Design System layer can open outside the region while it traps\\n focus.\\n- **A Design System package that wraps a library.** For example, the legacy path of a Design System\\n layering component.\\n\\nAn `eslint-disable` comment silences this rule. In the Atlassian Frontend Monorepo, the ratchet \\\"Do\\nnot disable @atlaskit/design-system/no-third-party-focus-traps (AFM-wide)\\\" counts these comments,\\nand `'off'` for this rule in an ESLint config, so a new one fails ratcheting. For a real exception,\\ngive a reason after `--` in the disable comment, and add the file to the ratchet's `excluded` list\\nin `platform/monorepo.config/tasks/global-ratcheting/rules/no-third-party-focus-traps.ts` with an\\nowner and a reason.\\n\"}",
225
+ ruleName: 'no-third-party-focus-traps',
226
+ description: 'Do not use a third-party focus trap library, such as `react-focus-lock` or `focus-trap`. Design'
227
+ }, {
228
+ content: "{\"ruleName\":\"no-third-party-layering\",\"description\":\"Do not use a third-party layering library, such as Popper.js, Floating UI, Tippy or Radix dialogs\",\"content\":\"# no-third-party-layering\\n\\nDo not use a third-party layering library, such as Popper.js, Floating UI, Tippy or Radix dialogs\\nand popovers. Use a Design System component. If no Design System component fits, use\\n`@atlaskit/top-layer`.\\n\\nLayers are moving to the browser\\n[top layer](https://developer.mozilla.org/en-US/docs/Glossary/Top_layer). Design System layers share\\none layer stack. A layer that another library builds is not in that stack:\\n\\n- It usually renders in a portal with a `z-index`. Every top layer surface paints above it, at any\\n `z-index`. Inside a modal dialog, it is also inert and hidden behind the backdrop.\\n- It handles Escape and outside presses with its own listeners. One press of Escape can close it and\\n the Design System layer under it.\\n\\nDesign System components also give you focus management, placement, a fallback for browsers without\\nCSS anchor positioning, and testing utilities.\\n\\nUse, in this order:\\n\\n1. A Design System component:\\n - Overlays: [popup](https://atlassian.design/components/popup),\\n [tooltip](https://atlassian.design/components/tooltip),\\n [inline-dialog](https://atlassian.design/components/inline-dialog)\\n - Messaging: [modal-dialog](https://atlassian.design/components/modal-dialog),\\n [drawer](https://atlassian.design/components/drawer),\\n [flag](https://atlassian.design/components/flag),\\n [spotlight](https://atlassian.design/components/spotlight)\\n - Forms and inputs: [dropdown-menu](https://atlassian.design/components/dropdown-menu),\\n [select](https://atlassian.design/components/select),\\n [datetime-picker](https://atlassian.design/components/datetime-picker)\\n2. `@atlaskit/top-layer`, only if no Design System component fits. `Popover` with\\n `useAnchoredPopover` replaces a positioning library.\\n\\n## Examples\\n\\nThis rule marks each module that a file loads from a layering library, as a whole package or a\\nsubpath:\\n\\n- `import` and `import type` declarations, and `import 'module'`\\n- `export … from 'module'`\\n- `import('module')`\\n- `require('module')`\\n\\nThese libraries are marked:\\n\\n- Positioning: `@floating-ui/*`, `@popperjs/core`, `popper.js`, `react-laag`, `react-popper`,\\n `react-tether`, `tether`\\n- Popovers and tooltips: `@rc-component/tooltip`, `@rc-component/trigger`, `@react-aria/overlays`,\\n `@tippyjs/react`, `rc-tooltip`, `rc-trigger`, `react-overlays`, `react-popover`,\\n `react-popper-tooltip`, `react-tiny-popover`, `react-tooltip`, `tippy.js`\\n- Dialogs and portals: `react-modal`, `react-portal`\\n- Layering packages from headless component libraries: `@radix-ui/react-alert-dialog`,\\n `@radix-ui/react-context-menu`, `@radix-ui/react-dialog`, `@radix-ui/react-dropdown-menu`,\\n `@radix-ui/react-hover-card`, `@radix-ui/react-menubar`, `@radix-ui/react-popover`,\\n `@radix-ui/react-popper`, `@radix-ui/react-portal`, `@radix-ui/react-select`,\\n `@radix-ui/react-tooltip`, `@reach/combobox`, `@reach/dialog`, `@reach/listbox`,\\n `@reach/menu-button`, `@reach/popover`, `@reach/tooltip`\\n\\n### Not covered\\n\\n- `@atlaskit/popper`, `@atlaskit/portal` and `@atlaskit/layering`. These are Design System packages.\\n- General component libraries that also have layers, such as Material UI or Headless UI.\\n- `jest.mock('module')` and `vi.mock('module')`. A mock does not render a layer.\\n- Specifiers that are only known at runtime, such as `import(name)`.\\n- TypeScript `import name = require('module')`.\\n\\n### Incorrect\\n\\n```tsx\\nimport { usePopper } from 'react-popper';\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\nimport { computePosition } from '@floating-ui/dom';\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\nimport type { Instance } from '@popperjs/core';\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\nimport * as Popover from '@radix-ui/react-popover';\\n^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\\n\\nconst tippy = await import('tippy.js');\\n ^^^^^^^^^^^^^^^^^^\\n\\nconst Modal = require('react-modal');\\n ^^^^^^^^^^^^^^^^^^^^^^\\n```\\n\\n### Correct\\n\\n```tsx\\nimport Popup from '@atlaskit/popup';\\nimport Tooltip from '@atlaskit/tooltip';\\n\\n<Popup\\n\\tisOpen={isOpen}\\n\\tonClose={onClose}\\n\\tcontent={() => <Menu />}\\n\\ttrigger={(props) => <Button {...props}>Open</Button>}\\n/>;\\n\\n<Tooltip content=\\\"Save\\\">\\n\\t{(props) => <IconButton {...props} label=\\\"Save\\\" icon={SaveIcon} />}\\n</Tooltip>;\\n```\\n\\n## When not to use it\\n\\n- **A Design System package that wraps a library.** For example, `@atlaskit/popper` wraps Popper.js\\n for its legacy path.\\n- **Positioning for something that is not a layer.** For example, a drag preview or a measuring\\n helper that never takes focus, Escape or an outside press.\\n\\nAn `eslint-disable` comment silences this rule. In the Atlassian Frontend Monorepo, the ratchet \\\"Do\\nnot disable @atlaskit/design-system/no-third-party-layering (AFM-wide)\\\" counts these comments, and\\n`'off'` for this rule in an ESLint config, so a new one fails ratcheting. For a real exception, give\\na reason after `--` in the disable comment, and add the file to the ratchet's `excluded` list in\\n`platform/monorepo.config/tasks/global-ratcheting/rules/no-third-party-layering.ts` with an owner\\nand a reason.\\n\"}",
229
+ ruleName: 'no-third-party-layering',
230
+ description: 'Do not use a third-party layering library, such as Popper.js, Floating UI, Tippy or Radix dialogs'
215
231
  }, {
216
232
  content: '{"ruleName":"no-to-match-snapshot","description":"This rule disallows the use of Jest snapshot matchers in unit tests:","content":"# no-to-match-snapshot\\n\\nThis rule disallows the use of Jest snapshot matchers in unit tests:\\n\\n- `toMatchSnapshot()`\\n- `toMatchInlineSnapshot()`\\n\\nUse explicit assertions instead (for example `toEqual`, `toMatchObject`, `toContain`, or Testing\\nLibrary assertions like `toHaveTextContent`).\\n\\n## Examples\\n\\n### Incorrect\\n\\n```tsx\\nexpect(container).toMatchSnapshot();\\nexpect(container).toMatchSnapshot(\'snapshot-name\');\\nexpect(screen.getByTestId(\'test\')).toMatchSnapshot();\\n```\\n\\n### Correct\\n\\n```tsx\\nexpect(container).toEqual(expect.any(HTMLElement));\\nexpect(container.querySelector(\'span\')).not.toBeNull();\\n\\n// Testing Library examples\\nexpect(screen.getByText(\'test\')).toBeInTheDocument();\\nexpect(screen.getByTestId(\'my-thing\')).toHaveTextContent(\'test\');\\n```\\n\\n## Rationale\\n\\nSnapshot matchers are intentionally disallowed in unit tests to avoid brittle, hard-to-review\\nbaselines.\\n\\nInstead of snapshots, assert on the specific behavior you care about (text, attributes, structure,\\nand key style properties) using explicit assertions.\\n\\nIf you’re migrating an existing snapshot-based test, a good approach is:\\n\\n- replace snapshots with focused `toEqual` / `toMatchObject` assertions for data objects\\n- prefer Testing Library queries/assertions for UI behavior\\n- if you need to validate styles, assert on specific resolved style properties rather than a whole\\n serialized blob\\n\\n## When not to use it\\n\\nThis rule should be enabled for unit test files to enforce the snapshot-ban policy across the\\ncodebase.\\n\\n> Note: ESLint rule fixture tests may still include snapshot matcher examples because they exist to\\n> validate the lint rule behavior.\\n"}',
217
233
  ruleName: 'no-to-match-snapshot',
@@ -229,7 +245,7 @@ export var lintRulesMcpStructuredContent = [{
229
245
  ruleName: 'no-unsafe-style-overrides',
230
246
  description: "Unsafe style overrides cause friction and incidents when internals of the component you're"
231
247
  }, {
232
- content: '{"ruleName":"no-unsupported-drag-and-drop-libraries","description":"We encourage the use of Pragmatic drag and drop to power all drag and drop experiences - from table","content":"# no-unsupported-drag-and-drop-libraries\\n\\nWe encourage the use of Pragmatic drag and drop to power all drag and drop experiences - from table\\nto external files. Pragmatic drag and drop is a performance optimised drag and drop framework that\\nhas been designed to power any drag and drop experience on any tech stack. Please avoid using\\nalternative drag and drop libraries as it will lead to poorer performance, increased maintenance\\ncosts, (likely) worse accessibility and fragmented user experiences. See\\nhttps://staging.atlassian.design/components/pragmatic-drag-and-drop/\\n\\n## Examples\\n\\nLibraries such as `react-beautiful-dnd` and `@atlassian/jira-dnd` that are no longer supported, as\\nwell as external libraries such as `react-dnd` and `react-sortable-hoc`.\\n\\n### Incorrect\\n\\n```ts\\nimport { DraggableLocation } from \'react-beautiful-dnd\';\\n ^^^^^^^^^^^^^^^^^^^\\n\\nimport { useDrag } from \'react-dnd\'\\n ^^^^^^^^^\\n```\\n"}',
248
+ content: '{"ruleName":"no-unsupported-drag-and-drop-libraries","description":"We encourage the use of Pragmatic drag and drop to power all drag and drop experiences - from table","content":"# no-unsupported-drag-and-drop-libraries\\n\\nWe encourage the use of Pragmatic drag and drop to power all drag and drop experiences - from table\\nto external files. Pragmatic drag and drop is a performance optimised drag and drop framework that\\nhas been designed to power any drag and drop experience on any tech stack. Please avoid using\\nalternative drag and drop libraries as it will lead to poorer performance, increased maintenance\\ncosts, (likely) worse accessibility and fragmented user experiences. See\\nhttps://atlassian.design/components/pragmatic-drag-and-drop/\\n\\n## Examples\\n\\nLibraries such as `react-beautiful-dnd` and `@atlassian/jira-dnd` that are no longer supported, as\\nwell as external libraries such as `react-dnd` and `react-sortable-hoc`.\\n\\n### Incorrect\\n\\n```ts\\nimport { DraggableLocation } from \'react-beautiful-dnd\';\\n ^^^^^^^^^^^^^^^^^^^\\n\\nimport { useDrag } from \'react-dnd\'\\n ^^^^^^^^^\\n```\\n"}',
233
249
  ruleName: 'no-unsupported-drag-and-drop-libraries',
234
250
  description: 'We encourage the use of Pragmatic drag and drop to power all drag and drop experiences - from table'
235
251
  }, {
@@ -325,7 +341,7 @@ export var lintRulesMcpStructuredContent = [{
325
341
  ruleName: 'use-primitives-text',
326
342
  description: 'Using primitives allows you to delete bespoke component code and replace it with ready made'
327
343
  }, {
328
- content: "{\"ruleName\":\"use-should-render-to-parent\",\"description\":\"Popups and dropdown menus render to portals by default. This puts their content outside of the\",\"content\":\"# use-should-render-to-parent\\n\\nPopups and dropdown menus render to portals by default. This puts their content outside of the\\nstandard DOM order which creates accessibility issues for users.\\n\\n## Examples\\n\\nThis rule will indicate user with a recommendation to use the `shouldRenderToParent` prop set to\\n`true`.\\n\\n### Incorrect\\n\\n```tsx\\nimport Popup from '@atlaskit/popup';\\nimport { DropdownMenu } from '@atlaskit/dropdown-menu';\\nimport { DropdownTrigger } from '@atlassian/entry-points/dropdown-trigger';\\nimport { PopupTrigger } from '@atlassian/entry-points/popup-trigger';\\n\\n<Popup>\\n ^^^^^ The default value of `shouldRenderToParent` is `false`. Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Popup content\\n</Popup>\\n\\n<DropdownMenu>\\n ^^^^^^^^^^^^ The default value of `shouldRenderToParent` is `false`. Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Dropdown content\\n</DropdownMenu>\\n\\n<DropdownTrigger>\\n ^^^^^^^^^^^^^^^ The default value of `shouldRenderToParent` is `false`. Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Dropdown content\\n</DropdownTrigger>\\n\\n<PopupTrigger>\\n ^^^^^^^^^^^^^^^ The default value of `shouldRenderToParent` is `false`. Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Popup content\\n</PopupTrigger>\\n\\n<Popup shouldRenderToParent={false}>\\n ^^^^^^^^^^^^^^^^^^^^ Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Popup content\\n</Popup>\\n```\\n\\n### Correct\\n\\n```tsx\\nimport Popup from '@atlaskit/popup';\\nimport { DropdownMenu } from '@atlaskit/dropdown-menu';\\nimport { DropdownTrigger } from '@atlassian/entry-points/dropdown-trigger';\\nimport { PopupTrigger } from '@atlassian/entry-points/popup-trigger';\\n\\n<Popup shouldRenderToParent>\\n Popup content\\n</Popup>\\n\\n<DropdownMenu shouldRenderToParent>\\n Dropdown content\\n</DropdownMenu>\\n\\n<DropdownTrigger shouldRenderToParent>\\n Dropdown content\\n</DropdownTrigger>\\n\\n<PopupTrigger shouldRenderToParent>\\n Popup content\\n</PopupTrigger>\\n```\\n\"}",
344
+ content: "{\"ruleName\":\"use-should-render-to-parent\",\"description\":\"Popups and dropdown menus render to portals by default. This puts their content outside of the\",\"content\":\"# use-should-render-to-parent\\n\\nPopups and dropdown menus render to portals by default. This puts their content outside of the\\nstandard DOM order which creates accessibility issues for users.\\n\\n## Examples\\n\\nThis rule will indicate user with a recommendation to use the `shouldRenderToParent` prop set to\\n`true`.\\n\\n### Incorrect\\n\\n```tsx\\nimport Popup from '@atlaskit/popup';\\nimport { DropdownMenu } from '@atlaskit/dropdown-menu/dropdown-menu';\\nimport { DropdownTrigger } from '@atlassian/entry-points/dropdown-trigger';\\nimport { PopupTrigger } from '@atlassian/entry-points/popup-trigger';\\n\\n<Popup>\\n ^^^^^ The default value of `shouldRenderToParent` is `false`. Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Popup content\\n</Popup>\\n\\n<DropdownMenu>\\n ^^^^^^^^^^^^ The default value of `shouldRenderToParent` is `false`. Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Dropdown content\\n</DropdownMenu>\\n\\n<DropdownTrigger>\\n ^^^^^^^^^^^^^^^ The default value of `shouldRenderToParent` is `false`. Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Dropdown content\\n</DropdownTrigger>\\n\\n<PopupTrigger>\\n ^^^^^^^^^^^^^^^ The default value of `shouldRenderToParent` is `false`. Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Popup content\\n</PopupTrigger>\\n\\n<Popup shouldRenderToParent={false}>\\n ^^^^^^^^^^^^^^^^^^^^ Setting the `shouldRenderToParent` prop to anything other than `true` causes accessibility issues. Only set to `false` as a last resort.\\n Popup content\\n</Popup>\\n```\\n\\n### Correct\\n\\n```tsx\\nimport Popup from '@atlaskit/popup';\\nimport { DropdownMenu } from '@atlaskit/dropdown-menu/dropdown-menu';\\nimport { DropdownTrigger } from '@atlassian/entry-points/dropdown-trigger';\\nimport { PopupTrigger } from '@atlassian/entry-points/popup-trigger';\\n\\n<Popup shouldRenderToParent>\\n Popup content\\n</Popup>\\n\\n<DropdownMenu shouldRenderToParent>\\n Dropdown content\\n</DropdownMenu>\\n\\n<DropdownTrigger shouldRenderToParent>\\n Dropdown content\\n</DropdownTrigger>\\n\\n<PopupTrigger shouldRenderToParent>\\n Popup content\\n</PopupTrigger>\\n```\\n\"}",
329
345
  ruleName: 'use-should-render-to-parent',
330
346
  description: 'Popups and dropdown menus render to portals by default. This puts their content outside of the'
331
347
  }, {
@@ -333,9 +349,9 @@ export var lintRulesMcpStructuredContent = [{
333
349
  ruleName: 'use-simple-field',
334
350
  description: 'Simple field implementations should be used when extended features or complex implementations are'
335
351
  }, {
336
- content: '{"ruleName":"use-simple-form","description":"Simple form implementations should be used when extended features or complex implementations are not","content":"# use-simple-form\\n\\nSimple form implementations should be used when extended features or complex implementations are not\\nnecessary.\\n\\n## Examples\\n\\nThis rule marks code as a violation when it finds Design System form components that don’t use\\nrender props or only use the `formProps` render prop.\\n\\n### Incorrect\\n\\n```jsx\\nimport { Field, Form } from \'@atlaskit/form\';\\n\\n<Form\\n\\tonSubmit={() => {\\n\\t\\t/* ... */\\n\\t}}\\n>\\n\\t{({ formProps }) => (\\n\\t\\t<form {...formProps}>\\n\\t\\t\\t<Field name=\\"username\\" component={({fieldProps}) => <input {...fieldProps} />}>\\n\\t\\t</form>\\n\\t\\t)}\\n</Form>;\\n```\\n\\n```jsx\\nimport { Field, Form } from \'@atlaskit/form\';\\n\\n<Form\\n\\tonSubmit={() => {\\n\\t\\t/* ... */\\n\\t}}\\n>\\n\\t{({ formProps }) => (\\n\\t\\t<form {...formProps} name=\\"form\\" data-testid=\\"testId\\" data-foo=\\"bar\\">\\n\\t\\t\\t<Field name=\\"username\\" component={({fieldProps}) => <input {...fieldProps} />}>\\n\\t\\t</form>\\n\\t\\t)}\\n</Form>;\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { Field, Form } from \'@atlaskit/form\';\\n\\n<Form\\n\\tonSubmit={() => {\\n\\t\\t/* ... */\\n\\t}}\\n>\\n\\t<Field name=\\"username\\" component={({fieldProps}) => <input {...fieldProps} />}>\\n</Form>;\\n```\\n\\n```jsx\\nimport { Field, Form } from \'@atlaskit/form\';\\n\\n<Form\\n\\tonSubmit={() => {\\n\\t\\t/* ... */\\n\\t}}\\n\\tname=\\"form\\"\\n\\ttestId=\\"testId\\"\\n\\tformProps={{\\n\\t\\t\'data-foo\': \\"bar\\"\\n\\t}}\\n>\\n\\t<Field name=\\"username\\" component={({fieldProps}) => <input {...fieldProps} />}>\\n</Form>;\\n```\\n"}',
352
+ content: '{"ruleName":"use-simple-form","description":"Use Form\'s plain JSX children when the render function only spreads `formProps` onto an HTML form.","content":"# use-simple-form\\n\\nUse Form\'s plain JSX children when the render function only spreads `formProps` onto an HTML form.\\nApply the **Convert form to simple form** editor suggestion when offered; ESLint\'s `--fix` does not\\napply suggestions.\\n\\nThe suggestion preserves string, expression and boolean HTML attributes. It is withheld for custom\\nspreads, references to the removed `formProps` binding, conflicting outer props, and native\\nhandlers, refs or styling/naming props whose meaning differs on Form. The diagnostic still requires\\nreview: move safe attributes to Form\'s supported props or `formProps` object and preserve custom\\nbehavior before removing the render function. Consult\\n`platform/packages/design-system/form/src/form.tsx` for the current API.\\n\\n## Incorrect\\n\\n```jsx\\nimport Form from \'@atlaskit/form\';\\n\\n<Form onSubmit={submit}>\\n\\t{({ formProps }) => (\\n\\t\\t<form {...formProps} name=\\"profile\\" data-owner={owner}>\\n\\t\\t\\t<p>Profile settings</p>\\n\\t\\t</form>\\n\\t)}\\n</Form>;\\n```\\n\\n## Correct\\n\\n```jsx\\nimport Form from \'@atlaskit/form\';\\n\\n<Form onSubmit={submit} name=\\"profile\\" formProps={{ \'data-owner\': owner }}>\\n\\t<p>Profile settings</p>\\n</Form>;\\n```\\n"}',
337
353
  ruleName: 'use-simple-form',
338
- description: 'Simple form implementations should be used when extended features or complex implementations are not'
354
+ description: "Use Form's plain JSX children when the render function only spreads `formProps` onto an HTML form."
339
355
  }, {
340
356
  content: '{"ruleName":"use-spotlight-package","description":"This rule raises a violation for usages of `@atlaskit/onboarding`. This is to assist with the","content":"# use-spotlight-package\\n\\n## Examples\\n\\nThis rule raises a violation for usages of `@atlaskit/onboarding`. This is to assist with the\\nmigration to `@atlaskit/spotlight`.\\n\\n### Incorrect\\n\\n```jsx\\nimport { Spotlight } from \'@atlaskit/onboarding\';\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { Spotlight } from \'@atlaskit/spotlight\';\\n```\\n"}',
341
357
  ruleName: 'use-spotlight-package',
@@ -353,9 +369,9 @@ export var lintRulesMcpStructuredContent = [{
353
369
  ruleName: 'use-tokens-motion',
354
370
  description: 'This rule marks code as violations when a motion duration or easing token should be used. It will'
355
371
  }, {
356
- content: '{"ruleName":"use-tokens-shape","description":"This rule marks code as violations when a shape token should be used. It will auto-fix values that","content":"# use-tokens-shape\\n\\n## Examples\\n\\nThis rule marks code as violations when a shape token should be used. It will auto-fix values that\\ncan be mapped 1:1 with an ADS shape token. Values that can\'t be mapped to a token will still be\\nreported, however no auto-fix will happen.\\n\\n### Incorrect\\n\\n```jsx\\nconst someStyles = css({\\n borderRadius: \'3px\';\\n \\t\\t\\t^^^^^\\n borderWidth: \'2px\';\\n \\t\\t ^^^^^\\n})\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { token } from \'@atlaskit/tokens\'\\n\\nconst someStyles = css({\\n borderRadius: token(\'radius.small\');\\n borderRadius: token(\'border.width.outline\');\\n})\\n```\\n\\nSee the list of available shape tokens on the\\n[ADS website](https://atlassian.design/components/tokens/all-tokens).\\n"}',
372
+ content: '{"ruleName":"use-tokens-shape","description":"Use shape tokens for border radius and border width. This rule offers an autofix only when a value","content":"# use-tokens-shape\\n\\n## Examples\\n\\nUse shape tokens for border radius and border width. This rule offers an autofix only when a value\\nmaps directly to a token; choose the intended shape manually for other values.\\n\\n### Incorrect\\n\\n```jsx\\nconst styles = css({\\n\\tborderRadius: \'3px\',\\n\\tborderWidth: \'2px\',\\n});\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { css } from \'@atlaskit/css\';\\nimport { token } from \'@atlaskit/tokens\';\\n\\nconst styles = css({\\n\\tborderRadius: token(\'radius.small\'),\\n\\tborderWidth: token(\'border.width\'),\\n});\\n```\\n\\nSee the available shape tokens on the\\n[ADS website](https://atlassian.design/components/tokens/all-tokens).\\n"}',
357
373
  ruleName: 'use-tokens-shape',
358
- description: 'This rule marks code as violations when a shape token should be used. It will auto-fix values that'
374
+ description: 'Use shape tokens for border radius and border width. This rule offers an autofix only when a value'
359
375
  }, {
360
376
  content: '{"ruleName":"use-tokens-space","description":"This rule marks code as violations when a space token should be used. It will auto-fix values that","content":"# use-tokens-space\\n\\n## Examples\\n\\nThis rule marks code as violations when a space token should be used. It will auto-fix values that\\ncan be mapped 1:1 with an ADS space token. Values that can\'t be mapped to a token will still be\\nreported, however no auto-fix will happen.\\n\\n### Incorrect\\n\\n```jsx\\nconst someStyles = css({\\n padding: \'8px\';\\n ^^^^^\\n})\\n```\\n\\n### Correct\\n\\n```jsx\\nimport { token } from \'@atlaskit/tokens\'\\n\\nconst someStyles = css({\\n padding: token(\'space.100\');\\n})\\n```\\n\\nSee the list of available space tokens on the\\n[ADS website](https://atlassian.design/foundations/spacing#space-tokens).\\n\\nFor Atlassians:\\n\\n- See the [Token Migration Guide](https://go.atlassian.com/space-token-migration) for instructions\\n on how to migrate to tokens when a suggestion is not provided by the ESLint rule.\\n"}',
361
377
  ruleName: 'use-tokens-space',
@@ -457,7 +473,7 @@ export var lintRulesMcpStructuredContent = [{
457
473
  ruleName: 'no-nested-selectors',
458
474
  description: 'Blocks nested selectors in style declarations.'
459
475
  }, {
460
- content: "{\"ruleName\":\"no-styled\",\"description\":\"Blocks the `styled` API, which creates unnecessary indirection.\",\"content\":\"# no-styled\\n\\nBlocks the `styled` API, which creates unnecessary indirection.\\n\\nThis indirection:\\n\\n- obfuscates which tag is being rendered\\n- adds linting complexity\\n- promotes exported styles\\n- can complicate refactoring\\n\\nUse the `css` API instead. It has better performance and clarity.\\n\\n## Examples\\n\\n### Incorrect\\n\\n```tsx\\nimport styled from 'styled-components';\\n\\nconst Component = styled.div`\\n\\tcolor: red;\\n`;\\nexport default styled.div({ color: 'red' });\\n```\\n\\n```tsx\\nimport styled2 from '@emotion/styled';\\n\\nexport const Component = styled2('div')`…`;\\n```\\n\\n```tsx\\nimport styled from 'styled-components';\\nimport { styled as styled3 } from '@compiled/react';\\n\\nconst Component = styled.div`color: red;`\\nexport const ComponentTwo = styled3(Component)({ … });\\n```\\n\\n```tsx\\nimport styled from 'styled-components';\\n\\nexport default styled.div.attrs((props) => ({ 'data-testid': props.testId }))({\\n\\tcolor: 'red',\\n});\\n```\\n\\n```tsx\\nimport styled from 'styled-components';\\n\\nexport default styled.div.attrs((props) => ({ 'data-testid': props.testId }))`\\n\\tcolor: red;\\n`;\\n```\\n\\n### Correct\\n\\n```tsx\\nimport { css, jsx } from '@emotion/react';\\nimport { token } from '@atlaskit/tokens';\\n\\nconst styles = css({ color: token('color.text.subtlest') });\\n\\nconst Component = ({ children }) => {\\n\\treturn <div css={styles}>{children}</div>;\\n};\\n```\\n\\n```tsx\\nimport { Box, xcss } from '@atlaskit/primitives';\\n\\nconst styles = xcss({\\n\\tcolor: 'color.text.subtlest',\\n});\\n\\nconst Component = ({ children }) => {\\n\\treturn <Box xcss={styles}>{children}</Box>;\\n};\\n```\\n\\n## FAQ\\n\\n### How will I extend like `styled(Button)`?\\n\\nDon't modify the styles of components you don't own, unless they provide an explicit bounded\\ninterface for doing so — such as the `xcss` prop.\\n\\nUse props (excluding `className` which is prohibited) to modify component styles instead.\\n\\nThe Atlassian Design System, for example, no longer supports `styled(Button)` because it is unsafe\\nfor us to evolve the system with.\\n\"}",
476
+ content: "{\"ruleName\":\"no-styled\",\"description\":\"Blocks the `styled` API, which creates unnecessary indirection.\",\"content\":\"# no-styled\\n\\nBlocks the `styled` API, which creates unnecessary indirection.\\n\\nThis indirection:\\n\\n- obfuscates which tag is being rendered\\n- adds linting complexity\\n- promotes exported styles\\n- can complicate refactoring\\n\\nUse module-scoped `cssMap()` or `css()` from `@atlaskit/css` instead, and apply styles directly to\\nthe element. Keep runtime-only values in the `style` prop.\\n\\n## Examples\\n\\n### Incorrect\\n\\n```tsx\\nimport styled from 'styled-components';\\n\\nconst Component = styled.div`\\n\\tcolor: red;\\n`;\\nexport default styled.div({ color: 'red' });\\n```\\n\\n```tsx\\nimport styled2 from '@emotion/styled';\\n\\nexport const Component = styled2('div')`…`;\\n```\\n\\n```tsx\\nimport styled from 'styled-components';\\nimport { styled as styled3 } from '@compiled/react';\\n\\nconst Component = styled.div`color: red;`\\nexport const ComponentTwo = styled3(Component)({ … });\\n```\\n\\n```tsx\\nimport styled from 'styled-components';\\n\\nexport default styled.div.attrs((props) => ({ 'data-testid': props.testId }))({\\n\\tcolor: 'red',\\n});\\n```\\n\\n```tsx\\nimport styled from 'styled-components';\\n\\nexport default styled.div.attrs((props) => ({ 'data-testid': props.testId }))`\\n\\tcolor: red;\\n`;\\n```\\n\\n### Correct\\n\\n```tsx\\n/**\\n * @jsxRuntime classic\\n * @jsx jsx\\n */\\nimport { cssMap, jsx } from '@atlaskit/css';\\nimport { token } from '@atlaskit/tokens';\\n\\nconst styles = cssMap({\\n\\troot: { color: token('color.text.subtlest') },\\n});\\n\\nconst Component = ({ children }) => <div css={styles.root}>{children}</div>;\\n```\\n\\n```tsx\\nimport { cssMap } from '@atlaskit/css';\\nimport { Box } from '@atlaskit/primitives/compiled/box';\\nimport { token } from '@atlaskit/tokens';\\n\\nconst styles = cssMap({\\n\\troot: { color: token('color.text.subtlest') },\\n});\\n\\nconst Component = ({ children }) => <Box xcss={styles.root}>{children}</Box>;\\n```\\n\\n## FAQ\\n\\n### How will I extend like `styled(Button)`?\\n\\nDon't modify the styles of components you don't own, unless they provide an explicit bounded\\ninterface for doing so — such as the `xcss` prop.\\n\\nUse props (excluding `className` which is prohibited) to modify component styles instead.\\n\\nThe Atlassian Design System, for example, no longer supports `styled(Button)` because it is unsafe\\nfor us to evolve the system with.\\n\"}",
461
477
  ruleName: 'no-styled',
462
478
  description: 'Blocks the `styled` API, which creates unnecessary indirection.'
463
479
  }, {