naming-convention

Structured naming convention system for code identifiers. Use when naming or renaming variables, functions, methods, classes, files, DB tables/columns, routes, or CSS classes; when validating identifiers against a convention; or when the user mentions naming, camelCase, snake_case, kebab-case, prefixes, or suffixes. Enforces a closed vocabulary (prefix + entity + suffix) with per-language casing rules.

Jump to install

Repository: thonymg/skills
Last source activity: July 20, 2026 at 13:05
Detected SKILL.md language: English
Stars: 1
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/thonymg/skills --skill naming-convention

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

19 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

plan-feat

Produce module-level implementation plans for a NEW feature or application — markdown plan files in a per-feature folder, never code. Takes a free prompt, a *.md file, or a folder of *.md docs; cross-checks project docs against each other and against the code before planning, splits large scope into modules, and writes one directive plan file per module (needs, order, checks, relations, vigilance points, Gherkin scenarios, glossed invariants) with a progress tracker and critique rounds. Scales to a whole application via staged batches. Use when the user asks for an implementation plan, to plan a new feature or app, un plan d'implémentation, plan de feature, découpage en modules, planifier une application, or invokes "/plan-feat". Planning only — never implements. NOT for modifying, extending, or updating an existing feature or its plans — use the sibling skill plan-update for that.

2026-08-01

plan-update

Produce module-level update plans for changing an existing feature or adding features to an existing system — markdown plan files, never code. Reuses plan-feat's discipline and adds what change requires: current-state reconnaissance, impact analysis with a ripple set, delta plans (current → target), regression vigilance, data migration, backward compatibility, deprecation, and blocking coherence gates. Revises existing plan files in place, keeping the set coherent. Use when the user asks to plan a change to an existing feature (e.g. "plan a change to the checkout flow"), to update or evolve a feature, modifier une feature, faire évoluer une feature, ajouter une feature à l'existant, plan de modification, plan d'évolution, or invokes "/plan-update". Planning only — never implements. NOT for green-field features with no existing plans or code — use the sibling skill plan-feat for that.

2026-08-01

fix-root

End-to-end bug fix workflow, root cause first. Given a bug description, an error message, or a pasted stack trace, generates at least 3 distinct hypotheses for the cause before picking one (anchoring-bias gate), gathers evidence per hypothesis via the codebase graph (trace_path, search_graph, get_code_snippet, query_graph), maps every caller/consumer the fix would touch, writes a failing test first, applies the minimal fix at the root cause only, then re-verifies the change's actual impact and consequences with the same graph (detect_changes, trace_path, search_graph) — comparing what actually changed against what was planned, checking sibling occurrences of the same bug, confirming every caller still holds — before running the full suite and a separate self-critique pass. Use when the user asks to fix a bug, find or understand the root cause, corrige ce bug, debug this error, resolve this stack trace or exception, do a root cause analysis, or invokes "/fix-root". Not for refactoring without a bug present.

2026-07-20

View all from this repository

name

naming-convention

description