Tag List

This document defines the rules and shared vocabulary for tags used in blog articles. Update this document when adding or changing tags.

Tag Rules

Brand/product name tags: Use official naming (e.g., Claude Code, GitHub Actions)
Technical term tags: Use English as-is (e.g., Git, SSH)
General concept tags: Use Japanese (e.g., 自動化, セキュリティ)
When English + Japanese clarification is needed: Add clarification in full-width parentheses (e.g., DX（開発者体験）)

tags:
  - claude-code
  - ai
  - automation

Avoid creating duplicate tags representing the same concept (e.g., do not create both dev-tools and development-tools)

When selecting tags for an article, follow these rules:

Maximum 7 tags per article: Each article should have at most 7 tags. More than 7 tags are not allowed in general.
Pick tags from the article content: Read the article and pick relevant tags based on its actual content. Do not tag based on loosely related topics.
Prefer broader tags over overly specific ones: If a tag is too specific or niche, remove it from the candidates. Tags should be useful for categorization, not exhaustive labeling.
Check the full tag list: Before finalizing tags, review the full tag list below. Consider whether existing tags can cover the concept, or whether tags should be combined.
Exception for very long articles: If an article is very long and genuinely covers many distinct topics, exceeding 7 tags is acceptable. Apply this exception sparingly.
No limit on total tags: There is no restriction on the total number of unique tags across the whole site. The limit applies per article only.

Tags that should NOT be created. These are too broad, vague, or not useful for categorization.