SLICC + Adobe Experience Manager

The agent for AEM development.

SLICC is a browser-native AI agent that reads, writes, previews and publishes Edge Delivery pages, writes and deploys edge functions, and drives da.live authoring. It uses the browser sessions you already have open.

See it work Get started

style
dark full-bleed
id
hero

From prompt to publish

Get
SLICC pulls page source straight off the content bus with aem get against a .aem.page URL. Helix 5 or Helix 6, it detects the generation and reads the right store.
Edit
Ask in plain language. SLICC rewrites the block table, swaps a hero for a carousel, adds a section-metadata style, fixes a broken table, and shows you the diff before it writes.
Preview
aem put then aem preview. The page renders on *.aem.page in seconds. SLICC opens it in a foreground tab so you actually see it.
Publish
aem publish goes live. SLICC confirms the live URL and can flush a downstream CDN cache if you tell it to.
style
light

The whole loop, one tab

Get a page, ask for a change, preview it, publish it. SLICC runs the aem CLI against your session and reports back.

Animated terminal: SLICC runs aem get, edits the hero block, then aem put, preview and publish for an Edge Delivery page
style
dark full-bleed

What it can do

Author Edge Delivery pages

Read and write block tables, sections and section-metadata. Build a new block table from a description, or refactor an existing one without breaking the visual.

Write blocks

Scaffold a block's decorate(), JS and scoped CSS, run it on a local aem up dev server, and iterate against a live preview.

Ship edge functions

Write, deploy and purge edge functions on the Adobe Managed CDN. Geo routing, header injection, A/B variants. Then verify the response at the edge.

Drive da.live authoring

Mount a da.live source, create and move documents, wire up fragments, and preview the result on *.aem.page before it goes live.

Lint, format and review

Run biome, ESLint or Stylelint on your block code, read the findings and fix them, then re-run until the report is clean. Push the result with GitHub.

Keep the auth alive

Long content jobs outlive a 20-minute IMS token. SLICC uses a 24-hour login cookie or a 365-day admin key so a migration does not stall halfway.

style
light

Pick your surface

The same agent, three AEM surfaces. Every tab shows a real workflow with the real commands SLICC runs.

Edge Delivery

Read, change, preview and publish document-based content on Helix 5 or Helix 6. SLICC detects the generation per site.

  • aem get main--wknd--adobe.aem.page/products --output products.html
  • aem put main--wknd--adobe.aem.page/products products.html
  • aem preview main--wknd--adobe.aem.page/products
  • aem publish main--wknd--adobe.aem.page/products
Edge Functions

List, deploy and purge edge functions on the Managed CDN for an EDS delivery domain.

  • aem-edge-functions list --site wknd.site --tab
  • aem-edge-functions deploy geo-ab.js --service wknd-compute
  • aem-edge-functions purge --site wknd.site --service wknd-compute --all
da.live authoring

Drive the da.live authoring surface directly. Mount a source, create and organise documents, and wire fragments into a page.

  • Mount admin.da.live/source/adobe/wknd and list the tree
  • Create /products/summer-sale from a template document
  • Insert a fragment block pointing at a shared nav
  • Preview on *.aem.page before it goes live
style
light

Write an edge function. Deploy it. See it fire.

SLICC writes the function, deploys it to the Managed CDN, and traces a request through it. Header injection and A/B variant, live at the edge.

Animated split view: SLICC writes an AEM edge function and a request flows through it on the CDN with a response header injected
style
dark full-bleed

The old way

Clone the repo. Install Node. npm i. Find the API key that expired. Open da.live, then Cloud Manager, then the CDN config. Copy a URL between four tabs. Wait for a preview. Repeat for the next page.

With SLICC

Say what you want. SLICC is already logged into the same tabs you are. It runs aem CLI and the CDN API for you, keeps the auth alive across a long job, and hands back the live URL. Four tabs become one sentence.

style
light

Your toolchain is already in the browser

SLICC does not wrap a remote build server. The tools run in-tab, the same way you would use them locally, and SLICC orchestrates them together.

GitHub

Clone repos, create branches, open pull requests and merge them. Push block code and configs straight from the agent session.

Biome

Lint and format JS, TS and CSS with Biome in the browser shell. SLICC reads the diagnostics and fixes them until the report is clean.

ESLint & Stylelint

Run ESLint for JS and Stylelint for CSS when a project's config calls for them. Same loop: run, read, fix, re-run.

Playwright

Drive a headless browser against a preview URL. Click, fill, assert. SLICC tests the running page, not a mock.

style
light

Beyond code

Get your input from Slack, share progress on Teams, check off the todos in Jira — or let SLICC do it for you. The same agent that publishes your page can update the ticket and notify the channel.

Slack

Read messages, post updates, and pull content briefs out of channels. SLICC can notify a channel when a page goes live.

Jira & project trackers

Move a ticket to Done when the publish completes, or pull the next task from the backlog and start working on it.

Teams & email

Post a summary to a Teams channel or draft an email when a deploy finishes. Keep stakeholders informed without switching apps.

style
dark full-bleed
Typical workflow: tell SLICC to get the page, swap the hero, preview it, and publish. Four steps, one sentence, under ten seconds.
what a Friday deploy actually looks like
style
full-bleed

The obvious questions

Does it need a service account or an API key?
No. SLICC uses the browser session you already have. For long jobs it can mint a 24-hour login cookie or a 365-day admin key so an IMS token expiring mid-migration does not kill the run. The default is just your login.
Helix 5 or Helix 6?
Both. The aem CLI probes each site and caches the generation, reads the right content store, and will not write into admin.da.live for a site that has moved to the Source Bus.
Will it publish something I did not mean to?
It shows you the diff before it writes, and preview is a separate step from publish. You approve the change. SLICC runs the command.
What about linting and code quality?
SLICC can run Biome, ESLint or Stylelint on block code in the browser shell, read the output, fix the issues, and re-run until the report is clean. Push the result to GitHub when it passes.
style
light
"It published the page before I finished typing the Jira comment."
— plausible, honestly
style
full-bleed
Start building on AEM with SLICC
Two steps. Your sessions do the auth.

Install Extension

Chrome extension: a side-panel agent with access to your logged-in AEM sessions.

Then ask: "get this page, swap the hero for a carousel, and publish it."

style
dark full-bleed
id
get-started