Furquan AhmadValidation and security  ·  furquan101.com
Introduction

Hey, I'm
Furquan

  • Lead Product Designer at Scale AI, previously at Meta. Based in London.
  • I build my own products with AI: TrainTimesUK, Sahara Studio, AutoScout and more.
Furquan at Hulm Club, London
Hulm Club, London
Furquan at AI Tinkerers, Doha
AI Tinkerers, Doha
Furquan at Muslim Tech Fest, London
Muslim Tech Fest, London
Furquan at Hulm Club, London
Hulm Club, London
Furquan at Crescent Creatives
Crescent Creatives
Furquan at Crescent Creatives
Crescent Creatives
Chapter 01

The bar
moved

Anyone can ship now. Speed and craft are both expected.

01

Everything is moving faster than ever

Photo: Felix yu, Unsplash
The process

The design process is dead

  • We lead with prototypes now, not mocks and docs.
  • Hold many ideas loosely. Stay anchored on the problem, and prune toward what works.
THE OLD WAY · ONE STRAIGHT LINE Idea→Mocks→PRDCode→Launch→Iterate THE NEW WAY · A LOOP Prototype→Test→Learn→Prune repeat until the prototype earns its place
Source: Jenny Wen (Anthropic), Julie Zhuo
The tools

Everyone has the same tools

  • Anyone can ship now. PMs are vibe coding their own ideas, and engineers prototype the UI themselves.
  • Most of these are free or cheap. The tools aren't the advantage any more.
Claude Code
Codex
Cursor
Lovable
Replit
v0
Bolt
Figma Make
Gemini
GitHub Copilot
Windsurf
Perplexity
2026

Output exploded

200%+more code changes saved than two years ago (34.3 billion)
200%+more changes approved and added to products (1.3 billion)
CODE CHANGES STARTED BY AN AI AGENT March 2026 17% September 2026 40%
Source: GitHub Octoverse 2026, Oct 2025 to Sep 2026
But

80% of features are rarely or never used

More output doesn't mean more value. Now we can build the unused 80% faster than ever.

20%frequently or sometimes 80%rarely or never
Source: Pendo Feature Adoption Report, 615 products, 2019
Easier than ever

It's never been easier to build

  • Sahara Studio: an AI voice tutor I built to practise Arabic in real scenarios.
  • Voice models and Google sign-in, built on my own with AI.
saharastudio.cc
The pressure

Speed and craft

The scope of a designer's job keeps growing, and both are expected at once.

Pressure 01
Speed

Prototype it, ship it, document it. This sprint.

Pressure 02
Craft

When everyone can ship, quality is what people notice.

The hard part

Knowing what to build is the hard part

  • Step up your product thinking and critical thinking.
  • Don't wait to be told what to build. Help decide it.
“Anyone can build and ship. So much code today is wasted.”
The polish trap

We're not just here to make it pretty

  • Designers are being brought in at the end, to polish someone else's prototype.
  • Advocate for a seat earlier, and grow your product sense.
What's happening Idea Prototype Polish Designer brought in Where we should be Idea Prototype Polish Designer shaping the direction
Chapter 02

Build with
intention

When generation is cheap, judgement is what's left.

02
Rapid prototyping

Higher fidelity, same willingness to bin it

  • Faster high fidelity doesn't mean we should latch on to it.
  • Treat a vibe-coded prototype like a wireframe: easy to throw away.
LOW FIDELITYHIGH FIDELITY Wireframe Vibe-coded prototype Same mindset: easy to throw away
Prototyping tips

Start from inspiration

  1. References. Use tools like Mobbin, and connect MCPs for context.
  2. Meeting notes. They're a goldmine.
  3. Design system. Base it on the apps you're inspired by.
  4. Inspiration. Tell it what to start from.
furquan101.com/guestboard
No design system. Just FigJam as the reference, plus context.
Research

Tell people it's a prototype

  • High fidelity makes participants polite. Polite feedback doesn't help.
  • Change their mentality, and check your own bias too.
“This is literally a prototype. Say whatever you want about it.”
What to say before every session
The dopamine loop

The slot machine in your IDE

  • Every prompt is a lever pull. Intermittent good output keeps you pulling.
  • Output feels like progress, even when it isn't.
f
1
0
Every prompt is a lever pull
Source: Anna Lembke, Dopamine Nation
Pre-flight

Run the pre-flight checklist

  1. Problem. Is it real?
  2. Person. Who exactly?
  3. Scope. The smallest version?
  4. Quality. What does good mean?
  5. Direction. Are we heading the right way?
Pilots never skip it
Pseudo-productivity

AI inflates the output, not the judgement

A manager can't tell judgement applied from judgement skipped. Both look the same.

OutputJudgement Time
Illustration, not data
Source: Cal Newport, Slow Productivity
Craft is the moat

Craft isn't a choice. Be intentional about it.

  • When generation becomes cheap, craft and judgement become the only real moat.
  • Intuition is compressed experience. AI can't fake the years behind it.
Every ring, a year of judgement
Source: Karri Saarinen, Linear
Dogfooding

Live the problem, every single day

  • I built TrainTimesUK for my own commute and hit every bug myself.
  • I shipped fewer features. The product got real.
26errors in March
3errors by late May
Source: TrainTimesUK, PostHog
Four moves

Four moves AI can't make for you

Build intuition first, then build with intention.

01Dogfood

Use it daily. Watch the replays.

02Research

Real complaints, real customers.

03Craft

The eye over the hand.

04Preview

Ship in preview. Learn in public.

Chapter 03

Unlock your
capacity

PMs who build can be extra capacity, not extra work.

03
Roles have changed

PM roles now ask for prototyping

  • You're swamped. The PM has an idea. Let them build it.
  • A PM prototyping their own idea is capacity you didn't have last year.
What PM job posts now ask for · example
  • Prototype ideas with AI tools
  • Ship small changes yourself
  • Work in the code alongside design and engineering
Give them tools

Don't stop PMs building. Give them the right tools.

Your design system, plus skills: one orchestrator, four specialists.

design-orchestrator ContentdesignUXresearchBrand +design systemQAtests You write them once. Every PM gets your judgement.
How it works

The orchestrator and its sub-agents

  • A skill is a written playbook. When it runs, the main agent becomes the boss.
  • It sends sub-agents off with one job each, and they report back before anything ships.
Orchestratorthe boss Contentsub-agentDesign systemsub-agentUX researchsub-agentQAsub-agent each one reports back Pass or fail? Fail: fix and run again · Pass: send for review
What they know

Give every specialist your context

  1. Content design. How your brand writes. Words to use, words to avoid.
  2. Design system. Brand tokens, design tokens, real components only.
  3. UX research and QA. Past findings, flows to test, screenshots.
## content-design
Voice: plain, warm, British spelling
Use:   "sign in", "save", "try again"
Avoid: "leverage", "seamless", "oops!"

## design-system
Brand tokens:  colour.brand, font.display
Design tokens: space.4, radius.md, text.body
Components:    src/components/ui only
Never:         raw hex values or one-off CSS
Excerpts from two specialist skills
The gate

A gate before anything ships

  • Before the agent can send its work for review, the checks have to pass.
  • It's not perfect, but it gives the agent far more context than a one-line prompt.
01Agent finishesThe change is ready
02Checks runContent, design system, tests
03FailIt goes back and fixes it
04PassOnly now can it go for review
Set up once, runs automatically
Why it helps

What PM prototypes are for

  • The point isn't to ship their prototype.
  • PMs will inevitably be building. So collaborate with them closer than ever.
  • Review prototypes together early, before they harden into plans.
01
More ideas

We don't ship their prototype. It shows what the product could be.

02
Faster buy-in

Roadmaps get agreed sooner when people can click the idea.

03
Closer work

They're going to build anyway. Shape it with them, early.

Roadmaps

Roadmaps go redundant faster than ever

  • 8 frontier model launches in under ten months. Each one changes what's possible.
  • A roadmap you agree today can be redundant in three months.
  • So work as closely with PMs as you can.
Opus 4.524 NovGPT-5.211 DecOpus 4.65 FebGemini 3.1 Pro19 FebOpus 4.716 AprGPT-5.523 AprOpus 524 JulOpus 5.522 SepNOV 2025SEP 20268 frontier model launches in under 10 months
Source: Anthropic, OpenAI and Google launch posts
Feedback

Give feedback in one place

  • Commenting on a coded prototype is harder than on a Figma file.
  • So I built a feedback button into Sahara Studio. Press send and a Linear ticket is created, screenshot and all.
The Send feedback panel in Sahara Studio
Send
LinearSAH-142
Voice session stops after 30 seconds
BugFeedbackPrototype
Status
Triage
Source
In-app feedback
Page
/practice/voice

Tried a voice session on my phone. It stopped mid-sentence after about 30 seconds. Expected it to keep listening.

screenshot.pngMarked up, attached automatically
Design system

Hand over your design system

  1. Components. Real parts, not raw HTML.
  2. Tokens. Colour, type and spacing.
  3. Tone of voice. So the copy sounds like you.
DayWeekMonth
Gap−24+
Search talks
Frame
104 × 84
Live

Design

Build

Ship

Weekly
Sign-ups1,240+19%
TalkWorkshopDemoEvent
Your tokens and components, ready for every prompt
Copy this

An orchestrator skill

  • A boss skill plus four specialists, and a script for the checks a machine does better.
  • Tone of voice adapted from Monzo's public guide; design system from my site. Swap in yours.
design-orchestrator/
  SKILL.md            routes the change
  references/
    content-design.md tone of voice
    design-system.md  tokens, components
    ux-research.md    patterns, edge cases
    qa.md             tests, secrets
  scripts/
    check_tokens.py   flags raw colours
Download it at furquan101.com/ship-safe
Context is fuel

More context, better results

  • The more context you give, the better the result.
  • I record my meetings in Granola and feed in the PRD from Notion.
Granola notesNotion PRDsTone of voiceDesign system Claude
Connect it

Connect Figma to Claude

  • Claude reads your real tokens and components.
  • Every connection is access: only connect tools you trust, and give them as little as they need.
Figma MCP Claude Code Real tokens, real components, checked against the design
Chapter 04

Ship with
speed

Once the right set-up is in, you can actually go fast.

04
The boring work

The boring work got fast

  1. Documentation. Claude documented my whole website and gathered every screenshot.
  2. White-labelling. A whole site rebranded, with a new name, colours and copy.
  3. Translation. An entire website, Arabic to English.
furquan101.com
Visuals

Image models for the visuals

Describe it like a director, not with buzzwords like “8k”.

  1. Medium
  2. Subject and position
  3. Setting and light
  4. Framing
A felt fox in a yellow raincoat on a misty railway platform, made with an image model
Made with a six-slot prompt
Models

Don't pick just one model

Same prompt, three models, three different answers. Compare, then take the best parts.

61%of GitHub Copilot users used more than one model
Claude
GPT
Gemini
Source: GitHub Octoverse 2026, September 2026
Chapter 05

Build
your own

If work won't change how it works, change yours.

05
Change how you work

Change your ways of working

  • It might feel intimidating. The only way past that is to start, on your own ideas.
  • It's not as hard as you think. Seeing what agents can do gives you the confidence.
Without: 1×1×WithoutWith: 8×8×With
Code changes per new project, set up for AI agents vs not
Source: GitHub Octoverse 2026
My side projects

What I've built

  1. TrainTimesUK
  2. Runner Journal
  3. Arabic Workbook
  4. Guestboard
  5. Sahara Studio and AutoScout
TrainTimesUK
Runner Journal
Arabic Workbook
Guestboard
Prompt to product

One prompt, then iterate

  • Each of these started as one plain-English prompt.
  • The first prompt is the easy part. The iterating after it is the work.
traintimesuk.co.uk

Build a live departures board for my commute. Show delays first, and make it load fast on my phone.

autoscout.fyi

Before I buy a used car, pull its MOT history and common faults, and tell me in plain English if it's worth it.

saharastudio.cc

Make a voice tutor that lets me practise speaking Arabic out loud, and corrects me gently.

arabicworkbook.ink

Turn my tutor's PDF workbook into a site with audio and practice for every lesson.

Example prompts: each one was the first of hundreds
Missed the market

“Trash. Slop.”

  • Reddit, on AutoScout.
  • Eight features on one site. None past 80% reliable.
autoscout.fyi
Missed the market

Sahara Studio: 193 visitors

It's never been cheaper to build. It still missed the market I was going for.

Visitors193Tried Google sign-in8Started a voice session5
Source: PostHog, Sahara Studio, Oct to Nov 2026
No regrets

I'm not discouraged

  • I learnt a whole stack my day job never asked for.
  • Every product taught me something, even the ones nobody used.
Build

React, Vite, Astro, Claude Code, Codex

Data and APIs

Supabase, Row Level Security, live rail APIs, scraping

Sign-in and payments

Google sign-in, auth, Stripe

AI

Voice models, image models, MCP servers

Ship

Vercel, git worktrees, pull requests, secret scanning

Test and learn

Playwright end-to-end tests, PostHog, email funnels

Job interviews

In interviews, expect this question

  • When you're job hunting, it's now a standard interview question.
  • Bring your own AI build projects. Next year, no AI case study means you look outdated.
The interviewer asks
“What's your AI build process?”
Have a real project ready to walk through
Then and now

We moved slower, with intention

If you're junior: you're not latched on to old biases. That's what companies want.

Two years ago
Slow

We sweated every detail, and we moved with intention.

Today
Fast

I don't think we always move with intention.

Try it

I reverse-engineered FigJam

Add a sticky: one thing you'll try this week
furquan101.com/ship-safe/board
furquan101.com/ship-safe/board
Chapter 06

Guardrails
before ship

Set the safeguards up once. Let them run on every change.

06
Checks

Run the checks before you ship

  • On every change, whoever made it.
  • The last step stays human.
01ContentTone of voice
02Design systemTokens and components
03TestingAutomated tests click through it
04SecretsScan for passwords and keys
05AccessWho can see which data
06Human reviewSomeone who can read the code
Protect the live product

Protect the live product

A few protections your engineers can set up in an afternoon.

01Review

Every change is checked by someone before it goes live.

02Owners

The instruction files agents follow have a named owner.

03Secrets

Every change is scanned for passwords and keys.

04Ask once

Your engineers set this up one time.

What the AI can see

Guardrails on what the AI can see

  • Decide what the AI can reach before it starts. Client data and the live database stay off limits.
  • Password-protect prototypes by default. An open preview link can leak client information.
client-prototype.vercel.app
This prototype is private
Password
View prototype
Can seeThe code, test data, the design system
Ask firstNew connectors, shared drives, analytics
NeverClient data, the live database, API keys
Work together

Give PMs a sandbox, and stay close

  1. Stay informed. Know what the PM is building.
  2. Work together. Review and polish it side by side.
  3. Check in regularly. Short and often.
  4. Have one way to give feedback. Not scattered across chats.
01PrototypeSandbox or preview link
02Design reviewPolish it with the orchestrator
03SpecThe prototype becomes the spec
04Engineers shipThrough the normal checks
Chapter 07

What goes
wrong

You don't need to be technical, just aware. Every example here really happened.

07
The happy path

Models finish the happy path

  • AI writes code that works when everything goes right.
  • If nobody reads the code, nobody catches the gaps.
Tasks with a flaw: 45%45%Tasks with a flawFailed a web attack test: 86%86%Failed a web attack test
Source: Veracode GenAI Code Security Report, Jul 2025
Real incidents

It's already happening

Four public incidents, all from missing basics.

Moltbook · 20261.5M API tokens

A secret key was visible in the website's code.

Lovable · 2025170 apps

Database tables anyone could read or write.

Replit · 2025Prod deleted

An agent wiped a live database in a code freeze.

Coding tools · 2025Rules files

Hidden instructions that steer what agents write.

Source: Wiz, NVD (CVE-2025-48757), SaaStr, Pillar Security
Shadow vibe coding

Shipped from someone's own account

  • Apps put live from a personal account, outside the company's systems.
  • No record, no checks, and nobody knows it exists until it breaks.
2,500%more software bugs from people building apps with prompts by 2028, in Gartner's worst case
Source: Gartner, Predicts 2026 (forecast, via secondary reports)
Environments

Keep testing away from the real thing

  • Replit, July 2025: the agent could reach the live data.
  • Over 1,200 executives' records, gone. Keep test versions separate.
DevAgent works here ProductionReal customer data No direct access
Source: SaaStr, eWeek, Fortune
Before you connect

Before you connect a tool, ask

  • Connectors, often called MCP servers, let an agent reach your files and other apps.
  • Keep a list of what you've connected, and get an engineer to check the access.
01Why is it needed?
02What can it read?
03What can it change?
04Whose access does it use?
05When is it removed?
Source: SANS AI security course notes
Test the unsafe path

Test the unsafe path, not just the happy one

  • What are we building? What could go wrong? What controls exist?
  • Don't let the agent be the only judge of its own security.
A document that hides an unrelated instructionTest
Ask the agent to use a tool it doesn't needTest
Can one user see another user's data?Test
A connected service returns misleading contentTest
Do risky actions stop and ask for approval?Test
Source: SANS AI security course notes
Keep it current

Skills and connectors go stale

  • Models, tools and your own design system keep changing.
  • Give skills and connectors an owner, and review them regularly.
SkillsConnectorsModelsTools review
Put a date on it: check them every few months
API keys

Treat API keys like passwords

  • Keep API keys secret, and never paste them into a chat.
  • Rotate them regularly, and straight away if one leaks.
01Keep it secretLike a password
02Store it safelyIn a password manager
03Rotate itEvery few months
04Leaked? Rotate nowThen check its use
Guardrails

Set up guardrails on your agent

  • Decide what your agent can access and do, before it starts.
  • If it doesn't need the browser, don't give it the browser. Start small.
Read and edit this projectAllowed
Run testsAllowed
BrowserOff
Email and calendarOff
Production databaseOff
Deploy to productionOff
An agent that only needs to fix a bug
Your information

Be careful where it goes

  • Be careful where you paste client information, passwords and private docs.
  • Check whether the tool trains on what you type, and where its training data came from.
Where you paste
Think first

Client details, passwords and private docs don't belong in any chat or tool you haven't checked.

Training data
Know the source

Check whether the tool learns from what you type, and where its own training data came from.

Be aware

Five things to be aware of

  • You don't need to be technical. Just be aware.
  • For anything going live, a second pair of eyes still matters.
01API keysSecret and rotated
02Agent guardrailsOnly what it needs
03Where you pasteNot in unchecked tools
04Training dataKnow the source
05Engineer reviewBefore it goes live
Close

Your judgement leads. AI helps.

Use AI for inspiration and help. The thinking is still yours.

“Vibe coding got me to 90%. The last 10% is the job.”
AI Tinkerers Doha, June 2026
Monday

Set this up on Monday

  1. Connect your design system
  2. Write a tone of voice file
  3. Add an orchestrator skill
  4. Turn on secret scanning
  5. Give PMs a sandbox
Before you send it for review:
1. Run design-orchestrator on your changes.
2. Check who can see each new table of data.
3. Scan for secrets.
4. Run the automated tests, attach screenshots.
5. List what you couldn't check.
The pre-ship prompt
Resources

Get the slides and prompts

  1. furquan101.com/ship-safe · slides, prompts, skill, PDF
  2. linkedin.com/in/furquan101 · say hi
furquan101.com/ship-safe

Thank you!

furquan101.com/ship-safe

← → to navigate · N toggles notes