@tomako/tools-runtime 0.1.0

package/src/i18n/messages/en/tools/product-hunt-launch-planner.ts

@@ -0,0 +1,272 @@
+const productHuntLaunchPlanner = {
+  meta: {
+    title: "Product Hunt Launch Planner",
+    description: "Enter your product, audience, and launch readiness to create a Product Hunt checklist, launch page asset pack, day-of operations table, and platform-risk review notes.",
+    intro: "Turn scattered product notes into an executable Product Hunt launch workflow: what to fix, what to write, who handles launch day, and which asks to avoid.",
+    category: "Launch tools",
+    keywords: [
+      "Product Hunt launch planner",
+      "Product Hunt launch checklist",
+      "Product Hunt launch template",
+      "PH launch assets",
+      "startup launch workflow",
+    ],
+    inputSignal: "Product brief + launch readiness",
+    outputSignal: "Checklist + assets + day-of plan",
+    boundarySignal: "Review prototype; no auto-posting or vote tasks",
+  },
+  examples: [
+    {
+      label: "AI launch material tool",
+      input: "Product: a tool that helps indie makers generate launch design assets; audience: makers preparing for Product Hunt or app-store launches; stage: beta.",
+      expectedOutput: "A checklist, launch page asset pack, day-of operations plan, reply prep, outreach boundaries, recap actions, and copyable Markdown.",
+    },
+  ],
+  guide: {
+    heroVisualAlt:
+      "A Product Hunt launch kit with checklist cards, copy assets, and a warm coral launch accent.",
+    workspaceHeading: "Build a Product Hunt launch checklist and asset pack",
+    workspaceHint:
+      "Enter the minimum product context and current readiness. This review version submits an online task and only renders the structured launch checklist, copy drafts, launch-day plan, and review notes after writeback.",
+    workspaceBadge: "Review prototype",
+    outputs: "What you get from the planner",
+    outputItems: [
+      {
+        title: "Readiness score",
+        body: "See whether your account, community, assets, URL, and timing are ready enough to schedule.",
+      },
+      {
+        title: "Execution checklist",
+        body: "Get phase-by-phase tasks for account prep, launch assets, launch day, and recap.",
+      },
+      {
+        title: "Launch page assets",
+        body: "Draft taglines, a short description, maker comment, topic ideas, gallery brief, and social copy.",
+      },
+      {
+        title: "Rules and review notes",
+        body: "Keep vote asks, unsupported claims, and missing product proof visible before you publish.",
+      },
+    ],
+    supportHeading: "Use it when you need a launch plan, not another generic template",
+    supportVisualAlt:
+      "Messy launch notes turning into a clean Product Hunt asset pack.",
+    supportItems: [
+      "Works best for indie makers, early SaaS teams, developer tools, apps, open-source brands, and launchable product updates.",
+      "Accepts a public URL when you have one, but can also start from a manual product brief for beta or waitlist products.",
+      "Focuses on Product Hunt page assets, comment readiness, social outreach boundaries, and day-of operations.",
+      "Treats Product Hunt as a manual launch workflow. Final posting still happens on Product Hunt.",
+    ],
+    boundaryHeading: "The prototype keeps Product Hunt boundaries visible",
+    boundaryVisualAlt:
+      "A review desk with launch rule markers and a human review checklist.",
+    boundaryItems: [
+      "It submits an online Agent task for planning, but it does not post to Product Hunt, create maker accounts, submit products, track ranking, or connect to Product Hunt APIs.",
+      "It does not create upvote tasks, paid voting plans, fake comments, or coordinated vote instructions.",
+      "It writes outreach as trial and feedback invitations, not as upvote requests.",
+      "It marks the output as a draft that still needs human review against the live product and Product Hunt rules.",
+    ],
+    failureHeading: "If the plan looks weak, check these inputs",
+    failureItems: [
+      "The product description is too generic, so the tagline cannot express a sharp user outcome.",
+      "The target audience is too broad, which makes the first comment and outreach copy sound vague.",
+      "There is no public URL, demo, waitlist, or proof point to anchor the launch.",
+      "The Product Hunt account or launch assets are not ready, so the schedule should move back.",
+    ],
+    resultUseHeading: "Use the result as a launch-day operating document",
+    resultUseVisualAlt:
+      "A Product Hunt launch-day operations timeline with reply cards and recap notes.",
+    resultUseItems: [
+      "Copy the Markdown into your launch doc and assign owners before the launch date.",
+      "Paste the tagline, short description, and maker comment into Product Hunt only after human review.",
+      "Use the supporter note for warm users, but keep the ask focused on trial, comment, and feedback.",
+      "After launch, turn repeated comments into FAQ updates, social follow-ups, and product fixes.",
+    ],
+    whyTomakoHeading: "Why use Tomako instead of a static PH template",
+    whyTomakoItems: [
+      {
+        title: "It starts from readiness",
+        body: "A generic template assumes you are ready. This one exposes whether account, audience, URL, and assets are still blocking you.",
+      },
+      {
+        title: "It separates assets from operations",
+        body: "Product Hunt success is not only a tagline. You also need launch-day coverage, replies, and post-launch learning.",
+      },
+      {
+        title: "It keeps platform risk in the workflow",
+        body: "Vote manipulation and overpromising are treated as risks to review, not growth hacks to automate.",
+      },
+      {
+        title: "It exports a usable document",
+        body: "The result is structured enough to copy into a launch doc, assign owners, and keep editing.",
+      },
+    ],
+    standardHeading: "A good Product Hunt launch planner should be concrete and careful",
+    standardVisualAlt:
+      "A polished launch planning standard card with Product Hunt assets and review checkpoints.",
+    standardItems: [
+      "Quality: output should include actual copy, not only advice about writing copy.",
+      "Ease of use: the first version should require only product basics, not a full launch PRD.",
+      "Trust: the plan should clearly say what it cannot do and what a human must review.",
+      "Platform fit: outreach should invite trial and feedback, not encourage coordinated upvotes.",
+      "Actionability: every checklist item should have an owner, a status, and a next action.",
+    ],
+    faq: "FAQ",
+    faqItems: [
+      {
+        question: "Does this publish my product to Product Hunt?",
+        answer:
+          "No. It creates a draft plan and copy assets. Final submission, scheduling, and account actions must happen manually on Product Hunt.",
+      },
+      {
+        question: "Can I use it without a product URL?",
+        answer:
+          "Yes, but the output will be less specific. A public website, demo, waitlist, or docs page gives the planner stronger proof and clearer copy.",
+      },
+      {
+        question: "Will it help me get more upvotes?",
+        answer:
+          "It helps you prepare a clearer launch and better feedback asks. It does not create vote tasks, incentives, or coordinated upvote campaigns.",
+      },
+      {
+        question: "Is this connected to a real Agent yet?",
+        answer:
+          "This review version submits an online Agent task and waits for a structured Skills-OL writeback. It is still not Product Hunt automation.",
+      },
+    ],
+    ctaHint:
+      "Not ready for Product Hunt yet? Check GTM readiness first, or decide whether Product Hunt should be your first launch channel.",
+    ctaPrimary: "Check GTM readiness",
+    ctaSecondary: "Compare launch channels",
+  },
+  widget: {
+    formTitle: "Launch brief",
+    formHint:
+      "Use a real product description and audience. Results come only from online structured writeback; the widget does not use a frontend template fallback.",
+    productNameLabel: "Product name",
+    productNamePlaceholder: "Tomako",
+    productUrlLabel: "Product URL",
+    productUrlPlaceholder: "https://example.com",
+    oneLinerLabel: "What does the product help users do?",
+    oneLinerPlaceholder:
+      "Helps indie makers turn product context into launch-ready marketing assets and day-of workflows.",
+    audienceLabel: "Who is the launch for?",
+    audiencePlaceholder:
+      "Indie makers and early SaaS teams preparing their first public launch.",
+    stageLabel: "Product stage",
+    goalLabel: "Launch goal",
+    advancedTitle: "Readiness details",
+    launchDateLabel: "Target launch date",
+    launchDatePlaceholder: "Next Tuesday / 2026-07-14",
+    accountLabel: "Product Hunt account",
+    communityLabel: "Existing audience",
+    assetLabel: "Asset readiness",
+    generate: "Generate launch workflow",
+    generating: "Generating...",
+    status: {
+      idle: "Draft preview",
+      submitting: "Submitting",
+      running: "Generating",
+      done: "Plan ready",
+      error: "Needs attention",
+    },
+    previewItems: [
+      "Checklist, assets, and launch-day ops",
+      "No auto-posting or vote-task automation",
+      "Copyable Markdown export",
+    ],
+    stages: {
+      idea: "Idea / validation",
+      beta: "Beta or waitlist",
+      launched: "Already launched",
+      majorUpdate: "Major update or relaunch",
+    },
+    goals: {
+      feedback: "Feedback",
+      traffic: "Traffic",
+      users: "First users",
+      credibility: "Public credibility",
+    },
+    accountStates: {
+      yes: "Ready",
+      no: "Not created",
+      unsure: "Not sure",
+    },
+    communityStates: {
+      none: "No audience yet",
+      small: "Small warm list",
+      active: "Active users or community",
+    },
+    assetStates: {
+      rough: "Rough notes only",
+      some: "Some copy or visuals",
+      ready: "Launch assets ready",
+    },
+    statusLabels: {
+      ready: "Ready",
+      needsWork: "Needs work",
+      manual: "Manual",
+    },
+    errors: {
+      validation: {
+        title: "Add the minimum launch brief",
+        body: "Product name, a concrete product outcome, and target audience are required before the planner can create a useful checklist.",
+      },
+      weakInput: {
+        title: "Use a real product description",
+        body: "The brief still looks like placeholder or too-short text. Add what the product does, who uses it, and why the launch matters.",
+      },
+      submitFailed: {
+        title: "Online task submission failed",
+        body: "The planner could not create a generation task. Try again later or check whether the task gateway is available.",
+      },
+      taskFailed: {
+        title: "Generation task failed",
+        body: "The Agent task did not finish. Keep the task ID for logs and confirm the Skills-OL script is deployed and able to write back.",
+      },
+      resultTimeout: {
+        title: "Structured result is not ready",
+        body: "The task may still be running, or Skills-OL did not complete the writeback. This page does not use a local template to fake success.",
+      },
+      wrongResultType: {
+        title: "Unexpected result type",
+        body: "The writeback was not a Product Hunt launch plan, so the frontend refused to render it.",
+      },
+      invalidResultSchema: {
+        title: "Result shape failed validation",
+        body: "The Agent wrote a result, but the fields did not pass schema validation. The Skills-OL output contract needs a fix.",
+      },
+      resultWritebackMissing: {
+        title: "Structured writeback is missing",
+        body: "The task completed without a Skill Result. Confirm the writeback script used the correct task ID and HTTPS API URL.",
+      },
+    },
+    resultPendingTitle: "Asking the Agent to build the launch plan",
+    resultPendingHint:
+      "The page waits for Skills-OL to write back a structured result. It will not show the final plan until resultType and schema validation pass.",
+    taskId: "Task ID: {taskId}",
+    resultReady: "Generated launch workflow",
+    copied: "Copied",
+    copy: "Copy Markdown",
+    download: "Download",
+    reset: "Reset",
+    primaryRisk: "Primary risk",
+    missingInfo: "Missing information",
+    checklist: "Execution checklist",
+    assetPack: "Launch page asset pack",
+    taglines: "Tagline options",
+    topics: "Topic ideas",
+    description: "Short description",
+    thumbnail: "Thumbnail brief",
+    makerComment: "Maker comment",
+    gallery: "Gallery brief",
+    socialPost: "Social post",
+    supporterNote: "Supporter note",
+    launchDay: "Launch day plan",
+    reviewChecklist: "Human review checklist",
+    risks: "Risk notes",
+    owner: "Owner: {owner}",
+  },
+} as const;
+
+export default productHuntLaunchPlanner;

package/src/i18n/messages/en/tools/product-name-generator.ts

@@ -0,0 +1,383 @@
+const productNameGenerator = {
+  meta: {
+    title: "AI Product Name Generator for SaaS",
+    displayTitle: "Product Name Generator",
+    description: "Enter your product idea, users, style, and domain extensions to get 3-5 name candidates, then screen finalists for domain, search, and trademark risks.",
+    intro: "Built for early app, web, SaaS, and AI product naming. Start with a small shortlist backed by clear rationale, then run deeper domain, search-noise, and trademark entrypoint checks only for names worth keeping.",
+    category: "Brand tools",
+    keywords: [
+      "product name generator",
+      "app name generator",
+      "SaaS naming",
+      "AI product naming",
+      "domain pre-screening",
+      "startup name ideas",
+    ],
+  },
+  guide: {
+    workspaceHeading: "Product Name Generator",
+    workspaceHint:
+      "Enter a product idea and get a screened shortlist.",
+    workspaceBadge: "3-5 names",
+    standard: {
+      benefits: {
+        title: "What this product name generator gives you",
+        cards: [
+          {
+            title: "A shortlist worth reviewing",
+            body: "Start with 3-5 candidate names, each backed by a core idea and basic brand signals, so the naming discussion stays focused.",
+          },
+          {
+            title: "Fewer early naming traps",
+            body: "Pronunciation, length, style fit, domain extensions, and search noise are separated so weak directions can be removed early.",
+          },
+          {
+            title: "Clear review boundaries",
+            body: "Domain and trademark checks are treated as pre-screening entrypoints and risk notes, not as legal clearance or guaranteed availability.",
+          },
+        ],
+      },
+      imageTextSections: [
+        {
+          id: "name-shortlist",
+          title: "Turn a rough product idea into a reviewable name shortlist",
+          body: [
+            "Early naming work breaks down when you receive dozens of similar words without a reason to choose. This tool starts with a small set of directions shaped by the product idea, audience, and naming vibe.",
+            "Each candidate includes the core idea and basic fit notes, making it easier for product, design, growth, and founder teams to decide what deserves another look.",
+          ],
+          image: {
+            src: "/tools/product-name-generator-section-primary-8bit-v2.webp",
+            alt: "Pixel-art product name generator visual showing a rough product idea becoming a focused name shortlist.",
+          },
+          imageFirst: true,
+        },
+        {
+          id: "name-variations",
+          title: "Use style, market, and domain preferences to shape the direction",
+          body: [
+            "The same product can need a clear, technical, friendly, premium, or invented name. The form keeps only the controls that materially change the result.",
+            "Target market and preferred extensions influence pronunciation, length, and the next review path, instead of treating every app, SaaS, and AI tool as the same naming problem.",
+          ],
+          image: {
+            src: "/tools/product-name-generator-section-variation-8bit-v2.webp",
+            alt: "Pixel-art naming direction visual showing style, market, and domain preferences shaping candidate names.",
+          },
+        },
+        {
+          id: "name-review",
+          title: "Decide whether a name is worth deeper checks before spending time on it",
+          body: [
+            "Domain, search, and trademark pre-screening continue only after you expand one candidate. That keeps the first pass faster and avoids spending analysis on names you will discard.",
+            "Expanded checks provide search entrypoints, risk notes, and next actions. Final commercial use still needs registrar confirmation and professional trademark review.",
+          ],
+          image: {
+            src: "/tools/product-name-generator-section-support-8bit-v2.webp",
+            alt: "Pixel-art candidate review visual showing domain, search, and trademark pre-screening signals.",
+          },
+          imageFirst: true,
+        },
+      ],
+      generation: {
+        title: "How to generate a product name shortlist",
+        imageAlt: "Pixel-art product naming workflow visual showing a product brief becoming candidate names and review material.",
+        ctaLabel: "Generate names",
+        steps: [
+          {
+            title: "Describe the product idea",
+            body: "Explain what the product does, who it serves, and what job it solves. A rough idea is enough, but placeholders are blocked.",
+          },
+          {
+            title: "Set naming constraints",
+            body: "Choose audience, naming style, target markets, and domain extensions. Add working names or existing candidates in advanced settings if you have them.",
+          },
+          {
+            title: "Generate the shortlist",
+            body: "The tool returns 3-5 candidates with the core idea, basics, screening dimensions, and copy-ready decision material.",
+          },
+          {
+            title: "Expand names for review",
+            body: "Open the candidates that feel promising to inspect domain signals, search entrypoints, trademark sources, risks, and next checks.",
+          },
+        ],
+      },
+      faqIntro: "Use these answers to understand how to use the shortlist, what needs manual review, and why deeper checks run after the first pass.",
+      faqCtaLabel: "View questions",
+    },
+    outputs: "What you get",
+    outputItems: [
+      {
+        title: "A focused name shortlist",
+        body:
+          "The first pass returns a small set of candidates, each with a core idea and basic fit notes for team discussion.",
+      },
+      {
+        title: "Basic brand signals",
+        body:
+          "Pronunciation, length, naming style, and selected domain extensions are screened first so weak directions can be removed early.",
+      },
+      {
+        title: "Per-name deep checks",
+        body:
+          "Open a candidate to continue with domain signals, search noise, trademark entrypoints, risk notes, and next checks.",
+      },
+      {
+        title: "Copy-ready decision material",
+        body:
+          "Names, rationale, screening signals, and risk notes can be copied into a naming review with product, design, growth, or legal teammates.",
+      },
+    ],
+    howToUse: "How to use the product name generator",
+    howToUseSteps: [
+      "Describe the product idea, target users, naming vibe, and any working name.",
+      "Choose target markets, domain extensions, and a budget ceiling; the first pass stays lightweight.",
+      "Review 3-5 candidates with the core idea, pronunciation fit, and basic background first.",
+      "Expand a promising name to trigger a separate domain, SEO, and trademark pre-screen.",
+    ],
+    capabilityNote:
+      "The first pass answers whether there are names worth keeping. Domain price, search noise, and trademark safety are not guaranteed up front; expanded checks are pre-screening only, not registrar confirmation or legal advice.",
+    stagedOutput: "Why the output is staged",
+    stageLabel: "Stage",
+    stagedOutputBullets: [
+      "Stage one answers whether there are names worth considering, keeping wait time and unnecessary deep-check cost low.",
+      "Stage two analyzes only the candidate the user opens, adding domain, search, trademark entrypoints, and risk notes.",
+      "Stage three is for final decisions: compare 2-3 finalists with red/yellow/green verdicts and next actions.",
+    ],
+    resultGuidance: "How to judge the shortlist",
+    resultGuidanceBullets: [
+      "Remove names that are hard to say, too generic, too close to competitors, or unclear about the product direction before buying domains.",
+      "Read 2-3 candidates to real users or teammates and watch whether they can repeat, spell, and roughly understand the product.",
+      "Run expanded checks only for finalists, then review domain price, search noise, trademark entrypoints, and manual review risks.",
+    ],
+    whyTomako: "Why use this naming tool",
+    whyTomakoItems: [
+      {
+        title: "Shortlist first, not a word dump",
+        body:
+          "A good naming tool should reduce choice cost. This page starts with 3-5 directions worth judging instead of flooding you with dozens of similar words.",
+      },
+      {
+        title: "Screened around your product context",
+        body:
+          "Candidates use your product idea, audience, naming style, working names, and target markets instead of treating every app, SaaS, and AI tool the same.",
+      },
+      {
+        title: "Judge the name before paying for deeper checks",
+        body:
+          "Domain, search, and trademark pre-screening are triggered per expanded candidate, which fits early naming work while positioning is still moving.",
+      },
+      {
+        title: "Clear boundaries for review",
+        body:
+          "Domain states, trademark entrypoints, and legal boundaries are separated clearly, so each name becomes a decision starting point rather than a false clearance claim.",
+      },
+    ],
+    strongName: "What makes a strong product name",
+    strongNameBullets: [
+      "Sayable: teammates, users, and investors can repeat it after hearing it once.",
+      "Expandable: it is not trapped inside today's narrow feature scope.",
+      "Findable: brand search, app stores, GitHub, social handles, and domains still have room.",
+      "Explainable: the metaphor connects naturally to positioning, user context, or brand voice.",
+      "Distinct: spelling and pronunciation do not blur into nearby software, AI tools, or category leaders.",
+    ],
+    mistakes: "Common naming mistakes",
+    mistakeBullets: [
+      "Treating `.com` availability as the only signal while ignoring market fit and memory.",
+      "Generating dozens of attractive names without staged domain, SEO, trademark, and category checks.",
+      "Chasing abstract premium vibes so early that users cannot tell what the product does.",
+      "Forcing keywords into the name until it becomes too long to remember, say, or share.",
+    ],
+    useCases: "Use cases",
+    useCaseBullets: [
+      "Indie builders naming a new app, web tool, plugin, or AI side product.",
+      "Early teams that need expandable name directions while positioning is still moving.",
+      "Founders with 2-5 candidates who need to decide which one deserves domain spend.",
+      "Global products balancing English readability, Chinese perception, and search noise.",
+      "Product, design, and growth teams preparing a naming workshop with a shared shortlist and criteria.",
+    ],
+    faq: "FAQ",
+    faqItems: [
+      {
+        question: "Why not return every domain and trademark check at once?",
+        answer:
+          "Most early names will be discarded. A lightweight first pass followed by per-name expansion lowers wait time and unnecessary analysis cost.",
+      },
+      {
+        question: "Do I need a complete product positioning brief?",
+        answer:
+          "No. Describe what the product does, who it serves, and the feeling it should create. A rough idea is enough for a first direction, and the shortlist can help you refine positioning.",
+      },
+      {
+        question: "Does the tool guarantee that a domain is buyable?",
+        answer:
+          "No. Domain status comes from fast RDAP/DNS signals. Final availability and price must be confirmed at a registrar, especially for premium domains.",
+      },
+      {
+        question: "Can trademark pre-screening replace legal review?",
+        answer:
+          "No. The tool provides official database entrypoints, search queries, and risk notes. It cannot provide legal clearance. Run professional clearance before investing heavily in a brand.",
+      },
+      {
+        question: "Can I analyze names I already have?",
+        answer:
+          "Yes. Add your candidates line by line. The tool will include them in the first screen and can generate nearby variants from the product positioning.",
+      },
+      {
+        question: "How is my product idea used?",
+        answer:
+          "The form content is used as context for name generation and expanded checks. Do not submit confidential source code, unreleased trade secrets, customer data, or sensitive personal information.",
+      },
+      {
+        question: "Can I use the generated names commercially?",
+        answer:
+          "Use the names as starting points. Before commercial use, confirm domains, app stores, social handles, trademark similarity, and target-market meaning, with professional trademark review when needed.",
+      },
+    ],
+    ctaPrimary: "Continue to GTM checklist",
+    ctaSecondary: "Back to all tools",
+    ctaHint:
+      "Once you have a shortlist, check whether positioning, channels, assets, and launch metrics are ready.",
+    visualAlt: {
+      hero: "Product name generator hero showing rough ideas becoming candidate directions and check signals.",
+      value: "Focused shortlist visual showing scattered naming thoughts reduced into a few high-quality directions.",
+      checks: "Candidate pre-screen visual showing domain, search, and review entrypoints.",
+      decision: "Naming decision packet visual showing keep, check, and decide markers for finalists.",
+    },
+  },
+  widget: {
+    formTitle: "Generate product name candidates",
+    formHint:
+      "Generate reviewable candidates first; deeper checks run after expansion.",
+    workingNameLabel: "Existing product or working name",
+    workingNamePlaceholder: "e.g. Kitepath, optional",
+    descriptionLabel: "Product idea",
+    descriptionPlaceholder:
+      "Describe what the product does, who it serves, and the job it solves. Example: an AI workspace that helps indie founders create launch assets and channel plans.",
+    targetUsersLabel: "Target users",
+    targetUsersPlaceholder: "e.g. indie developers, SaaS founders, outbound product teams",
+    desiredVibeLabel: "Desired vibe",
+    desiredVibePlaceholder: "e.g. clear, trustworthy, technical, lighter than enterprise",
+    styleLabel: "Naming style",
+    marketLabel: "Target market / language",
+    marketPlaceholder: "Choose markets",
+    domainLabel: "Domain extensions to prioritize",
+    domainPlaceholder: "Choose extensions",
+    maxPriceLabel: "Max acceptable price (USD)",
+    countLabel: "Result count",
+    advancedLabel: "More screening settings",
+    fallbackLabel: "Allow backup domain patterns",
+    fallbackHint: "Examples: get + name, try + name, name + app, name + hq.",
+    candidateNamesLabel: "Existing candidates",
+    candidateNamesPlaceholder: "One per line, or comma-separated. Example:\nKitepath\nNimbly\nAuralis",
+    optional: "Optional",
+    generateAgent: "Generate names",
+    generatingAgent: "Generating names",
+    retryAgent: "Regenerate names",
+    reset: "Reset",
+    emptyTitle: "Ready for name candidates",
+    emptyHint:
+      "The first pass reveals names one by one. Each card starts with the core idea and basics; domain, SEO, and trademark pre-screening runs only after expansion.",
+    emptyBullets: ["3-5 candidate names", "Core idea and basic fit", "On-demand second-stage checks"],
+    workspaceVisualAlt:
+      "Workspace side visual showing rough naming inputs becoming three candidate directions and domain-extension signals.",
+    loadingTitle: "Generating and screening",
+    loadingStatus: "Preparing the name shortlist",
+    loadingCountdown: "about 1 min",
+    loadingHint:
+      "Generating name candidates from your product idea and running basic pronunciation, length, and domain-extension screening. The first pass does not perform full trademark clearance.",
+    loadingSteps: [
+      "Build naming strategy and candidates",
+      "Run pronunciation, length, and brand-fit screening",
+      "Check only selected domain extensions",
+      "Prepare expandable detail paths",
+    ],
+    errorTitle: "No naming result yet",
+    agentResult: "Name shortlist",
+    resultTitle: "First-pass shortlist",
+    copyAll: "Copy all candidates",
+    copyName: "Copy name",
+    copied: "Copied",
+    expandDetail: "Expand details",
+    detailLoading: "Checking",
+    detailRunning: "Preparing expanded checks",
+    detailAwaiting: "The deeper check finished its first pass and is preparing displayable results.",
+    score: "Score",
+    coreIdea: "Core idea",
+    basics: "Basics",
+    domains: "Domain snapshot",
+    checks: "Screening checks",
+    seoDetail: "SEO / search pre-screen",
+    trademarkDetail: "Trademark pre-screen",
+    risks: "Risk notes",
+    nextChecks: "Next checks",
+    openLink: "Open link",
+    taskIdLabel: "Task ID",
+    styles: {
+      clear: "Clear",
+      technical: "Technical",
+      friendly: "Friendly",
+      premium: "Premium",
+      invented: "Invented",
+    },
+    markets: {
+      globalEnglish: "Global English",
+      mainlandChina: "Mainland China",
+      us: "United States",
+      eu: "Europe",
+      japan: "Japan",
+      sea: "Southeast Asia",
+    },
+    tlds: {
+      ai: ".ai",
+      com: ".com",
+      io: ".io",
+      app: ".app",
+      dev: ".dev",
+      co: ".co",
+      so: ".so",
+      studio: ".studio",
+    },
+    verdicts: {
+      green: "Green",
+      light_yellow: "Light yellow",
+      yellow: "Yellow",
+      orange: "Orange",
+      red: "Red",
+      unknown: "Unknown",
+      manual_required: "Manual check",
+    },
+    stages: {
+      unchecked_idea: "Unchecked idea",
+      fast_screened: "Fast-screened",
+      domain_checked: "Domain-checked",
+      deep_researched: "Deep-researched",
+    },
+    errors: {
+      required: "Enter the product idea and choose at least one market and domain extension.",
+      fixFields: "Fix the highlighted fields before generating names.",
+      descriptionRequired: "Enter the product idea first.",
+      descriptionShort: "Add a little more to the product idea. Use at least 4 characters.",
+      descriptionMeaningful: "Enter a real product idea, not only numbers or placeholder text.",
+      market: "Choose at least one target market or language.",
+      domain: "Choose at least one domain extension to prioritize.",
+      maxPrice: "Max acceptable price must be a number from 0 to 50000.",
+      candidateNames: "Existing candidates are too long. Keep them under 500 characters.",
+      copy: "This browser could not copy the text. Try again later.",
+      agent:
+        "Name generation failed to submit or complete. Retry shortly; there is no displayable naming result yet.",
+      gateway:
+        "The online task service is temporarily unavailable, so the task was not created. This is not a form-selection issue. Retry shortly.",
+      noResult:
+        "The naming flow ended without a displayable structured result. Retry shortly.",
+      invalidResult:
+        "The returned result structure or content does not meet this tool's requirements. Regenerate.",
+      demoFallbackResult:
+        "The returned names look like example or default candidates, so the page refused to display them. Regenerate, or confirm the remote naming flow has been updated.",
+      noDetail:
+        "The detail task ended without a displayable result. Retry.",
+      invalidDetailResult:
+        "The detail result does not match the structure required by this tool. Retry.",
+    },
+  },
+} as const;
+
+export default productNameGenerator;