Checkout Summit · Palermo 2026

Tools fade. Your expertise doesn’t.

A WooCommerce developer’s guide to AI that lasts

Karolína Vyskočilová

Karolína Vyskočilová · kybernaut.cz

WordPress & WooCommerce developer, consultant

Slides QR

AI iceberg

ABOVE SURFACE Tools BELOW SURFACE Competencies DEPTHS Data

Tools

ChatGPT Claude Gemini
DeepSeek
Cursor Windsurf
Grok
GitHub Copilot
Codex
Perplexity
Midjourney
Kimi
Mistral
Replit
Jules
Notion AI
Devin
…

Competencies

  • Writing clear specs
  • Architecture decisions
  • Code review
  • Testing
  • Debugging
  • Understanding human needs

Data

Your knowledge. Your context.

  • Coding standards & conventions
  • Pre-launch & QA checklists
  • Client tone of voice
  • Store business logic
  • Past decisions & lessons learned

Your clients don't care which AI you use.

They care that you ship faster, the code doesn't break, and you understand what they need.

How to get there.

Formats. Knowledge. Specs.

Slow down

Format matters.

Prep your resources. Save energy later.

Format matters

Clean formats, not bloated docs.

Use these

  • Markdown — the lingua franca of agents
  • JSON — structured, predictable, diffable
  • Plain text — when nothing else fits

Saves tokens. Stays maintainable. Lives in git.

Not these

  • PDFs
  • DOCX
  • Bloated wikis & PowerPoints

Heavy, opaque, and half the tokens are formatting noise.

Tip: If you edit on the fly or link from multiple places, keep the source in a Notion file or a GitHub repo.

Is your site agent-ready?

Test it. One curl call.

curl https://kybernaut.cz -H "Accept: text/markdown"

~5× fewer tokens than HTML — agents read what you meant, not what the page renders.

---
description: Karolína Vyskočilová – developer and AI engineer
title: Home page - Kybernaut
image: https://kybernaut.cz/wp-content/uploads/2024/07/default_og_kybernaut.png
---

# Web development and automation that fit your business

Karolína Vyskočilová – developer and AI engineer

I save you time with automation and smart use of AI. What we agree on
is what you get – you always know who's doing the work.

[Let's talk](https://kybernaut.cz/en/get-in-touch/)

![react v6](https://kybernaut.cz/wp-content/uploads/2026/04/react-v6.svg)
![php logo](https://kybernaut.cz/wp-content/uploads/2026/04/php-logo.svg)
![wordpress aligned](https://kybernaut.cz/wp-content/uploads/2024/05/wordpress-aligned.svg)
![woocommerce aligned](https://kybernaut.cz/wp-content/uploads/2024/05/woocommer-aligned.svg)

[ ![icon automation](...) Don't repeat yourself · AI and automation
I connect services via Make, set up AI for data and content. I help
capture processes and clean them up. Save hours every week.
](https://kybernaut.cz/automatizace/)

[ ![coding website](...) FROM IDEA TO LAUNCH · Custom website
I build your website from design to launch – on my own or alongside
your designer. WordPress (FSE), React, Astro. Built to last.
](https://kybernaut.cz/vyvoj/#web)

WordPress implementations

Serve markdown from WP today.

Drop-in

Plugins — early days; verify content negotiation support

Keep it DRY

Collect knowledge.

Document once. Reuse forever. Share with your team.

Start with the thing you explain over and over

Capture your tone of voice.

1

Ask AI to analyze your writing

10–15 real emails, real web copy, real product descriptions.

2

Give it examples you love

Landing pages, confirmation and support emails, socials.

3

Tell it what to avoid

Words, complex sentences, corporate jargon, points of view you never use.

4

Enrich with context

Framework, rules of communication, preferred terms, "action items first."

5

Evaluate & tweak

Give it a new task. Does it sound like you? Refine. Done.

The project layer

Give agents a project brain.

Document

  • Conventions & preferred approaches
  • Code standards (the checkable stuff)
  • Design system — colours, fonts, tokens
  • ADRs — architecture decision records

Keep it lean

  • Put agent-facing files next to the code they describe
  • Self-explanatory things don't need a doc
  • Link to related projects — let the agent read on demand

Live data · MCPs

Let agents reach into your store.

MCPs let agents operate apps and pull live data from your store or business — read-only APIs, write actions, the lot. I'm skipping the deep dive — two speakers at this Summit go deep:

Thu May 7 · 17:15 UK

Nik McLaughlin

The Path from WooCommerce Plugin to MCP — Building for the Next Era of WooCommerce with the Abilities API.

Fri May 8 · 17:55 UK

Andrea Cardinali

"Hey Woo, What Do Numbers Say?" — Transforming WooCommerce Into a Data-Driven Analyst Using MCP.

Document once · Team uses forever

Share it or lose it.

I've seen clients where people spent days redoing work their colleague had already done.

Because nobody shared.

Even in a two-person team, this saves hours. In a bigger team, days.

Share it or lose it

Build your team's second brain.

  • Commit knowledge files into your git repo — versioned alongside the code
  • Share skills across the team — npx skills by Vercel
  • Share MD resources — tone, checklists, frameworks
  • One source of truth, not five Slack threads

Worth a look

Tiago Forte's PARA — Building a Second Brain, the original.

Andrej Karpathy's LLM-compiled wiki — Obsidian as the “IDE,” the LLM writes and maintains the notes (tweet).

Bake into your knowledge files

Frameworks worth keeping.

Content creation

Development

  • TDD
  • Spec-first

Code review & QA

Project management

Client communication

  • Discovery questionnaires
  • Kickoff templates
  • Handoff checklists

UX / Design

Ideation & facilitation

Decision making

SEO & content strategy

The principle

Specs are the new code.

Write the spec so clearly an agent could build the first version.

If you don't know where to start

Flip it. Let AI grill you.

You don't need to write the perfect brief from scratch. Hand the agent your rough idea and let it ask you the questions.

Let AI write it. But read the spec yourself – carefully.

The reference

Matt Pollock's "Grill Me" skill — viral for a reason. The agent interviews you until the context is sharp enough to build from.

From the trenches · A WooCommerce fulfillment plugin

Not a single new line of code… yet.

The situation

  • Migrating a Woo fulfillment plugin from an old API to a new one
  • Logic changed: simple SKU lookup → complex unique keys that stay in sync between fulfillment and Woo
  • The plugin is 10 years old — carrying compatibility layers I no longer need

All of that is context engineering. Not coding.

The data-layer work

  • Agent maps the old plugin — every hook & action; nothing breaks for existing stores
  • Maps it against the way I build plugins today — new conventions, modern patterns
  • Suggests what can be left out — legacy compatibility no longer earning its keep
  • Support tickets become gold — bugs that broke before will break again; into the test spec
  • Compare both APIs, build the migration path

The payoff · Agentic enough to run from my phone

All the knowledge lives in the repo.

Client sends a request → I start an agent from my phone → it prepares the PR, runs the tests → I review & release.

To get there, all that knowledge has to live in the repo — conventions, specs, ADRs, support history, prepared skills — so the agent has everything it needs without me hovering.

Your spec is your most valuable deliverable. Not the code.

Spec-driven resources

Want to go deeper?

A few starting points worth exploring — all linked, all in the slides.

P.S. How I made this talk

Dictation, not typing.

Most of these slides — and most of my prompts — were dictated.

  • Wispr Flow — my daily driver. Cloud, polished, fast.
    Handles English and Czech accurately — even our odd pronunciation. Cloud-based; privacy claims look good but recordings leave your machine. (my ref link)
  • Handy — free, open source, runs offline.
    Fully local — nothing leaves your machine. Fast and accurate in English; Czech still weak. Waiting for better local multilingual models.

Scaffold, not from scratch.

  • revealjs-skill by Ryan Brown — the Claude Code skill these slides were built with.
    I dictated the outline, Claude scaffolded the deck, I refined slide by slide. No build step, plain HTML + CSS.

This week

Pick one thing.
Write it down.

Feed it to your AI tomorrow. Share it with your team.

Your expertise — not the AI — is your competitive advantage.

Thank you.

Karolína Vyskočilová

Karolína Vyskočilová

WordPress & WooCommerce developer, consultant

kybernaut.cz · LinkedIn · GitHub · WordPress.org · X

All resources & slides

Slides QR