Find agent skills by outcome

- keep business components separate from primitives: components/marketplace

features/*/ui

ENVIRONMENT: extreme minimal void — a single seamless bone-white plane meeting a clay-toned floor

one thin horizontal copper line at knee height as the only scene element. Nothing else. Negative space is 70% of the frame.

- Option 2: Results-Oriented (focused on business value

metrics

Business model: [B2B/B2C

pricing model if visible]

| Contact | [email / phone / address

or Not found] |

- Acquisition or partnership assessment: leadership

business model

For the most critical business paths

create:

- Config management: env vars

feature flags

- Catalog business rules: validations

formulas

- Use smart sampling for expensive analyses (e.g.

function-level call graphs) prioritizing business-critical paths.

- Executives: business capabilities

critical flows

3. HTTP Lifecycle: server.Module() own mux provide + start/shutdown Invoke

no business route logic inside server module

1. dig.Build(opts ...Option): Assemble DI container

return app startup function

6. Business domains fully encapsulated via Module()

internal registration hidden

2. Viper centralized multi-source configuration management

compatible dev/prod environment separation

- No godotenv standalone usage

fully unified viper env management

- Every business domain must own a dedicated module.go file

expose unique Module() dig.Option to encapsulate domain internal Provide + domain exclusive route Invoke

- One business domain = one vertical independent module

internal all layers encapsulated inside domain folder

Each business domain forms independent vertical closed module under /internal/domain/

self-contains model/repo/service/handler + dedicated module.go.

You are a senior industrial Go backend architect

specializing in vertical autonomous business domain modular architecture based on shanjunmei/dig compile-time DI. All output strictly implement full business domain isolation

Go Industrial Autonomous Business Module Coding Spec (shanjunmei/dig Compile-Time DI)

Scene: Industrial independent vertical business domain modularization

lightweight infra simplification(config/pgdb no module.go)

- When new information contradicts prior research (e.g.

an official email reply from a venue)

- All business types

constructors and constants must be placed in separate .go files without build tags (e.g. main.go). Failing to do so will cause missing-type compilation errors during normal builds.