·Updated March 16, 2026
Getting started by role
Start with an existing Axon component, pattern, or token before designing or building a custom solution. Choose the path below for your role.
Designers
- Request access to Axon Figma libraries through #prd-design-team.
- Enable the libraries in Figma: Assets → Team Libraries.
- Start with an Axon component and its variants; use auto layout and the spacing scale rather than recreating a pattern.
- Review Design Tokens for color, typography, and spacing decisions.
Resources: Figma Foundations and the Component Library.
Engineers
- Identify the existing component or pattern in the Components and UX Templates sections.
- Use the documented semantic and component tokens; do not hard-code visual values.
- Preserve the documented keyboard, focus, label, and error behavior as part of the component implementation.
- If no existing pattern fits, validate the use case before introducing a one-off component or token.
Product managers
- Check existing components and patterns before writing a feature scope.
- Use the pattern guidance to decide which workflow and interaction model is appropriate.
- Include the intended component states, validation, empty states, and accessibility expectations in the requirement.
- Use Axon components in prototypes so delivery estimates reflect the system that will be built.
For help finding the right starting point, begin with Components or UX Templates.