Skill Store 33

Naming

The code-naming rules.

by timschoch

The skill

The code-naming rules. Use before naming a variable, function, file, type, table, route, component, event, or env var, and when a request's word differs from the repo's.

This skill's licence does not allow redistribution, so the store does not show its text. Read it at the source.

Use this skill

Connect your agent to the Skill Store MCP server and ask for it by ref: timschoch/naming-404275861.

Markdown version

Details

Publisher
timschoch
Category
Software Development › Languages & frameworks
Updated
2026-10-17

References

More from timschoch

  • Check Upstream Compare this fork with its upstream and merge upstream in.
  • Ask Matt Ask which skill or flow fits your situation.
  • Code Review Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Stand…
  • Implement Implement a piece of work based on a spec or set of tickets.

Related skills

  • Go Naming Use when naming any Go identifier — packages, types, functions, methods, variables, constants, or…
  • Coding Guidelines Use when asking about Rust code style or best practices.
  • Naming Format Use when reviewing file names, renaming files, fixing naming conventions, or auditing exports.
  • Typescript Naming Apply, review, and explain TypeScript naming conventions.
  • Naming Convention Establish naming rules for components, tokens, and layers with patterns and worked examples.