스킬 golang-design-patterns

📦

golang-design-patterns

Name: golang-design-patterns
Author: samber

v1.2.1 콘텐츠 리비전 r1 중간 위험 ⚙️ 외부 명령어🔑 환경 변수⚡ 스크립트 포함🌐 네트워크 접근

Design Idiomatic Go APIs and Architecture

Go services become harder to maintain when initialization, resource ownership, and architectural boundaries are unclear. This skill guides practical pattern selection with focused Go examples.

지원: Codex Code(CC)

📊 70 적절함

Maintain this Skill? Claim it 📊 70 적절함

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "golang-design-patterns" from https://skillstore.io/skills/samber-golang-design-patterns.md and its manifest at https://skillstore.io/api/skills/samber-golang-design-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/samber-golang-design-patterns.md 서명된 manifest GET /api/skills/samber-golang-design-patterns/manifest 서명된 lockfile GET /api/skills/samber-golang-design-patterns/lockfile

테스트해 보기

"golang-design-patterns" 사용 중입니다. What architecture should I use for a small CSV-processing CLI?

예상 결과:

Confirm team preferences and expected growth before adding layers.
Use a flat layout with a small entry point and focused transformation functions.
Introduce additional packages only when responsibilities or testing needs justify them.

"golang-design-patterns" 사용 중입니다. Our service opens its database in init and has no shutdown deadline. What should change?

예상 결과:

Finding: Implicit database initialization hides dependencies and prevents normal error propagation.
Recommendation: Open the database explicitly during startup and inject it into repositories.
Finding: Shutdown can wait indefinitely without a separate deadline.
Recommendation: Handle termination signals, drain requests with a timeout, then close shared resources.

"golang-design-patterns" 사용 중입니다. How should Order and Billing communicate in a DDD application?

예상 결과:

Keep each bounded context responsible for its own domain model.
Publish an order event and translate it into a billing-specific representation.
Avoid importing another context's internal domain types directly.

보안 감사

중간 위험

v1 • 2026. 10. 15. 버전별 보고서 열기

All 89 static findings are false positives involving documentation syntax, ordinary Go constructs, illustrative configuration access, and homepage metadata. One semantic finding identifies internal errors returned directly to HTTP clients in two architecture examples. No evidence found of credential exfiltration, malicious command execution, or instructions to manipulate this audit.

스캔된 파일

1,779

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (1)

중간

references/clean-architecture.md:174-176 references/hexagonal-architecture.md:169-171

Internal Errors Exposed in HTTP Responses

Both architecture handlers pass err.Error() directly to http.Error. Wrapped repository or payment failures can expose infrastructure diagnostics to clients when these examples are adopted.

Both handlers explicitly write service error strings to response bodies without message sanitization. The exact disclosed details depend on downstream errors.

위험 요인

⚙️ 외부 명령어 (50)

🔑 환경 변수 (2)

evals/evals.json:35 SKILL.md:124

⚡ 스크립트 포함 (2)

references/ddd.md:158-163 references/ddd.md:199-202

🌐 네트워크 접근 (1)

SKILL.md:12

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/samber-golang-design-patterns/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-design-patterns/security.svg)](https://skillstore.io/skills/samber-golang-design-patterns?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/samber-golang-design-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-design-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/samber-golang-design-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

samber. (2026). golang-design-patterns security audit report (audit version 1) [Author version 1.2.1]. Skillstore. https://skillstore.io/skills/samber-golang-design-patterns/audits/1

BibTeX 인용

@techreport{samber-samber-golang-design-patterns-2026,
  author = {samber},
  title = {golang-design-patterns security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-design-patterns/audits/1},
  note = {Author version 1.2.1}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-design-patterns security audit report (audit version 1)"
version: "1.2.1"
type: report
authors:
  - name: "samber"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/samber-golang-design-patterns/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-design-patterns:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

100

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Design an Extensible Constructor

Define defaults, optional settings, and validation behavior for a Go library API that will evolve.

Review Service Resource Lifecycles

Identify hidden initialization, missing timeouts, unbounded pools, and incomplete shutdown handling before changing a service.

Choose Application Boundaries

Compare architecture styles for a growing service with multiple entry points and external integrations.

이 프롬프트를 사용해 보세요

Beginner: Choose a Simple Layout

I am building a Go CLI that transforms a CSV file. It should remain small. Ask about my architecture preference, then recommend a minimal layout.

Intermediate: Design Functional Options

Design a Go server constructor with read timeout, write timeout, and maximum connections. Use explicit defaults and explain how invalid options return errors.

Experienced: Review Lifecycle Risks

Review the attached Go service for implicit initialization, resource leaks, missing timeouts, and cancellation handling. Report findings first, then suggest focused changes and shutdown ordering.

Advanced: Compare Architecture Styles

Our Go order service has HTTP, gRPC, and message consumers with database and payment integrations. Ask about team preferences. Compare clean, hexagonal, and DDD approaches, including dependency direction and testability.

모범 사례

State the Go version, project scope, and team architecture preferences before requesting design guidance.
Keep resource ownership explicit and review cancellation, limits, and shutdown ordering together.
Adapt illustrative examples to local conventions and verify behavior with focused tests and security review.

피하기

Adding clean architecture or DDD layers to a small CLI without a concrete need.
Hiding runtime dependencies in init functions or mutable global variables.
Copying illustrative handlers into production without validating error disclosure and project-specific security requirements.