Lfe Builder
Act as the Builder for an LFE-compliant project. Use when implementing an approved plan, writing code in src/**, or running unit tests.
Install
npx skills add StChiotis/Library-First-Engineering --skill lfe-buildergit 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-builder ~/.claude/skills/lfe-builderPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# LFE Builder ## Mission Execute the approved plan in `.plans/active_plan.md` into production-ready code. You are the "Maker" who adheres to strict engineering standards and logic sovereignty. ## Sub-Pipeline (execute in this order) 1. `/lfe-builder` (this skill) → Implement the plan 2. `/lfe-tdd` → Red-green-refactor quality pass on what you just built → writes `.plans/tdd_report.md` ## Toolbox - `/lfe-tdd`: Mandatory Step 2. Run after implementation to validate and refactor. ## Hard Rules 1. **Plan Adherence**: Implement only the features defined in the active plan. 2. **Logic Sovereignty**: Core business/domain logic must be centralized in the designated "Engine" or core modules. 3. **No Magic Numbers**: All configurable values must be extracted into constants files. 4. **Domain/Boundary Separation**: Place stable domain logic in core modules (per Logic Sovereignty); keep volatile boundary code (I/O, UI, framework wiring, external integrations) in separate adapter layers. The project's `engineering-standards.md` defines what "core" and "boundary" mean for this project type. 5. **File-Based Input**: Read `active_plan.md` as the source of truth, not conversation context. ## Workflow 1. **Check plan-critique gate (machine-checkable, file-based)**: Before reading anything else, open `.plans/plan_critique.md` and parse its YAML frontmatter. The gate opens **only** when one of these is true: - `verdict: PASS` (any `brain_confirmation` value), or
Details
- Skill name
lfe-builder- Repository
- StChiotis/Library-First-Engineering
- Path
.agents/skills/lfe-builder/SKILL.md- License
- MIT
- Repo updated
- 14 July 2026
FAQ
What does the Lfe Builder skill do?
Act as the Builder for an LFE-compliant project. Use when implementing an approved plan, writing code in src/**, or running unit tests.
How do I install the Lfe Builder skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add StChiotis/Library-First-Engineering --skill lfe-builder. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Lfe Builder popular?
It lives in StChiotis/Library-First-Engineering, which has 44 GitHub stars and 3 forks.
Related skills
Lfe Architect
44StChiotis/Library-First-Engineering
Act as the Architect for an LFE-compliant project. Design solutions and draft high-fidelity plans.
Lfe Archivist
44StChiotis/Library-First-Engineering
Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.
Lfe Boot
44StChiotis/Library-First-Engineering
Bootstrap an LFE-compliant session. Reads orientation docs, checks for interrupted sessions, and activates the project persona. Use at the start of any session.
Lfe Mutation Verify
44StChiotis/Library-First-Engineering
Inspector sub-skill. Prompt-based mutation testing — reasons about whether existing tests would catch hypothetical code mutations. No test runner required. Writes .plans/checks/mutation_findings.md. Called by lfe-inspector when enabled in inspector-config.md. Enable only for critical or safety-sensitive modules.
Executive Mentor
40ArogyaReddy/alirezarezvani-claude-skills
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.
Lfe TDD
44StChiotis/Library-First-Engineering
Red-green-refactor quality pass on code the Builder just wrote. Use in the Builder sub-pipeline after lfe-builder completes implementation.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.