# Five ideas for a mask factory

The examples above use made-up data. These five are the same building blocks pointed at a real factory's work. Each is a text you can copy and give to your agent as it is; the agent asks you for what only you have (a file, a list of suppliers, a customer's name) and uses example data where you have none yet, saying so on the page. Start with the one closest to a question you are asked every week.

A word on real data: an ordinary page is unlisted, so anyone who has its link can read it. When a page carries customer names, prices or anything else you would not forward to a stranger, the texts below ask for a private page with one share link per person.

## An order sheet from the ERP's export

Your order system can already export a spreadsheet file (CSV). The agent turns that file into a sortable, filterable order sheet your team opens on a phone, and a single command refreshes it from the next export.

```prompt
Load the ccc-pages skill and make me an order sheet page fed by my ERP's CSV export.
Ask me for the path to the latest export. If I have none yet, make a made-up CSV of 30 mask orders (customer, sku, quantity, due, status) and say on the page that the rows are examples.
Use the data-table template with the data store on. Because the rows name real customers, publish the page `--private` from its first publish, and mint one viewer share link per colleague I name, labelled with their name; give me the links in chat only, never on any page.
Write a small script that reads the CSV and writes it as one record `orders` of schema `table@1`, and keep the script beside the page's files.
Show me: the page URL, the raw URL of the `orders` record, and the one command I run after each new export to refresh the sheet without republishing the page. Then run that command on a changed copy of the CSV and show me the page picked up the change.
```

## A shift dashboard from the line lead's evening message

At the end of each shift the line lead already sends someone the numbers. Paste that message into your agent's window and the dashboard updates; the whole plant reads the same four numbers in the morning.

```prompt
Load the ccc-pages skill and make me a shift dashboard page that I update by pasting the line lead's end-of-shift message to you.
Use the dashboard template with the data store on, and a record `metrics` of schema `metrics@1` holding four tiles (masks made this shift, first-pass yield %, orders open, next due date) and a 14-day series of daily output. Start it with made-up numbers and say on the page that they are examples until the first real message.
Write down the exact short message format the line lead should send, one number per line, so I can pass it on. From then on, when I paste such a message to you, update `metrics`: the four tiles, today's point in the series, and the "as of" time, and drop the oldest point so the series stays at 14 days.
Show me the page URL, the raw URL of `metrics`, and the message format. Then take this sample message and update the page from it: "Shift B, line 2: 18,240 masks, first-pass yield 97.8%, 42 orders open, next due Friday."
```

## A supplier scorecard, refreshed monthly

Which supplier of melt-blown fabric, ear-loop elastic, nose wire or cartons delivered on time and to spec last month? The agent keeps one record per month, so the page shows this month's ranking and how each supplier is trending.

```prompt
Load the ccc-pages skill and make me a supplier scorecard page, refreshed once a month.
Ask me for my suppliers and last month's figures. If I have none at hand, use made-up suppliers for melt-blown fabric, ear-loop elastic, nose wire and packaging cartons, and say on the page that they are examples.
Data store on. Keep one record per month named `scorecard.<yyyy-mm>` holding, per supplier: on-time delivery %, defects per million, lead time in days and price change %. The page lists the records with prefix `scorecard.`, shows the newest month as a table ranked by on-time delivery, marks each figure better or worse than the month before in words as well as colour, and shows a small trend per supplier across the months it has.
Because supplier prices are confidential, publish the page `--private` from its first publish and give me one labelled viewer share link for myself, in chat only.
Write three months of records, then show me the page URL, the raw URL of the newest record, and the command I run next month to add a month without republishing the page.
```

## A quote page for each customer, with its own expiry

A customer opens a clean page with their quote on it, and the page tells them when the quote expires. Each person at the customer gets their own link, and you can switch off one person's link without touching anyone else's.

```prompt
Load the ccc-pages skill and read its publishing reference on private pages. Make me a quote page for one customer that I can repeat for the next customer with one command.
Ask me for the customer's name, the line items (product, quantity, unit price), the payment and delivery terms and how many days the quote is valid. If I give none, use a made-up customer and say on the page that it is an example.
Use the markdown template, published `--private --data on` from its first publish. Store the quote as a `raw@1` record named `quote` whose `stale_after` is the end of the validity period; the page renders the quote with a line saying when it expires and, once it has expired, says so instead of showing the prices.
Mint one viewer share link per person at the customer that I name, each labelled with that person's name and expiring when the quote does; give me the links in chat only, never on any page.
Show me the page without a link (the unlock form) and with one, the command that switches off one person's link, and the command that makes the next customer's quote page from this one.
```

## A machine event log fed by the MES

If your manufacturing execution system (MES) or a line controller can call a web address, it can send the page a short message whenever a machine stops, starts or runs low on material. The page keeps every event, and anyone on the floor can see what happened today and which machine stopped most.

```prompt
Load the ccc-pages skill and read its data-and-endpoints reference on inbox ingestion and on computed views. Make me a machine event log page that my MES posts events to.
Data store on. Mint the page's inbox secret with `page-inbox secret`, keep it in a file with mode 600, and never show it to me in chat or on any page.
The page lists records with prefix `inbox.` newest first: event name (for example `machine.stop`, `machine.start`, `material.low`), machine, reason and time, with a filter by machine. Add a `handler.js` with a computed view `stops` that counts today's `machine.stop` events per machine, declared in `handler.json` as `{"views":["stops"]}`; publish, replay and activate it, and show those counts at the top of the page.
Post six made-up events with `page-inbox send`, each with its own delivery id, across three machines.
Show me the page URL, the output of `page-data get <slug> '~stops' --data-only`, and the exact curl my MES would run to post one event, with the secret shown as a placeholder and a delivery id so a retry is stored once.
```