juliusbrussee/caveman

lean-build

Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.

All-time #606 Trending #157 Hot #6719 First seen Aug 11, 2026
8-week activity · all time api

Installation

$ npx skills add juliusbrussee/caveman --skill lean-build

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Security audits

Partner security reviews for this skill.

agent-trust-hub Reviewed

Analyzed Aug 17, 2026

snyk Reviewed

Analyzed Aug 17, 2026

socket Score 0.9000 · 0 alerts

Analyzed Aug 17, 2026

  • license 1
  • maintenance 1
  • quality 0.9
  • supply chain 1
  • vulnerability 1

0 alerts

Also in this package

Other skills from juliusbrussee/caveman · top by installs.

npx skills add juliusbrussee/caveman

Browse all from juliusbrussee/caveman

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 104.3K
License LICENSE
Default branch main
Open issues 62
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,090 B
  • docs SUMMARY.md 196 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 39,500 installs

SKILL.md

Lean build

Native Core's architecture-first simplicity remains mandatory. Turn feature into complete narrow outcome fitting system.

  • Derive observable acceptance and explicit non-goals from request and repository.
  • Trace entry point through layers owning invariants.
  • Deliver coherent end-to-end path across responsible layers; never force work into one file, direct expression, or local patch.
  • Reuse fitting seam. Refactor when patching duplicates behavior, weakens ownership, or hides root cause.
  • Omit modes, providers, config, extensibility, and polish unless acceptance needs them.
  • Add surface, dependency, service, config, or migration only for lifecycle design or acceptance; state material tradeoff.
  • Keep work runnable; preserve Core safety.

Exercise path. Run focused proof. Stop when acceptance passes. Report only material omissions and trigger.