Prompt file imported from rhixecompany/sandbox (.github/prompts/web/next-intl-add-language/next-intl-add-language.prompt.md). Copyright stays with the author.

Table of Contents

Goal

Walks through adding a new locale to a Next.js app using next-intl, including message catalog setup, routing, and type-safe translations.

Context

Phases

Table of Contents

• Goal

• Context

• Inputs

• Outputs

• Rules

• Phases

  • Phase 1: Intake
  • Phase 2: Execute
  • Phase 3: Verify
  • Phase 4: Hand off

• Template References

• Personas

• Personality

• Best Practices

• Verification Checklist

• Dependencies

• Subgoals

• Skills Required

• MCP Servers & Tools

• Tasks

• Hooks

• Scripts

• Goal

• Context

• Inputs

• Outputs

• Rules

• Phases

• Phase 1: Intake

• Phase 2: Execute

• Phase 3: Verify

• Phase 4: Hand off

• Template References

• Personas

• Personality

• Best Practices

• Verification Checklist

• Dependencies

• Subgoals

• Skills Required

• MCP Servers & Tools

• Tasks

• Hooks

• Scripts

Add new language to a Next.js + next-intl application.

Use when you need to work on the current workspace or task.

Inputs

• The current workspace, repo, or document state.
• The specific request, diff, spec, or files provided by the user.
• Any prompt variables, paths, or constraints named in the original instructions.

Outputs

• A complete result that matches the prompt's purpose.
• A concise verification note when the task benefits from one.

Rules

Core rules: templates/rules-core.md

• Follow the prompt literally and prefer evidence from the current workspace.
• Keep the response structured, deterministic, and easy to act on.
• Avoid changing unrelated files or adding unnecessary scope.
• If something is unclear, state the assumption instead of guessing.

Phase 1: Intake

• Read the request and identify the exact scope.
• Locate the relevant files, diffs, or references.

Phase 2: Execute

• Perform the requested work with the smallest safe change set.
• Keep the steps explicit and reproducible.

Phase 3: Verify

• Check the result against the goal, rules, and inputs.
• Confirm the output is usable and complete.

Phase 4: Hand off

• Return the final artifact or findings .
• Stop once the requested result is delivered.

Template References

Templates in templates/:- legacy_prompt_details.md- phases.md

Personas

See templates/personas.md for shared persona templates.

Personality

See templates/personality.md for shared personality guidelines.

• Tone: Direct, practical, actionable
• Style: Structured with clear steps and verification
• Avoid: Ambiguity, assumptions, scope creep
• Encourage: Evidence-based decisions, minimal changes

Best Practices

See templates/best-practices.md for cross-cutting best practices.

1. DRY — Reference shared templates instead of duplicating content.
2. Structured output — Use clear sections with consistent heading levels.
3. Verification gates — Always verify before claiming completion.
4. Minimal changes — Fix root cause, not symptoms.

Verification Checklist

Dependencies

See templates/deps-core.md for shared dependency patterns.

Subgoals

1. Prepare — Understand requirements and prerequisites.
2. Execute — Follow structured workflow with incremental progress.
3. Verify — Confirm output meets requirements and standards.
4. Document — Record results, decisions, and lessons learned.

Skills Required

See templates/skills-table-core.md for shared skills table.

MCP Servers & Tools

The following MCP servers and tools are available for this task. Use them in preference to native equivalents per MCP-first tooling policy.

| ast-grep | AST-based code search and replace | | filesystem | File read/write operations | | sequential-thinking | Structured reasoning for complex problems | | fetch | Web page content extraction | | playwright | Browser automation for interactive pages | | github | GitHub API operations |

Tasks

• Understand requirements and scope
• Plan approach and identify resources
• Execute work incrementally
• Verify against acceptance criteria
• Document results and decisions

Hooks

Shared workspace hooks run around this prompt's execution — see .github/hooks/README.md: session-logger, session-auto-commit, governance-audit, pre-exec-validate.sh, post-exec-state-log.py.

Scripts

Workflow

Prompt-library tooling (see .enhance/):

• .enhance/analyze_prompts.py — prompt-library analyzer (Phase 5/7 gate)
• .enhance/verify_phase3.py, .enhance/fix_class_e.py, .enhance/fix_frontmatter_plan.py — Class C–E repair/verify tooling
• .github/hooks/* — hook implementations referenced in the Hooks section

# Prompt template
Execute the workflow defined in this file.