Skip to content
R
03AI workflow

AI in the loop. Not on autopilot.

The tools are only half of it. The other half is the MCP layer that gives them the design file, the repo, the database, and the ticket — plus a review habit that never goes away.

How AI fits into the workflow

I use AI to move through the boring parts faster — scaffolding, refactors, copy, tests — then read every line and own what ships. The difference is the MCP layer: the tools can see the design file, the repo, the database, and the ticket, not just the chat window.

Daily drivers

  • Cursor
  • Windsurf
  • GitHub Copilot
  • Lovable
  • Codex

For research, planning & content

  • Claude
  • Gemini

Tools change every few months. The standard doesn’t: every change gets read, tested, and reviewed before it reaches a user.

workflow — zshlive

$ whoami

rameez — front-end developer, Lahore

$ cat workflow.txt

write → review → ship

AI in the loop, never on autopilot

$ mcp status

figma ......... connected

github ........ connected

postgres ...... connected

slack / jira .. connected

$

Illustrative workflow — the tools, not a screenshot of client code.

MCP connections

Context stays where the work is.

Four servers wired into the everyday loop, so the assistant is working with the real project — not a summary of it.

Figma

01

Design-to-code handoff

Reads frames, tokens, and component structure straight into the build.

GitHub

02

Repo, PR & issue management

Keeps branches, reviews, and issue context inside the same workflow.

PostgreSQL

03

Schema & query access

Inspects tables and tests queries without leaving the editor.

Slack / Jira

04

Task & team sync

Pulls task context and keeps delivery updates close to the code.

Where AI fits

01

Explore

Read unfamiliar code, map a feature, and compare approaches before writing a line.

02

Build

Scaffold components, clear repetitive refactors, write tests, and handle translation passes.

03

Review

Catch edge cases, explain diffs, and tighten the pull request before a human sees it.

04ContactOpen to work

Let’s build
something worth shipping.

Have a product, a role, or a messy front-end that needs a steady hand? I’m one message away.

Start a conversation
mrameezch16@gmail.comLahore, PunjabOpen to front-end & full-stack roles