As a WD/WB designer and developer, I want to contribute with a new [Name of the component] component to our component library and reuse it in [Name of the app/feature], because it will allow users to [insert use case in the context of the app/feature].

Acceptance criteria

• The [component] is implemented according to the [[ insert link to Figma file | Figma specs]] (which are fully outlined using tokens)
• The component follows the [[ insert link to documentation | component documentation]] and displays the predefined accessible and responsive behaviors
• The [component]'s component-level tokens are created according to the naming convention used to style the component
• The component is displayed in Storybook according to the specifications (see below)
• The component should have browser test implemented.

States

[List of the states that the component should display, mapping the specs]

• Default
• Hover
• Active and/or Focus
• Disabled
• Error
• Warning

Sizes

[Does the component have different sizes? If so, list here]

• Small
• Medium
• Large

Storybook:

• Structure: (Does the component have its own section is Storybook, or should it be nested under one of the existing sections? Are only a "Basic "(Controllable) and "All" pages needed?)
• Behavior: (What should users be able to do with the component in Storybook? What type of behavior should the component display?)
• Controls: (Should users be able to apply specific arguments/properties to the component using the Controls panel? e.g. disable it, replace the label and placeholder text with custom text)

Notes:

[Collect any topics that need discussion with the hike team in this area. Provide a heads-up in case assets are attached]