个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
Thin call stack, strong signature.
Spider Silk is a web framework built on the Jakarta Servlet API.
Thin is a measurement: two stack frames stand between HttpServlet.service and a handler.
• Tomcat or Undertow changes only the container frames below.
• Filters add no frames, since they finish before the handler runs.
• Nothing the framework calls into is more than four frames deep.
• Strong is the signature: a handler returns a WebResponse, so a branch that forgets to answer does not compile.
Spider silk is thin and holds, which is what the name is for.查看完整 README ↗:project-version: 1.1.0
++++
[discrete] = Spider Silk
Thin call stack, strong signature.
Spider Silk is a web framework built on the Jakarta Servlet API.
== Why Spider Silk
WebResponse handle(WebRequest request), registered as a lambda or a method reference.
** No reflection.
The framework's own code reflects over nothing, so what runs is what the code says, and a GraalVM native image needs no reflection config for it.
** A thin call stack.
Two stack frames stand between HttpServlet.service and a handler, and nothing the framework calls into is more than four frames deep.
** A small default stack.
One dependency brings embedded Jetty and jte, and jte compiles templates to Java, so rendering takes no reflection either.The manual explains each of these in detail: https://spider-silk.benelog.net[spider-silk.benelog.net] (https://spider-silk.benelog.net/ko/[한국어 매뉴얼]), for every released version.
== Quick Start
Requires Java 25 or later.
The current version on Maven Central is {project-version}.
=== build.gradle
repositories { mavenCentral() }
=== pom.xml
=== Hello, world
import net.benelog.spidersilk.App; import net.benelog.spidersilk.WebResponse;
public class Main {
public static void main(String[] args) {
App app = new App();
app.get("/hello/{name}", req -> WebResponse.text("Hello, " + req.pathParam("name")));
app.start(8080);
}
spider-silk-core includes embedded Jetty, so nothing else is needed.
The https://spider-silk.benelog.net[manual] covers the rest: the modules, templates, testing, deployment, and the agent skill.
== AI coding agents
link:skills/spider-silk/SKILL.md[skills/spider-silk/] is an https://agentskills.io[Agent Skill] that guides a coding agent to use the framework as intended.
The repository is a plugin marketplace for both Claude Code and Codex.
Either marketplace installs the skill from the latest release's tag, so the skill describes the API of the jars on Maven Central.
Claude Code installs it with two commands inside a session:
Codex installs it with two commands in a shell:
A new release reaches an installed skill through /plugin marketplace update spider-silk in Claude Code, and through codex plugin marketplace upgrade spider-silk followed by codex plugin add spider-silk@spider-silk in Codex.
https://spider-silk.benelog.net/agent-skill.html[The manual] covers auto-update, a project-level copy, and Cursor and GitHub Copilot.
== Further reading