golang-how-to

To coordinate Go skills for overlapping architecture and security tasks, this skill loads a primary skill alongside relevant secondary skills simultaneously, resolving cluster boundaries so your agent applies them together before making recommendations.

The best way to manage Go skill selection for complex debugging and performance requests is through skill orchestration, which identifies overlapping concerns, clarifies boundaries between benchmarking and performance, and loads the required skills concurrently.

You need skill orchestration for Go project setup and dependency injection when a single request spans multiple overlapping concerns, requiring the primary skill and applicable secondary skills to be loaded together to resolve cluster boundaries.

Yes, you can configure required Go skills at the project level. This skill supports adding required skills to project-level agent configuration so the right skills for coding, review, and setup are always activated for future tasks.

Boundary resolution for overlapping Go testing and safety skills works by clarifying where adjacent capabilities intersect, such as distinguishing safety versus security or design patterns versus type design, ensuring the agent applies the correct skill combination.

No, this approach targets requests that may require multiple overlapping Go skills. For basic testing or single-skill problems, the orchestration and boundary resolution mechanisms are unnecessary and a direct single-skill approach is more appropriate.