friday-james

Imagine saving a newly released gpt5 or any project doc in the system memory and EVERY claude session can retrieve it without polluting the context. This is what the project do.

Benchmarks & research: github.com/friday-james/z… (held-out validated, 5 benchmarks, full ablations) Skill: github.com/friday-james/z… (MIT) Built with Claude Opus. The retrieval problem is solved. The future is structure, not similarity.

I made Claude Code remember everything across sessions. Plain text + SQLite beat a 79MB neural embedding model (MemPalace/ChromaDB). No embeddings. No vector DB. Just FTS5 and the right structure.

a Claude Code skill that scans your npm and pip dependencies for vulnerabilities, typosquatting, and supply chain attacks. github.com/friday-james/d…

2. let gpt and claude cook until it is approved by gpt. done.

I built a tool that can audit and iteratively edit your code until it reaches a defined quality bar — think automated review + fix loops (a “Ralph loop” style workflow). Designed for individual devs who want strong guardrails without slowing down. Repo: #code-audit" target="_blank" rel="nofollow noopener">github.com/friday-james/l…

1. go to a project directory. specify the contract. let gpt to do the audit and claude to do the code changes