Loading...
Loading...
Found 8 Skills
Build tool for Go projects. Use when the user wants to create, edit, or understand Way-specific Magefiles, build targets, or automate Go project tasks.
You are a Python project architecture expert specializing in scaffolding production-ready Python applications. Generate complete project structures with modern tooling (uv, FastAPI, Django), type hint
Recommended Go linters and golangci-lint configuration. Use when setting up linting for a Go project or configuring CI/CD.
Exclusive skill set for the GoFrame development framework. Provides a complete framework usage guide for Go language developers, covering best practices for core components such as command-line management, configuration management, logging components, error handling, data validation, type conversion, cache management, template engines, database ORM, and I18n internationalization. Includes project engineering structure specifications, development model guidelines, solutions to common problems, and rich practical code examples. Suitable for building various Go projects such as RESTful APIs, gRPC microservices, and web applications, helping developers quickly master the features of the GoFrame framework and improve development efficiency and code quality.
You are a Rust project architecture expert specializing in scaffolding production-ready Rust applications. Generate complete project structures with cargo tooling, proper module organization, testing
Use when building, testing, linting, or running Go code in projects that have a Makefile. Prefer make targets over calling go commands directly.
Modern Go Web application architecture guide. Use when creating new Go web projects, APIs, or microservices. Covers project structure, tech stack selection, and best practices based on Go standards.
Generate or update tests for changed files in the current git branch, using statement coverage as the evaluation metric (target: 80%+). Use when: (1) the user asks to "write tests for my changes", "add tests for the current branch", or "improve coverage", (2) after implementing a feature to ensure adequate test coverage, (3) before a PR to verify changed code is tested. Supports Vitest and Cargo projects. Invoked with /test-generator or phrases like "generate tests", "test my changes", "cover the diff".