Skip to content
View WsNodeX's full-sized avatar

Block or report WsNodeX

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
WsNodeX/README.md

喆 · WsNodeX

Backend engineer working on AI tooling. I write zero-dependency libraries in Python and Java, and Agent Skills that fix what AI writes.


Quiver — 12 Agent Skills for the job hunt.

Read a JD, work out what you are missing, drill the interview, fix the résumé, write the weekly report, defend the internship, negotiate the offer, pick between them. One chain, twelve skills, installs in one command.


Two skills, one idea: write for the reader, not the author.

Project The failure it fixes
readme-forge A README written for its author — launch plans, headline shortlists, diagrams that were never drawn. 13-point audit + rewrite skeleton.
inheritor Code that withholds what the next reader needs — unnamed literals, TODOs with no exit condition, errors you cannot act on. 8 rules + a checker.

Both ship a checker rather than advice, and both are held to their own rules: readme-forge audits its own README on every push; inheritor's CI fails if the checker reports anything against itself.

Same design, two languages. Each pair below is one piece of thinking implemented twice — once on the JDK, once on the Python standard library, with the same seams and the same trade-offs.

graph LR
  D[one design] --> J[Java<br/>JDK standard library]
  D --> P[Python<br/>stdlib]
  J --> A[aether · halo · nexus]
  P --> S[sage · beacon · prism]
  A -.->|same seams<br/>same trade-offs| S
Loading
Problem Java Python
MCP servers aether sage
Hybrid retrieval + RAG halo beacon
LLM resilience (retry · breaker · cache · meter) nexus prism

Writing it twice is the only way I have found to tell which parts of a design are essential and which are just the shape of one language's idioms.


Single takes

  • ember — a 1,135-line autograd engine, no NumPy
  • forge — byte-level BPE from scratch
  • lumen — vector search with a real HNSW graph
  • cobalt — seven cache eviction policies, one API
  • slate — validation that reports every error at once
  • meter — what your LLM calls actually cost
  • neon-protocol — a raycasting FPS in pure Python, no engine, no asset files

Most of what I write is an attempt to make a decision survive the person who made it. A literal with no source, a commit message that repeats the diff, a README that addresses the author — all the same failure: the reasoning was never written down, so it has to be rediscovered.


readme-forge · inheritor · quiver

Popular repositories Loading

  1. vellum vellum Public

    零依赖的本地知识库:BM25 中英文检索 + 纯标准库 Web UI,一行命令把文档变成可搜索的知识库。

    Python 1

  2. cairn cairn Public

    A zero-dependency cron expression parser and scheduler for Python.

    Python 1

  3. neon-protocol neon-protocol Public

    纯 Python + NumPy 光线投射赛博朋克 FPS:WASD 移动 / 鼠标转向 / Shift 冲刺 / 8 波生存。无引擎、无外部资源。

    Python 1

  4. sluice sluice Public

    Zero-dependency Java rate limiting library: token bucket, fixed window, sliding window log & counter. Thread-safe, deterministic-testable, JDK 17+.

    Java 1

  5. lumen lumen Public

    A zero-dependency vector database in pure Python with HNSW indexing.

    Python 1

  6. aether aether Public

    零依赖的 Java MCP 服务端框架:用标准库实现 MCP 协议,把任意 Java 方法暴露给 AI 客户端。

    Java 1