@tomako/tools-runtime 0.1.0 → 0.1.2

package/src/i18n/messages/en/tools/app-icon-resizer.ts

@@ -1,10 +1,10 @@
 const appIconResizer = {
   meta: {
-    title: "App Icon Resizer for iOS & Android",
+    title: "App Icon Resizer for iOS and Android",
     description:
-      "Resize one app icon into iOS AppIcon.appiconset, App Store 1024, Google Play 512, and Android launcher PNGs—then download a ZIP locally.",
+      "Upload one square app icon and locally generate an Xcode AppIcon, Google Play 512 icon, and Android legacy launcher package, then review and download one ZIP.",
     intro:
-      "Prepare app submission and engineering icon assets. Upload a 1024px+ square source icon, choose Apple, Google Play, or both, and keep processing local in your browser.",
+      "Upload one 1024px+ square source and locally generate Xcode, Google Play, and Android legacy launcher files.",
     category: "App submission tools",
     keywords: [
       "app icon resizer",
@@ -21,48 +21,61 @@ const appIconResizer = {
   guide: {
     heroVisualAlt:
       "App icon asset package visual showing one source icon exported into store submission, Xcode, and Android launcher files.",
-    workspaceHeading: "App icon resizer",
+    workspaceHeading: "App icon package generator",
     workspaceHint:
-      "Upload one source icon and generate store plus brand icon ZIPs locally.",
+      "One source, one local ZIP for store and engineering handoff.",
     workspaceBadge: "PNG + ZIP",
     standard: {
       benefits: {
-        title: "What the App Icon Resizer gives you",
+        title: "Why use this app icon resizer",
         cards: [
           {
-            title: "One source for every target",
-            body: "Generate Xcode AppIcon, App Store 1024, Google Play 512, and Android mipmap assets in one pass.",
+            title: "Generate the handoff at once",
+            body: "Skip individual artboards and exports. Generate Xcode AppIcon, Google Play 512, and Android legacy launcher files together.",
           },
           {
-            title: "Organized sizes and folders",
-            body: "Group, name, and package files by Apple, Google Play, or both so design and engineering get the right assets.",
+            title: "Folders and names are ready",
+            body: "Store uploads, Xcode assets, and Android project files are grouped by destination, with no manual renaming or folder setup.",
           },
           {
-            title: "Local generation with review",
-            body: "Keep the source in your browser, inspect crops, edges, transparency, and file-size risks, then download PNGs or a ZIP.",
+            title: "Review before download",
+            body: "Check transparency, crop mode, and file-size warnings first. Resizing and ZIP packaging stay in the current browser.",
           },
         ],
       },
-      imageTextSections: [
-        {
-          id: "icon-package",
-          title: "Turn one source icon\ninto a complete package",
-          body: [
-            "App icon resizing usually fails when sizes, folders, and filenames get mixed. This tool groups iOS AppIcon.appiconset, App Store 1024, Google Play 512, and Android mipmap outputs into clear folders.",
-            "Your source icon is read locally in the browser. After generation, download the full ZIP or filter by platform and inspect individual PNG files.",
-          ],
-          image: {
-            src: "/tools/app-icon-resizer-section-primary-8bit-v3.webp",
-            alt: "8bit scene showing one app icon source turning into platform icon asset packages.",
+      outputPreview: {
+        eyebrow: "Example output",
+        title: "What is inside the download",
+        intro: "With both platforms selected, the ZIP groups files by their real handoff destination. These are the files the current tool generates.",
+        inputLabel: "Example input",
+        input: "One 1024 × 1024 square PNG with Apple + Google Play / Android selected",
+        outputLabel: "Main ZIP contents",
+        fields: [
+          {
+            label: "Apple/AppIcon.appiconset",
+            body: "Compatible iPhone, iPad, and ios-marketing sizes with Contents.json.",
           },
-          imageFirst: true,
-        },
+          {
+            label: "Apple/AppStoreIcon-1024.png",
+            body: "A 1024px review copy for checking composition, padding, and brand consistency.",
+          },
+          {
+            label: "GooglePlay/app-icon-512.png",
+            body: "The 512 × 512 PNG for the Play Console store listing.",
+          },
+          {
+            label: "Android/res/mipmap-*",
+            body: "mdpi through xxxhdpi legacy launcher PNGs; no adaptive icon layers.",
+          },
+        ],
+      },
+      imageTextSections: [
         {
           id: "platform-scope",
-          title: "Choose platform scope\nwithout mixing file roles",
+          title: "How to use the files",
           body: [
-            "Apple, Google Play, and Android brand resources are not the same file. Apple assets belong in Xcode, Google Play needs a 512 x 512 listing icon, and Android launcher assets are grouped by density.",
-            "Once you choose a package scope, the result panel can filter by platform so design, engineering, and ASO teammates can take the right files.",
+            "Import Apple/AppIcon.appiconset into the Xcode asset catalog and submit it with the build. GooglePlay/app-icon-512.png is for the Play Console store listing.",
+            "Android/res/mipmap-* contains legacy launcher resources. If the project uses adaptive icons, configure foreground, background, and optional monochrome layers in Android Studio.",
           ],
           image: {
             src: "/tools/app-icon-resizer-section-variation-8bit-v3.webp",
@@ -71,10 +84,10 @@ const appIconResizer = {
         },
         {
           id: "handoff-review",
-          title: "Preview before download\nto avoid release-week fixes",
+          title: "What to know before use",
           body: [
-            "The result grid previews each PNG on a transparency checkerboard, so transparent pixels are not mistaken for a gray background. Non-square sources are center-cropped, and undersized sources are blocked.",
-            "The downloaded README explains where each folder is used and reminds you to review corners, shadows, adaptive icons, copyright, and the latest platform rules.",
+            "Non-square images are center-cropped without stretching. Use square full-bleed source artwork for final handoff, and do not pre-apply rounded corners or outer shadows.",
+            "Image reading, resizing, and ZIP packaging happen locally in your browser. Before release, review current platform rules, brand rights, and legibility on light and dark backgrounds.",
           ],
           image: {
             src: "/tools/app-icon-resizer-section-support-8bit-v3.webp",
@@ -84,21 +97,17 @@ const appIconResizer = {
         },
       ],
       generation: {
-        title: "App icon\nresizing workflow",
+        title: "Finish in three steps",
         imageAlt: "8bit workflow scene showing upload, package scope, resize preview, and ZIP export.",
         ctaLabel: "Generate icon package",
         steps: [
           {
-            title: "Upload one source icon",
-            body: "Export square full-bleed artwork from the design source when possible. Apple or dual-platform packages need at least 1024px on the shortest side.",
-          },
-          {
-            title: "Choose the platform scope",
-            body: "Pick Apple, Google Play, or both. The tool maps that choice to the right size list and folder structure.",
+            title: "Upload and choose platforms",
+            body: "Upload a PNG, JPG, or WebP, then choose Apple, Google Play / Android, or both. Apple packages need at least 1024px on the shortest side.",
           },
           {
-            title: "Generate PNGs and README",
-            body: "The browser resizes, crops, preserves transparency, and writes the README locally without uploading your source file.",
+            title: "Generate the package locally",
+            body: "Your browser crops, resizes, names, and organizes the files, then creates PNGs, Contents.json, and README.",
           },
           {
             title: "Review and download the ZIP",
@@ -106,9 +115,38 @@ const appIconResizer = {
           },
         ],
       },
+      referenceTable: {
+        title: "Actual outputs and destinations",
+        intro: "Modern Xcode can generate smaller variants from one 1024px icon. Tomako still exports a compatible full AppIcon.appiconset for existing projects and team handoff.",
+        mobileHint: "Swipe the table sideways to review every file destination.",
+        columns: ["Output group", "Included files", "Current purpose", "Destination"],
+        rows: [
+          {
+            label: "Xcode AppIcon",
+            cells: ["Compatible 20–1024px sizes with Contents.json", "iOS / iPadOS project icons", "Xcode asset catalog"],
+          },
+          {
+            label: "Apple 1024 review copy",
+            cells: ["Apple/AppStoreIcon-1024.png", "Team review copy, not a separate fixed upload flow", "Check composition and padding"],
+          },
+          {
+            label: "Google Play",
+            cells: ["GooglePlay/app-icon-512.png", "512 × 512 PNG; warns above 1024KB", "Play Console store listing"],
+          },
+          {
+            label: "Android legacy launcher",
+            cells: ["48 / 72 / 96 / 144 / 192px", "Compatible launcher PNGs", "Android/res/mipmap-*"],
+          },
+          {
+            label: "Handoff notes",
+            cells: ["README.txt", "Folder roles and output boundaries", "Design, engineering, and ASO"],
+          },
+        ],
+        note: "Google Play icons must also meet the platform's PNG, file-size, and content rules. This version does not generate Android adaptive foreground, background, or monochrome layers.",
+      },
       faqIntro:
-        "These answers help you decide whether your source icon is ready, how the files should be used, and which platform rules still need manual review.",
-      faqCtaLabel: "Review boundaries",
+        "Confirm source requirements and file destinations before deciding whether this package fits your release workflow.",
+      faqCtaLabel: "Back to workspace",
     },
     whatYouGetHeading: "What you get after generation",
     valueVisualAlt: "Organized app icon package with Xcode assets, store upload icons, Android brand folders, and a downloadable zip.",
@@ -194,44 +232,34 @@ const appIconResizer = {
     faqHeading: "FAQ",
     faqItems: [
       {
-        question: "Are uploaded app icons stored on a server?",
+        question: "What size and format should the source icon be?",
         answer:
-          "No. This tool reads the image, renders canvas outputs, and builds the PNG ZIP locally in the browser. Refreshing the page clears the file state, and the source icon is not uploaded to a server.",
+          "Use a 1024 × 1024 or larger square PNG when possible. JPG and WebP are supported; Google Play / Android-only packages need at least 512px on the shortest side.",
       },
       {
-        question: "Can I upload the generated files directly to App Store and Google Play?",
+        question: "Are uploaded app icons stored on a server?",
         answer:
-          "GooglePlay/app-icon-512.png targets the Play Console App icon upload requirement. For Apple, the more accurate path is to place AppIcon.appiconset in Xcode and submit it with your build to App Store Connect.",
+          "No. Image reading, canvas resizing, and ZIP packaging happen locally in your browser. Refreshing the page clears the file state, and the source icon is not uploaded.",
       },
       {
-        question: "What size and format should the source icon be?",
+        question: "Can I use the generated files for App Store and Google Play?",
         answer:
-          "Use a 1024 x 1024 or larger square PNG when possible. JPG and WebP are supported, but final handoff is safest when you export full-bleed square artwork from the design source.",
+          "They are ready as project and store assets, but you should still review them before release. GooglePlay/app-icon-512.png goes to Play Console; Apple/AppIcon.appiconset belongs in Xcode and ships with your build to App Store Connect.",
       },
       {
         question: "Why does the tool not add rounded corners or shadows?",
         answer:
-          "Stores and operating systems apply their own masks, corners, or shadows. Pre-rounding the artwork can cause double clipping, uneven edges, or platform rejection.",
-      },
-      {
-        question: "What if my source image is not square?",
-        answer:
-          "The tool center-crops it to a square without stretching. For final delivery, export square full-bleed artwork from the design source to avoid shifted subjects or clipped edges.",
+          "Do not add them in advance. Stores and operating systems apply their own masks, corners, or shadows, and pre-processing can cause double clipping or uneven edges.",
       },
       {
-        question: "How are transparent icons handled?",
+        question: "What if the source is not square or has transparency?",
         answer:
-          "Transparency is preserved, and the result preview uses a transparency grid. Before final submission, review the icon on light, dark, and platform-masked backgrounds.",
+          "It is center-cropped without stretching. Transparent pixels are preserved, but review alignment, crop edges, and legibility on different backgrounds before release.",
       },
       {
         question: "Does this generate Android adaptive icons?",
         answer:
-          "No. It exports Google Play 512 and legacy launcher mipmap PNGs, but it does not generate adaptive icon foreground/background XML pairs.",
-      },
-      {
-        question: "What happens if the image is too small?",
-        answer:
-          "Apple or dual-platform packages require 1024px or larger on the shortest side. Google Play / Android packages require at least 512px. The tool also warns when the Google Play 512 PNG exceeds 1024KB.",
+          "No. It exports Google Play 512 and legacy launcher mipmap PNGs, but it does not generate adaptive icon foreground/background XML. Configure adaptive icons separately in the Android project.",
       },
     ],
     ctaPrimary: "Create store screenshots",

package/src/i18n/messages/en/tools/index.ts

@@ -14,6 +14,7 @@ import kokoCodexAssistant from "./koko-codex-assistant";
 import logoGenerator from "./logo-generator";
 import marketForecastReport from "./market-forecast-report";
 import millionUserGrowthTest from "./million-user-growth-test";
+import mrrCalculator from "./mrr-calculator";
 import ogImageGenerator from "./og-image-generator";
 import productAgreementGenerator from "./product-agreement-generator";
 import pitchDeckGenerator from "./pitch-deck-generator";
@@ -59,6 +60,7 @@ const toolsPages = {
   logoGenerator,
   marketForecastReport,
   millionUserGrowthTest,
+  mrrCalculator,
   ogImageGenerator,
   appStoreScreenshotGenerator,
   twitterGifDownloader,

package/src/i18n/messages/en/tools/mrr-calculator.ts

@@ -0,0 +1,202 @@
+const mrrCalculator = {
+  meta: {
+    title: "MRR Calculator for SaaS Revenue",
+    description:
+      "Calculate MRR and ARR from customer data, or estimate SaaS MRR from public website traffic, pricing and editable assumptions.",
+    intro:
+      "Normalize monthly, quarterly or annual subscriptions into monthly recurring revenue, then inspect the formula or switch to a rough public-data estimate.",
+    category: "SaaS metrics tools",
+    keywords: [
+      "mrr calculator",
+      "monthly recurring revenue calculator",
+      "monthly recurring revenue formula",
+      "how to calculate mrr",
+      "mrr to arr calculator",
+      "saas mrr calculator",
+    ],
+    inputSignal: "Customer and billing data, or public traffic and pricing",
+    outputSignal: "MRR, ARR, monthly ARPA, growth or a public-data estimate",
+    boundarySignal: "Browser-side calculation; estimates are directional, not reported revenue",
+  },
+  guide: {
+    workspaceHeading: "MRR Calculator for SaaS",
+    workspaceHint:
+      "Calculate monthly recurring revenue from known customer data, or switch to a rough SaaS MRR estimate using public traffic and pricing.",
+    standard: {
+      benefits: {
+        title: "What you get from this MRR calculator",
+        cards: [
+          {
+            title: "MRR and ARR together",
+            body: "See monthly recurring revenue, annual recurring revenue and monthly ARPA without building a spreadsheet.",
+          },
+          {
+            title: "Billing periods normalized",
+            body: "Enter monthly, quarterly or annual subscription prices and let the calculator convert them to one monthly basis.",
+          },
+          {
+            title: "A second view for competitors",
+            body: "When customer counts are unknown, use public traffic and pricing with editable assumptions to get a clearly labeled rough estimate.",
+          },
+        ],
+      },
+      imageTextSections: [
+        {
+          id: "choose-the-right-mrr-method",
+          title: "Choose the right way\nto calculate MRR",
+          body: [
+            { text: "To calculate MRR or ARR for your own product, use the default Calculate MRR mode. Enter active paying customers, recurring amount per customer and billing period for a direct result.", highlights: ["Calculate MRR"] },
+            { text: "To roughly understand a competitor's or another SaaS product's revenue scale, switch to Estimate SaaS MRR. Use public website traffic and plan pricing as inputs; the result is directional, not reported company revenue.", highlights: ["Estimate SaaS MRR"] },
+          ],
+          image: {
+            src: "/tools/mrr-calculator-section-steps-8bit.webp",
+            alt: "Pixel-art workspace comparing calculated MRR from customer data with estimated SaaS MRR from public traffic and pricing.",
+          },
+          imageFirst: true,
+          hideImageOnMobile: true,
+        },
+        {
+          id: "monthly-recurring-revenue-formula",
+          title: "How to calculate\nmonthly recurring revenue",
+          body: [
+            { text: "The monthly recurring revenue formula is MRR = active paying customers × monthly ARPA. Divide a quarterly recurring amount by 3 or an annual amount by 12 before multiplying by the customer count.", highlights: ["MRR = active paying customers × monthly ARPA"] },
+            "Example: 12 customers paying $1,200 per year have monthly ARPA of $100, MRR of $1,200 and ARR of $14,400. If previous MRR was $1,000, MoM growth is ($1,200 − $1,000) ÷ $1,000 = 20%.",
+          ],
+          image: {
+            src: "/tools/mrr-calculator-section-primary-8bit.webp",
+            alt: "Pixel-art SaaS ledger normalizing monthly, quarterly and annual subscriptions into one calculated MRR result.",
+          },
+        },
+        {
+          id: "estimate-saas-mrr",
+          title: "Estimate SaaS MRR\nfrom public data",
+          body: [
+            "Estimate mode calculates new paid customers as visits × acquisition-eligible share × visitor-to-paid rate. It then uses average paid lifetime to approximate active customers and multiplies them by the normalized monthly plan price.",
+            "Repeat visits, existing customers, channel mix, conversion, plan mix and churn remain unknown. Use the same assumptions when comparing products, and change them when the business model differs; the result is directional, not factual revenue.",
+          ],
+          image: {
+            src: "/tools/mrr-calculator-section-variation-8bit.webp",
+            alt: "Pixel-art public traffic chart and pricing card feeding a clearly labeled estimated SaaS MRR result.",
+          },
+          imageFirst: true,
+        },
+      ],
+      editorialSections: [
+        {
+          id: "what-counts-as-mrr",
+          title: "What counts as monthly recurring revenue",
+          body: [
+            "MRR means recurring subscription revenue normalized to one month. Include active plan revenue that continues under the current contract, and convert quarterly or annual recurring amounts to a monthly basis.",
+            "Exclude one-time setup and implementation fees, professional services, hardware, tax and other non-recurring payments. For discounts, refunds, usage billing, expansion, contraction or churn movements, use billing-system data and a fuller revenue model.",
+          ],
+        },
+        {
+          id: "common-mrr-calculation-mistakes",
+          title: "Common MRR calculation mistakes",
+          body: [
+            "Do not put a full annual payment into one month's MRR, count one-time revenue, or confuse new MRR with the company's total MRR. If several plans are involved, calculate each plan separately or use a weighted monthly average instead of assuming customers are evenly distributed.",
+            "In estimate mode, do not treat all website visits or direct traffic as new prospects. Visits can include returning users, current customers, employees and repeated sessions, so the acquisition-eligible share must remain an explicit assumption.",
+            "Most importantly, do not present an Estimated MRR scenario as a competitor's actual revenue. Public traffic and pricing do not reveal its real customers, discounts, retention or channel mix.",
+          ],
+        },
+        {
+          id: "use-mrr-and-arr-results",
+          title: "How to use your MRR and ARR results",
+          body: [
+            "Use calculated MRR for a quick operating check, monthly reporting or pricing scenarios after verifying the customer count, recurring amount and billing period. Use the optional previous MRR to inspect month-over-month growth, and convert MRR to ARR for an annualized run-rate view.",
+            "Use estimated MRR only for directional competitor comparisons. Keep the assumptions consistent across products, save the basis with the number and rerun the scenario when traffic or pricing changes.",
+            "These results can lead into churn, retention and LTV:CAC analysis, but they are not accounting statements, financial advice or a valuation opinion.",
+          ],
+        },
+      ],
+      faqIntro:
+        "Short answers about mixed plans, zero growth denominators, direct traffic, estimate limits and browser-local data.",
+      faqCtaLabel: "Use the calculator",
+    },
+    faqHeading: "MRR calculator FAQ",
+    faqItems: [
+      {
+        question: "How do I use this MRR calculator?",
+        answer: "To calculate MRR or ARR for your own product, stay in the default Calculate MRR mode and enter active paying customers, recurring amount per customer and billing period. To roughly understand a competitor or another SaaS product, switch to Estimate SaaS MRR and use public website traffic and plan pricing as inputs. The first is a direct calculation from your inputs; the second is directional only.",
+      },
+      {
+        question: "Can I calculate several pricing plans together?",
+        answer: "V1 accepts one blended average recurring amount. Calculate each plan separately and add the MRR values, or first compute a weighted average monthly price if your plan mix is known.",
+      },
+      {
+        question: "What happens when previous MRR is zero?",
+        answer: "The calculator still returns current MRR and ARR but hides month-over-month growth, because percentage growth from a zero denominator is not meaningful.",
+      },
+      {
+        question: "Should direct traffic be treated as new customers?",
+        answer: "No. Direct traffic can include returning visitors, current customers, employees, bookmarked visits and unattributed sessions. Count only an editable acquisition-eligible share when building an estimate.",
+      },
+      {
+        question: "How accurate is the SaaS MRR estimate?",
+        answer: "Treat it as directional, not precise. Its usefulness depends on whether the traffic, price, conversion and paid-lifetime assumptions are reasonable for the product being compared.",
+      },
+      {
+        question: "Is the estimate financial advice or a valuation opinion?",
+        answer: "No. It is a scenario based on public inputs and your assumptions. Do not use it as accounting evidence, a factual claim about a company, financial advice or a valuation conclusion.",
+      },
+      {
+        question: "Does my calculator data leave the browser?",
+        answer: "No. This version calculates in the browser and does not upload the values or require an account.",
+      },
+    ],
+  },
+  widget: {
+    calculateMode: "Calculate MRR",
+    estimateMode: "Estimate SaaS MRR",
+    modeSwitchLabel: "Switch between calculated and estimated MRR",
+    calculateHint: "Use known paying-customer and subscription data for a calculated result.",
+    estimateHint: "Use public traffic and pricing for a rough estimate—not reported company revenue.",
+    activeCustomers: "Active paying customers",
+    recurringAmount: "Recurring amount per customer",
+    billingPeriod: "Billing period",
+    previousMrr: "Previous month MRR",
+    optional: "Optional",
+    addPreviousMrr: "Add previous month MRR (optional)",
+    currency: "Currency",
+    monthlyVisits: "Estimated monthly website visits",
+    planPrice: "Representative public plan price",
+    showAssumptions: "Adjust estimate assumptions",
+    hideAssumptions: "Hide estimate assumptions",
+    assumptionNote: "Starter assumptions, not industry benchmarks. Change them to match the product you are evaluating.",
+    eligibleVisitShare: "Acquisition-eligible visit share (%)",
+    visitorToPaidRate: "Visitor-to-paid rate (%)",
+    averagePaidLifetime: "Average paid lifetime (months)",
+    periods: { month: "Monthly", quarter: "Quarterly", year: "Annual" },
+    calculatedLabel: "Calculated",
+    estimatedLabel: "Estimated",
+    calculatedResultTitle: "Monthly recurring revenue",
+    estimatedResultTitle: "Directional SaaS revenue estimate",
+    calculatedMrr: "Calculated MRR",
+    estimatedMrr: "Estimated MRR",
+    arr: "ARR",
+    estimatedArr: "Estimated ARR",
+    monthlyArpa: "Monthly ARPA",
+    monthlyPlanPrice: "Monthly plan price",
+    momGrowth: "MoM growth",
+    newPaidCustomers: "New paid customers / month",
+    activePaidCustomers: "Estimated active paid customers",
+    formula: "Formula check",
+    perMonth: "per month",
+    assumptionsUsed: "Assumptions used",
+    notAvailable: "Not available",
+    calculatedGuidance: "Include recurring subscription revenue. Exclude one-time fees, tax and non-recurring services.",
+    estimateDisclaimer: "Public-data estimate only. Actual traffic quality, conversion, plan mix, churn and revenue may differ.",
+    copyResult: "Copy result",
+    copied: "Copied",
+    reset: "Reset",
+    fixInputsTitle: "Check the highlighted inputs",
+    fixInputsBody: "Enter valid values to update the result.",
+    errors: {
+      nonNegative: "Enter zero or a positive number.",
+      positive: "Enter a number greater than zero.",
+      percent: "Enter a percentage from 0 to 100.",
+    },
+  },
+} as const;
+
+export default mrrCalculator;

package/src/i18n/messages/en/tools-ui.ts

@@ -648,9 +648,10 @@ const toolsUi = {
     downloadZip: "Download ZIP",
     selectedTitle: "Selected icon",
     downloadPng: "Download PNG",
-    outputEmptyTitle: "Upload a source icon and choose a platform",
+    outputEmptyTitle: "Review the package here after upload",
     outputEmptyHint:
-      "Upload a 1024px+ square source icon, choose Apple, Google Play, or both, then generate. The ZIP download and icon previews will appear here.",
+      "Your current platform choice will create these main folders. After generation, this area switches to real PNG previews and the ZIP download.",
+    outputExampleLabel: "Example app-icon-assets.zip structure",
     platforms: {
       all: "App Store + Google Play",
       apple: "Apple App Store / iOS",

package/src/i18n/messages/zh/page/tools.ts

@@ -5,10 +5,9 @@ const tools = {
       "免费使用产品起名、市场调研、App 上架图和社媒内容等在线工具。",
   },
   eyebrow: "全部工具",
-  title: "免费工具，帮你完成产品、营销与内容任务",
+  title: "Tomako 工具",
   heroTitle: "用可执行工具，把上线前的 GTM 工作跑清楚",
-  description:
-    "产品起名、市场调研、App 上架图和社媒内容等工具都在这里，选择一个即可开始。",
+  description: "免费工具，帮你完成产品、营销与内容任务，任选一个即可开始",
   toolsCount: "{count} 个工具可免费使用",
   filters: {
     all: "全部工具",