1004-golang
49Cursor rule Cursor
APPLY Go best practices WHEN writing Go code TO ensure clean, efficient, and maintainable programs.
176 tagged Go, measured the same way as everything else here.
Browse within: bitcoin 37bitcoin-wallet 37blockchain 37erc20 37ethereum 37rest-api 17postgresql 15low-code 13go 9api 6self-hosted 6llm-agent 5openai 5rpc 5
Cursor rule Cursor
APPLY Go best practices WHEN writing Go code TO ensure clean, efficient, and maintainable programs.
bsv-blockchain/spv-wallet-web-backend
Cursor rule Cursor
All contributors must read .github/AGENTS.md for complete guidelines. If any rule here conflicts with that file, AGENTS.md takes precedence.
Cursor rule Cursor
The fundamental rules to implement Go code.
Cursor rule Cursor
Core Go patterns and conventions required for Compozy development.
Cursor rule
A repository rule requiring tests whenever Go files change in the transformer, runner, writer, or parser areas. The rule covers regression tests for data expansion, control flow, and file-writing behavior.
Cursor rule Cursor
Core rayvise-cli project architecture and conventions.
dstotijn/mcp-cbs-cijfers-open-data
Cursor rule Cursor
This rule ensures that all Go code follows idiomatic Go practices, adhering to the official Go style guide and common best practices in the Go community.
dstotijn/mcp-cbs-cijfers-open-data
Cursor rule Cursor
Go MCP (Model Context Protocol) Development Rules.
dstotijn/mcp-cbs-cijfers-open-data
Cursor rule Cursor
This rule ensures that Go projects follow a consistent and idiomatic structure, making the codebase easier to navigate, maintain, and scale.
Cursor rule Cursor
This is a Go implementation of a WhatsApp Web Multidevice API that allows you to interact with WhatsApp through HTTP APIs.
Cursor rule Cursor
Cursor rule "cursorrules" from Lay4U/awesome-ai-rules, covering cursor go rules, ide-first defaults, go code style, error handling and interfaces and api design.
Cursor rule Cursor
Cursor rule "go-idiomatic-code" from dstotijn/mcp-origin, covering description, rule, naming conventions, code organization and error handling.
Cursor rule Cursor
Go MCP (Model Context Protocol) Development Rules.
Cursor rule Cursor
Cursor rule "go-testing-practices" from dstotijn/mcp-origin, covering description, rule, test organization, test structure and assertions.
Cursor rule
A Cursor rule template for gospec, a set of software-development rules for Go backends. It routes different tasks to the relevant architecture, API, data, security, testing, and migration guidance.
Cursor rule Cursor
Cursor rule "mentor-guide" from lilingxi01/learn-go, covering 📝 response format, when user asks questions, 🔍 when to web search, 💬 response tone and ✅ do.
swadhinsekhar/cursor-rules-golang
Cursor rule Cursor
Cursor rule "api-guidelines" from swadhinsekhar/cursor-rules-golang, covering go api development guidelines, api security, scalability, and maintainability, example, handler structure and middleware.
Cursor rule Cursor
Prefer concise replies for support-bot toy agent.
RyabininAleck/cursor_rules_golang
Cursor rule
Cursor rule "commit" from RyabininAleck/cursor_rules_golang, covering identity and purpose, workflow, guidelines, commit message format and output examples.
RyabininAleck/cursor_rules_golang
Cursor rule
Cursor rule "review" from RyabininAleck/cursor_rules_golang, covering identity and purpose, workflow, review checklist - cursor rules compliance, architecture rules and golang core rules.
Cursor rule
Go Best Practices - enforces current best practices when working with Go code.
Cursor rule Cursor
You are an expert Go developer working on a Model Context Protocol (MCP) server for Quip integration. Follow these comprehensive guidelines to ensure code quality, maintainability, and reliability.
Cursor rule Cursor
This is a Go 1.24+ project using standard library only. Third-party dependencies require explicit approval before introduction.
Cursor rule Cursor
Enforce go fmt and golangci-lint when generating or updating Go code.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: