القائمة
Icon usage conventions and semantic mappings. Use when adding, modifying, or choosing icons.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | icons |
| description | Icon usage conventions and semantic mappings. Use when adding, modifying, or choosing icons. |
@radix-ui/react-icons): UI primitives (dropdowns, modals, tables)| Concept | Icon | Import |
|---|---|---|
| Error | MdError | react-icons/md |
| Warning | IoWarningOutline | react-icons/io5 |
| Success | GrStatusGood | react-icons/gr |
| Info | FaRegLightbulb | react-icons/fa |
| Help | BsQuestionCircle | react-icons/bs |
| Close | Cross2Icon | @radix-ui/react-icons |
| Search | FiSearch | react-icons/fi |
| External link | ExternalLinkIcon | @radix-ui/react-icons |
| Settings | GearIcon | @radix-ui/react-icons |
| Copy | LuCopy | react-icons/lu |
| Trash | TrashIcon | @radix-ui/react-icons |
| Chevrons | ChevronDownIcon etc | @radix-ui/react-icons |
| Arrows | ArrowDownIcon etc | @radix-ui/react-icons |
| Filter | GoFilter | react-icons/go |
| Star | GoStar / GoStarFill | react-icons/go |
| User | LuUser | react-icons/lu |
| Reload | ReloadIcon | @radix-ui/react-icons |
| Concept | Icon | Import |
|---|---|---|
| Supply | BsArrowUpCircle | react-icons/bs |
| Deposit | BsArrowUpCircle | react-icons/bs |
| Borrow | BsArrowDownLeftCircle | react-icons/bs |
| Repay | BsArrowUpRightCircle | react-icons/bs |
| Withdraw | BsArrowDownCircle | react-icons/bs |
| Swap | LuArrowRightLeft | react-icons/lu |
| History | GoHistory | react-icons/go |
| Rewards | FiGift | react-icons/fi |
| Fire | HiFire | react-icons/hi2 |
| Morpho | PiButterflyDuotone | react-icons/pi |
| Component | Path |
|---|---|
SpinnerIcon | @/components/icons/SpinnerIcon |
RefetchIcon | @/components/ui/refetch-icon |
TokenIcon | @/components/shared/token-icon |
NetworkIcon | @/components/shared/network-icon |
16-18px inline, 20-24px standaloneArchitecture patterns for organizing feature modules in the codebase. Use when creating new files, brand new features or pages.
Patterns to follow for implementing transaction hooks with tracking. Use when implementing new features interacting with EVM contracts, signing transactions, permit... etc.
Core patterns for data fetching, state management, and user preferences. Use when implementing new features that require getting data from Our APIs, Morpho API, on-chain states or managing shared state.
Core component library and design system patterns. Use when building UI, building new components, new page, using design tokens, or working with the component library.