store-metadata

Generate ASO-optimized App Store metadata into fastlane/metadata with keyword deduplication.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/no-problem-dev/store-craft --skill store-metadata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: store-metadata
Source: https://github.com/no-problem-dev/store-craft/tree/main/plugins/store-assets/skills/store-metadata
Command: npx skills add https://github.com/no-problem-dev/store-craft --skill store-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

App Store のメタデータを最適化・一元管理する作業を軽減し、タイトル・サブタイトル・キーワード・説明文・プロモーションテキスト・リリースノートを 4文字体系対応で自動生成します。

Core Features & Use Cases

  • ASO 最適化されたメタデータを自動生成し、fastlane/metadata/{locale}/ に直接書き出す
  • 4 文字体系(ひらがな・カタカナ・漢字・ローマ字)を活用した日本語対応のキーワード設計
  • 複数ロケール対応とタイトル/サブタイトル/キーワードの重複排除を実現
  • store-craft.config.json の情報を元に統一性のあるメタデータを生成
  • fastlane/metadata/{locale}/ ディレクトリ構造への適切なファイル出力を保証

Quick Start

Generate and write ASO-optimized App Store metadata to fastlane/metadata/{locale} using the metadata-writer

Frequently Asked Questions about store-metadata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate ASO optimized App Store metadata for Japanese localization?

To generate ASO optimized App Store metadata for Japanese localization, this Skill outputs titles, subtitles, keywords, and descriptions utilizing four character systems: Hiragana, Katakana, Kanji, and Romaji. It writes the translated files directly into your fastlane metadata directory structure for immediate delivery.

Can I write App Store metadata directly into the fastlane directory structure?

Yes, you can write App Store metadata directly into the fastlane directory structure. This Skill generates the localized text and saves it into the respective fastlane/metadata/{locale}/ folders, ensuring the output meets fastlane constraints and is ready for delivery.

How do I prevent keyword duplication across App Store titles and subtitles?

To prevent keyword duplication across App Store titles and subtitles, this Skill applies keyword deduplication across multiple locales. It validates text length and ensures title, subtitle, and keyword fields remain unique and compliant with App Store limits.

What is the best way to manage four character systems for Japanese ASO keywords?

The best way to manage four character systems for Japanese ASO keywords is to leverage a unified configuration file. This Skill uses store-craft.config.json to design keywords across Hiragana, Katakana, Kanji, and Romaji, generating consistent metadata.

Does fastlane metadata localization support automatic length validation for App Store fields?

Yes, fastlane metadata localization supports automatic length validation for App Store fields. This Skill enforces ready-for-delivery constraints by validating the length of generated titles, subtitles, keywords, and promotional texts before writing them to the locale directories.

What configuration is required to automate App Store metadata generation across multiple locales?

To automate App Store metadata generation across multiple locales, a store-craft.config.json file is required. This configuration provides the foundational information needed to generate unified, ASO-optimized text and write it to the respective fastlane/metadata/{locale}/ directories.