Implement or stub Neru functionality for a specific OS/backend: port contract, build-tagged file slots, factory wiring, CodeNotSupported stubs, capability matrix, contract tests, and the docs ownership table. Use for any change under internal/adapter/platform or any *_darwin/_linux/_windows file. Not for pure-Go domain logic.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Platform code carries Neru's strictest guardrails, and this is where agents
most often guess. A change that lands cleanly sits in an existing file slot,
crosses the boundary through a port, returns CodeNotSupported wherever it is
unimplemented, and reports itself honestly in the capability matrix.
internal/adapter/platform/AGENTS.md, the single home for the rules
this skill obeys: the One Rule, file slots, the factory and Linux's runtime
compositor axis, loud stubs, capability honesty, coordinates, generated
Wayland bindings. Add the darwin/ or linux/ guide for the native
boundary you touch.internal/adapter/platform/profile.go. It is the source of truth for
each subsystem's backend family, primary-modifier expectations, and whether
a backend needs CGO. CGO is a per-backend decision, not a per-OS one.internal/ports/. If the capability
doesn't have a port yet, define the interface there first and add a mock in
internal/ports/mocks.*_integration_<os>_test.go tagged
//go:build integration && <os>.CodeNotSupported per subsystem, not per stub. Update the
subsystem's existing one if it has one, and write a new one when a caller
could read the stub's nil as success, so a later "implementation" that
silently no-ops fails a test. internal/adapter/platform/AGENTS.md names the
ones that exist.docs/contributing/porting.md has the ownership table ("Documentation Checklist"),
and each fact has exactly one home. Capability status goes in
docs/reference/platform-support.md, the API or protocol behind it in
docs/contributing/platform-internals.md, and never either in
docs/contributing/architecture.md (shape only).
Linux setup specifics go in docs/guide/linux.md / docs/guide/linux-desktops.md.
just lint # depguard enforces the One Rule
go test ./internal/architecture/
just test-foundation
Cross-compile the platforms you touched (just build-linux,
just build-windows) even when you can't run them, because build tags hide breakage
from a darwin-only just build. Then the standard pre-commit gate, and ask a
maintainer to run integration tests on the target OS if you can't.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Add a Neru CLI command or flag: cobra command in internal/cli, IPC handler in internal/app/ipcctrl, service/mode work behind it, man pages, and docs/reference/cli.md. Use when adding or changing user-facing commands, subcommands, or flags. Not for config.toml options.
中文简介正在准备中。当前显示原文说明。
Add or change a Neru config.toml option end to end: struct field, shared and platform defaults, validation, examples, docs, and hot-reload behavior. Use whenever a change adds, renames, or removes a key in the TOML config schema. Not for theme palette entries or CLI flags.
中文简介正在准备中。当前显示原文说明。
Answer a Neru user's question about what Neru does, which command, flag, or config key does a thing, why something does not work, or what to try next, from the help, man pages, and docs of their installed version rather than from memory. Routes config work to neru-setup-config. Use when a Neru user asks what Neru can do, how to do something with it, which command to run, why hints or a hotkey do nothing, or which skill to use.
中文简介正在准备中。当前显示原文说明。
Help a Neru user build a tool on top of Neru, such as a status bar, a launcher, voice control, a companion UI, automation from another hotkey tool, a Go program, or a client for the IPC socket in another language. Picks the interface, checks the installed version has it, reads the contract from that version's docs, and runs the result against the live daemon. Routes config and hooks work to neru-setup-config. Use when a Neru user wants to script Neru, read its state, follow its events, drive it from another program, or write code against its CLI, socket, or Go client.
中文简介正在准备中。当前显示原文说明。
Commit working changes and open a Neru pull request the maintainer's way: conventional commit subjects, a PR title written for the changelog, the just ci gate, and the repo PR template filled honestly. Use when asked to commit, create a PR, open a pull request, or ship finished work in this repo.
中文简介正在准备中。当前显示原文说明。
File a Neru bug report or feature request that matches the repo's issue forms: duplicate check first, every required field filled with real diagnostics, correct labels. Use when asked to open, file, or draft a GitHub issue for Neru. Not for pull requests.
中文简介正在准备中。当前显示原文说明。