All micro-internships
Micro-internship brief ≈13h across 3 days — learn Figma components, build, then assemble and prove propagationlow-code

Build a tiny design system in Figma

Real product teams design with components, not pictures. Build a tiny design system in Figma — button, input, and card with variants, AI as your on-call tutor — then prove it works by assembling 2 different app screens from ONLY those components.

AI-assisted DesignDesign Systems

Posted by The AI Internships

The work brief

  1. 01Learn Figma components + variants — free tutorials, with AI as your on-call tutor: when variants or auto layout confuse you, ask, apply the answer, and verify it in the file.
  2. 02Build 3 components: a button (default/hover/disabled variants), an input field (empty/filled/error), and a card.
  3. 03Assemble 2 different screens (e.g. a login screen and a list screen) using only your components.
  4. 04Change one component’s style and show both screens updating automatically — that’s the whole point. Screenshot before/after.

What you’ll produce

4 deliverables

Submission standard

Submit the public Figma link, the 2 assembled screens, and the propagation proof, plus your AI workflow. Also submit a screenshot of your Figma Assets/layers panel showing your components with your account name and today's date.

  • Public view link to your Figma file

    Public view link that opens to a file with real components and working variants (not drawn rectangles) — a dead, private, or component-less file fails.

    Public linkRequired

  • The 2 screens assembled from your components (one image)

    Image uploadRequired

  • Before/after screenshot: one component edit updating both screens

    Image uploadRequired

  • What was hard about components vs. drawing, and when you’d use each

    Written responseRequired

You’ll complete these inside your private workspace.

What you must submit as proof

This brief requires evidence an AI can’t fabricate.

  • Screenshot of your OWN Figma editor with the Assets/layers panel showing your components — account name and today's date visible

    Show the Assets panel with your published components plus your username and system date, backing up the propagation proof.

    Image uploadRequired

Submissions without this evidence cannot be submitted.

Protect other people in your proof. Blur faces, names, phone numbers and email addresses before you upload, and refer to anyone you worked with by role or number ("Listener 1", "the stall owner"). Your proof is only ever used to check your work — it is never published, never appears on your certificate, and is never shown in your public portfolio.

How your work is evaluated

The passing benchmark is 70/100.

Real components

29%

The file contains true components with working variants.

System proof

29%

Both screens are genuinely built from the components and look coherent.

Understanding

14%

The notes show they get WHY systems beat drawings.

Real components, first-party

29%

Auto-fail if the Figma link is dead/private or has no real components, if the assets screenshot is missing, or if the two screens are not genuinely assembled from the components shown.

How we grade your AI usage

30% of your score

Using AI is the point — it’s the skill this certificate proves. You’ll answer three short questions about how you used it: what you asked, what was wrong with its first answer, and what you changed. Specific, honest answers score high. “I pasted the brief and submitted the answer” scores near zero.