All skills
gogf avatar

/goframe-v2

@911705d
by GoFramegogf/skills81 stars
3

GoFrame v2 development skill. Use only when the target Go project uses or is explicitly adopting GoFrame v2: the nearest go.mod requires github.com/gogf/gf/v2, existing Go files import github.com/gogf/gf/v2 or any github.com/gogf/gf/v2/... component package, or the user asks to scaffold, migrate, or build with GoFrame. Trigger for GoFrame-backed Go work such as APIs/controllers/services, middleware, routing/config, ORM/DAO/DO/entity/database operations, gf CLI/codegen, HTTP/gRPC services, and microservice conventions. Do not trigger for generic Go projects without GoFrame evidence, frontend-only work, shell scripts, or unrelated infrastructure tasks.

Use this Skill: https://skilld.dev/gh/gogf/skills/goframe-v2

This session only. Nothing lands on disk.

examplesconfigapolloREADME.MD

≈1.1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Apollo Configuration Center Example

Description

This directory contains an example demonstrating how to integrate Apollo configuration center with GoFrame applications. It shows:

  1. Apollo Client Configuration

    • Apollo client setup and initialization
    • Configuration adapter implementation
    • Error handling and logging
  2. Configuration Management

    • Configuration loading and parsing
    • Dynamic configuration updates
    • Configuration value retrieval

Directory Structure

.
├── boot/           # Bootstrap configuration
│   └── boot.go     # Apollo client initialization
├── main.go         # Main application entry
├── go.mod          # Go module file
└── go.sum          # Go module checksums

Requirements

Features

The example showcases the following features:

  1. Apollo Integration

    • Client configuration
    • Connection management
    • Namespace handling
    • Error handling
  2. Configuration Management

    • Configuration loading
    • Value retrieval
    • Type conversion
    • Default values
  3. Dynamic Updates

    • Configuration watching
    • Change notification
    • Hot reload support

Configuration

Apollo Server

  1. Server Configuration:

    • Default port: 8080
    • Default cluster: default
    • Default namespace: application
  2. Authentication:

    • AppID based authentication
    • Optional access key support
    • Cluster level isolation

Client Configuration

  1. Basic Settings:

    • AppID: Application identifier
    • Cluster: Configuration cluster
    • IP: Apollo server address
  2. Advanced Options:

    • Namespace customization
    • Cache management
    • Retry settings

Usage

  1. Start Apollo Server:

    # Start Apollo server using Docker
    docker run -p 8080:8080 apolloconfig/apollo-portal
  2. Configure Apollo:

    • Create application namespace
    • Add configuration items
    • Publish configuration
  3. Run Example:

    go run main.go

Implementation Details

  1. Client Setup

    • Apollo client initialization
    • Configuration adapter setup
    • Error handling configuration
  2. Configuration Access

    • Value retrieval methods
    • Type conversion handling
    • Default value management
  3. Error Handling

    • Connection errors
    • Configuration errors
    • Type conversion errors

Best Practices

  1. Client Configuration

    • Use environment variables for sensitive data
    • Configure appropriate timeouts
    • Implement proper error handling
  2. Configuration Management

    • Use structured configuration keys
    • Implement configuration validation
    • Handle configuration updates gracefully
  3. Error Handling

    • Log configuration errors
    • Provide fallback values
    • Implement retry mechanisms

Troubleshooting

  1. Connection Issues:

    • Verify Apollo server status
    • Check network connectivity
    • Validate authentication settings
  2. Configuration Issues:

    • Check namespace configuration
    • Verify configuration format
    • Review access permissions
  3. Client Issues:

    • Check client configuration
    • Verify AppID settings
    • Review cluster configuration
  4. General Issues:

    • Check application logs
    • Verify dependencies
    • Review error messages

Source: SKILL.md on GitHub

1 alert16d5 checks · Risk MEDIUM
  • Gen Agent Trust Hub16d

    The skill provides a comprehensive development guide and code examples for the GoFrame v2 framework. While highly informative for Go developers, it contains several examples with hardcoded placeholder secrets, tokens, and specific local file paths to sensitive configuration files (like Kubernetes credentials). These elements are provided for demonstration purposes but represent insecure practices if used in production without modification.

  • Socket16d

    5 alerts: gptSecurity, gptAnomaly

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer6mo

    227/949 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 911705d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 months ago.

Steadyupdated 4 months ago
  • Go
  • Database
  • goframe
  • orm
  • http
  • grpc
  • microservices
  • crud
  • scaffolding
  • middleware

README badge

README badge for gogf/skills

Provides instruction and conventions for developing with GoFrame v2, a modular Go framework for building HTTP and gRPC services, microservices, and database operations using its ORM, CLI tooling, and project scaffolding. Use this skill when the target project has GoFrame v2 as a dependency or when the user requests scaffolding, migrations, or service development with GoFrame conventions.

Generated from the current SKILL.md.

When should I use this skill?
Use this skill only when your Go project uses GoFrame v2, indicated by github.com/gogf/gf/v2 in go.mod or imports. Do not use for generic Go projects, frontend work, or infrastructure tasks unrelated to GoFrame.
Should I manually set created_at and updated_at fields?
No. GoFrame automatically writes created_at on insert and updated_at on insert/update/save. Manually setting these fields is redundant and violates project conventions.
What should I use for database operations instead of g.Map?
Always use DO objects from internal/model/do/. DO struct fields are interface{}, unset fields remain nil and are automatically ignored by the ORM.
How does soft delete work in GoFrame?
Call Delete() on the DAO; GoFrame automatically converts it to UPDATE SET deleted_at = NOW(). Queries automatically filter out soft-deleted rows without requiring manual WhereNull conditions.
Where should I implement business logic?
Implement business logic directly in the service/ directory. Do not use the logic/ directory unless explicitly requested.

Generated from the current SKILL.md. These answers refresh after source changes.