agentleFS
clideyclidey/whodb/.agents/skills/platform-constrained-handler/SKILL.md

platform-constrained-handler

Skill5.1k starsChanged 3 days agoApache-2.0View on GitHub

Add a new CE-owned HTTP handler with ARM/RISC-V64 build constraints (platform-excluded features)

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 8 mentionsApr 2026: 4 mentionsMay 2026: 5 mentionsJun 2026: 6 mentionsJul 2026: 5 mentionsAug 2026: 6 mentionsSep 2026: 6 mentionsOct 2026: 9 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the clidey/whodb repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about clidey/whodb

The biggest 5 of 60 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 60

Talked about on GitHub, Bluesky and Hacker News (60 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this only when adding a CE-owned HTTP handler that depends on CGO libraries or platform-specific bindings unavailable on ARM/RISC-V64.

    line 8
  2. Very specific:

    Do not use this workflow for edition or add-on HTTP routes.

    line 10
  3. Very specific:

    Every file with //go:build !arm && !riscv64 MUST have a matching //go:build arm || riscv64 stub that defines the same symbols.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add a Platform-Constrained HTTP Handler

Use this only when adding a CE-owned HTTP handler that depends on CGO libraries or platform-specific bindings unavailable on ARM/RISC-V64.

Do not use this workflow for edition or add-on HTTP routes. Add-on routes should be registered by the add-on package with graph.RegisterHTTPRoutes, so CE does not carry add-on route names or unsupported stubs.

Steps

1. Create Main Handler

core/graph/http_<name>_handler.go:

//go:build !arm && !riscv64

package graph

import "net/http"

func Setup<Name>Handler(mux *http.ServeMux) {
    mux.HandleFunc("/api/<name>", handle<Name>)
}

func handle<Name>(w http.ResponseWriter, r *http.Request) {
    // Implementation
}

2. Create Unsupported Stub

core/graph/http_<name>_unsupported.go:

//go:build arm || riscv64

package graph

import "net/http"

func Setup<Name>Handler(mux *http.ServeMux) {
    mux.HandleFunc("/api/<name>", func(w http.ResponseWriter, r *http.Request) {
        http.Error(w, "not supported on this platform", http.StatusNotImplemented)
    })
}

3. Register in SetupHTTPServer

The handler registration call must be in unconditionally-compiled CE code (no build tags):

Setup<Name>Handler(mux)

For add-on routes, register from the add-on package instead:

func init() {
    graph.RegisterHTTPRoutes(func(router chi.Router) {
        router.Post("/api/<name>", handle<Name>)
    })
}

4. Verify

cd core && go build ./cmd/whodb

PR CI does not cross-compile. Check by hand that the stub defines every symbol the tagged file defines. A real arm/riscv64 build needs CGO cross compilers (riscv64-linux-gnu-gcc, arm-linux-gnueabihf-gcc) and the BAML build-tag step from .github/workflows/_build-linux-terminal.yml; with those in place, make server-riscv64 in desktop-ce/ mirrors the release build.

Key Rule

Every file with //go:build !arm && !riscv64 MUST have a matching //go:build arm || riscv64 stub that defines the same symbols. A missing stub first fails in the release job "Build Linux Server Binaries (CE)".

Existing Examples

  • http_ai_stream_handler.go → http_ai_stream_unsupported.go

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.