{
  "language": "en",
  "translations": {
    "template.title.rules": "Branch Memory Bank Usage Guidelines",
    "template.description.rules": "Purpose and recommended content for branch memory bank core files",
    "template.section.global_memory_bank": "Global Memory Bank",
    "template.content.global_memory_bank": "The Global Memory Bank is a central repository for storing knowledge that is shared across the entire project. It is accessible from all branches and contains important information such as project basics, architecture, design decisions, and more.",
    "template.section.purpose_of_global_memory_bank": "Purpose of Global Memory Bank",
    "template.content.purpose_of_global_memory_bank": "The main purpose of the Global Memory Bank is to centralize project knowledge and share it among team members. This facilitates onboarding of new members and maintains consistency across the project.",
    "template.section.global_memory_bank_structure": "Global Memory Bank Structure",
    "template.content.global_memory_bank_structure": "The Global Memory Bank is organized according to the following directory structure:\n\n- core/ - Basic information\n- 01-project/ - Detailed project information\n- 02-architecture/ - Detailed architecture information\n- 03-implementation/ - Detailed implementation information\n- 04-guides/ - Detailed guides and manuals\n- 05-testing/ - Testing information\n- 06-releases/ - Release information\n- 07-infrastructure/ - Infrastructure information\n- 08-i18n/ - Internationalization information\n- 09-refactoring/ - Refactoring information\n- meta/ - Metadata and management information\n- tags/ - Tag system information",
    "template.section.tag_system": "Tag System",
    "template.content.tag_system": "Tags are an important means of classifying and searching for documents. Follow these rules for effective use of tags:\n\n- Tags should only use lowercase letters, numbers, and hyphens (no uppercase, spaces, underscores, or dots)\n- Example: `architecture`, `design-patterns`, `v1-beta` (OK)\n- Example: `Design`, `user_guide`, `v2.0` (NG)",
    "template.section.json_architecture": "JSON Structure",
    "template.content.json_architecture": "Memory bank documents are stored in JSON format with the following structure:\n\n```json\n{\n  \"schema\": \"memory_document_v2\",\n  \"metadata\": {\n    \"id\": \"unique-identifier\",\n    \"title\": \"Document Title\",\n    \"documentType\": \"document-type\",\n    \"path\": \"relative-path\",\n    \"tags\": [\"related-tags\"],\n    \"lastModified\": \"last-modified-date\",\n    \"createdAt\": \"creation-date\",\n    \"version\": 1\n  },\n  \"content\": {\n    // Document content\n  }\n}\n```",
    "template.section.branch_memory_bank": "Branch Memory Bank",
    "template.content.branch_memory_bank": "The Branch Memory Bank is a memory bank for storing information related to a specific branch (feature implementation or bug fix). Each branch has its own memory bank that holds context information specific to that branch.",
    "template.section.memory_bank_structure": "Memory Bank Structure",
    "template.content.memory_bank_structure": "The memory bank is a collection of documents. Each document is stored as a JSON file with metadata and content. The metadata includes information such as the document's ID, title, type, path, tags, update date, etc.",
    "template.section.required_files": "Required Files",
    "template.content.required_files": "Each branch memory bank requires the following four core files:\n\n1. **branchContext.json** - Branch purpose, user stories, requirements\n2. **activeContext.json** - Current work, recent changes, active decisions\n3. **systemPatterns.json** - Technical decisions, related file structure\n4. **progress.json** - Current progress, unimplemented features, known issues",
    "template.section.additional_context": "Additional Context",
    "template.content.additional_context": "Additional documents can be stored in the memory bank as needed. These documents can include detailed information about specific features or implementations, design documents, test plans, etc.",
    "template.section.core_workflow": "Core Workflow",
    "template.content.core_workflow": "The basic workflow for using the memory bank is as follows:\n\n1. Initialize the branch memory bank when creating a branch\n2. Record relevant information in the branch memory bank as you work\n3. Record important decisions and design patterns\n4. Update progress\n5. Consider migrating important information to the global memory bank when merging the branch",
    "template.section.task_progress_workflow": "Task Progress Workflow",
    "template.content.task_progress_workflow": "The workflow for recording task progress is as follows:\n\n1. Record the current work in activeContext.json when starting a task\n2. Record implemented features in progress.json\n3. Record unimplemented features or remaining work in progress.json\n4. Record known issues or challenges in progress.json\n5. Update activeContext.json when the task is complete",
    "template.section.document_updates": "Document Updates",
    "template.content.document_updates": "When updating documents, follow these rules:\n\n1. Update the `lastModified` field in the metadata to the current date and time\n2. Increment the `version` field in the metadata\n3. Record the changes appropriately\n4. Update tags as needed",
    "template.section.migration_strategy": "Migration Strategy",
    "template.content.migration_strategy": "When merging branches, consider migrating important information to the global memory bank. In particular, reusable patterns and important design decisions should be saved in the global memory bank so that other team members can reference them.",
    "template.section.file_editing_rules": "File Editing Rules",
    "template.content.file_editing_rules": "When editing memory bank files, follow these rules:\n\n1. Use CLI commands instead of editing files directly\n2. Ensure that the JSON syntax is correct\n3. Do not remove required fields\n4. Do not change the schema version",
    "template.section.finally": "Finally",
    "template.content.finally": "The memory bank is a powerful tool for managing project knowledge. By using it appropriately, you can improve team productivity and collaboration.",
    "template.section.footer": "(Footer)",
    "template.content.footer": "---\n\n_This document explains the basic rules and structure of the memory bank_",

    "template.title.active_context": "Active Context Template",
    "template.description.active_context": "Template for documenting current work status and recent changes",
    "template.section.current_work": "Current Work",
    "template.content.current_work": "<!-- Describe the specific work currently in progress -->\n{{CURRENT_WORK}}",
    "template.section.recent_changes": "Recent Changes",
    "template.content.recent_changes": "<!-- Describe recent implementations or feature additions -->\n{{RECENT_CHANGES}}",
    "template.section.active_decisions": "Active Decisions",
    "template.content.active_decisions": "<!-- Describe important technical decisions recently made -->\n{{ACTIVE_DECISIONS}}",
    "template.section.considerations": "Considerations",
    "template.content.considerations": "<!-- Describe issues or questions currently under consideration -->\n{{CONSIDERATIONS}}",
    "template.section.next_steps": "Next Steps",
    "template.content.next_steps": "<!-- Describe the next tasks to tackle or priorities -->\n{{NEXT_STEPS}}",
    "template.placeholder.current_work": "Placeholder for current work",
    "template.placeholder.recent_changes": "Placeholder for recent changes",
    "template.placeholder.active_decisions": "Placeholder for active decisions",
    "template.placeholder.considerations": "Placeholder for considerations",
    "template.placeholder.next_steps": "Placeholder for next steps",

    "template.title.branch_context": "Branch Context Template",
    "template.description.branch_context": "Template for documenting the purpose and background of a branch",
    "template.section.purpose": "Purpose of this Branch",
    "template.content.purpose": "<!-- Describe the purpose of this branch concisely -->",
    "template.section.background": "Background",
    "template.content.background": "<!-- Explain the background or reasons why this branch was created -->",
    "template.section.user_stories": "User Stories",
    "template.content.user_stories": "### Problem to Solve\n\n<!-- Describe the problem to solve -->\n{{PROBLEM}}\n\n### Required Features\n\n<!-- Describe required features -->\n{{FEATURES}}\n\n### Expected Behavior\n\n<!-- Describe expected behavior -->\n{{BEHAVIOR}}",
    "template.section.related_issues": "Related Issues",
    "template.content.related_issues": "<!-- List related GitHub Issues, JIRA tickets, etc. -->\n{{ISSUES}}",
    "template.section.technical_considerations": "Technical Considerations",
    "template.content.technical_considerations": "<!-- Describe technical considerations for implementation -->\n{{TECH_CONSIDERATIONS}}",
    "template.placeholder.problem": "Placeholder for problem to solve",
    "template.placeholder.features": "Placeholder for required features",
    "template.placeholder.behavior": "Placeholder for expected behavior",
    "template.placeholder.issues": "Placeholder for related issues",
    "template.placeholder.tech_considerations": "Placeholder for technical considerations",

    "template.title.progress": "Progress Template",
    "template.description.progress": "Template for documenting feature implementation status and remaining work",
    "template.section.working_features": "Currently Working Features",
    "template.content.working_features": "<!-- Describe implemented features that are working correctly -->\n{{WORKING_FEATURES}}",
    "template.section.unimplemented_features": "Unimplemented Features and Remaining Work",
    "template.content.unimplemented_features": "<!-- Describe features not yet implemented or remaining tasks -->\n{{UNIMPLEMENTED_FEATURES}}",
    "template.section.current_status": "Current Status",
    "template.content.current_status": "<!-- Describe the current state of development and overall progress -->\n{{CURRENT_STATUS}}",
    "template.section.known_issues": "Known Issues",
    "template.content.known_issues": "<!-- Describe known bugs or problems -->\n{{KNOWN_ISSUES}}",
    "template.section.completion_criteria": "Completion Criteria",
    "template.content.completion_criteria": "<!-- Describe the criteria for considering this branch complete -->\n{{COMPLETION_CRITERIA}}",
    "template.placeholder.working_features": "Placeholder for working features",
    "template.placeholder.unimplemented_features": "Placeholder for unimplemented features",
    "template.placeholder.current_status": "Placeholder for current status",
    "template.placeholder.known_issues": "Placeholder for known issues",
    "template.placeholder.completion_criteria": "Placeholder for completion criteria",

    "template.title.system_patterns": "System Patterns Template",
    "template.description.system_patterns": "Template for documenting technical decisions and architectural patterns",
    "template.section.technical_decisions": "Technical Decisions",
    "template.content.technical_decisions": "<!-- Describe major technical decisions (ADR format preferred) -->\n\n### Testing Strategy\n\n#### Context\n\n<!--Background for the decision-->\n\n#### Decision\n\n<!--What was decided-->\n\n#### Consequences\n\n<!--Impact of the decision-->\n\n### Folder Structure\n\n#### Context\n\n<!--Background for the decision-->\n\n#### Decision\n\n<!--What was decided-->\n\n#### Consequences\n\n<!--Impact of the decision-->",
    "template.section.file_structure": "Related Files and Directory Structure",
    "template.content.file_structure": "<!-- Describe the main file structure or directory layout of the code -->\n```\n# Example directory structure\nsrc/\n  ├── domain/\n  ├── application/\n  ├── infrastructure/\n  └── interface/\n```",
    "template.section.design_patterns": "Design Patterns",
    "template.content.design_patterns": "<!-- Describe design patterns being used and how they are applied -->\n{{DESIGN_PATTERNS}}",
    "template.section.architecture": "Architecture",
    "template.content.architecture": "<!-- Describe the architecture overview or notable aspects -->\n{{ARCHITECTURE}}",
    "template.placeholder.design_patterns": "Placeholder for design patterns",
    "template.placeholder.architecture": "Placeholder for architecture",

    "template.section.branchMemoryGuidelines": "Introduction",
    "template.content.branchMemoryGuidelines": "このガイドラインは、ブランチメモリバンクの効果的な運用方法と、各コアファイルの目的および推奨される記録内容を定義します。ブランチメモリバンクは、特定の機能開発や修正作業に関するコンテキスト情報を集約し、チーム内の情報共有と作業の引き継ぎを円滑にすることを目的とします。",
    "template.section.branchContextJson": "1. branchContext.json",
    "template.content.branchContextJson": "**目的:** ブランチの基本的な情報と目的を定義します。\n**推奨される記録内容:**\n- `purpose`: このブランチが解決しようとしている課題や目的を具体的に記述します。\n- `userStories`: 関連するユーザーストーリーやタスクをリストアップし、進捗（completed）や優先度（priority）を管理します。\n- `additionalNotes`: その他、ブランチ全体に関する補足情報があれば記述します。\n**更新タイミング:** ブランチ作成時、またはブランチの目的やスコープに変更があった場合。",
    "template.section.activeContextJson": "2. activeContext.json",
    "template.content.activeContextJson": "**目的:** ブランチにおける現在の作業状況、直近の変更履歴、アクティブな決定事項、検討中の課題、次のステップを記録します。\n**推奨される記録内容:**\n- `currentWork`: 現在取り組んでいる具体的なタスクや作業内容を記述します。\n- `recentChanges`: 直近で行った重要な変更（コード修正、ドキュメント更新、設定変更など）を日付と共に記録します。\n- `activeDecisions`: 作業中に決定した事項（技術選定、仕様変更など）とその理由（任意）を記録します。\n- `considerations`: 現在検討中の課題や選択肢、そのステータス（open, resolved, deferred）を記録します。\n- `nextSteps`: 次に取り組むべきタスクやアクションアイテムを優先度と共にリストアップします。\n**更新タイミング:** 日々の作業終了時、重要な変更や決定があった時、作業を引き継ぐ前など、頻繁に更新することが推奨されます。",
    "template.section.progressJson": "3. progress.json",
    "template.content.progressJson": "**目的:** ブランチにおける機能実装の進捗状況、未実装のタスク、既知の問題点を管理します。\n**推奨される記録内容:**\n- `workingFeatures`: 実装が完了し、動作している機能やコンポーネントをリストアップし、実装日時を記録します。\n- `pendingImplementation`: これから実装する予定の機能やタスクを優先度と共にリストアップします。完了予定日（estimatedCompletion）も任意で記録できます。\n- `status`: ブランチ全体の開発ステータス（planning, in-development, testing, completedなど）を記述します。\n- `completionPercentage`: ブランチ全体の完了率（目安）を記録します。\n- `knownIssues`: 現在認識されているバグや問題点を重要度（severity）と共にリストアップします。回避策（workaround）も任意で記録できます。\n**更新タイミング:** 機能の実装が完了した時、新しい問題を発見した時、ブランチのマージ前など、進捗に変化があった場合に更新します。",
    "template.section.systemPatternsJson": "4. systemPatterns.json",
    "template.content.systemPatternsJson": "**目的:** ブランチ内で行われた重要な技術的決定や、採用された実装パターンを記録します。\n**推奨される記録内容:**\n- `technicalDecisions`: アーキテクチャに関する決定、ライブラリ選定、API設計など、将来の参照価値がある技術的決定事項を記録します。決定の背景（context）、具体的な決定内容（decision）、その影響（consequences）、ステータス（status）、代替案（alternatives）なども含めるとより有用です。\n- `implementationPatterns`: ブランチ内で繰り返し使用される特定の実装パターンやコードスニペットがあれば記録します（任意）。\n**更新タイミング:** 重要な技術的決定が行われた際や、特筆すべき実装パターンが確立された場合に記録します。",
    "template.section.bestPractices": "Best Practices for Operation",
    "template.content.bestPractices": "- **こまめな更新:** 各コアファイルは、情報が古くならないように、関連する変更があった際にこまめに更新しましょう。\n- **簡潔かつ具体的に:** 誰が読んでも理解できるように、内容は簡潔かつ具体的に記述しましょう。\n- **チームでの共有:** ブランチメモリバンクの情報はチームメンバーと共有し、認識合わせに活用しましょう。\n- **タグの活用:** 各ドキュメントには適切なタグを付与し、将来的な情報検索に備えましょう（例: `core`, `decision`, `refactoring-plan` など）。"
  },
  "metadata": {
    "version": "1.0.0",
    "updatedAt": "2025-04-01T01:38:00.000Z"
  }
}