Menú
Exercise local UI changes in the in-app browser. Use for "test the UI", "check the page", "screenshot this", and layout QA.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
How changes are classified, gated, approved, committed, and shipped in the Lamprey Harness repo. Load this BEFORE making any change — code, docs, config, or release — or when you see terms like P-SPR, STS, verify gate, era-lock, commit trailer, push policy, or when a commit/push is rejected by a hook.
How Lamprey runs and ships — run modes, userData layout, Windows release artifacts, the one-command "Bucket" pipeline, macOS/Linux CI mirroring, GitHub publication, CDN purge, and failure recovery. Load when the user says "ship", "release", "tag it", "Bucket", or when a release step fails partway.
The multi-provider LLM domain pack for Lamprey — OpenAI-compatible streaming across 17 built-in providers (frontier labs, open-source hosts, keyless local runtimes) plus user-defined custom endpoints, per-provider quirks (reasoning field names, Anthropic's compat-layer limits, base-URL overrides), capability flags, the native-vs-fallback tool-calling contract, retry/backoff, retired-model handling, and the checklists for adding a model or a provider. Load when touching electron/services/providers/, debugging provider HTTP errors, or adding/retiring models.
Lamprey's load-bearing design decisions, the invariants that must hold, what was deliberately deleted, and the honestly-stated weak points. Load before modifying electron/ipc, electron/services, the provider or tool layers, or the renderer stores — or when you need to know WHY the system is shaped the way it is.
Recreate the Lamprey dev environment from scratch and get past its known traps — Node/Electron/better-sqlite3 ABI story, the ELECTRON_EXEC_PATH dev-server workaround, esbuild antivirus blocks, the tsconfig node/web split, electron-vite and electron-builder specifics. Load when setting up a machine, when npm install / dev server / build fails, or before touching build configuration.
Catalog of every Lamprey configuration axis — AppSettings keys with defaults and readers, inert retired keys, keychain/keys.json, custom models, loop and timeout knobs, environment variables, per-conversation runtime state — plus the exact checklist for adding a setting without breaking the parity-lock test. Load when reading/changing settings.json, adding a setting, or wondering what a flag does or whether anything still reads it.
| name | Frontend QA |
| description | Exercise local UI changes in the in-app browser. Use for "test the UI", "check the page", "screenshot this", and layout QA. |
| triggers | ["test the UI","check the page","screenshot this"] |
Use this skill when a change affects visible UI, page behavior, or browser interaction.
Ask for or use the exact local URL. Do not guess that a dev server exists. If the user gives a URL, call frontend_qa with that URL and any expected text, selectors, or interaction notes from the request. Use browser_open and browser_screenshot only for targeted follow-up when the composed QA report needs another view.
Inspect for blank pages, console-visible crashes when surfaced by the tool, missing expected text, broken selectors, overlapping controls, unreadable text, layout clipping, and obvious mobile/desktop framing issues. For visual work, prefer evidence from the screenshot over assumptions from code.
Report PASS, FAIL, or NEEDS-REVIEW. Include the screenshot path when one was captured, and distinguish automated assertions from manual visual judgment.
Stop when the page has been observed at the requested URL or when the missing URL/server is the only blocker.
