個人 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