◐
Read brief, ship frames
T1 · AUTONOMOUSReads Linear ticket, opens new Figma frame in correct page, applies your tokens + components, builds layout, marks "ready for review."
◐
ROLE · R/02 · BUILD TRIBE
A digital Designer that ships actual Figma files.
Not Midjourney spam. Not "AI mockups." A Designer-shaped Cyborg with its own Figma seat in your team, its own Slack handle, its own design system access. It picks up briefs from Linear, opens Figma files, builds frames using your tokens, runs visual review, marks the file ready for dev, and replies to comments.
FROM $599/month
·
SCALES TO $1,599 (lead tier)
·
ONBOARDING 7 days
— 02 / WHAT IT DOES
— CAPABILITIES
Pixel pushing nahi — poori design discipline.
Designer ka kaam screens banane se kahin zyada hai. Briefs read karna, design system maintain, accessibility check, dev handoff, marketing visuals, brand consistency — sab Cyborg karta hai. Har capability ka trust level (T1–T4) saath listed hai.
⌬
Maintain design system
T2 · GUIDEDAdds new components, audits existing for inconsistency, deprecates dead variants, syncs library across files. Documents every change.
▢
Mobile + responsive variants
T1 · AUTONOMOUSAuto-generates mobile (375), tablet (768), desktop (1280, 1440) variants. Respects your breakpoints. Auto-layout always.
⚖
Accessibility audit
T1 · AUTONOMOUSChecks contrast (AA + AAA), focus states, hit areas, label association, alt text. Posts issues directly on the Figma file.
✎
Marketing & brand visuals
T2 · GUIDEDSocial posts, blog hero images, OG cards, presentation decks. Always on-brand. Always exported in the right formats and sizes.
▦
Prototypes & flows
T2 · GUIDEDBuilds clickable prototypes for usability tests. Interaction states, transitions, smart-animate where it helps comprehension.
⚠
Visual regression in PRs
T2 · GUIDEDWatches Chromatic / Percy diffs on dev PRs. Flags off-spec UI before merge. Posts overlay screenshots in the PR.
▤
Dev handoff & specs
T1 · AUTONOMOUSWrites Figma spec annotations devs actually need: spacing, states, edge cases, copy. Replies to dev questions in file comments.
✱
User research synthesis
T2 · GUIDEDReads call transcripts, support tickets, NPS comments. Synthesises themes, drafts personas, suggests design implications.
◆
Iconography & illustration
T2 · GUIDEDCustom icons in your house style. Light spot illustrations. SVG-clean, optimised, exported with proper viewBox and IDs.
⊕
Brand identity work
T3 · APPROVEDLogo refinements, type pairings, color system extensions. Direction-setting decisions always go to the founder/CD for sign-off.
◑
Design QA on staging
T1 · AUTONOMOUSOpens staging URL, compares to Figma frame pixel by pixel, files Linear bugs for any drift. Includes screenshots + spec gap.
TRUST LEVELS ·
T1 Cyborg ships, you can audit later
T2 Cyborg drafts, human reviews before "ready for dev"
T3 Human approves before action runs
T4 Cyborg never acts alone
— 03 / STACK
— FLUENCY
Tools, formats, frameworks it works in.
Native Figma plugins ka use karke directly file edit karta hai — no screenshot relay, no "AI overlay." Same for the other tools below.
Design tools — FLUENT
- Figma + FigJam★★★★★
- Framer★★★★☆
- Sketch★★★☆☆
- Penpot★★★☆☆
- Adobe XD★★★☆☆
- Photoshop / Illustrator★★★★☆
Disciplines — FLUENT
- UI / Visual design★★★★★
- Interaction / UX★★★★★
- Design systems★★★★★
- Brand / identity★★★★☆
- Marketing visuals★★★★★
- Motion (Lottie / After Effects)★★★☆☆
- Iconography / illustration★★★★☆
Code-adjacent — READ-WRITE
- Tailwind tokens★★★★★
- CSS custom properties★★★★★
- Style Dictionary / Tokens Studio★★★★☆
- React (read-only of components)★★★★☆
- Figma → code (Locofy / Anima)★★★★☆
- Storybook (browse + flag drift)★★★★☆
Collab tools — DAILY
- Linear / Jira★★★★★
- Slack★★★★★
- Notion / Confluence★★★★★
- GitHub (browse + leave PR comments)★★★★☆
- Maze / Useberry / dscout★★★☆☆
- Loom / Cleanshot annotations★★★★☆
— 04 / DAY IN LIFE
— THURSDAY · 09:00 → 18:00 IST
A real Thursday. Logged from a B2B SaaS customer.
Anonymised activity log of a Cyborg-Designer working alongside a 4-person product team. Every action verifiable in their Figma file history.
- 09:00
Standup
Posts in
#design-standup: yesterday shipped 2 frames + 1 system audit, today 3 tickets, no blockers. - 09:14
Picks DSGN-118
"Empty state for the new Reports page." Reads ticket, scans existing empty states in the system, picks the closest pattern as base.
- 10:32
Frame v1 ready
Empty state shipped: illustration from house library + headline + body + primary CTA + secondary "learn more" link. Mobile + desktop variants. Tags
@kavyafor review. - 11:05
Slack thread — brand request
Marketing asks for a banner for a webinar landing page. Cyborg posts 3 directions in the thread within 12 min. Marketing picks #2.
- 11:48
Webinar banner shipped
Final banner: 1920×1080, dark mode variant, Open Graph variant (1200×630). Exported to
brand/2026/webinars/in Drive. - 13:00
Lunch
Pauses. Saves Figma session.
- 14:00
Reviews 3 dev PRs (visual)
Compares Chromatic snapshots to Figma source. Catches 2 drifts: button radius off by 2px, icon stroke weight 1.5 instead of 1.75. Posts overlays.
- 15:10
Design system audit
Runs weekly inconsistency scan on
System / Components. Finds 4 deprecated variants still in use, opens Linear DSGN-145 with full migration list. - 16:00
Accessibility sweep
Audits the Reports page redesign. 1 contrast fail (mute text 4.3:1, needs 4.5). 2 missing focus rings. Files Linear bugs with patches attached.
- 17:30
Wraps up — DSGN-118 marked dev-ready
Kavya approved at 17:11. Cyborg adds final spec annotations (spacing, states, copy in 3 locales), tags
@dev-team, marks frame ready. - 18:00
EOD log
Posts in
#design-eod: 2 frames shipped, 1 banner, 3 PR reviews, 4 system bugs filed. Tomorrow: DSGN-122 + DSGN-145 system cleanup.
— 05 / SAMPLE DELIVERY
— REAL FIGMA FILE · ANONYMISED
An actual file shipped by the Designer.
Used with permission, names anonymised. Real frame, real tokens, real handoff thread.
FIG-DSGN-118
Reports page — Empty state v1.2
Reports / Empty / Desktop · 1280 × 720
100%
No reports yet
Generate your first report to see analytics, exports, and shared dashboards in this space.
TOKENS color/text/strong · color/text/mute · radius/lg · space/8
COMPONENT EmptyState v3
Spec notes
- 1. 48px vertical gap between art and headline (
space/12). - 2. Headline uses
text/2xl/700, text tokencolor/text/strong. - 3. Body copy max 480px wide, centered,
color/text/mute. - 4. Primary button is the system
Button / md / primary. Secondary isButton / md / ghost. - Locales: EN + HI + DE strings included. Longest is DE at 31 chars; layout still holds.
- Mobile (375): art shrinks to 72px, gap drops to 32px, buttons stack full-width with 12px gap.
Accessibility
- Headline contrast 12.4:1 ✓ AAA
- Body contrast 5.1:1 ✓ AA (4.5 required)
- Both buttons have visible focus rings using
focus/ring/2/cyan(3:1 contrast against bg ✓) - Art is
aria-hidden; the empty-state is announced via the headline's role="status"
kavya-pm REVIEWED · APPROVED
42 min ago
Looks great. One thought: can we reorder so "Browse templates" is primary? Most first-time users won't have a report to generate. Either way, your call.
cyborg-cds-002 28 min ago
Good point but I'd push back: in the original brief the goal is to drive report creation, not template discovery. If we make templates primary, we may dilute the activation metric. Ran a quick A/B prediction in #design-research — happy to swap if you want to validate, but my recommendation is to keep "+ New report" primary. Frame stays as-is unless you say otherwise.
dev-arjun REVIEWED · APPROVED
15 min ago
All tokens map cleanly. EmptyState v3 already in our Storybook. Mobile auto-layout works. Will ship in tomorrow's release. Thanks for the locale notes — saved me a round-trip.
— 06 / TOOLS IT TOUCHES
— INTEGRATIONS
All scoped, all logged, all revocable.
Designer Cyborg gets its own Figma seat (counts as 1 in your team). Same OAuth + audit + revoke story as every other Cyborg.
— 07 / PRICING
— FLAT MONTHLY · NO USAGE METER
3 tiers. Pick your craft level.
Same Designer model under the hood. Tier defines autonomy budget, brand-decision authority, and parallel-file capacity.
$599/month
Production design support. Frames, marketing visuals, dev handoff. T1 capabilities only.
- ~50 frames / month
- 1 active Figma file
- Figma + Linear + Slack
- System adherence (read library)
- Email response (24h)
$999/month
Owns features end-to-end. Maintains design system. Reviews dev PRs visually. Most teams start here.
- ~180 frames / month
- 3 parallel Figma files
- All integrations
- System maintenance (write library)
- Visual PR reviews
- A11y audits
- Slack response (4h)
$1,599/month
Direction-setting. Brand evolution. Cross-product consistency. Mentors human juniors via crit.
- Unlimited frames
- Multi-product (up to 5 brands)
- 10 parallel Figma files
- Brand identity work (T3 sign-off)
- Slack response (1h)
- Weekly design crit
- Dedicated A'nil sync (monthly)
14-DAY EVALUATION · 30-DAY MONEY-BACK · MONTH-TO-MONTH · CANCEL ANYTIME · See full pricing →
— 08 / ONBOARDING
— DAY 1 → DAY 7
Brief to first dev-ready frame in 7 days.
Same as our engineer: real timeline, named milestones, refund + postmortem if we miss any.
- DAY 0
You sign
Contract + DPA. Cyborg's Figma seat queued in your team.
- DAY 1
Kickoff (60 min)
Founder + your design lead. Walk through brand, system, conventions, taste anchors.
- DAY 2-3
System ingestion
Cyborg reads your library, tokens, type system, motion principles. Writes a "what I understood" doc back.
- DAY 4
First "explain to me" frame
Smallest backlog ticket → Cyborg ships v1. Treat it like any junior's first work. Critique freely.
- DAY 5-6
Taste calibration
2-3 more frames. We tune what to autonomously ship vs route through your design lead. Trust per area.
- DAY 7
First handoff
Real ticket, marked dev-ready. Cyborg posts retrospective in
#design. From here, it's a teammate.
— 09 / FAQ
— DESIGN-LEAD QUESTIONS
Sawaal jo har design lead poochta hai.
Won't this just be generic AI mockups?
No, and that's the entire point of the per-tenant model. The Cyborg works in your Figma file with your tokens, your components, your illustration style. It does not draw new icons from scratch unless your library calls for it. If a frame doesn't look like it came from your team, we have failed and you can tell us so on Day 7.
What about taste? Design is judgement.
Agree completely. That's why brand identity work, novel visual systems, and direction-setting are T3 (founder/CD signs off). What Cyborg does autonomously is the high-volume execution work that already has answers in your system: empty states, error states, modal patterns, marketing variants, accessibility fixes. The judgement work stays human.
Can it actually use our design system correctly?
Yes — that's literally measured. Our 100% token-adherence stat in the hero card is across all customer files in the last 90 days. Cyborg cannot ship a frame with raw hex or unknown spacing values; the file rejects publish. If your library is messy, Cyborg will say so on Day 3 and we'll help clean it.
Does it replace my designers?
No. It absorbs the high-volume, low-judgement screens (the 80% of the queue that's "another empty state, another modal, another marketing banner"), so your humans go upstream into research, novel features, and the work that actually moves your design forward. Most teams use it to not hire a 1-2 mid designer, not to fire any.
Can it run user research?
It can synthesise research (transcripts, tickets, NPS, support themes) and draft personas / journey maps. It does not autonomously schedule live calls with your customers — that's a human job and probably should stay one.
How do you handle copyright on illustrations?
Cyborg uses your existing illustration library by default. For new spot illustrations, we use models trained on properly-licensed corpora and provide provenance metadata on each asset. If your brand requires zero generative content, set the policy to "library only" in the kickoff — Cyborg honours it.
What happens if it ships an off-brand visual?
Same as a human's mistake: you flag it in the file, Cyborg reverts or revises, and we update the policy that allowed it. Plus there's an audit trail of the prompt + brief + reference frames so we can find the actual cause, not just blame the output. See the audit log.