Menu
Use when naming a project, repository, tool, or product and wanting a memorable, unique name
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | project-namer |
| license | MIT |
| description | Use when naming a project, repository, tool, or product and wanting a memorable, unique name |
| argument-hint | <project description or domain> |
| compatibility | NA |
| metadata | {"author":"jackchuka","scope":"generic","layer":"renderer"} |
Guide users from vague naming requirements to a memorable, unique name through structured exploration of scope, constraints, and style preferences.
digraph naming {
rankdir=TB;
"Understand scope" -> "Clarify constraints" -> "Offer style categories" -> "Generate options" -> "Iterate on feedback" -> "Converge";
"Iterate on feedback" -> "Offer style categories" [label="style shift"];
"Iterate on feedback" -> "Generate options" [label="refine"];
}
Ask what the project contains and does:
Identify naming constraints:
Present naming styles - let user pick direction:
| Style | Examples | When to suggest |
|---|---|---|
| Functional | toolkit, dev-tools, workflows | User wants clarity over personality |
| Character/Butler | friday, jeeves, pennyworth | User wants personality, memorability |
| Compound | devbox, workstation, codekit | Balance of clear + catchy |
| Metaphor | forge, lighthouse, compass | Evokes purpose without stating it |
| Coined | vercel, kubectl, nginx | Maximum uniqueness, brand potential |
Within chosen style, generate 5-8 options. For each:
Listen for signals:
When user shows interest, validate:
Good names are:
Avoid:
| Mistake | Fix |
|---|---|
| Jumping to suggestions without understanding scope | Ask what goes in it first |
| Only offering one style | Present style categories, let user choose |
| Giving up after one rejection | Rejection = information about preferences |
| Suggesting overused pop culture | Dig deeper - lesser-known references or original |
Triage and fix dependency update PRs (Renovate, Dependabot, etc.). Use when the user wants to review dependency PRs, check which are mergeable, fix failing CI on dependency updates, or clean up a backlog of automated dependency PRs. Also triggers when the user mentions "renovate PRs", "dependabot PRs", "dependency updates", "dep PRs".
Generate per-meeting prep briefs for today's calendar. Use when the user says "meeting prep", "prep my meetings", "prep brief", or invokes "/p-meeting-prep". Suitable for early-morning scheduled runs.
Generate an interactive HTML org explorer from a GitHub organization. Surfaces team hierarchy, members, owned repos, and CODEOWNERS path attributions. Two stages: collect.sh writes a canonical JSON, render.py emits a self-contained HTML file. The JSON is the cache (mtime ≤ 24h skips re-collection) and is hand-editable. Triggers: "org chart", "team chart", "visualize github org", "who owns this repo", "github team hierarchy", "/gh-org-chart"
Review and reorganize Claude Code permission settings across all config files (global settings.json, project settings.local.json, dotfiles copies). Identifies redundancy, misplaced permissions, and lack of read/write organization. Produces a clean layout where global settings are the source of truth and project-local files only contain project-specific overrides. Use this skill whenever the user mentions reviewing permissions, cleaning up settings, auditing allowed tools, reorganizing settings.json, or asking "what permissions do I have". Also use when adding new MCP servers or tools and wanting to decide what to pre-allow. Triggers: "review permissions", "audit settings", "clean up settings.json", "permissions audit", "/permissions-audit".
Audit skills for agentic orchestration quality. Checks subagent dispatch patterns, parallelism opportunities, anti-patterns, and alignment with the three-phase pattern (setup → dispatch → aggregate). Use when reviewing skill quality, saying "audit orchestration", "check my skills for parallelism", "skill orchestration review", or "/claude-skill-orchestration-audit".
Scan skills for prerequisite tools, MCP servers, and auth requirements, then check if everything is installed and authenticated. Offers to fix issues. Use when setting up a new machine, after installing skills, or to verify your environment. Triggers: "check prerequisites", "skill prereqs", "are my tools installed", "verify skill dependencies", "/claude-skill-prereq-audit".