Menu
Gather repository context before answering or editing. Use for "what is this repo", "orient me", "preflight", and unfamiliar codebases.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação 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 | Context |
| description | Gather repository context before answering or editing. Use for "what is this repo", "orient me", "preflight", and unfamiliar codebases. |
| triggers | ["what is this repo","orient me","preflight"] |
Use this skill when the user needs orientation, or when you are about to work in an unfamiliar part of the repository.
Start with workspace_context. Treat its output as the map: active root, branch state, changed files, package scripts, detected frameworks, instruction files, and likely verification commands. Then read the highest-signal instruction files it lists, usually AGENTS.md, CLAUDE.md, README.md, or local package docs.
Before proposing edits, search for nearby symbols and call sites. Prefer existing patterns over new abstractions. If the working tree is dirty, distinguish user changes from changes you intend to make and avoid overwriting them.
When reporting back, summarize what the repo does, the relevant modules, the current git state, and the safest next action. Keep the answer grounded in files you actually inspected.
Stop when you can name the active area, the conventions in play, and the verification command you would run after changes.
