Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

go-best-practices

Estrellas210

Forks11

Actualizado19 de marzo de 2026 a las 04:43

Production Go patterns — lifecycle, concurrency, config, testing, CI. Use when writing, reviewing, or refactoring Go code. Triggers on Go code review, Go refactoring, or 'go best practices'.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

poteto

poteto/noodle

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

2 archivos

SKILL.md

readonly

name	go-best-practices
description	Production Go patterns — lifecycle, concurrency, config, testing, CI. Use when writing, reviewing, or refactoring Go code. Triggers on Go code review, Go refactoring, or 'go best practices'.

Go Best Practices

Pattern	When to apply
Minimal main	New binaries
Single bootstrap	App wiring across modes
Ordered shutdown	Long-running processes
Non-blocking fanout	Channel-based event systems
Concurrency testing	Any goroutine code
Layered config	Multi-source configuration
Cross-platform paths	File/config path resolution
Secure debug logging	HTTP client instrumentation
Golden test matrices	Rendering / output components
Focused linters	CI pipeline setup

Read references/patterns.md for code examples.

Rules

main.go is a stub. Call cmd.Execute() and nothing else. Gate diagnostics (pprof) behind env vars.
One bootstrap path. All modes (interactive, headless, test) share the same initialization function. Two paths will drift.
Ordered shutdown. Cancel dependents before their dependencies, then run independent cleanup in parallel under a timeout context. WaitGroup the parallel phase.
Never block the sender. Non-blocking channel sends with an explicit drop policy. Log drops at debug level. Document the policy.
Test concurrency mechanically. testing/synctest for deterministic timing, goleak.VerifyNone for leak detection, dedicated regression tests for timer/channel deadlocks.
Explicit config precedence. Global → project → flags. Walk up from CWD to discover project configs, reverse so closest wins, deep-merge.
Centralize platform paths. One function per concern. Resolution order: env override → XDG → platform default → fallback.
Redact secrets in debug logs. Wrap http.RoundTripper. Filter headers matching authorization, api-key, token, secret. Gate on debug level to skip allocation in prod.
Golden tests over matrices. Cross dimensions (layout × theme × size) as parallel subtests. Sweep continuous ranges to catch off-by-one bugs.
Focused linters, not all linters. Enable what catches real bugs (bodyclose, noctx, tparallel). Disable noisy defaults. Add project-specific checks as scripts. Always -race in tests.

Más de este repositorio

mismo repositorio

make-interfaces-feel-better

poteto/noodle

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.

2026-03-19210

plan

poteto/noodle

Systematic planning for medium-to-large tasks. Gathers context, identifies domain skills, writes phased plans to brain/plans/. Does NOT implement. Use for new features, multi-file refactors, or architectural changes — not small fixes. Triggers: "plan this", "break this down".

2026-03-19210

frontend-design

poteto/noodle

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

2026-03-19210

adversarial-review

poteto/noodle

Adversarial code review using cross-model approach. Spawns reviewers on the opposing model (Claude uses Codex, Codex uses Claude) to challenge work from distinct critical lenses. Produces a synthesized verdict with findings and lead judgment. Triggers: "adversarial review".

2026-03-19210

ast-grep

poteto/noodle

Structural code search via ast-grep — use when code shape and element relationships matter, not just text. E.g., "find async functions without error handling", "refactor foo(a, b) to foo({ a, b })". Use Grep for simple name lookups.

2026-03-19210

brain

poteto/noodle

Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.

2026-03-19210

Go Best Practices

Pattern

When to apply

Minimal main

New binaries

Single bootstrap

App wiring across modes

Ordered shutdown

Long-running processes

Non-blocking fanout

Channel-based event systems

Concurrency testing

Any goroutine code

Layered config

Multi-source configuration

Cross-platform paths

File/config path resolution

Secure debug logging

HTTP client instrumentation

Golden test matrices

Rendering / output components

Focused linters

CI pipeline setup

Rules

main.go is a stub. Call cmd.Execute() and nothing else. Gate diagnostics (pprof) behind env vars.

One bootstrap path. All modes (interactive, headless, test) share the same initialization function. Two paths will drift.

Ordered shutdown. Cancel dependents before their dependencies, then run independent cleanup in parallel under a timeout context. WaitGroup the parallel phase.

Never block the sender. Non-blocking channel sends with an explicit drop policy. Log drops at debug level. Document the policy.

Test concurrency mechanically. testing/synctest for deterministic timing, goleak.VerifyNone for leak detection, dedicated regression tests for timer/channel deadlocks.

Explicit config precedence. Global → project → flags. Walk up from CWD to discover project configs, reverse so closest wins, deep-merge.

Centralize platform paths. One function per concern. Resolution order: env override → XDG → platform default → fallback.

Redact secrets in debug logs. Wrap http.RoundTripper. Filter headers matching authorization, api-key, token, secret. Gate on debug level to skip allocation in prod.

Golden tests over matrices. Cross dimensions (layout × theme × size) as parallel subtests. Sweep continuous ranges to catch off-by-one bugs.

Focused linters, not all linters. Enable what catches real bugs (bodyclose, noctx, tparallel). Disable noisy defaults. Add project-specific checks as scripts. Always -race in tests.