Module 01 · The Modern AI Design Stack
Building a Personal Reference Library of Styles
Open lesson + course map
On this lesson
Course outline
Module 1 · The Modern AI Design Stack
Module 2 · Creative Ideation
Module 3 · Brand Asset Production
Module 4 · Client-Ready Deliverables
A reference library should teach you why a design works, preserve source and rights information, and help you brief original work. It should not become a folder of unattributed screenshots or a machine for copying another designer.
// concept
Store Analysis, Not Just Images
For every reference, record:
reference_id | creator/source | URL | accessed date | rights/use note
project type | audience | composition | grid | type behavior | palette
image treatment | material/texture | what works | what not to copyUse four buckets: licensed/owned production assets, public inspiration for analysis only, cultural/research references requiring context, and your own experiments. Never mix them without labels. A moodboard shown to a client should make clear which elements are direction references and which are proposed original assets.
Tag visual properties such as asymmetric-grid, high-contrast-serif, monochrome-product, or dense-urdu-display, rather than only industries like restaurant. This lets you retrieve a useful principle across unrelated jobs.
// worked_example
Worked Example
A designer saves 40 bakery posts. The folder is unusable because filenames and sources are missing. The rebuilt library keeps 12 strong references and analyzes hierarchy, crop, color temperature, spacing, type scale and call-to-action placement.
For a new bakery brief, the designer selects three principles: close product crop, warm neutral field and one high-contrast ordering block. It does not copy the original illustrations or layout. The resulting work can be explained from the client’s problem, not defended as “inspired by Pinterest.”
// concept
Maintain a Monthly Review
Delete duplicates, repair missing sources, move expired licenses out of production, and add your own finished outcomes. Keep a do-not-use tag for references with unclear rights, harmful stereotypes or misleading mockups. The best library becomes more selective over time.
// failure_cases
Failure Cases to Diagnose
6 cases to diagnose
Saving images with no creator or source URL.
Treating public visibility as permission to reuse.
Organizing only by tool or industry.
Mixing client-confidential work with public inspiration.
Prompting with copyrighted/client assets without authorization.
Collecting endlessly and never translating references into principles.
// pakistan_angle
Pakistan Angle
Document the context of truck art, ajrak, regional embroidery, calligraphy and architectural motifs before using them. “Pakistani style” is too broad. Note region, material, meaning and whether commercial adaptation needs permission or specialist review. Avoid reducing living traditions to a generic border pattern.
// hands_on
Hands-On Exercise
5 steps
Create the four library buckets.
Add ten sourced references with rights notes.
Tag each by visual behavior.
Write three transferable principles from one cluster.
Create an original mini-composition using the principles without copying assets.
// completion_rubric
Completion Rubric
5 checks — tick as you verify
// sources
Sources
3 official sources — check every claim yourself