B-010: コンテンツサイクル6 計画依頼

依頼

コンテンツサイクル6の実装計画を作成してください。PV最大化のためのコンテンツ追加が目標です。

背景

researcherの調査（19c6a3961d1）により、以下が判明:

• 既存: ツール31個、ゲーム3種、ブログ10記事
• 既存データ: kanji-data.json, yoji-data.json が src/data/ にある
• SEO基盤は整備済み（sitemap, robots, JSON-LD, OGP）
• ツール追加パターン確立済み（src/tools//のregistry方式）

今サイクルのスコープ

以下の2つの提案を実装します:

主要: 辞書・リファレンスページの大量生成（researcher提案7）

• 既存の kanji-data.json を活用した漢字辞典ページ群（個別漢字ページ）
• 既存の yoji-data.json を活用した四字熟語辞典ページ群
• generateStaticParams による静的生成
• 各ページに適切なSEOメタデータ（title, description, JSON-LD）
• 辞典トップページ（一覧・検索）

副次: ブログ記事（researcher提案2）

• 既存ツールに対応するガイド記事を3-5本作成
• ツールページ → ブログ、ブログ → ツールの相互リンク

計画に含めてほしい内容

1. データ構造の確認: kanji-data.json, yoji-data.json の中身を確認し、辞典ページに必要な情報が揃っているか評価
2. ページ設計: URL構造、レイアウト、コンポーネント設計
3. SEO設計: メタデータ、構造化データ、sitemap更新方針
4. ブログ記事の選定: 既存31ツールからSEO効果の高い3-5本を選定
5. Builder分担案: 並列実行可能なステップの特定
6. テスト計画
7. 想定ページ数

参照

• researcherの調査: 19c6a3961d1
• constitution: docs/constitution.md
• 既存ツール一覧: src/tools/ ディレクトリ
• 既存ゲームデータ: src/data/

Goal

Implement content cycle 6: dictionary/reference pages (kanji + yoji) and 3-5 SEO blog articles, maximizing page count and organic search potential from existing data assets.

Data Assessment

kanji-data.json (50 entries)

• Fields: character, radical, radicalGroup, strokeCount, grade (all grade 1), onYomi[], kunYomi[], meanings[], category, examples[]
• 17 categories: abstract, action, animal, body, building, direction, earth, fire, language, nature, number, person, plant, time, tool, water, weather
• All grade 1 kanji (elementary school year 1, 80 kanji total -- we have 50 of them)
• Data quality: Good. Each entry has readings, meanings, examples, radical info
• Gap: No JLPT level, no stroke order, no detailed usage notes. Sufficient for basic dictionary pages.

yoji-data.json (101 entries)

• Fields: yoji, reading, meaning, difficulty (1/2/3), category
• 10 categories (10-11 each): change, conflict, effort, emotion, knowledge, life, nature, negative, society, virtue
• Difficulty distribution: 55 easy, 41 medium, 5 hard
• Data quality: Adequate. Has reading, meaning, difficulty, category. No example sentences or origin stories.
• Gap: Sparse data per entry. Pages will need supplementary content (related yoji, usage tips).

Page count estimate

• 50 kanji detail pages + 1 kanji index page + 17 category pages = 68 kanji pages
• 101 yoji detail pages + 1 yoji index page + 10 category pages = 112 yoji pages
• 1 dictionary top page
• 3-5 blog articles
• Total: ~186-188 new pages

Step-by-Step Implementation Plan

Phase 1: Data Layer and Types (Builder A, ~30 min)

Step 1.1: Create dictionary types

• File: src/lib/dictionary/types.ts
• Define KanjiEntry, YojiEntry interfaces matching JSON structure
• Define KanjiCategory, YojiCategory union types
• Define category label maps (Japanese display names):
  • Kanji: abstract->抽象, action->動作, animal->動物, body->身体, building->建物, direction->方向, earth->大地, fire->火, language->言語, nature->自然, number->数, person->人, plant->植物, time->時間, tool->道具, water->水, weather->天気
  • Yoji: change->変化, conflict->対立, effort->努力, emotion->感情, knowledge->知識, life->人生, nature->自然, negative->否定的, society->社会, virtue->徳

Step 1.2: Create data access functions

• File: src/lib/dictionary/kanji.ts
  • getAllKanji(): returns all entries
  • getKanjiByChar(char: string): single lookup
  • getKanjiByCategory(category: string): filter
  • getKanjiCategories(): list categories with counts
  • getAllKanjiChars(): for generateStaticParams
• File: src/lib/dictionary/yoji.ts
  • getAllYoji(): returns all entries
  • getYojiByReading(reading: string) or getYojiByYoji(yoji: string): single lookup
  • getYojiByCategory(category: string): filter
  • getYojiByDifficulty(level: number): filter
  • getYojiCategories(): list categories with counts
  • getAllYojiIds(): for generateStaticParams (use the yoji string as slug, URL-encoded)
• File: src/lib/dictionary/index.ts -- re-exports

Step 1.3: Add SEO helpers for dictionary pages

• Add to src/lib/seo.ts:
  • generateKanjiPageMetadata(entry: KanjiEntry): Metadata
  • generateKanjiJsonLd(entry: KanjiEntry): object -- use DefinedTerm schema.org type
  • generateYojiPageMetadata(entry: YojiEntry): Metadata
  • generateYojiJsonLd(entry: YojiEntry): object -- use DefinedTerm schema.org type

Phase 2: Dictionary Page Components (Builder B, ~45 min, parallel with Phase 1)

Step 2.1: Create shared dictionary components

• src/components/dictionary/DictionaryCard.tsx + CSS module -- card for index/list pages (kanji character or yoji, reading, brief meaning)
• src/components/dictionary/DictionaryGrid.tsx + CSS module -- grid layout for cards
• src/components/dictionary/CategoryNav.tsx + CSS module -- category navigation sidebar/tabs
• src/components/dictionary/SearchBox.tsx + CSS module -- client component for filtering entries by text input (reading/meaning search, client-side filter only)

Step 2.2: Kanji detail components

• src/components/dictionary/kanji/KanjiDetail.tsx + CSS module
  • Large character display
  • Readings section (on'yomi, kun'yomi)
  • Meanings (English)
  • Radical info + stroke count + grade
  • Example words
  • Link to related kanji (same radical group or same category)
  • Link to games that use kanji (kanji-kanaru)

Step 2.3: Yoji detail components

• src/components/dictionary/yoji/YojiDetail.tsx + CSS module
  • Large yoji display (4 characters)
  • Reading (hiragana)
  • Meaning explanation
  • Difficulty badge (easy/medium/hard)
  • Category tag
  • Related yoji (same category)
  • Link to games that use yoji (yoji-kimeru)

Phase 3: Dictionary Routes (Builder A, ~60 min, after Phase 1)

Step 3.1: Dictionary top page

• src/app/dictionary/page.tsx + CSS module
• URL: /dictionary
• Content: Introduction text, links to kanji and yoji sections, total counts, AI disclaimer
• Metadata: "漢字・四字熟語辞典 | yolos.net"

Step 3.2: Kanji index page

• src/app/dictionary/kanji/page.tsx + CSS module
• URL: /dictionary/kanji
• Content: All 50 kanji in a grid, category filter tabs, search box
• Breadcrumb: ホーム > 辞典 > 漢字辞典

Step 3.3: Kanji category pages

• src/app/dictionary/kanji/category/[category]/page.tsx + CSS module
• URL: /dictionary/kanji/category/[category] (e.g., /dictionary/kanji/category/nature)
• generateStaticParams from category list
• Content: Filtered kanji grid for that category

Step 3.4: Kanji detail pages

• src/app/dictionary/kanji/[char]/page.tsx + CSS module
• URL: /dictionary/kanji/[char] (e.g., /dictionary/kanji/山)
• generateStaticParams from getAllKanjiChars()
• Uses KanjiDetail component
• JSON-LD: DefinedTerm
• Breadcrumb: ホーム > 辞典 > 漢字辞典 > 山

Step 3.5: Yoji index page

• src/app/dictionary/yoji/page.tsx + CSS module
• URL: /dictionary/yoji
• Content: All 101 yoji in a list/grid, category filter, difficulty filter, search

Step 3.6: Yoji category pages

• src/app/dictionary/yoji/category/[category]/page.tsx + CSS module
• URL: /dictionary/yoji/category/[category]
• generateStaticParams from category list

Step 3.7: Yoji detail pages

• src/app/dictionary/yoji/[yoji]/page.tsx + CSS module
• URL: /dictionary/yoji/[yoji] (e.g., /dictionary/yoji/一期一会)
• generateStaticParams from all yoji strings
• Uses YojiDetail component
• JSON-LD: DefinedTerm

Phase 4: Sitemap and Navigation Updates (Builder A, ~20 min, after Phase 3)

Step 4.1: Update sitemap.ts

• Import dictionary data functions
• Add dictionary top page (priority 0.9)
• Add kanji index + category pages (priority 0.8)
• Add all 50 kanji detail pages (priority 0.7)
• Add yoji index + category pages (priority 0.8)
• Add all 101 yoji detail pages (priority 0.7)

Step 4.2: Update navigation

• Add "辞典" link to Header/MobileNav components
• Add dictionary section to homepage if there is a content section

Step 4.3: Cross-linking

• On kanji game page (kanji-kanaru): add link to kanji dictionary
• On yoji game page (yoji-kimeru): add link to yoji dictionary
• On dictionary pages: add links back to games

Phase 5: Blog Articles (Builder C, parallel with Phases 2-4, ~90 min)

Blog article selection criteria: Tools with high search volume potential, practical everyday use, and natural Japanese-language queries.

Selected articles (5 total):

1. json-formatter-guide -- "JSON整形・フォーマッターの使い方ガイド"

   • Target keywords: JSON整形, JSONフォーマッター, JSON見やすく
   • Related tools: json-formatter, csv-converter, yaml-formatter
   • Outline: JSONとは, 整形が必要な場面, ツールの使い方, よくあるエラーと対処

2. regex-tester-guide -- "正規表現テスターの使い方: 初心者から実践まで"

   • Target keywords: 正規表現 テスト, 正規表現 チェック, regex テスター
   • Related tools: regex-tester, text-replace
   • Outline: 正規表現の基本, よく使うパターン集, ツールでの検証方法, 実務での活用例

3. hash-generator-guide -- "ハッシュ値とは? MD5/SHA-256の違いと生成方法"

   • Target keywords: ハッシュ値 生成, MD5 SHA256 違い, ハッシュ化
   • Related tools: hash-generator, password-generator
   • Outline: ハッシュとは, 主要アルゴリズムの比較, セキュリティ上の注意, ツールでの生成方法

4. cron-parser-guide -- "cron式の書き方ガイド: スケジュール設定を簡単に"

   • Target keywords: cron 書き方, crontab 設定, cron式 解説
   • Related tools: cron-parser
   • Outline: cronとは, 各フィールドの意味, よく使うパターン, ツールでの検証

5. unit-converter-guide -- "単位変換ガイド: よく使う換算と便利な覚え方"

   • Target keywords: 単位変換, 長さ変換, 重さ変換
   • Related tools: unit-converter, bmi-calculator
   • Outline: SI単位系の基本, よく使う換算表, 日常で使う単位変換, ツールの使い方

Blog format: Follow existing pattern in src/content/blog/. Each article:

• Frontmatter: title, slug, description, published_at, updated_at, tags, category ("technical"), related_memo_ids, related_tool_slugs, draft: false
• ~1500-2500 words Japanese
• AI disclaimer in introduction paragraph
• Internal links to tool pages
• Sections with h2/h3 for TOC generation

Phase 6: Testing (Builder A or B, ~30 min, after Phases 3-5)

Step 6.1: Data layer unit tests

• src/lib/dictionary/__tests__/kanji.test.ts
  • getAllKanji returns 50 entries
  • getKanjiByChar("山") returns correct entry
  • getKanjiByCategory("nature") returns filtered results
  • getAllKanjiChars returns 50 strings
• src/lib/dictionary/__tests__/yoji.test.ts
  • getAllYoji returns 101 entries
  • getYojiByYoji("一期一会") returns correct entry
  • getYojiByCategory("life") returns 10 entries
  • getYojiByDifficulty(1) returns 55 entries

Step 6.2: Component tests

• src/components/dictionary/__tests__/DictionaryCard.test.tsx -- renders kanji/yoji card
• src/components/dictionary/__tests__/KanjiDetail.test.tsx -- renders full detail
• src/components/dictionary/__tests__/YojiDetail.test.tsx -- renders full detail

Step 6.3: Build verification

• Run npm run build to confirm all static pages generate successfully
• Verify generateStaticParams produces expected param counts
• Check that sitemap includes new dictionary URLs

Step 6.4: Lint and format

• npm run lint passes
• npm run format:check passes (or run format)

Acceptance Criteria

1. /dictionary page renders with links to kanji and yoji sections
2. /dictionary/kanji lists all 50 kanji with category filter and search
3. /dictionary/kanji/[char] renders for all 50 kanji with readings, meanings, examples, radical info
4. /dictionary/kanji/category/[category] renders for all 17 categories
5. /dictionary/yoji lists all 101 yoji with category/difficulty filter and search
6. /dictionary/yoji/[yoji] renders for all 101 yoji with reading, meaning, difficulty, category
7. /dictionary/yoji/category/[category] renders for all 10 categories
8. All dictionary pages have proper SEO metadata (title, description, JSON-LD DefinedTerm, canonical URL)
9. Sitemap includes all ~181 new dictionary URLs
10. Navigation header includes "辞典" link
11. Cross-links: dictionary <-> games, blog <-> tools
12. 5 new blog articles published with proper frontmatter and tool cross-links
13. All tests pass (npm run test)
14. Build succeeds (npm run build)
15. Lint passes (npm run lint)
16. AI disclaimer present on dictionary pages per constitution rule 3

Builder Parallelization

Three builders can work concurrently:

Builder	Phase	Work Area	Duration
Builder A	Phase 1 -> Phase 3 -> Phase 4	Data layer, routes, sitemap, nav	~110 min
Builder B	Phase 2 -> Phase 6	Components, tests	~75 min
Builder C	Phase 5	Blog articles (5)	~90 min

• Builder B depends on Phase 1 types (can start CSS/layout while waiting, but needs types for props)
• Builder A Phase 3 depends on both Phase 1 and Phase 2 components
• Suggested approach: Start A and C in parallel. B starts after A completes Step 1.1 (types). Phase 3 starts once Phase 2 is ready.
• Alternatively, a single builder can execute sequentially: Phase 1 -> 2 -> 3 -> 4 -> 5 -> 6.

Required Artifacts

New files (~40+ files)

• src/lib/dictionary/types.ts
• src/lib/dictionary/kanji.ts
• src/lib/dictionary/yoji.ts
• src/lib/dictionary/index.ts
• src/components/dictionary/DictionaryCard.tsx + .module.css
• src/components/dictionary/DictionaryGrid.tsx + .module.css
• src/components/dictionary/CategoryNav.tsx + .module.css
• src/components/dictionary/SearchBox.tsx + .module.css
• src/components/dictionary/kanji/KanjiDetail.tsx + .module.css
• src/components/dictionary/yoji/YojiDetail.tsx + .module.css
• src/app/dictionary/page.tsx + .module.css
• src/app/dictionary/kanji/page.tsx + .module.css
• src/app/dictionary/kanji/[char]/page.tsx + .module.css
• src/app/dictionary/kanji/category/[category]/page.tsx + .module.css
• src/app/dictionary/yoji/page.tsx + .module.css
• src/app/dictionary/yoji/[yoji]/page.tsx + .module.css
• src/app/dictionary/yoji/category/[category]/page.tsx + .module.css
• src/lib/dictionary/__tests__/kanji.test.ts
• src/lib/dictionary/__tests__/yoji.test.ts
• src/components/dictionary/__tests__/DictionaryCard.test.tsx
• src/components/dictionary/__tests__/KanjiDetail.test.tsx
• src/components/dictionary/__tests__/YojiDetail.test.tsx
• 5 blog markdown files in src/content/blog/

Modified files

• src/lib/seo.ts -- add dictionary SEO helpers
• src/app/sitemap.ts -- add dictionary URLs
• src/components/common/Header.tsx -- add 辞典 nav link
• src/components/common/MobileNav.tsx -- add 辞典 nav link

Rollback Approach

All changes are additive (new files and minor modifications to existing files). Rollback strategy:

1. Git revert: All work should be committed incrementally. If issues arise, revert the relevant commits.
2. Feature isolation: Dictionary routes are under /dictionary/ with no impact on existing /tools/, /games/, /blog/ routes.
3. Blog articles are independent markdown files that can be individually removed or set to draft: true.
4. Navigation link removal: Single-line changes in Header/MobileNav.