Talons is a self-developed project that integrates an LLM model into an applicant tracking system, aiming to reduce the number of resumes HR needs to review from 100 to just 3.
In this project, we built the platform from the ground up, requiring extensive preparation in both communication and materials. Our primary focus was on accelerating the MVP launch while ensuring a sustainable design and seamless collaboration with developers. To maintain clarity and consistency, I took the initiative to implement a design system.
My usual design practice mainly relies on component libraries, and I have never created a design system entirely on my own.
Referencing
Discussing with developers about the main programming language used helps build a design system that is both feasible and easy to code. Using successful examples as a foundation, I modified my design files and components based on these principles.
The two libraries below serve as the foundation for my design system, which I used to modify my design files and components.
ShadCN UI
React-based UI library designed for building flexible, customizable, and accessible web applications. It offers pre-built, modular components that integrate seamlessly with TailwindCSS, allowing for easy styling and customization.
Good Habit
Config Practice
Using a config file minimizes the need for hard coding, allowing developers to directly embed the file into the system. It also helps detect and correct potential errors efficiently
Standardized Naming
A standardized naming pattern reduces token-related misunderstandings, enhance file storage and organization, and simplifies future edits, even after multiple handovers.
Seperate Token Layer
Categorizing tokens into color, number, string, and boolean streamlines system maintenance, enabling designers to make changes based on data type, even if they're new to the system
