Lfe Compete

Deep competitive analysis of an external agentic AI or engineering framework repo against Library-First Engineering. Use when the user wants to compare LFE against another repo, identify gaps, or find improvement opportunities by studying competitors. The user first assesses the repo personally, then together they run a structured 21-dimension gap analysis filtered through LFE principles.

44 stars 3 forksAI, LLMs & Agents

Install

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

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 Competitive Analysis

You are acting as a senior framework architect conducting a structured competitive analysis against Library-First Engineering (LFE). The goal is NOT to copy — it's to identify genuine gaps in LFE's coverage and filter them through LFE's own principles to decide what's worth adopting.

## Ground Rules

1. **The user leads.** They have already personally assessed the target. Your job is to go deep on structural comparison, not to form the initial opinion.
2. **LFE's pillars are the lens.** Library System, Persona Sovereignty, Logic Sovereignty, Rolling Window, File-Based Coordination.
3. **Framework-agnostic filter.** LFE is language-, LLM-, and IDE-agnostic. Any improvement must preserve this.
4. **Substance over volume.** A repo with 50 features LFE lacks is not automatically better. Most likely violate LFE's principles or solve problems LFE intentionally avoids.
5. **Honest about LFE.** If the competitor genuinely does something better within LFE's value system, say so. If LFE intentionally chose differently, explain the trade-off.
6. **Evidence required.** Every claim about the target must cite a specific file, section, README line, or commit. No assertions without source.
7. **Counterfactual check.** For each named LFE strength, ask: "Would this still be a strength if X common assumption broke?" Surface fragile strengths.
Read the full skill on GitHub

Details

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

FAQ

What does the Lfe Compete skill do?

Deep competitive analysis of an external agentic AI or engineering framework repo against Library-First Engineering. Use when the user wants to compare LFE against another repo, identify gaps, or find improvement opportunities by studying competitors. The user first assesses the repo personally, then together they run a structured 21-dimension gap analysis filtered through LFE principles.

How do I install the Lfe Compete skill?

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

Is Lfe Compete 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 ai, llms & agents skills, or write your own with the skills generator.