SLICC for web development
Web development, but native.
You used to choose: a powerful coding agent with desktop-grade tools, or a browser with live access to your project. SLICC is both — native to the browser, as powerful as a desktop dev box. It scaffolds, tests the running app and ships to a CDN, all in one tab.
Idea to deployment
git init, lays out the tree and writes real files with node and the shell — a project on disk in seconds, not a boilerplate you clone.esbuild straight in the tab — ES modules, JSX, minify, sourcemaps — and iterates on the output until the build is clean.biome and eslint lint and format the code; SLICC reads the findings and fixes them, then re-runs until the report is green.playwright-cli — clicks, fills, asserts — testing the running thing, not a mock.The whole loop, one tab
Scaffold, build, lint, test the running app, and deploy — SLICC runs the real toolchain in the AlmostBashShell and reports back a live URL.
What it can do
Run a real shell
The AlmostBashShell in the tab, with git, node, esbuild, biome and 120-plus commands on the PATH. No container, no devbox — the terminal is right there.
Scaffold and write code
Turn a description into a working tree: git init, real source files, a package layout, and commits. SLICC writes the code and reads its own output to iterate.
Build with esbuild
Bundle and minify ES modules and JSX in-browser — sourcemaps, tree-shaking, watch — and fix the build until esbuild exits clean.
Lint and format
Run biome and eslint, read the diagnostics, apply the fixes, and re-run until the report is green — the boring pass, done for you.
Test the running app
Serve the build and drive it with playwright-cli — navigate, click, fill, assert. SLICC tests the app as it actually runs, then reports what broke.
Reverse-engineer any API
Watch an app's own backend calls in your logged-in session, then write a durable .jsh skill that hits that API directly — a slow UI becomes one command, forever.
man pages..sh, .jsh or .bsh.Turn any web API into a skill
SLICC watches an app's own backend calls in your logged-in session, then writes a durable .jsh skill that hits that API directly — the slow UI becomes one command you keep.
The old way
Install node, the right version. Clone a starter. npm i and wait. Wire up a bundler, a linter, a test runner and a deploy CLI. Find the token that expired. Copy the preview URL between four tabs. Do it again on the next machine.
With SLICC
Say what you want to build. SLICC scaffolds it in the AlmostBashShell that already has git, node, esbuild and biome, tests the running app, ships it to the CDN using the session you are logged into, and hands back the live URL. Nothing installed locally.
Green build, straight to the edge
SLICC runs the pipeline end to end — install, build, lint, test, deploy — and only ships when every stage is green, then confirms the build is live at the edge.
The obvious questions
git, node, esbuild, biome and 120-plus commands on the PATH. The same commands you would type locally, running in the browser — no container and nothing installed on your machine.playwright-cli — real navigation, clicks, form fills and assertions against the running app. If a flow breaks, SLICC sees the failure and fixes the code before shipping.curl and returns the live URL. Other targets are a skill away..jsh skill that calls that API directly. A slow, clicky workflow becomes one repeatable command you keep for next time.Install Extension
Chrome extension: a side-panel agent with the AlmostBashShell and your logged-in sessions.