kf-g-skill-naming-creation-organization-rules

Creation and Organization Conventions for skills

This skill is for consistently applying naming conventions and placement policies when adding, renaming, or organizing skills in this repository.

When to use this skill

Use this skill for requests such as the following.

• Want to create a new skill
• Want to decide the directory name of a skill
• Want to review whether the names of existing skills conform to the conventions
• Want to organize skills so they can be easily sorted in category order
• Want to distinguish external skills from self-made skills
• Want to decide how to add English frontmatter

Assumptions in this repository

Distinguish external skills from self-made skills

• skills-lock.json Skills contained in are treated as originating from an external repository
• External skills are premised on incorporating future updates, so as a rule do not directly change their directory names or contents
• Self-made skills are .agents/skills/ add under

Emphasize that similar skills are listed near each other

• .agents/skills/ When is displayed in alphabetical order, name skills so that skills in the same subject area are listed near each other
• Place the major category near the beginning of the name so that subject areas are aligned in the list

Naming conventions

Basic form

The directory name starts with a major category representing the subject area, and if necessary continues with a subcategory and a short English summary.

• Example: large-category-subcategory-subsubcategory-short-summary
• For the English rules for frontmatter, follow the later section "Unify frontmatter in English".

A major category is required

• A major category is not an extension but a noun representing the skill's subject area
• Example: markdown, skill, git, python, shell, research

Subcategories are optional

• After the major category, you may add a subcategory only when necessary
• Do not fix it to three levels: major, medium, and minor
• First prioritize considering whether a major category + about one subcategory is sufficient
• Do not increase unnecessary categories just for classification

Place the English summary at the end

• At the end, place a short English summary that makes the skill's content clear at a glance
• Stop at a noun phrase or short function name whenever possible
• Do not make it too long

Good examples:

• change-review-checkpoints
• paper-summary
• log-analysis
• comparison-table-formatting

Examples to avoid:

• review-changes-clearly-for-humans
• read-papers-and-organize-key-points
• investigate-logs-and-list-possible-causes

Unify frontmatter in English

• description Make an English sentence of about 1 to 2 sentences explaining the skill's purpose and trigger conditions
• The body and normal output may be in Japanese, but do not use Japanese in frontmatter

How to decide the major category

Reuse existing major categories as much as possible

When creating a new skill, first look at existing skill names and check whether there is a word that can naturally be used as a major category.

Examples that are easy to reuse at present:

• markdown
• skill

If it does not already exist, you may add it as new

If no existing top-level category fits the skill being created, you may create a new top-level category.

Examples of addition candidates:

• git
• python
• shell
• research
• docs
• agent
• prompt

Do not use unnatural words as top-level categories for a subject area

• Do not use verbs or temporary purpose names as top-level categories
• Make top-level categories nouns that function as an axis for grouping and listing similar skills together

Naming procedure

When deciding on a skill name, think in the following order.

1. Decide the subject area that the skill mainly deals with.
2. Check whether there is a top-level category that can be used for existing skills, and reuse it if there is.
3. If there is not enough, add a new top-level category with a short English noun.
4. Only if necessary, add one or two lower-level categories.
5. At the end, place a short English overview.
6. frontmatter の description Write in English.
7. Check whether it is not too long and whether its meaning is understandable when viewed in a list.

Naming examples

Use names like the following as a standard.

melumuccu/ai Examples in :

• kf-g-markdown-table-comparison-table-formatting
• kf-g-markdown-link-internal-link-organization
• kf-g-skill-review-skill-description-review
• kf-g-skill-tuning-description-optimization
• kf-g-git-commit-japanese-commit-message
• kf-g-git-review-change-review-checkpoints
• kf-g-python-test-pytest-test-addition
• kf-g-shell-log-log-analysis
• kf-g-research-paper-paper-summary

Examples in other repositories:

• kf-pj-markdown-list-ordered-list-cross-reference
• kf-pj-skill-review-skill-description-review
• kf-pj-git-commit-japanese-commit-message
• kf-pj-shell-log-log-analysis

Policy for organization and renaming

Exclude external skills from organization

• skills-lock.json External skills in are not subject to the naming convention
• If changes to external skills are needed, prioritize supplementing them with your own skills

Organize only your own skills according to the convention

• When adding, renaming, or relocating your own skills, follow this convention
• Prioritize having skills of the same lineage listed together, and align the granularity of top-level categories

After changes, update the list information as well

• .claude-plugin/marketplace.json If you are using , reflect the addition, renaming, and deletion of skills and update the plugin classification as well

Policy for output

• If the user is only asking for name ideas, present multiple candidate names
• If the user is asking for creation as well, prepare a directory name that follows the convention and SKILL.md prepare
• SKILL.md When creating , write the frontmatter's description write in English
• If necessary, briefly explain why you chose that top-level category
• Avoid excessively fine-grained categorization

Final check

Before returning, check the following.

• The top-level category is a natural noun as a subject area
• Lower-level categories have not increased more than necessary
• The English overview at the end is short and easy to understand
• frontmatter の description is in English
• External skills and your own skills are not being confused
• You have checked whether the list needs to be updated after adding or renaming a skill