@tomako/tools-runtime 0.1.0

package/src/i18n/messages/en/tools/commercial-bp-generator.ts

@@ -0,0 +1,304 @@
+const commercialBpGenerator = {
+  meta: {
+    title: "AI Business Plan Deck Generator",
+    description: "Enter a product website or manual product context, then let an online Agent create a business plan outline, image-based deck pages, style direction, per-slide downloads, and a full package.",
+    intro: "Turn rough product context, brand constraints, audience, and go-to-market goals into an image-based business plan deck for fundraising, hiring, launches, and partnerships.",
+    category: "Commercial tools",
+    keywords: [
+      "AI business plan generator",
+      "pitch deck image generator",
+      "startup BP generator",
+      "business plan deck",
+    ],
+    inputSignal: "Product URL or brief, brand rules, deck purpose",
+    outputSignal: "Deck outline, image slides, sources, QA, download package",
+    boundarySignal: "Market data and in-image text need review",
+  },
+  guide: {
+    heroImageAlt: "Product context becoming a business plan outline, image slides, and a download package.",
+    workspaceHeading: "Tool workspace",
+    workspaceHint:
+      "Enter a product website or write the product context manually. The Agent returns the deck outline first, then generates image-based BP pages in order.",
+    workspaceBadge: "Image business plan deck",
+    outputs: "What you get",
+    outputsIntro:
+      "The output is not just business-plan prose. It is a reviewable, downloadable, revisable image deck production package.",
+    outputItems: [
+      {
+        title: "Deck outline",
+        body: "See the page list, core message, density, and visual role before the image generation queue starts.",
+      },
+      {
+        title: "Ordered image pages",
+        body: "Each slide appears as it is generated, while the front end preserves the intended order across batches.",
+      },
+      {
+        title: "Style direction",
+        body: "Pick one of three abstract visual directions, or skip selection and let the Agent choose from the product context.",
+      },
+      {
+        title: "Sources and QA",
+        body: "Market evidence, public sources, image-text risks, missing information, and review notes are returned separately.",
+      },
+      {
+        title: "Single-page downloads",
+        body: "Download each generated page for replacement, review, or reuse in another presentation flow.",
+      },
+      {
+        title: "Full package download",
+        body: "The final package supports batch download with recognizable product and slide names instead of random filenames.",
+      },
+    ],
+    pipelineVisualAlt: "A business plan production workflow with outline, sources, prompts, QA, and final image deck package.",
+    standards: "What a good BP generator should do",
+    standardsIntro:
+      "A useful BP Agent needs more than a filled template. It must coordinate narrative, evidence, brand consistency, image quality, and delivery rules.",
+    standardsItems: [
+      {
+        title: "Narrative before images",
+        body: "Clarify why the product exists, who needs it, why now, how it works, and who should join before producing pages.",
+      },
+      {
+        title: "Low page density",
+        body: "Each page should carry one core judgment. If the content is too much, split the page instead of shrinking type.",
+      },
+      {
+        title: "Brand constraints first",
+        body: "Product name, logo, banned terms, old names, IP rules, and visual constraints are locked into the brief.",
+      },
+      {
+        title: "Traceable evidence",
+        body: "Market, trend, and numeric claims need sources. Uncertain facts become QA notes rather than confident claims.",
+      },
+      {
+        title: "Progressive generation",
+        body: "The user sees the outline and current stage first, then image pages appear in batches with clear status.",
+      },
+      {
+        title: "Clear versioning",
+        body: "Final images, contact sheet, outline, sources, QA, and package links should all point to one authoritative version.",
+      },
+    ],
+    boundary: "Support, limits, and recovery",
+    boundaryIntro:
+      "A business plan can affect fundraising, hiring, and public commitments, so the output should be treated as a strong first draft, not an unreviewed final asset.",
+    boundaryGroups: [
+      {
+        title: "Good fit",
+        items: [
+          "Internet products, SaaS, AI agents, developer tools, consumer apps, platforms, and early-stage startup brands.",
+          "Fundraising decks, hiring decks, launch materials, partnership decks, and mixed-audience business narratives.",
+          "Brands with a website, product notes, brand rules, logo/IP references, audience definition, and commercial goals.",
+        ],
+      },
+      {
+        title: "Needs review",
+        items: [
+          "Funding amounts, financial forecasts, market sizing, user metrics, customer stories, competitor claims, and legal wording.",
+          "In-image text, numbers, sources, logos, mascot/IP details, banned terms, and old product names.",
+          "Disclosure level and wording differences between investor, hiring, launch, and partnership versions.",
+        ],
+      },
+      {
+        title: "How to recover",
+        items: [
+          "If the outline is generic, add audience, real product capabilities, stage, differentiation, and existing data.",
+          "If the visual system drifts, choose a style direction and add colors, logo rules, banned visuals, or references.",
+          "If market pages feel weak, add citable sources or ask the Agent to downgrade exact numbers into trend evidence.",
+        ],
+      },
+    ],
+    useCases: "Use cases",
+    useCaseItems: [
+      {
+        title: "Indie founder fundraising or hiring",
+        body: "Turn product progress and long-term vision into material investors, candidates, and supporters can understand.",
+      },
+      {
+        title: "Early-stage team communication",
+        body: "Create a discussable first version for pitches, partnerships, internal strategy reviews, and product introductions.",
+      },
+      {
+        title: "Internet product launches",
+        body: "Package positioning, pain points, timing, and commercialization path into image assets that are easier to share.",
+      },
+      {
+        title: "Accelerator or advisory workflows",
+        body: "Help teams with uneven starting points reach a decent BP baseline before focusing on evidence and story quality.",
+      },
+    ],
+    faq: "FAQ",
+    faqItems: [
+      {
+        question: "Why generate the outline before images?",
+        answer:
+          "The value of a BP starts with narrative order and page-level judgment. Direct image generation often creates nice pages that do not tell a clear story.",
+      },
+      {
+        question: "Can I only enter a product website?",
+        answer:
+          "Yes. URL mode can start from a website, but if the site is thin, the result will list missing information such as audience, commercial goals, brand rules, or data sources.",
+      },
+      {
+        question: "Are the style presets industry categories?",
+        answer:
+          "No. They are lower-level visual directions such as narrative impact, operating structure, and market mapping. They can apply across internet product categories.",
+      },
+      {
+        question: "Will it generate editable PPT?",
+        answer:
+          "This version is image-based. It does not promise HTML or editable PPT output yet, though the manifest can support future export flows.",
+      },
+      {
+        question: "Can the in-image text be used directly?",
+        answer:
+          "It needs review. Image models can alter words, numbers, or punctuation, especially for long text and market-data pages.",
+      },
+      {
+        question: "How are downloads named?",
+        answer:
+          "The Agent should return product, page index, and slide-topic based filenames such as tomako-business-bp-01-cover.png instead of random task IDs.",
+      },
+    ],
+    ctaTitle: "Keep building your go-to-market package",
+    ctaPrimary: "Plan a Product Hunt launch",
+    ctaSecondary: "Back to all tools",
+    ctaHint:
+      "After the BP is clear, continue with launch plans, store screenshots, social profiles, and campaign assets.",
+  },
+  widget: {
+    urlMode: "Use URL",
+    manualMode: "Write manually",
+    productUrlLabel: "Product website URL",
+    productUrlPlaceholder: "https://your-product.com",
+    productContextLabel: "Product context",
+    productContextPlaceholder:
+      "Describe product features, audience, stage, commercial goals, vision, evidence, brand rules, and who the BP should persuade.",
+    productNameLabel: "Product name",
+    productNamePlaceholder: "e.g. Tomako",
+    positioningLabel: "One-line positioning",
+    positioningPlaceholder: "e.g. An AI commercialization Agent platform for indie founders",
+    targetUsersLabel: "Target users",
+    targetUsersPlaceholder: "e.g. indie developers, solo operators, early-stage teams",
+    purposeLabel: "BP purpose",
+    densityLabel: "Density",
+    languageLabel: "Output language",
+    styleLabel: "Style direction",
+    styleHint: "Swipe horizontally, or skip it",
+    brandNotesLabel: "Brand, logo, IP, and visual rules",
+    brandNotesPlaceholder:
+      "Add colors, logo links, mascot rules, fonts, reference images, or visuals to avoid.",
+    referenceImagesLabel: "Reference and context images",
+    referenceImagesHint:
+      "PNG, JPG, or WebP. Up to 6 images; they are compressed before being sent to the Agent.",
+    referenceImagesButton: "Upload images",
+    referenceImagesEmpty: "No reference images uploaded yet",
+    referenceImagesPlaceholder:
+      "Upload logos, product screenshots, old BP pages, style references, or competitor screenshots.",
+    referenceImagesCount: "{count} / {max} images uploaded",
+    referenceImageMeta: "{width} x {height} · {size}",
+    removeReferenceImage: "Remove {name}",
+    mustIncludeLabel: "Must include",
+    mustIncludePlaceholder:
+      "Market data, team strengths, a feature, a user scenario, or a required page.",
+    mustAvoidLabel: "Must avoid",
+    mustAvoidPlaceholder:
+      "Old product names, wrong mascots, funding amounts, unconfirmed customers, or hype claims.",
+    optional: "Optional",
+    generate: "Generate BP deck",
+    submitting: "Submitting request...",
+    running: "Generating BP deck...",
+    retry: "Retry",
+    emptyTitle: "The BP outline and image pages will appear here",
+    emptyHint:
+      "You will see the page outline and thinking process first, then generated images appear in order. Final output supports single-page and package downloads.",
+    resultReady: "Business plan deck ready",
+    resultRunning: "Agent is generating the BP deck",
+    resultFallbackTitle: "Business plan deck in progress",
+    resultFallbackSummary:
+      "The Agent is organizing product context, narrative structure, visual direction, and the image generation queue.",
+    progressFallback: "Preparing the next slide batch",
+    outlineTitle: "Deck outline",
+    slidesTitle: "Image pages",
+    downloadAll: "Download full deck",
+    downloadManifest: "Download manifest",
+    downloadContactSheet: "Download contact sheet",
+    downloadSlide: "Download page",
+    workspaceVisualAlt: "A rough product brief becoming ordered business plan image pages and a download package.",
+    revisionLabel: "Ask the Agent to revise",
+    revisionHint: "Be specific",
+    revisionPlaceholder:
+      "For example: split market size into two pages, make the cover calmer, redraw page 6, and include the product name in every filename.",
+    sendRevision: "Send revision",
+    status: {
+      PENDING: "Queued",
+      STREAMING: "Generating",
+      AWAITING_INPUT: "Waiting for structured result",
+      AWAITING_FINAL: "Generating more image pages",
+      SUCCEEDED: "Finishing result",
+      default: "Processing",
+    },
+    slideStatus: {
+      queued: "Queued",
+      generating: "Generating",
+      ready: "Ready",
+      failed: "Failed",
+    },
+    errors: {
+      invalid:
+        "URL mode only needs a valid product website. Manual mode needs real product context, product name, positioning, and target users.",
+      revision: "Write a concrete revision instruction before sending it to the Agent.",
+      referenceImageType: "Only PNG, JPG, or WebP images are supported.",
+      referenceImageSize: "Each image must be under 8 MB.",
+      referenceImageLarge: "This image is still too large after compression. Use a smaller image.",
+      referenceImageRead: "Could not read this image. Please upload it again.",
+      referenceImageLimit: "You can upload up to 6 reference images.",
+      submit: "Request submission failed.",
+      task: "Generation task failed.",
+      timeout: "Structured result did not arrive in time.",
+      schema: "The Agent result does not match the BP schema.",
+      generic: "BP generation failed.",
+      recover:
+        "Check the product URL or add more product context, brand rules, audience, and required content before retrying.",
+    },
+    copy: {
+      purposes: {
+        fundraising: "Fundraising",
+        recruiting: "Hiring",
+        launch: "Launch",
+        partnership: "Partnership",
+        strategy: "Strategy",
+        combined: "Combined",
+      },
+      languages: {
+        zh: "Chinese",
+        en: "English",
+      },
+      densities: {
+        lean: "Lean",
+        standard: "Standard",
+        complete: "Complete",
+      },
+      styles: {
+        none: {
+          name: "No preset",
+          summary: "Let the Agent choose based on product, audience, and brand rules.",
+        },
+        signalEditorial: {
+          name: "Signal Editorial",
+          summary: "More belief, emotion, shareability, photography, and breathing room.",
+        },
+        operatorGrid: {
+          name: "Operator Grid",
+          summary: "More workflows, metrics, product systems, and execution clarity.",
+        },
+        marketAtlas: {
+          name: "Market Atlas",
+          summary: "More ecosystem, growth, market evidence, and business structure.",
+        },
+      },
+    },
+  },
+};
+
+export default commercialBpGenerator;

package/src/i18n/messages/en/tools/community-feedback-inbox.ts

@@ -0,0 +1,218 @@
+const communityFeedbackInbox = {
+  meta: {
+    title: "Community Feedback Inbox",
+    description: "Paste Reddit, Indie Hackers, Product Hunt, or X comments and turn scattered community feedback into pain points, objections, competitor signals, feature requests, beta invite leads, build-in-public material, backlog candidates, and landing page FAQ.",
+    intro: "Turn post-launch comments, DMs, and trial feedback into a learning system: classify user language, find beta invite candidates, capture backlog evidence, and turn objections into landing page copy.",
+    category: "User feedback tools",
+    keywords: [
+      "community feedback inbox",
+      "Reddit product feedback analyzer",
+      "build in public feedback organizer",
+      "customer feedback categorizer",
+      "product feedback to roadmap tool",
+    ],
+    inputSignal: "Community comments + product context",
+    outputSignal: "Feedback clusters + beta leads + content/backlog assets",
+    boundarySignal: "Review prototype; local heuristic analysis, no scraping or user messaging",
+  },
+  examples: [
+    {
+      label: "Reddit launch comments",
+      input: "Product: a GTM learning tool for indie founders. Comments include pricing doubts, comparisons with Canny and Notion, export requests, and beta interest.",
+      expectedOutput: "Pain, objection, competitor, feature, pricing, and copy clusters plus beta invite leads, build-in-public angles, backlog candidates, and FAQ drafts.",
+    },
+  ],
+  guide: {
+    heroVisualAlt:
+      "A workspace where scattered community comments become feedback clusters, beta leads, content material, and product backlog evidence.",
+    workspaceHeading: "Turn community comments into growth learning assets",
+    workspaceHint:
+      "Paste Reddit, Indie Hackers, Product Hunt, X, or Discord comments. This review prototype classifies feedback into pain points, objections, competitors, feature requests, pricing feedback, and copy feedback, then suggests reviewable next steps.",
+    workspaceBadge: "Review prototype",
+    workspaceVisualAlt:
+      "Scattered community feedback turning from loose paper notes into a report with signal clusters, beta candidates, content, and backlog tabs.",
+    outputs: "What you get",
+    outputItems: [
+      {
+        title: "Feedback clusters",
+        body: "Classify comments into pain points, objections, competitors, feature requests, pricing feedback, and copy feedback with evidence snippets.",
+      },
+      {
+        title: "Beta invite shortlist",
+        body: "Flag people who show a clear workflow, trial intent, or useful follow-up question, with an editable DM draft.",
+      },
+      {
+        title: "Build-in-public material",
+        body: "Turn high-quality comments into the angle, hook, and user language for the next public building post.",
+      },
+      {
+        title: "Backlog and FAQ candidates",
+        body: "Convert repeated feedback into backlog hypotheses, landing page FAQ, and objection-handling material.",
+      },
+    ],
+    supportHeading: "For learning after a post, not just counting exposure",
+    supportVisualAlt:
+      "Community comments, DMs, and trial feedback organized into product learning assets.",
+    supportItems: [
+      "Useful for indie founders, early SaaS teams, developer tools, AI tools, open-source brands, and build-in-public creators.",
+      "Best for post-launch comments, DMs, trial feedback, Product Hunt comments, Reddit discussions, and Indie Hackers replies.",
+      "This is not a public voting board. It turns real community language into the next product and GTM decision.",
+      "If comments include usernames or sources, beta leads become more useful. Anonymous comments can still be clustered.",
+    ],
+    boundaryHeading: "This version intentionally avoids scraping and auto-DMs",
+    boundaryVisualAlt:
+      "A community feedback analysis workspace with manual boundaries and privacy review markers.",
+    boundaryItems: [
+      "It does not connect to Reddit, Indie Hackers, Product Hunt, X, or Discord APIs, and does not bypass platform rules.",
+      "It does not message users automatically. Beta invites are candidate leads and drafts for manual judgment.",
+      "Classification uses local heuristics, not a formal AI research result. Review original comments before adding backlog items.",
+      "Before publishing build-in-public content, remove usernames, private details, and anything that could misquote a user.",
+    ],
+    resultUseHeading: "Connect the result to Tomako's GTM workflow",
+    resultUseVisualAlt:
+      "Community feedback flowing into build-in-public posts, landing page FAQ, beta invites, and backlog.",
+    resultUseItems: [
+      "Send content angles to the Social Platform Asset Adapter and rewrite them for X, LinkedIn, Reddit, or Product Hunt follow-up.",
+      "Turn high-signal beta candidates into a manual DM list. Ask about the workflow before inviting them to try the beta.",
+      "Move objections into landing page FAQ and comment replies instead of leaving them in internal notes.",
+      "Write repeated feedback as a hypothesis, evidence count, and acceptance criteria before adding it to backlog.",
+    ],
+    whyTomakoHeading: "Why not just use a spreadsheet or feedback board",
+    whyTomakoItems: [
+      {
+        title: "Built around the post-feedback loop",
+        body: "Classic feedback boards focus on collection and voting. This tool focuses on turning community comments into content, beta users, and the next validation loop.",
+      },
+      {
+        title: "Keeps the original language",
+        body: "The result includes evidence snippets, so you can return to the source instead of prioritizing from vague tags.",
+      },
+      {
+        title: "Turns objections into assets",
+        body: "When users are confused, concerned, or comparing alternatives, that language becomes FAQ, reply, and landing page material.",
+      },
+      {
+        title: "Avoids over-automation",
+        body: "Community growth breaks when real conversations become bulk workflows. Tomako organizes signals while keeping DMs and product decisions human.",
+      },
+    ],
+    standardHeading: "A good community feedback tool helps you judge, not blindly obey",
+    standardVisualAlt:
+      "Community feedback split into evidence, priority, human review, and next actions.",
+    standardItems: [
+      "Evidence: every cluster should point back to original comments, not just abstract labels.",
+      "Restraint: feature requests should be merged and validated before entering a roadmap.",
+      "Actionability: results should become beta invites, FAQ, content angles, or backlog hypotheses.",
+      "Boundaries: the tool should be clear about no scraping, no auto-DM, and no replacement for product judgment.",
+      "Workflow: community feedback should return to GTM instead of staying as one-time exposure data.",
+    ],
+    faq: "Frequently asked questions",
+    faqItems: [
+      {
+        question: "Does this tool scrape Reddit or Indie Hackers automatically?",
+        answer:
+          "No. The current version only processes comments you paste manually, which keeps platform rules, login access, and privacy boundaries clearer.",
+      },
+      {
+        question: "How is this different from Canny, Productboard, or Featurebase?",
+        answer:
+          "Those products are stronger for long-running feedback portals, roadmaps, and voting. This tool is lighter and focuses on turning community launch comments into GTM learning assets.",
+      },
+      {
+        question: "Can I put these results directly into backlog?",
+        answer:
+          "Not directly. The report gives candidates, evidence counts, and next actions, but you should still review original comments and product strategy.",
+      },
+      {
+        question: "Can this help invite beta users?",
+        answer:
+          "Yes, as a shortlist. Final outreach should stay manual, especially to avoid mass-DM behavior.",
+      },
+    ],
+    ctaHint:
+      "After organizing community feedback, turn one high-quality comment into a user interview record or rewrite the content angles for platform-specific follow-up.",
+    ctaPrimary: "Structure one user interview",
+    ctaSecondary: "Adapt follow-up content",
+  },
+  widget: {
+    formTitle: "Feedback brief",
+    formHint:
+      "Paste real comments and keep usernames or source context when possible. The more specific the input, the more useful the beta leads, FAQ, and backlog candidates become.",
+    productNameLabel: "Product name",
+    productNamePlaceholder: "Tomako",
+    sourceLabel: "Main source",
+    productContextLabel: "Product context",
+    productContextPlaceholder:
+      "Tomako helps indie founders turn product launches, community feedback, and growth actions into an executable GTM workflow.",
+    commentsLabel: "Paste comments, DMs, or trial feedback",
+    commentsPlaceholder:
+      "@founder42: I like the idea, but I already use Notion and Canny. How is this different?\n\n@maker_jane: Would love export to Linear. I would try the beta if it handles Reddit comments.\n\nanonymous: Pricing as a subscription makes me hesitate unless it helps me update the landing page directly.",
+    goalLabel: "Goal for this pass",
+    generate: "Organize feedback",
+    status: {
+      idle: "Waiting for comments",
+      done: "Feedback organized",
+      error: "Needs clearer input",
+    },
+    previewItems: [
+      "Comments",
+      "Signals",
+      "Beta",
+      "The main feedback theme will appear here",
+      "The strongest evidence comment will appear here",
+      "The report will suggest the next GTM action",
+    ],
+    sources: {
+      mixed: "Mixed sources",
+      reddit: "Reddit",
+      indieHackers: "Indie Hackers",
+      hackerNews: "Hacker News",
+      productHunt: "Product Hunt",
+      x: "X",
+      discord: "Discord",
+    },
+    goals: {
+      launchLearning: "Post-launch learning",
+      betaRecruiting: "Invite beta users",
+      roadmap: "Organize product backlog",
+      landingPage: "Improve landing page / FAQ",
+    },
+    errors: {
+      validation: {
+        title: "Add the minimum feedback brief first",
+        body: "Add product context and at least two specific comments so the tool can create useful clusters, beta candidates, and next actions.",
+      },
+      weakInput: {
+        title: "Paste more realistic community feedback",
+        body: "The current input looks like placeholder text, too-short text, or a single comment. Paste at least two comments and keep the user's context when possible.",
+      },
+    },
+    resultReady: "Community feedback learning report generated",
+    copied: "Copied",
+    copy: "Copy Markdown",
+    download: "Download",
+    reset: "Reset",
+    totalComments: "Comments",
+    highSignals: "High signals",
+    betaCandidates: "Beta leads",
+    categories: "Feedback clusters",
+    signalCount: "{count} signals",
+    inviteShortlist: "Beta invite shortlist",
+    emptyInvite:
+      "No strong beta candidate yet. Add usernames, trial intent, or specific workflow context.",
+    contentAngles: "Build-in-public material",
+    backlog: "Backlog candidates",
+    faq: "Landing page FAQ candidates",
+    objections: "Objection handling",
+    emptyObjections:
+      "No clear objections yet. Comments about confusion, concern, or alternatives are especially useful here.",
+    reviewChecklist: "Missing info and human review",
+    confidence: {
+      low: "Low evidence",
+      medium: "Medium evidence",
+      high: "High evidence",
+    },
+  },
+} as const;
+
+export default communityFeedbackInbox;