@tomako/tools-runtime 0.1.0

package/src/i18n/messages/en/tools/email-template-generator.ts

@@ -0,0 +1,302 @@
+const emailTemplateGenerator = {
+  meta: {
+    title: "Email Template Generator",
+    description: "Turn marketing or common transactional email requirements into an Agent-generated MJML-first template package with HTML preview, plain text, variables, review notes, and developer handoff.",
+    intro: "Convert a rough email brief into a previewable, revisable, export-ready MJML template package for campaigns, verification codes, receipts, subscription confirmations, and account notifications.",
+    category: "Marketing tools",
+    keywords: [
+      "email template generator",
+      "MJML email template",
+      "HTML email generator",
+      "marketing email template",
+    ],
+    inputSignal: "Brief, audience, scenario, brand tone",
+    outputSignal: "MJML, HTML, plain text, variables, handoff notes",
+    boundarySignal: "Marketing compliance needs review",
+  },
+  guide: {
+    heroImageAlt: "Visual of a rough email brief becoming MJML, HTML, plain text, variables, and an export bundle.",
+    workspaceHeading: "Tool Workspace",
+    workspaceHint:
+      "Describe the email goal, audience, scenario, and brand tone. The Agent returns a structured MJML-first package you can preview, revise, copy, or export.",
+    workspaceBadge: "MJML package",
+    outputs: "What You Get",
+    outputsIntro:
+      "The result is designed for handoff, not just reading. You get source markup, rendered HTML, fallback text, variables, and review notes in one structured package.",
+    outputItems: [
+      {
+        title: "MJML Source",
+        body: "Use MJML as the editable source of truth for responsive email layouts, spacing, sections, buttons, and footer structure.",
+      },
+      {
+        title: "HTML Email",
+        body: "Export a matching HTML version for email service imports, developer review, and client-side preview.",
+      },
+      {
+        title: "Plain-Text Fallback",
+        body: "Get a readable text version for deliverability, accessibility, and clients that do not render HTML.",
+      },
+      {
+        title: "Variables And Placeholders",
+        body: "Receive suggested placeholders such as {{first_name}}, {{cta_url}}, {{verification_code}}, or {{invoice_url}} with examples.",
+      },
+      {
+        title: "Review Notes",
+        body: "See compliance, accessibility, rendering, and missing-information notes before handing the template to development.",
+      },
+      {
+        title: "Agent Revision Loop",
+        body: "After generation, describe the exact wording or module change and regenerate a new structured result from the Agent.",
+      },
+    ],
+    valueVisualAlt: "Visual of an email template package with MJML, HTML, variables, and developer handoff notes.",
+    standards: "What Makes A Good Email Template Generator",
+    standardsIntro:
+      "A useful email generator must do more than produce nice copy. It should create a format that developers, marketers, and lifecycle teams can actually ship.",
+    standardsItems: [
+      {
+        title: "Exportable Format",
+        body: "MJML, HTML, and plain text are separated so the source, rendered template, and fallback each have a clear job.",
+      },
+      {
+        title: "Scenario Awareness",
+        body: "Campaigns, lifecycle emails, verification codes, receipts, and subscription notices need different tone, CTA, and compliance treatment.",
+      },
+      {
+        title: "Developer Handoff",
+        body: "Variables, missing facts, preview text, and implementation notes reduce back-and-forth between marketing and engineering.",
+      },
+      {
+        title: "Reviewable Boundaries",
+        body: "The tool flags unsubscribe, transactional-vs-marketing, accessibility, and rendering checks instead of pretending every email is safe to send.",
+      },
+      {
+        title: "Fast Iteration",
+        body: "A rough brief can become a first package quickly, then the Agent can revise structure, wording, and sections from follow-up instructions.",
+      },
+      {
+        title: "Useful Preview",
+        body: "HTML preview, source view, plain text, and handoff notes help users inspect the result before export.",
+      },
+    ],
+    boundary: "Supported Scenarios, Boundaries, And Recovery",
+    boundaryIntro:
+      "Marketing email and transactional email share delivery constraints, but they should not be written the same way. The generator keeps those differences visible.",
+    boundaryGroups: [
+      {
+        title: "Good Fit",
+        items: [
+          "Marketing newsletters, launch emails, promotional campaigns, onboarding and lifecycle nurture emails.",
+          "Common transactional templates such as verification codes, invoices, receipts, subscription confirmation, and account notifications.",
+          "Developer handoff packages for teams that want MJML source, HTML export, plain text, variables, and review notes.",
+        ],
+      },
+      {
+        title: "Needs Human Review",
+        items: [
+          "CAN-SPAM, GDPR/ePrivacy, CASL, unsubscribe links, sender identity, legal footer, claims, discounts, and sweepstakes language.",
+          "Deliverability-sensitive content such as cold outreach, regulated products, financial promises, medical claims, or high-risk promotions.",
+          "Brand-critical copy, localization, image assets, merge variables, and email service provider requirements.",
+        ],
+      },
+      {
+        title: "How To Recover",
+        items: [
+          "If the result is too generic, add real product value, user segment, offer, CTA, objections, and brand examples.",
+          "If the template feels too promotional, switch to a transactional scenario or ask the Agent to remove sales language.",
+          "If a merge field or link is missing, add the required variable name and regenerate through the revision box.",
+        ],
+      },
+    ],
+    supportVisualAlt: "Visual of campaign, verification code, receipt, and review email cards.",
+    guidance: "How To Use The Result",
+    guidanceIntro:
+      "Treat the generated package as a developer-ready starting point. Preview it, review the variables, then test it in your email service provider before sending.",
+    guidanceItems: [
+      "Start from MJML when editing layout, spacing, buttons, sections, or footer blocks.",
+      "Use the HTML export for preview, implementation review, or importing into systems that accept raw HTML.",
+      "Keep the plain-text version aligned with the core message and CTA so accessibility and deliverability do not become afterthoughts.",
+      "Before sending, test desktop and mobile rendering, unsubscribe and preference links, merge variables, preview text, sender identity, and tracking requirements.",
+    ],
+    exportVisualAlt: "Visual of an editable email draft, responsive preview, MJML source, and export folder.",
+    useCases: "Use cases",
+    useCaseItems: [
+      {
+        title: "Campaign And Launch Emails",
+        body: "Turn a product launch, feature update, seasonal offer, or newsletter brief into a first MJML package.",
+      },
+      {
+        title: "Lifecycle Marketing",
+        body: "Create activation, onboarding, upgrade, win-back, and retention emails that include clear CTA and follow-up notes.",
+      },
+      {
+        title: "Transactional Templates",
+        body: "Draft verification, invoice, receipt, subscription confirmation, and account notification emails without making them sound like ads.",
+      },
+      {
+        title: "Marketing-To-Dev Handoff",
+        body: "Give engineers MJML, HTML, variables, plain text, and review notes instead of a loose copy doc.",
+      },
+    ],
+    faq: "FAQ",
+    faqItems: [
+      {
+        question: "Does this generate HTML or MJML?",
+        answer:
+          "It generates both. MJML is treated as the editable source, while HTML is included for preview, import, and developer handoff.",
+      },
+      {
+        question: "Can it handle transactional emails?",
+        answer:
+          "Yes. It supports verification codes, invoices, receipts, subscription confirmations, and account notifications. These scenarios are kept more factual and less promotional.",
+      },
+      {
+        question: "Can I edit the result?",
+        answer:
+          "Yes. You can inspect sections and send revision instructions back to the Agent. The next version is written back as a new structured result.",
+      },
+      {
+        question: "Is the generated HTML ready to send?",
+        answer:
+          "It is a strong starting point, but you should test it in your email service provider and review unsubscribe, sender identity, claims, variables, and rendering before sending.",
+      },
+      {
+        question: "What information should I provide?",
+        answer:
+          "A product name, audience, scenario, goal, offer or trigger, brand tone, CTA, and must-include details are enough for a useful first version.",
+      },
+      {
+        question: "What if the result is too generic?",
+        answer:
+          "Add product proof, customer segment, objections, offer details, sender identity, variable names, and a clearer CTA, then regenerate through the revision box.",
+      },
+    ],
+    ctaTitle: "Keep Building The Launch System",
+    ctaPrimary: "Try product name generator",
+    ctaSecondary: "Back to all tools",
+    ctaHint:
+      "After your email template is ready, continue tightening the product name, launch copy, and handoff materials.",
+  },
+  widget: {
+    formTitle: "Build the first usable package",
+    formHint: "Fill the essentials first. Brand rules and must-include details can stay in advanced settings.",
+    productNameLabel: "Product name",
+    productNamePlaceholder: "e.g. Tomako Launch",
+    audienceLabel: "Audience",
+    audiencePlaceholder: "e.g. trial users who have not finished setup",
+    scenarioLabel: "Scenario",
+    toneLabel: "Tone",
+    languageLabel: "Language",
+    briefLabel: "Email brief",
+    briefPlaceholder:
+      "Describe the email goal, trigger, offer, audience context, key message, and what the user should do next.",
+    ctaLabel: "Primary CTA",
+    ctaPlaceholder: "e.g. Complete setup",
+    brandNotesLabel: "Brand and style notes",
+    brandNotesPlaceholder:
+      "Tone examples, brand rules, forbidden words, sender identity, colors, or existing email examples.",
+    mustIncludeLabel: "Must include",
+    mustIncludePlaceholder:
+      "Specific merge variables, links, disclaimers, footer requirements, offer details, or code placeholders.",
+    advancedTitle: "Advanced settings",
+    optional: "Optional",
+    generate: "Generate email template",
+    submitting: "Submitting request...",
+    running: "Generating package...",
+    retry: "Retry",
+    emptyTitle: "Your generated package will appear here",
+    emptyHint:
+      "The result includes HTML preview, MJML source, HTML, plain text, variables, review notes, and export actions.",
+    runningTitle: "The Agent is building your template package",
+    runningHint:
+      "It is writing MJML, matching HTML, plain text, variables, and review notes. Short result fetch delays are normal.",
+    previewInput: "Input",
+    previewOutput: "Output",
+    previewTitle: "Workspace preview",
+    previewHint: "The panel switches from brief preview to live generation and final HTML preview.",
+    previewDraft: "Draft",
+    previewReady: "Ready",
+    previewProductFallback: "Your product",
+    previewAudienceFallback: "Target audience",
+    previewBriefFallback:
+      "Describe the campaign, trigger, user context, key message, CTA, and required variables.",
+    previewItems: ["MJML source", "HTML preview", "Plain text", "Variables", "Review notes"],
+    previewFooter: "After generation, the full package appears below with source tabs, handoff notes, copy, download, and revision actions.",
+    resultReady: "Template package ready",
+    copyPackage: "Copy package",
+    downloadPackage: "Download package",
+    copied: "Copied",
+    tabs: {
+      preview: "Preview",
+      plain: "Plain text",
+      handoff: "Handoff",
+    },
+    htmlPreviewTitle: "Generated HTML email preview",
+    sectionsTitle: "Editable sections",
+    copyMjml: "Copy MJML",
+    downloadMjml: "Download MJML",
+    copyHtml: "Copy HTML",
+    downloadHtml: "Download HTML",
+    copyPlain: "Copy text",
+    downloadPlain: "Download TXT",
+    handoff: {
+      variables: "Variables",
+      compliance: "Compliance notes",
+      developer: "Developer notes",
+      accessibility: "Accessibility notes",
+      render: "Render checklist",
+      missing: "Missing information",
+      empty: "No items returned.",
+    },
+    revisionLabel: "Ask the Agent to revise",
+    revisionHint: "Use a specific change request",
+    revisionPlaceholder:
+      "Example: Make the hero shorter, change the CTA to book a demo, and add {{calendar_url}} as a variable.",
+    sendRevision: "Send revision",
+    status: {
+      PENDING: "Queued",
+      STREAMING: "Generating",
+      AWAITING_INPUT: "Waiting for structured result",
+      SUCCEEDED: "Finalizing result",
+      default: "Working",
+    },
+    errors: {
+      invalid: "Add a real product name, audience, and email brief. Placeholder or numeric input cannot produce a useful template.",
+      revision: "Write a specific revision instruction before sending it to the Agent.",
+      copy: "Copy failed. You can still select and copy the text manually.",
+      submit: "The request could not be submitted.",
+      task: "The generation task failed.",
+      timeout: "The structured result did not arrive in time.",
+      schema: "The Agent returned a result that did not match the email template schema.",
+      generic: "The template could not be generated.",
+      recover:
+        "Check the brief, try again, or add more concrete product, audience, CTA, and variable details.",
+    },
+    copy: {
+      scenarios: {
+        newsletter: "Newsletter",
+        productLaunch: "Product launch",
+        promoCampaign: "Promotion",
+        lifecycleNurture: "Lifecycle nurture",
+        verificationCode: "Verification code",
+        invoiceReceipt: "Invoice or receipt",
+        subscriptionConfirmation: "Subscription confirmation",
+        accountNotification: "Account notification",
+      },
+      tones: {
+        clear: "Clear",
+        friendly: "Friendly",
+        premium: "Premium",
+        urgent: "Urgent",
+        minimal: "Minimal",
+        technical: "Technical",
+      },
+      languages: {
+        zh: "Chinese",
+        en: "English",
+      },
+    },
+  },
+};
+
+export default emailTemplateGenerator;

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

@@ -0,0 +1,69 @@
+/** Shared copy for package-driven tool widgets (archetype engine). */
+const engine = {
+  submit: "Generate",
+  submitting: "Submitting",
+  reset: "Reset",
+  advancedSettings: "More options",
+  copyMarkdown: "Copy Markdown",
+  copyValue: "Copy",
+  copied: "Copied",
+  taskId: "Task id: {taskId}",
+  resultReady: "Structured result",
+  pendingTitle: "Preparing the result",
+  pendingHint:
+    "Tomako reads the brief first, then returns a reviewable structured result. Keep this page open.",
+  invalidField: "Add real context here — placeholder or test text is blocked.",
+  modelLabel: "Model",
+  modelOptions: {
+    flash: "Flash · faster",
+    pro: "V4 Pro · stronger",
+  },
+  status: {
+    idle: "Waiting for input",
+    submitting: "Submitting",
+    running: "Tomako is generating",
+    awaitingResult: "Waiting for structured result",
+    done: "Result ready",
+    error: "Needs attention",
+  },
+  errors: {
+    validation: {
+      title: "Add real context",
+      body: "Required fields need specific input. Test text, numbers, and vague filler are blocked.",
+    },
+    authRequired: {
+      title: "Sign in required",
+      body: "Generation requires a Tomako account. Redirecting to sign-in; you will return to this tool afterward.",
+    },
+    submitFailed: {
+      title: "Task submission failed",
+      body: "The generation task was not created. Keep your input, retry later, or check the task service.",
+    },
+    taskFailed: {
+      title: "Generation task failed",
+      body: "The task failed and there is no structured result to display. Use the task id to inspect logs.",
+    },
+    resultTimeout: {
+      title: "Result wait timed out",
+      body: "The task may still be running, but the page did not receive a structured result within the wait window.",
+    },
+    wrongResultType: {
+      title: "Wrong result type",
+      body: "The backend returned a result for another tool, so the page will not display it as a success.",
+    },
+    invalidResultSchema: {
+      title: "Invalid result structure",
+      body: "The backend returned a result, but it did not match the page's renderable structure.",
+    },
+    resultWritebackMissing: {
+      title: "Missing writeback result",
+      body: "The task completed but no structured result was found. Check backend writeback and the API URL.",
+    },
+    computeFailed: {
+      title: "Could not process this input",
+      body: "This input combination could not be converted. Check the values and try again.",
+    },
+  },
+} as const;
+
+export default engine;

package/src/i18n/messages/en/tools/gtm-readiness-checklist.ts

@@ -0,0 +1,166 @@
+const gtmReadinessChecklist = {
+  meta: {
+    title: "Go-to-Market Checklist for Launch",
+    description:
+      "Check nine launch-readiness items across positioning, channels, assets, and measurement. Turn the gaps into a focused pre-launch backlog before you promote.",
+    intro:
+      "Use this 9-point go-to-market checklist to find the launch gaps worth closing before you invest in outreach, content, or ads.",
+    category: "GTM Tools",
+    keywords: [
+      "go to market checklist",
+      "gtm readiness checklist",
+      "launch readiness checklist",
+      "product launch checklist",
+    ],
+  },
+  widget: {
+    howToUse: "Check each item. Unchecked rows become your next GTM sprint backlog.",
+    score: "Readiness score",
+    gaps: "Gaps to close",
+    allDone: "All items checked",
+    sections: {
+      positioning: "Positioning and audience",
+      channels: "Channels and assets",
+      metrics: "Measurement and iteration",
+    },
+  },
+  guide: {
+    workspaceTitle: "Check your GTM readiness before you promote",
+    workspaceHint:
+      "Mark what is true today. The score flags gaps to close; it does not guarantee a successful launch.",
+    workspaceBadge: "9 launch checks",
+    whatItChecksHeading: "What the 9 GTM readiness checks cover",
+    whatItChecksIntro:
+      "This is a focused pre-launch check, not a full go-to-market plan. Each group maps directly to the items above.",
+    whatItChecksItems: [
+      {
+        title: "Positioning and audience",
+        body: "Verify a one-line value proposition, a specific ICP scenario, and a clear difference from alternatives.",
+      },
+      {
+        title: "Channels and launch assets",
+        body: "Confirm one or two primary channels, a single landing-page CTA, and reusable promotion material.",
+      },
+      {
+        title: "Measurement and iteration",
+        body: "Define the stage metric, distinguish traffic sources, and schedule a review within two weeks of launch.",
+      },
+    ],
+    howToUseHeading: "Turn the score into your next launch decision",
+    howToUseIntro:
+      "The result is deliberately small: use it to decide which gap to close first, whether to run a limited test, or whether a bigger promotion should wait.",
+    howToUseSteps: [
+      "Mark only work you can verify today—not plans you hope to finish later.",
+      "Start with the unchecked positioning, channel, and measurement items; turn them into the next sprint's smallest concrete tasks.",
+      "Re-check before you expand promotion, then review source data and learnings within two weeks of launch.",
+    ],
+    scoreHeading: "How to read a GTM readiness score",
+    scoreIntro:
+      "The score summarizes completion across nine checks. It helps you choose the scope of your next move, not predict demand or revenue.",
+    scoreItems: [
+      {
+        title: "0–3 checks complete",
+        body: "Close positioning and ICP gaps before external promotion. A clearer message is more useful than adding more channels.",
+      },
+      {
+        title: "4–6 checks complete",
+        body: "Run a limited pilot on a primary channel while you finish the missing assets and measurement basics.",
+      },
+      {
+        title: "7–9 checks complete",
+        body: "Increase investment gradually, keep source tracking in place, and use the planned review to adapt the next cycle.",
+      },
+    ],
+    useCasesHeading: "When to use this launch-readiness checklist",
+    useCasesIntro:
+      "Use it at a decision point—not as a substitute for customer research, product QA, or a channel-specific launch plan.",
+    useCaseItems: [
+      "Before a first public launch, when the product is built but the message, channel focus, or measurement plan is still unclear.",
+      "Before paid ads or outbound, when you need to decide whether the landing page, promotion assets, and source tracking are ready.",
+      "Before a small channel experiment, when a founder and growth lead need one shared view of the launch gaps.",
+      "After an early launch, when you need to schedule a short review and turn what you learn into the next GTM sprint.",
+    ],
+    boundaryHeading: "What this checklist does not cover",
+    boundaryIntro:
+      "A checked box means that one planning condition is in place. It is not evidence that the product, market response, or channel execution is ready.",
+    boundaryGroups: [
+      {
+        title: "Still needs separate review",
+        items: [
+          "Product quality, security, legal or compliance requirements, and channel-specific policies.",
+          "Whether your positioning resonates with customers, not just whether it has been written down.",
+          "Creative quality, budget fit, and real results from a specific channel test.",
+        ],
+      },
+      {
+        title: "Why the score is still useful",
+        items: [
+          "It turns an unclear feeling of not being ready into visible, shared gaps.",
+          "It gives a small team a repeatable pre-launch discussion before more time or budget is committed.",
+          "It does not forecast customer demand, revenue, or the outcome of a launch.",
+        ],
+      },
+    ],
+    faqHeading: "Go-to-Market Checklist FAQs",
+    faqItems: [
+      {
+        question: "What is a go-to-market readiness checklist?",
+        answer:
+          "A go-to-market readiness checklist is a short pre-launch review of the conditions needed to promote a product responsibly. This one checks positioning, channels and launch assets, plus the measurement and review loop you need to learn after launch.",
+      },
+      {
+        question: "What are the nine GTM readiness checks?",
+        answer:
+          "The nine checks cover a one-line value proposition, a specific ICP, differentiation, one or two primary channels, a landing-page CTA, reusable promotion material, a stage metric, source tracking, and a post-launch review date.",
+      },
+      {
+        question: "What should I do with an early or pilot score?",
+        answer:
+          "With 0–3 checks complete, close positioning and ICP gaps before promotion. With 4–6 checks complete, keep the test small: use one primary channel while you finish missing assets and measurement. Turn the unchecked rows into concrete sprint tasks, then re-check.",
+      },
+      {
+        question: "Does a high GTM readiness score mean I should launch?",
+        answer:
+          "No. A high score means the nine planning conditions are in place. You still need product-quality, compliance, channel-policy, creative, and customer-response review before committing significant budget or treating a launch as successful.",
+      },
+      {
+        question: "Can I customize this go-to-market checklist?",
+        answer:
+          "This page keeps the nine shared checks fixed so that small teams can make a quick comparison. Add team- or launch-specific checks to your sprint backlog after you complete the common baseline.",
+      },
+      {
+        question: "Does this checklist send my answers to a server?",
+        answer:
+          "No. The score is calculated in the browser from the boxes you check on this page. No API call is needed to calculate the current readiness score.",
+      },
+    ],
+    ctaHeading: "Turn one readiness gap into a smaller first test",
+    ctaPrimary: "Re-check the 9 items",
+    ctaSecondary: "Choose a first channel",
+    ctaHint:
+      "After the basics are in place, choose one channel to test first—or return here after you close the gaps. Neither step replaces customer validation.",
+  },
+  items: {
+    positioning_one_liner: "One-sentence value proposition",
+    icp_specific: "ICP with concrete scenarios",
+    competitor_diff: "Clear differentiation vs alternatives",
+    primary_channels: "One to two primary channels",
+    landing_cta: "Landing page has a single primary CTA",
+    social_templates: "Reusable social or ad templates",
+    north_star_metric: "North-star or stage metric defined",
+    utm_tracking: "Traffic sources distinguishable",
+    retro_schedule: "Review scheduled within two weeks after launch",
+  },
+  tiers: {
+    early: "Close positioning and ICP gaps first",
+    pilot: "Ready for a limited pilot",
+    scale: "Ready to scale channel spend",
+  },
+  recommendations: {
+    early: "Finish positioning, ICP, and differentiation before external promotion.",
+    pilot: "Core assets and metrics are in place—test primary channels in a small scope.",
+    scale: "GTM fundamentals look solid—increase content output and channel investment.",
+  },
+} as const;
+
+export default gtmReadinessChecklist;

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

@@ -0,0 +1,73 @@
+import appIconResizer from "./app-icon-resizer";
+import appStoreScreenshotGenerator from "./app-store-screenshot-generator";
+import buildInPublicStoryGenerator from "./build-in-public-story-generator";
+import coldStartChannelSelector from "./cold-start-channel-selector";
+import commercialBpGenerator from "./commercial-bp-generator";
+import communityFeedbackInbox from "./community-feedback-inbox";
+import communityPainPointExtractor from "./community-pain-point-extractor";
+import communityPostRiskChecker from "./community-post-risk-checker";
+import competitorAnalysis from "./competitor-analysis";
+import emailTemplateGenerator from "./email-template-generator";
+import engine from "./engine";
+import gtmReadinessChecklist from "./gtm-readiness-checklist";
+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 ogImageGenerator from "./og-image-generator";
+import productAgreementGenerator from "./product-agreement-generator";
+import pitchDeckGenerator from "./pitch-deck-generator";
+import productHuntLaunchPlanner from "./product-hunt-launch-planner";
+import productNameGenerator from "./product-name-generator";
+import productPosterGenerator from "./product-poster-generator";
+import productUiGenerator from "./product-ui-generator";
+import redditPainPointFinder from "./reddit-pain-point-finder";
+import shared from "./shared";
+import socialListeningResearchReport from "./social-listening-research-report";
+import socialMediaProfileGenerator from "./social-media-profile-generator";
+import socialPlatformAssetAdapter from "./social-platform-asset-adapter";
+import socialProfileKit from "./social-profile-kit";
+import startupIdeaResearch from "./startup-idea-research";
+import tarotReading from "./tarot-reading";
+import twitterGifDownloader from "./twitter-gif-downloader";
+import userInterviewInsightReportGenerator from "./user-interview-insight-report-generator";
+import userInterviewRecordGenerator from "./user-interview-record-generator";
+
+const toolsPages = {
+  shared,
+  engine,
+  appIconResizer,
+  buildInPublicStoryGenerator,
+  coldStartChannelSelector,
+  commercialBpGenerator,
+  communityFeedbackInbox,
+  communityPainPointExtractor,
+  communityPostRiskChecker,
+  pitchDeckGenerator,
+  productNameGenerator,
+  productPosterGenerator,
+  productUiGenerator,
+  productAgreementGenerator,
+  productHuntLaunchPlanner,
+  emailTemplateGenerator,
+  competitorAnalysis,
+  redditPainPointFinder,
+  socialListeningResearchReport,
+  socialMediaProfileGenerator,
+  gtmReadinessChecklist,
+  kokoCodexAssistant,
+  logoGenerator,
+  marketForecastReport,
+  millionUserGrowthTest,
+  ogImageGenerator,
+  appStoreScreenshotGenerator,
+  twitterGifDownloader,
+  socialPlatformAssetAdapter,
+  socialProfileKit,
+  startupIdeaResearch,
+  tarotReading,
+  userInterviewInsightReportGenerator,
+  userInterviewRecordGenerator,
+} as const;
+
+export default toolsPages;