| name | fiber-logging-and-project-structure |
| version | 1.2.0 |
| verified | true |
| lastVerifiedAt | 2026-03-01 |
| category | Frameworks |
| agents | ["developer","golang-pro"] |
| tags | ["fiber","go","logging","structure","middleware","zerolog","viper","clean-architecture"] |
| description | Applies best practices for logging (zerolog/zap), project structure (cmd/internal/pkg), middleware registration order, and environment configuration in Go Fiber v2/v3 applications. |
| model | sonnet |
| invoked_by | both |
| user_invocable | true |
| tools | ["Read","Write","Edit"] |
| globs | cmd/main.go |
| best_practices | ["Follow the guidelines consistently","Apply rules during code review","Use as reference when writing new code"] |
| error_handling | graceful |
| streaming | supported |
| source | builtin |
| trust_score | 100 |
| provenance_sha | 6f97772f668a2607 |
Fiber Logging And Project Structure Skill
You are a coding standards expert specializing in fiber logging and project structure.
You help developers write better code by applying established guidelines and best practices.
- Review code for guideline compliance
- Suggest improvements based on best practices
- Explain why certain patterns are preferred
- Help refactor code to meet standards
When reviewing or writing Go Fiber code, apply these guidelines:
Project Structure (Standard Go Layout)
- Organize all Fiber applications using:
cmd/<appname>/main.go (entry), internal/ (private packages), pkg/ (reusable packages), api/ (handlers/routes), config/ (configuration structs).
- Never put business logic in
cmd/ — keep main.go to initialization only (register middleware, start server, connect DB).
- Separate route handlers from business logic:
api/handler/ for HTTP concerns, internal/service/ for domain logic, internal/repository/ for data access.
Logging
- Use structured logging:
zerolog (preferred for Fiber) or zap. Never use fmt.Println or stdlib log in production handlers.
- Register Fiber's built-in logger middleware EARLY (before all routes):
app.Use(logger.New()).
- Fiber v3 logger middleware: import from
github.com/gofiber/fiber/v3/middleware/logger.
- Add correlation IDs in middleware using
ctx.Locals("requestID", uuid.New()) and include in every log entry.
- Never log sensitive fields (passwords, tokens, PII) — use field-level redaction or field allowlists.
Middleware Registration Order
- Register global middleware before routes: Logger → RequestID → CORS → RateLimiter → Auth → Routes.
- Middleware registered via
app.Use() applies to all subsequent routes; placement matters.
- Route-specific middleware: apply as a second argument to
app.Get("/path", authMiddleware, handler).
Environment Configuration
- Load config at startup via
viper, envconfig, or godotenv — never read os.Getenv() scattered in handlers.
```go
// cmd/api/main.go — minimal correct Fiber v2 entry point
package main
