cc-c-project-standard
Use when Pure C module interfaces, ownership contracts, error-code cleanup paths, build conventions or C engineering validation…
@bovinphangInstall SkillDevelopment
Skill
/cc-go-project-standard
Use when Go module/workspace organization, package ownership, error and context conventions, dependency boundaries or engineering validation need design or review.
Claude Code
$ npx -y skills add bovinphang/frontend-craft --skill cc-go-project-standard --agent claude-code
Codex
$ npx skills add bovinphang/frontend-craft --skill cc-go-project-standard -a codex -y
Cursor
$ npx skills add bovinphang/frontend-craft --skill cc-go-project-standard -a cursor -y
Gemini CLI
$ npx skills add bovinphang/frontend-craft --skill cc-go-project-standard -a gemini-cli -y
GitHub Copilot
$ npx skills add bovinphang/frontend-craft --skill cc-go-project-standard -a github-copilot -y
OpenCode
$ npx skills add bovinphang/frontend-craft --skill cc-go-project-standard -a opencode -y
Windsurf
$ npx skills add bovinphang/frontend-craft --skill cc-go-project-standard -a windsurf -y
SKILL.md
cc-go-project-standard.SKILL.mdname: cc-go-project-standard
description: "Use when Go module/workspace organization, package ownership, error and context conventions, dependency boundaries or engineering validation need design or review."
Go project engineering
Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language.
Locate go.work and the nearest go.mod; preserve module import paths and dependency versions. Do not run a root-level go get simply because the task is in a submodule.
Apply the workflow
1. Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now. 2. Apply the [specialist checks](references/practice.md), establishing the input evidence before selecting the smallest change. 3. Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result. 4. Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only.
Task boundary
A focused goroutine/channel lifecycle defect belongs to the concurrency specialty.
Engineering practices
Read the [local engineering decisions](references/engineering-practices.md) for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.
Read more
name: cc-go-project-standard description: "Use when Go module/workspace organization, package ownership, error and context conventions, dependency boundaries or engineering validation need design or review."
Go project engineering
Apply to libraries, CLI tools, desktop cores and services. Determine the application role from the actual project; a frontend/backend product name does not constrain the language.
Locate go.work and the nearest go.mod; preserve module import paths and dependency versions. Do not run a root-level go get simply because the task is in a submodule.
Apply the workflow
1. Locate the actual project, task boundary and existing contracts; load only the language and domain material needed now. 2. Apply the [specialist checks](references/practice.md), establishing the input evidence before selecting the smallest change. 3. Verify affected behavior with existing repository tools. Explicitly report missing tools, environments or execution; a plan is not a passing result. 4. Deliver scope, specialist decisions, actual verification and remaining risk. A review-only task stays read-only.
Task boundary
A focused goroutine/channel lifecycle defect belongs to the concurrency specialty.
Engineering practices
Read the [local engineering decisions](references/engineering-practices.md) for this task and follow their links to relevant shared principles. Apply levels and exceptions against actual project contracts; product frontend/backend labels do not constrain language or role.
Stats
24
Stars
3
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withfrontend-craft
frontend-craft is a universal frontend plugin that brings the same opinionated engineering standards to all 15 AI coding assistants.
2374 skills14 agents6 MCP
Stars on GitHub
Momentum
- stars in total
- 23
Other skills on frontend-craft.
@bovinphangInstall Skillcc-cpp-project-standar…
Use when C++ module/header boundaries, resource lifetime, exception safety, ABI, build-standard conventions or project-wide C++…
@bovinphangInstall Skillcc-debug-methodology
Use when diagnosing unexplained engineering failures, build errors, service exceptions, inconsistent data, or cross-layer faults…
@bovinphangInstall Skillcc-doc-sync-core
Use when project documentation, multilingual READMEs, setup instructions, CLI usage, or public capability descriptions drift from…
@bovinphangInstall Skillcc-drawio-studio
Use when creating editable technical diagrams with draw.io / diagrams.net sources, including architecture diagrams, ERD, UML,…
@bovinphangInstall Skillcc-electron-project-st…
Use when an Electron application needs work on main/preload/renderer boundaries, contextBridge IPC, sender validation, sandbox…
@bovinphangInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about cc-go-project-standard.
- Which coding agents can use cc-go-project-standard?
- cc-go-project-standard installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.