Pick and record the names of a new concept in every layer (database table and column, ORM model, DTO, route, JSON field, UI label), and give every stored item kind the same resource shape and the same actions. Holds the glossary format with an Avoid list, the per-layer name table, the resource template, standard and custom actions, field, enum, state and owner rules, the Agenta convention table, the folder naming rule, and the spec naming checklist. Use when writing or changing a spec, design or plan that adds or renames a table, column, index, route, DTO field, enum value, config field or UI label, when asked "what should this be called", "is this name consistent", "fill the naming section", or when another skill asks for the per-layer names. It applies even when the word "naming" never appears. Do not use it for field grouping by role (use design-interfaces), for migration errors, or for a rated review (use review-naming).
99%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
This skill hasn't been evaluated yet
tessl scenario generatetessl eval runAgenta-AI/agenta
8d6f0df
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.