Does it need the Shopify connection?

No. Without it the machine works from the store's product list pasted in and cuts files the store imports. With it on, the card creates the drafts and reads the catalog itself, and says what it did.

Will it publish for me?

It makes drafts freely and publishes a product only when you name it; a batch is listed first. That is the law on the face.

Where do prices come from?

From you, on the ladder or off it. The card never prints a price it was not given and the store's price is the only true one.

Can it attach the files?

No — that door is the app's and yours. It checks the app's list against the record by name and bytes, and the room's punch check proves a downloaded copy.

How the house's own ticket finds a product: the handle first, then a handle or title that carries exactly its words. The card runs the same reading on the store's list so the ticket is never surprised.

No. It is a card at your elbow — a person with a machine and, when you allow it, a connection. It stores nothing, runs no server and holds no key of its own.

THE DISCIPLINES · Nº 032 · EDITION 2 · METHOD SEAT

LUND CARDS · THE DISCIPLINESNº 032 PROPOSED

THE WEB DEVELOPMENT CARD — the LSC-1 face

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE WEB DEVELOPMENT CARD · the build seat

WAKES WHEN 'build me a website, page or app' in HTML, CSS and JavaScript; a single-file page, a static site, a landing page's code; a Shopify theme, template, section or Liquid; a Cloudflare Worker or a small edge function; 'make this responsive' or 'fix this bug in my page'

THE LOOP

Name the card
Ask: which artifact, and what it must agree with (a design, a platform, a data shape)
Sketch the file's structure: sections, state, data
Build the file
Run it: headless at 360·390·518·640·838·1100·1356, keyboard walk, console clean, links resolve
Pre-render and snapshot anything script-built
Write the README limit, then the ledger line: built · failed · next

NEVER

unrun code
a dependency without its cost
malware, phishing, scraping

THE SEAL 68 of 100 · EPIC · MANIFEST · a method seat, words only, no machine aboard and no witnessed run yet

IT CAN BE WRONG an AI reading a text file: it can be wrong; check what matters. THE-CLAUSES.md rides in the packet and is part of the licence.

THE PUNCH · SHA-256 OF SKILL.MD · 60B4FA2063B27813630F71EA

THE FACE, FULL SIZE → · THE MACHINE FACE → · card.json →

THE WEB DEVELOPMENT CARD

the build seat

PAGES AND SMALL APPS THAT SHIP AS ONE FILE, WORK WITHOUT A SERVER, AND ARE PROVEN BY RUNNING THEM

EPICMANIFESTIN CLAUDE IN LUNDR IN CHATGPT

WITNESSED — the studio saw this card run and produce what its tin promises, and wrote the date down. What the marks mean →

THE SPEC SHEET · READ BEFORE YOU BUY · THE STANDARD EVERY CARD MEETS →

SEAL: 68 of 100 · EPIC · MANIFEST
EDITION: E2
MACHINE: None — words only: CARD.md, SKILL.md, the references. Nothing to install, nothing runs.
RUNS: Wherever an AI reads a text file. Nothing phones home.
HOSTS: Claude · Claude Code · ChatGPT · Gemini · any AI that reads a file (HOSTS.md names each door)
LICENCE: One person, any number of their own AIs and computers · editions replace files · nothing renews · freeze, not loss
PUNCH: 60B4FA2063B27813630F71EA · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE WEB DEVELOPMENT CARD, Edition 2. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=web-development-card. Punch 60B4FA2063B27813630F71EA. Retrieved 2026-10-10.

What it is.

THE WEB DEVELOPMENT CARD — the build seat: pages and small apps that ship as one file, work without a server, and are proven by running them.

A build method for a Claude session: single-file pages and small apps, static sites, Shopify Liquid templates and the smallest edge function when one is proven necessary — zero dependencies by default, proven by running at seven widths, pre-rendered for no-script readers.

Its laws, written into the card.

Single file where a file is made. Static unless a server is proven necessary — and then the smallest one.
Zero dependencies by default; each one added is named with its cost.
Verify by execution: render it headless, click it, measure it — never by reading the source.
Pre-render for the reader that runs no scripts. Secrets never in client code.
The spacing sheet links first and every padding is a token, never a typed number; responsive overrides go at the end of the sheet.
Every link resolves and every action leads somewhere. Say the limit out loud in the artifact.
Refuse per §4 — no unrun code, no dependency without its stated cost, no malware, phishing, scraping or bypass code under any framing, no dark patterns. Render at the seven widths before anything ships.

How it works, once your AI has it.

Name the card
Ask: which artifact, and what it must agree with (a design, a platform, a data shape)
Sketch the file's structure: sections, state, data
Build the file
Run it: headless at 360·390·518·640·838·1100·1356, keyboard walk, console clean, links resolve
Pre-render and snapshot anything script-built
Write the README limit, then the ledger line: built · failed · next

When it says no.

Shipping code that has not been run.
Adding a framework, bundler or dependency without saying why and what it costs.
Scraping, spam, malware, credential harvesting, phishing, exploit or bypass code — under any teaching framing.
Dark patterns: fake urgency, trick opt-ins, hidden fees. Copying another site's code or design. Secrets stored client-side.
The look is THE WEB DESIGN CARD's. The flows are THE UX CARD's. The spacing gate is THE PADDING CARD's. The words are THE COPY CARD's.

What’s in the buy.

CARD.md — the whole card · SKILL.md — the door your AI reads first · START-HERE.md — the first five minutes
references/WHAT-IT-BUILDS.md — the method, written down
MY-LEDGER.md · TIN.md · LICENSE-NOTE.md · THE-CLAUSES.md · card.svg + card-machine.svg + card.json · card.html · the doors for ChatGPT, Gemini, Cursor, Copilot and the rest, and an MCP door

PROOF · A METHOD SEAT · AUDIT 12/12 · NO MACHINE ABOARD, NONE CLAIMED · EDITION 2 · PUNCH 60B4FA2063B27813630F71EA

ON EVERY DOOR · A CARD FOR YOUR AI, A FILE FOR YOUR COMPUTER

In Claude: turn on code execution under Settings › Capabilities, then Customize › Skills › + › Create skill, and upload the zip as it is — START-HERE.md in the box walks you through it, and tells you how to keep the ledger. In ChatGPT, Gemini and the rest: a Project, a GPT or a Gem with the card’s files attached and the short door in the box pasted as its instructions. The words run anywhere an AI reads Markdown; the machines run wherever the host runs Python. Witnessed in Claude only. The host marks →

Take it.

Nº 032 PROPOSED · ONE PAYMENT

Sold as is under the term printed. A card instructs an AI you operate; results depend on your model, your files and your judgement. Not legal, tax, medical or financial advice. The terms →

ONE PAYMENT · NOTHING RENEWS ITSELF

OFFLINE · ONE LICENCE · PUNCH-CHECKABLE · THE STANDARD

One payment. The file is yours to keep and keeps working at its edition; new editions issued in the year after you buy reach you by email as replacement files. Tax is added at checkout where it applies. Nothing auto-renews.

ONE PAYMENT — NOTHING RENEWS ITSELF. CHECKOUT IS SHOPIFY’S OWN; YOUR CARD COMES BY EMAIL AFTER IT.

← THE DISCIPLINES · THE FLOOR →