hai-naming

Name: hai-naming
Availability: InStock
Author: HylaruCoder

Analyze unclear software names and produce context-aware replacements.

278|15|Updated Mar 25, 2026

Search Tags:#architecture #code review #refactoring #domain modeling #api design #naming

Ready to run

npx skills add https://github.com/hylarucoder/hai-stack --skill hai-naming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hai-naming
Source: https://github.com/hylarucoder/hai-stack/tree/main/skills/hai-naming
Command: npx skills add https://github.com/hylarucoder/hai-stack --skill hai-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of confusing, vague, or misleading names that make software concepts harder to understand, maintain, and evolve.

Core Features & Use Cases

Three-Stage Naming Analysis: Generates research-stage, first-principles, and final-after-reading naming paths to make naming decisions transparent.
Architecture-Aware Naming Reviews: Evaluates names across concepts, responsibilities, call flows, boundaries, and system vocabulary instead of only applying style conventions.
Rename Planning: Produces prioritized rename suggestions with migration scope for variables, functions, modules, APIs, domain entities, events, and abstractions.

Quick Start

Ask the hai-naming skill to review the names in this module and recommend clearer replacements based on the system context.

Frequently Asked Questions about hai-naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I improve unclear names during code review?▼

Code review naming analysis evaluates unclear names across concepts, responsibilities, call flows, and boundaries to produce context-aware replacements. It generates a structured naming path to make decisions transparent and preserve system vocabulary.

What is the best way to rename domain entities for clearer architecture?▼

Architecture-aware naming reviews assess domain entities by analyzing responsibility boundaries and caller viewpoints. They produce prioritized rename suggestions with migration scope to ensure names align with system architecture and domain modeling.

How does naming analysis work for API design?▼

API design naming analysis applies a three-stage process: research-stage, first-principles, and final-after-reading. It evaluates API names against system vocabulary and caller viewpoints to generate replacements that clarify responsibility boundaries and endpoint contracts.

Can I use this for renaming variables and functions in module refactoring?▼

Module refactoring naming reviews cover variables, functions, files, and abstractions. They analyze unclear names within module boundaries and produce prioritized replacements with migration scope to maintain system vocabulary and responsibility separation.

When do I need structured naming analysis for product concepts and events?▼

Structured naming analysis is needed when product concepts or events affect system understanding and evolution. It analyzes names through research, first-principles, and final stages to ensure they preserve vocabulary and support migration planning.

Does naming analysis preserve existing system vocabulary during refactoring?▼

Yes, naming analysis explicitly preserves system vocabulary and responsibility boundaries. It evaluates unclear names against existing concepts and caller viewpoints before generating context-aware replacements with migration considerations.