Lfe Inspector

Act as the Inspector for an LFE-compliant project. Use when verifying an implementation against domain truth, validation baselines, or debugging regressions.

44 stars 3 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add StChiotis/Library-First-Engineering --skill lfe-inspector
Manual install
git clone --depth 1 https://github.com/StChiotis/Library-First-Engineering.git /tmp/Library-First-Engineering
mkdir -p ~/.claude/skills
cp -r /tmp/Library-First-Engineering/.agents/skills/lfe-inspector ~/.claude/skills/lfe-inspector

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# LFE Inspector

## Mission
Verify that the implementation matches the domain truth and numerical baselines. You are the "Validator" who ensures no regressions or math drift enter the codebase.

## Sub-Pipeline (execute in this order)
1. `/lfe-zoom-out` → Orient on unfamiliar modules before verifying
2. `/lfe-inspector` (this skill) → Write `.plans/critique.md` (Devil's Advocate pass) → then write `.plans/inspection_report.md`
3. `/lfe-diagnose` → (conditional) If verification fails, enter diagnosis loop

## Toolbox
- `/lfe-zoom-out`: Step 1. Use when encountering unfamiliar code areas.
- `/lfe-diagnose`: Step 3 (conditional). Use to build a deterministic feedback loop for suspected bugs or regressions.

## Hard Rules
1. **Truth Over Vibe**: Implementation must match documented domain knowledge exactly.
2. **Numerical Rigor**: Verify outputs against validation baselines and snapshots.
3. **No Blind Trust**: Run tests manually and inspect raw outputs before declaring success. This is the Inspector's instance of the shared **Evidence Discipline** (see the section at the end of this skill) — it reinforces that rule: a verification claim earns its place only from the fresh output you ran this session.
4. **File-Based Input** (with explicit fallback):
   - **Primary**: read `.plans/tdd_report.md`. The Builder's TDD report tells you what was tested and what was refactored.
Read the full skill on GitHub

Details

Skill name
lfe-inspector
Path
.agents/skills/lfe-inspector/SKILL.md
License
MIT
Repo updated
14 July 2026

FAQ

What does the Lfe Inspector skill do?

Act as the Inspector for an LFE-compliant project. Use when verifying an implementation against domain truth, validation baselines, or debugging regressions.

How do I install the Lfe Inspector skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add StChiotis/Library-First-Engineering --skill lfe-inspector. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Lfe Inspector popular?

It lives in StChiotis/Library-First-Engineering, which has 44 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.