iOS_hAT

® AI-native build studio

Loading experience0%
Available for new work

iOS_hAT — I build real software with AI and read every line before it ships

I build real software

with AI  shipped.

No CS degree, no bootcamp. I build in Cursor — prompting with intent, reviewing every diff, and verifying it works before it reaches anyone.

Scroll to explore
01What I Do

AI writes fast. I make sure it's right.

A few disciplines, one obsession: real software that works — reviewed line by line.

01

AI-Native Development

Full products built end-to-end in Cursor. AI writes the code fast; I steer it, review every diff, and decide what actually ships.

  • Cursor
  • React
  • Next.js
  • TypeScript

const app = await build({

reviewed: true,

verified: true,

blindShipped: false,

});

02

Interfaces & Tools

Dashboards, panels and utilities stripped to their essence, then polished until they work without friction.

  • UI/UX
  • Dashboards
  • Automation
03

iOS & Reverse Engineering

Jailbreak tweaks, runtime hooks and binary analysis. Understanding how systems actually work, then bending them.

  • Objective-C
  • Frida
  • IDA / Ghidra
04

Verified, Not Vibed

Not a blind vibe coder. Every build is checked against real behavior and confirmed working before it reaches users — no shortcuts.

  • Review
  • Testing
  • Shipping
120 FPS0 shortcuts
02The Approach

I build real, working software with AI  but I refuse to ship what I can't read. Every diff gets reviewed, every output questioned, every build verified before it reaches anyone. 

01

Read the code — always

AI writes fast, but I read what it changes. If I can't tell whether a change is right, it doesn't go in.

02

Understand enough to catch wrong

No CS degree needed to know when something is off. A working understanding is enough to question the output and push back.

03

Never ship what you can't verify

Shipping is the checkpoint, not the finish. I confirm the behavior before real users ever see it.

03Process

From prompt to shipped.

No mystery, no black box. A tight loop I run on every build — transparent enough to trust, disciplined enough that nothing ships unreviewed.

  1. Phase 01

    Prompt

    I direct the AI with clear, specific intent — I know what I want built, not just "make it work". The brief becomes a plan before a single line is written.

    • Intent
    • Plan
    • Constraints
  2. Phase 02

    Review

    Every change the AI makes gets read. Diffs are looked at, never rubber-stamped and merged blind. If a change is unclear, it does not go in.

    • Read every diff
    • No blind merges
  3. Phase 03

    Question

    When something looks off, I dig in and push back on the AI until the code is actually right — not just until it stops erroring.

    • Interrogate output
    • Fix root cause
  4. Phase 04

    Verify & Ship

    I confirm the behavior against the real thing, then it goes live. Only the code I can vouch for ever reaches users.

    • Verify behavior
    • Ship
    • Watch & tune
04Contact

Got something to build? Let's make it real.

For enquiries, collaborations, or building something together — reach out directly. One conversation to find out if it's a fit.