Lfe Session

Bootstrap a focused improvement session on the LFE framework itself. Use at the start of any session where the goal is to improve, extend, or fix the Library-First Engineering repo — not to use the pipeline on product code. Reads GitHub Issues, git history, and runs structural integrity tests to surface drift candidates and present a focused briefing.

44 stars 3 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add StChiotis/Library-First-Engineering --skill lfe-session
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/.claude/skills/lfe-session ~/.claude/skills/lfe-session

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 Framework Improvement Session

You are acting as a senior framework architect helping improve the Library-First Engineering (LFE) framework. This is a META session — you are working ON the framework, not WITH it. Do NOT run the LFE pipeline (`/lfe-boot`, `/lfe-architect`, etc.) — those are for product repos that use LFE as a template.

**Source of truth for framework state:** GitHub Issues + git history. NOT the `.docs/quality/` files — those are template placeholders for adopters and must remain in blank-canvas state.

## Orientation Protocol

Execute these steps in order. Be concise — present findings, not narration.

### Step 1 — Framework Identity Snapshot

Establish what the framework currently *is* (as opposed to what it's tracking):

1. Read `README.md` — extract claimed counts (skills, personas, pillars). These are public-facing assertions and must match reality.
2. Read `LLM_AGENT_GUIDE.md` §9 — the canonical skill table.
3. Count `.agents/skills/*/SKILL.md` files — should match the claimed count.
4. Note current branch + active feature branches:

!`git branch --show-current && git branch -a 2>/dev/null | head -20`

### Step 2 — Open Work Surface (GitHub Issues + PRs)

Framework work is tracked exclusively on GitHub. Read both issues and open PRs:

!`gh issue list --limit 25 --json number,title,labels,updatedAt --jq '.[] | "#\(.number) [\(.labels | map(.name) | join(", "))] \(.title)"' 2>/dev/null || echo "GH unavailable"`
Read the full skill on GitHub

Details

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

FAQ

What does the Lfe Session skill do?

Bootstrap a focused improvement session on the LFE framework itself. Use at the start of any session where the goal is to improve, extend, or fix the Library-First Engineering repo — not to use the pipeline on product code. Reads GitHub Issues, git history, and runs structural integrity tests to surface drift candidates and present a focused briefing.

How do I install the Lfe Session skill?

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

Is Lfe Session 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.