Make the next action obvious.
A clear primary action, supporting alternatives and predictable behaviour.
Interactive example
These demonstration actions announce feedback. Connect production buttons to your application. The data-feedback hook belongs to the documentation demo, not the component library.
Code
<div class="button-row"><button class="sk-button" type="button" data-feedback="Primary action selected">Primary action <span aria-hidden="true">→</span></button><button class="sk-button secondary" type="button" data-feedback="Secondary action selected">Secondary action</button><button class="sk-button ghost" type="button" data-feedback="Tertiary action selected">Tertiary action</button><button class="sk-button" type="button" disabled>Unavailable</button></div>Usage
- Choose one primary action per decision area. Use secondary and ghost variants for supporting actions.
- Use a button for an action and an anchor with href for navigation.
- Explain why an important action is unavailable; do not rely only on a disabled control.
- Keep labels concise and specific. Avoid icon-only primary actions.

