pastilhasandClaude Opus 5
919504901a
The engine was there and nothing pointed at it, which is the same failure as a comment outliving its code: an agent would go on asking the owner to open DevTools and read numbers back, because that is the only loop it knew. bin/lighthouse.ts is the callable surface — the panel's engine with a table instead of JSON, exiting non-zero when anything is short of 100 so it can gate something without being parsed. affordances/ carries the short always-loaded note: you can measure this yourself, here is the line, do not ask a person. skills/ carries what the findings mean, why the built site and the dev server are different questions, and the three defects this has already caught — each one a rename or a setting that left something behind and produced no error. Both are read in place from the plugin directory by capabilitySources, so they arrive with the plugin and need no publish step. The invocation globs ~/officer*/platform because the checkout is officer-dev on one machine and officerdev on the other, and a doc that is right on one box and wrong on the other is worse than no doc. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
---
|
|
name: Fofos lighthouse
|
|
description: The fofos website can be measured here — do not ask a person to run DevTools.
|
|
version: 1
|
|
---
|
|
|
|
**Anything you change on the fofos website, you can measure yourself.** Both form factors, about
|
|
twenty seconds:
|
|
|
|
```bash
|
|
# The checkout is named differently per machine, so the glob finds it either way.
|
|
bun "$(ls -d ~/officer*/platform/plugins/fofos-admin | head -1)/bin/lighthouse.ts" \
|
|
https://web.fofosfluffybastards.com/gallery/aldi/
|
|
```
|
|
|
|
Scores, the five metrics, and every failing audit **with the resources it names** — a URL and what it
|
|
cost, which is the difference between a finding and a fix. `--mobile` or `--desktop` for one,
|
|
`--json` for a script. It exits non-zero when anything is short of 100.
|
|
|
|
**Never ask the owner to run Lighthouse in DevTools and read numbers back.** That loop is why three
|
|
real defects lived on the site for weeks. Measure, fix, measure again.
|
|
|
|
**Always measure the BUILT site**, not the dev server — `bun run build:site` publishes to
|
|
`dist/`, and that is what visitors get. A number from `localhost:3011` is a different page.
|
|
|
|
Read the **`fofos-lighthouse`** skill for what the findings mean and the traps in reading them.
|