Capitalize type names so variables can use them

The go-code skill now asks for type names with a capital letter and for
all other package-level names in lower case. A lower-case type name
clashes with an import, such as a log type with the log package, and
with local variables that have the name of their type, such as a memory
variable of a memory type. A capital letter keeps both names free.

diff --git a/.agents/skills/go-code/SKILL.md b/.agents/skills/go-code/SKILL.md
index 71ff6c9eb749de60864ac6d91f84a2c1c594765f..edaf3770e2aee6b0619f27b7f29b00c31e2d0186 100644 (file)
--- a/.agents/skills/go-code/SKILL.md
+++ b/.agents/skills/go-code/SKILL.md
@@ -19,8 +19,9 @@ description: Go style rules. Use before you write or review Go code.
   integration with the name of that feature. Start the names of its
   files with the same name. Keep a name generic only when more than one
   feature uses it.
   integration with the name of that feature. Start the names of its
   files with the same name. Keep a name generic only when more than one
   feature uses it.

-- Use unexported names. In the `main` package, an exported name has no
-  effect.
+- Write type names with a capital letter, so that a variable can have
+  the name of its type. Write all other package-level names in lower
+  case.

 - Write all the letters of an initialism in one case.
 - Put entry points first, then each struct's methods as a group, then
   standalone utility functions. Do not put a utility function between
 - Write all the letters of an initialism in one case.
 - Put entry points first, then each struct's methods as a group, then
   standalone utility functions. Do not put a utility function between