Open to work · Isfahan · on-site, hybrid or remote

Abolfazl Sharifi

Senior AI-native engineer, CTO and product architect

I have been building software for nineteen years, from an airline ticketing system to a multi-tenant SaaS platform. Today I design the system and coding agents build it, with specs, guards and a code graph, so the architecture never pays for the speed.

Let’s talk
See how I work

building since 2007

❯ claude "add a chart layout to the history block"● reading specs/native-resume/spec.md● graph: ResumeBlocks → resume-blocks.tsx✓ layout: list | chart✓ check:* passed · pest green✓ PR opened · CI green❯

a session on this very repository

FIG. 1 · SIMACMS

One installation, many sites

Each site sees only its own plan’s modules. Agents read from the specs, and every change passes the guards before merge.

SimaCMS architecture: sites, modules, the shared chassis and the agent loop

AGENTS.md

How I work with agents

Tools: Claude Code MCP OpenSpec Playwright

  • A repository built for agents

    Path-scoped rules, AGENTS.md and sectioned documents, so a coding agent works without guessing.

  • Spec-driven

    Every capability has a spec, and every behaviour decision is recorded from proposal to archive.

  • Guards, not hope

    Static guards in CI hold module boundaries and contracts; an agent’s mistake is caught before merge.

  • A code knowledge graph

    The agent asks a graph for the code’s structure instead of searching text: sharper and cheaper.

  • From ticket to green CI

    Purpose-built skills and subagents start the app, check it in a browser and drive the PR to green.

NOTES/

Workshop notes

Have a system that has to be built right?

Based in Isfahan; open to on-site, hybrid or remote work. Email is the quickest way.

I usually answer the same working day

abolfazl.dev@gmail.com
+98 939 393 9309