Lagune Engineering Reference
Project-internal engineering rules for the Lagune codebase (toolchain, conventions, build)
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 24, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Jul 30, 2026 · 7e190b8
⚠ This skill is no longer available upstream. Our re-check on Aug 10, 2026 couldn't find it any more (repo unreachable/deleted). The test below is what we measured on Jul 24, 2026 and we're leaving it up as a record — but there is nothing left to install, so we've removed the command.
A single-project rulebook, not a general skill: it dictates Lagune's exact conventions (ESM-only, named exports only, all types confined to src/types/, no any or as-unknown-as, node: import prefix, Poku across three runtimes) that no baseline could infer — genuinely useful, but only if you are working inside the Lagune repo. Marked internal:true, and its two headline cross-links, CLAUDE.md and the architecture skill, are left dangling because the single-dir install copies neither.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 7/10
- Docs & honesty 3/5
What Lagune Engineering Reference does
The authoritative engineering reference for the Lagune project: its runtime-agnostic Node/Bun/Deno toolchain, TypeScript code conventions and type rules, the esbuild build/distribution path, and how its deterministic tracking hooks work. Triggers for contributors before writing or changing source under src/ or test/, or before the build — inside the Lagune repo.
How to install Lagune Engineering Reference
Nothing to install: the source repository no longer has this skill. If the author brings it back, our daily re-check will pick it up and the command will reappear here.
Commands — how to trigger Lagune Engineering Reference
-
/lagune-engineeringProject-internal engineering rules for the Lagune codebase (toolchain, conventions, build)
It also activates on plain-language prompts like these:
-
What are the TypeScript conventions before I edit src/? -
Explain Lagune's esbuild build and distribution path -
How do Lagune's deterministic tracking hooks actually work?
Frequently asked questions
- Is the Lagune Engineering Reference skill free?
- Yes. The skill itself is free from wellwelwel/lagune. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Lagune Engineering Reference work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 24, 2026. Verdict: Works with setup. A single-project rulebook, not a general skill: it dictates Lagune's exact conventions (ESM-only, named exports only, all types confined to src/types/, no any or as-unknown-as, node: import prefix, Poku across three runtimes) that no baseline could infer — genuinely useful, but only if you are working inside the Lagune repo. Marked internal:true, and its two headline cross-links, CLAUDE.md and the architecture skill, are left dangling because the single-dir install copies neither.
- What is the Lagune Engineering Reference SkillProof Score?
- 8.0/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 3/5.
- How do I install Lagune Engineering Reference?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Lagune Engineering Reference with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.