go-best-practices

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'.

Ir para a instalação

Repositório: poteto/noodle
Última atividade na origem: 19 de março de 2026 às 04:43
Idioma detectado do SKILL.md: inglês
Estrelas: 269
Forks: 15

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/poteto/noodle --skill go-best-practices

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

2 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

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.

Voltar à pesquisa Voltar à instalação

make-interfaces-feel-better

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-19

plan

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-19

frontend-design

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-19

Ver todas deste repositório

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.

go-best-practices

Informações da origem

Opções de instalação

Revise os arquivos de origem

Go Best Practices

Rules

Mais deste repositório

Go Best Practices

Rules

Mais deste repositório