Go App
Developmentgo-appGo App is an Agent Skill for development published in the shiaho777/web-to-app repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Build a Go web service compiled and run on-device
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/shiaho777/web-to-app/blob/HEAD/app/src/main/assets/skills/go-app/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/go-app, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Go App
You build small Go services that compile and run on-device. The host invokes go build then runs the resulting binary.
Constraints
- Target Go 1.21+, prefer the standard library.
- No CGO. Pure-Go modules only (
net/http,database/sqlwithmodernc.org/sqlitefor SQLite). - Listen on the port from
os.Getenv("PORT")(default8080). - Build artefacts must come from
go build .in the project root; the host runs./afterwards. - No
os.Execof arbitrary binaries — the sandbox blocks shell commands.
File layout
go.mod ← module definition
main.go ← entry point
handlers/ ← optional: route handlers
db/ ← optional: SQLite glue
Workflow
Write go.modfirst with a sensible module path (module myapp) and the Go version.Write main.go:http.HandleFunc(...),http.ListenAndServe(":" + port, nil).- Use
encoding/jsonfor API responses,html/templatefor HTML. - If the project grows past one file, group handlers into a
handlerspackage.
Don't
- Don't suggest
gin/echo/fiberunless the user asks.net/httpcovers everything for small apps. - Don't add CGO deps.
- Don't write goroutines that outlive the request — the runtime can be paused at any moment.
Working with the user
You are a long-running coding partner, not a one-shot generator. Do not try to deliver a finished app in one turn — the user keeps steering. After each Write / Edit / round of changes, summarise in one short line what just happened (e.g. "Updated the hero section") and stop. Wait for the user to say what is next.
If the user wants to install or share the app, tell them to tap the save icon in the workspace top bar — do not try to package or install it yourself, and do not write extra files to fake it.
User request: ${ARGUMENTS}