Lfe Improve Architecture

Find deepening opportunities in the codebase — turn shallow modules into deep ones. Use in Phase 5 (Hygiene sub-pipeline) or when scheduled by session count.

44 stars 3 forksSoftware Development

Install

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

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 Improve Architecture

## Position in Pipeline
- **Phase**: 5 (Hygiene sub-pipeline, Step 2)
- **Persona**: Architect
- **Trigger**: Scheduled every 5 sessions (tracked in `pipeline_status.md`)

## Vocabulary

Use these terms exactly; keep "component," "service," "API," and "boundary" out of architectural suggestions. See [LANGUAGE.md](./LANGUAGE.md) for full definitions.

- **Module** — anything with an interface and an implementation
- **Interface** — everything a caller must know to use the module
- **Implementation** — the code inside
- **Depth** — leverage at the interface: a lot of behavior behind a small interface
- **Seam** — where an interface lives; a place behavior can be altered without editing in place
- **Adapter** — a concrete thing satisfying an interface at a seam
- **Leverage** — what callers get from depth
- **Locality** — what maintainers get from depth

## Key Principles

- **Deletion test**: imagine deleting the module. If complexity vanishes, it was a pass-through. If complexity reappears across N callers, it was earning its keep.
- **The interface is the test surface.**
- **One adapter = hypothetical seam. Two adapters = real seam.**

## Process

### 1. Explore
Read the project's domain glossary (`CONTEXT.md`) and any ADRs first.

Then walk the codebase organically and note friction:
- Where does understanding one concept require bouncing between many small modules?
Read the full skill on GitHub

Details

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

FAQ

What does the Lfe Improve Architecture skill do?

Find deepening opportunities in the codebase — turn shallow modules into deep ones. Use in Phase 5 (Hygiene sub-pipeline) or when scheduled by session count.

How do I install the Lfe Improve Architecture skill?

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

Is Lfe Improve Architecture 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.