Skip to content

AI engineering · Systems architecture

AI that works inside your product, not next to it.

I build AI into existing software, from validated LLM features to MCP servers and agent workflows, and the systems businesses run on: integrations with ERP and e-invoicing, automations and device apps.

Talk about your projectSee what I have built
Portrait of Kamil StaśkoKamil StaśkoAI Engineer · Systems Architect10+ years in software, 5+ in production SaaS
years building software, 5+ of them running production SaaS
10+
devices managed by a platform I designed
10k+
test coverage on an API in production for 5+ years, with several thousand automated tests
99%
external systems integrated: ERP, e-invoicing, ad platforms and more
8+

Services

From AI features to the systems behind them

Two kinds of work, one engineer: AI that holds up in production, and the software and integrations it depends on. I work inside your codebase, your API and your CI.

AI engineering

  • LLM features in your product

    Structured outputs with strict JSON Schema, validated before anything touches your data, and exposed through the API you already have (REST or GraphQL).

  • MCP servers for your product

    Let Claude, ChatGPT or Gemini work in your system without exceeding their user’s permissions: typed tools, scoped tokens, tenant isolation, confirmation on writes, rate limits and an audit log.

  • AI-assisted engineering

    Claude Code set up for your repositories: review subagents, domain skills, hooks that load your docs, and tool access to Sentry, SonarQube or your database schema.

  • AI readiness assessment

    A maturity assessment, a list of gaps and a phased adoption plan with an estimate, plus internal guides that get engineers using AI tools day to day.

Software & systems

  • Custom systems & integrations

    Your tools talking to each other: ERP, KSeF e-invoicing and partner APIs over REST, SOAP or SFTP, XLSX and PDF imports and exports, and automations in Make, Zapier or n8n.

  • Device and desktop apps

    Apps for screens, players and kiosks in Electron and Node.js, with real-time control and remote updates for fleets on Linux, Windows and embedded hardware.

  • Backend & architecture

    APIs in Laravel, GraphQL and REST, multi-tenant platforms, AWS and Terraform, observability with OpenTelemetry and VictoriaMetrics, and tests that let you change things safely.

Projects

What I have built

Projects I designed and built as lead engineer and architect at a software house, for its products and clients. Client and product names stay confidential; the technical detail does not.

01

MCP server for a multi-tenant CMS

Context

AI agents needed to operate a CMS on behalf of real users, without becoming a security hole.

  • Laravel MCP
  • Sanctum
  • OpenAPI
  • Pest

What I built

  • Two MCP servers (tenant CMS and admin) with typed read and write tools
  • Access tokens with a dedicated MCP scope, inheriting the user’s permissions and tenant
  • Confirmation on writes, throttling, TOTP step-up, idle timeout and an audit log
  • An auto-generated OpenAPI wrapper exposing the same tools to ChatGPT and Gemini

Outcome

An agent can never do more than the user it acts for. Covered by feature tests.

02

Agent workflow across dozens of repositories

Context

The engineering team behind a large product family wanted AI tools to follow its standards, not fight them.

  • Claude Code
  • MCP
  • Subagents
  • Skills & hooks

What I built

  • Specialised subagents for planning, code, security, performance, database and DevOps review before commits
  • A library of domain skills loaded on demand, and hooks that load the relevant documentation
  • Persistent memory between sessions and model choice by task and cost
  • Tool access over MCP: SonarQube, Sentry and GlitchTip, database schema introspection

Outcome

In daily use by the team, backed by internal guides and onboarding docs.

03

Digital signage platform, 5+ years in production

Context

A multi-tenant platform driving tens of thousands of screens and players across Poland, designed from day one.

  • Laravel
  • GraphQL
  • Electron
  • Node.js
  • AWS
  • MariaDB

What I built

  • Laravel API with Lighthouse GraphQL and REST, multi-tenancy and content scheduling
  • Player apps in Electron, Node.js and HTML for Linux, Windows and embedded devices, with real-time WebSocket control and zero-downtime remote updates
  • Integrations: ERP, KSeF e-invoicing, ad platforms, music scheduling, weather and geolocation
  • AWS infrastructure with OpenTelemetry, VictoriaLogs, VictoriaMetrics, Vector, Grafana and Sentry

Outcome

The main API is 99% covered by tests: several thousand Pest tests run in CI on every change, with no SonarQube rules switched off.

Process

How we work together

  1. 01

    Discovery

    A short call about your goals, your systems and your team. You get a written summary of what is worth building, and what is not.

  2. 02

    Plan & estimate

    Scope, architecture, risks and an estimate before any code is written. No surprises later.

  3. 03

    Build

    Production code covered by automated tests, inside your repository and your CI, not a demo running on the side.

  4. 04

    Hand-over

    Documentation and guides so your team owns the result, or I stay on as your technical partner.

Stack

Tools I use every day

AI & LLM
  • Claude
  • Claude Code
  • MCP
  • OpenAI API
  • Structured outputs
  • Context engineering
Backend
  • PHP 8
  • Laravel
  • Lighthouse GraphQL
  • REST
  • Octane / FrankenPHP
  • WebSocket
Apps
  • Node.js
  • TypeScript
  • Electron
  • HTML
Integrations
  • REST
  • SOAP / WSDL
  • SFTP
  • Webhooks
  • Make
  • Zapier
  • n8n
Data
  • MariaDB
  • MySQL
  • Redis
  • Valkey
Cloud & infrastructure
  • AWS
  • Terraform
  • Docker
  • GitLab CI
  • Linux
Observability
  • OpenTelemetry
  • VictoriaLogs
  • VictoriaMetrics
  • Vector
  • Grafana
  • Sentry
  • GlitchTip
Quality
  • Pest
  • PHPUnit
  • SonarQube

Contact

Need AI in your product, or systems that finally work together?

Tell me what you are working on and where it hurts. I read every message and reply personally.

Available for new projects, for companies and private clients, on an invoice. A fixed-scope project or ongoing collaboration, whatever fits you. I usually reply within one business day.

Write an emailLinkedIn

Poland · working remotely (CET)