Farhan Shaikh

Aurascape · Aswaat · 2025–Present

Design system — maintenance and expansion log

Two systems, two different skills. At Aurascape I maintain and extend the design system under the main platform — taking the Untitled UI base and growing its components to carry the product. At Aswaat I founded one from zero: tokens, components, and documentation, built alone.

Extending the Library

The work isn't drawing components from scratch — it's extending the Untitled UI base with the properties and states a real product needs. Take the dropdown. The base ships a plain menu — text and a leading icon:

Before · the Untitled UI base (type: GT America)
Main Support
Placeholder
Placeholder
Placeholder
Placeholder

The base — text and a leading icon.

Extended, that same component becomes a configurable surface. Tap the field to open it, then flip any property to reshape the list live:

Dropdown + menu list item — extended for Aurascape (type: GT America)
Label*
Search...esc
Header
Subheader
Info2
PlaceholderLorem
100Label
Info2
PlaceholderLorem
100Label
Info2
PlaceholderLorem
100Label
Subheader
Info2
PlaceholderLorem
100Label
Info2
PlaceholderLorem
100Label

Properties · try me

12 total

Search
Header
Subheader
Checkbox
Leading Icon
Status Dot
Info Badge
Logo Badge
Supporting Text
Count
Label
Trailing Icon

Tap the field, then flip any property.


States

Default

Placeholder

Hover

Placeholder

Focused

Placeholder

Selected

Placeholder

Disabled

Placeholder
  1. One list item, twelve live content slots — checkbox, leading icon, status dot, Info badge, logo badge, supporting text, count, Label tag, trailing icon — plus menu-level search, header, and subheader.
  2. And a full row state set — default, hover, focus, selected, disabled — where the Untitled UI base shipped a single default.

From Zero — The Aswaat System

The other side of the skill: founding a system with nobody to hand it to you — tokens, components, and documentation for a mobile Mushaf app, built alone and configured in Figma to scale past v1.

The Aswaat system
The Aswaat design system cover — a component library for mobile apps with dark and light modes

Rather than screenshot the rest, the pieces below are rendered live from the system's own variables — the semantic color tokens and the Inter type ramp every component inherits:

Foundations — the token layer

Color · semantic tokens

Brand

button-brand-default
#049597
primary-600
#027778

Surface

background-container
#313237
background-object
#484951

Text

text-title
#fdfdfd
text-caption
#d9d9dc

Grey ramp

grey-500
#8d8f9b
grey-700
#484951
grey-800
#313237

Type · Inter

Search for your Riwaayahbody-MD · 14/400
Reset to Hafsaction-SM · 12/600
Kufa · Recitationbody-SM · 12/400
Locationbody-XS · 10/400

Those tokens resolve into components. Here is Sidecar, the Qari and Riwaayah selector, rebuilt from the same values — a genuinely hard bit of domain modelling: a qari can carry several riwaayaat, one is the fixed base, and you compare the rest against it, all inside one dark, space-constrained panel.

Sidecar — the Qari / Riwaayah selector · rebuilt from tokens
القراءات
Search for your Riwaayah
Reset to Hafs
Aasim
Kufa
Hafs
Kufa
Shubah
Kufa
Naafi'
Madinah
Warsh
Madinah
Qaaloon
Madinah
Qari Name
Location
Qari Name
Location
  1. Selected qaris carry primary-600 and expand in place, so you can open several at once and compare across them.
  2. Riwaayaat nest under their qari on a connector line. Hafs is the fixed base layer every reading overlays — its checkbox is locked, which is what Reset to Hafs returns you to.
  3. Checkbox states carry the meaning: locked base, selected reading, and unselected option — with a colored right-edge accent on the selected riwaayaat.