branding-iron

Whenever the user is struggling to name something — a project, a variable, a feature, a service, a team, a document — heat up the branding iron and stamp it…

Skill by aubcake

IndexedMIT★ 3

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/aubcake-branding-iron

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Whenever the user is struggling to name something — a project, a variable, a feature, a service, a team, a document — heat up the branding iron and stamp it: offer a few candidate names with the reasoning behind each, then a recommendation. Use this any time 'what should I call this' or 'I can't think of a good name' comes up.

Use cases: documents

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/branding-iron

What's inside

Skill name: branding-iron
Description: Whenever the user is struggling to name something — a project, a variable, a feature, a service, a team, a document — heat up the branding iron and stamp it: offer a few candidate names with the reasoning behind each, then a recommendation. Use this any time 'what should I call this' or 'I can't think of a good name' comes up.
License: MIT
Instructions: 31 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

Application:

Use this only in conversational replies to the user. Never apply it when producing work artifacts — writing code, documents, emails, or other deliverables.

THE MECHANIC

A name is a brand — it sticks to the thing forever and everyone reads it a hundred times. Heat the iron and offer a few stamps, each with its reasoning:

```
🔥🐄 BRANDING IRON — naming: "<the thing and what it does>"

   🅰️ <name>  — <style: literal / descriptive>
        why: <what it communicates instantly; who reads it and gets it>
        watch out: <collision, ambiguity, or how it ages>

   🅱️ <name>  — <style: metaphor / memorable>
        why: <…>     watch out: <…>

   🅲 <name>  — <style: short / neutral / boring-on-purpose>
        why: <…>     watch out: <…>

   🐄 Stamp this one: <recommendation + the single reason it wins>
```

Rules:
- Match the naming style to the CONTEXT. A variable wants clarity and convention; a product wants memorability; an internal tool can afford a little fun. Don't give a database column a brand-name.
- Always flag the practical hazards: name collisions, things that read badly when abbreviated, in-jokes that won't survive a new teammate, names that lie about what the thing does.
- Honor existing conventions in the user's codebase or org over cleverness. A consistent boring name beats a clever inconsistent one.
- Give a clear recommendation, not just a menu. The user came here because choosing is the hard part.

From aubcake/shills, MIT.

Signals

Stars: 3
Forks: 1
Open issues: 0
Last commit (this folder): Jun 12, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/aubcake/shills
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from aubcake

Cite this page

branding-iron skill. Agent Mart. https://agentmart.dev/skills/aubcake-branding-iron (last updated 2026-10-24)