@tomako/tools-runtime 0.1.0

package/src/i18n/messages/en/tools/app-store-screenshot-generator.ts

@@ -0,0 +1,145 @@
+const appStoreScreenshotGenerator = {
+  meta: {
+    title: "App Store Screenshot Generator",
+    displayTitle: "App Store Screenshot Generator",
+    description:
+      "Upload UI screenshots, add product context when useful, and generate App Store or Google Play listing images as a complete review-ready set.",
+    intro: "Create a coherent screenshot set, feature graphic direction, and benefit-led listing visuals with product context before checking the latest store rules.",
+    category: "ASO tools",
+    keywords: [
+      "app store screenshot generator",
+      "Google Play screenshots",
+      "App Store listing images",
+      "ASO creatives",
+    ],
+  },
+  guide: {
+    heroVisualAlt:
+      "Hero visual for an app store listing image generator, showing a complete app store screenshot set.",
+    workspaceHeading: "Upload UI screenshots to generate listing images",
+    workspaceHint:
+      "Upload real UI screenshots. A cloud Agent uses Skills-OL to fetch supporting context, plan the complete set, and submit live image tasks.",
+    whatYouGetHeading: "What you get after generation",
+    valueVisualAlt:
+      "App store listing image export bundle with phone screenshots, a feature graphic, PNG files, and SVG files.",
+    whatYouGetItems: [
+      {
+        title: "Platform-shaped image set",
+        body: "Generate up to 10 App Store screenshots, or a Google Play feature graphic plus up to 8 phone screenshots, so you can judge the full set early.",
+      },
+      {
+        title: "Downloadable PNG",
+        body: "Select one listing image and download a PNG for team review, store console upload, or design critique.",
+      },
+      {
+        title: "Handoff SVG wrapper",
+        body: "Download an SVG wrapper that preserves the generated image, dimensions, and prompt metadata for review and design polish.",
+      },
+      {
+        title: "Clear source boundary",
+        body: "UI screenshots are required visual source material. A URL is optional brief input for public context, so avoid private data or unauthorized brands in screenshots.",
+      },
+      {
+        title: "Recoverable failure hints",
+        body: "Missing URLs, missing screenshots, unsupported file types, and export failures return actionable messages instead of empty creatives.",
+      },
+    ],
+    comparisonHeading: "What a good app store screenshot generator should do",
+    comparisonItems: [
+      {
+        standard: "Clear dimensions",
+        manual: "Manual templates often reuse one composition across App Store portraits, Google Play phone shots, and feature graphics.",
+        tomako: "Tomako starts with the selected platform and layout, so you can see how each asset shape changes the composition.",
+      },
+      {
+        standard: "Fast exploration",
+        manual: "Starting from blank artboards makes every headline, size, and visual direction feel expensive to test.",
+        tomako: "Real UI screenshots are enough to produce a first creative set grounded in the actual interface, so teams can filter direction before design polish.",
+      },
+      {
+        standard: "Editable output",
+        manual: "Many generators only export flat PNGs, making later copy, color, or screenshot changes awkward.",
+        tomako: "Each live image result can be downloaded as PNG, with an SVG wrapper carrying image and prompt metadata for design handoff.",
+      },
+      {
+        standard: "Trustworthy limits",
+        manual: "Some tools imply generated assets are ready for store approval and skip policy, privacy, trademark, or sizing risk.",
+        tomako: "The page and result guidance state that final platform and brand review is still required.",
+      },
+      {
+        standard: "Safer assets",
+        manual: "Uploading unreleased product screenshots to unknown tools makes it hard to reason about file handling.",
+        tomako: "This page states when screenshots are sent to the image task, so teams can remove private or unlicensed content before generation.",
+      },
+    ],
+    supportHeading: "Supported inputs and failure boundaries",
+    supportVisualAlt:
+      "Support boundary visual for app store listing images, showing phone images, a feature graphic, privacy marker, and review checklist.",
+    supportBody: [
+      "You must upload local UI screenshots. Product URL, App Store or Google Play links, product name, and selling points provide supporting context for title, description, and page-summary clues.",
+      "Apple App Store and Google Play directions are supported, including complete screenshot sets, portrait screenshots, and feature graphics.",
+      "This version uses a cloud Agent and Skills-OL to submit live image tasks, but it does not connect to App Store Connect or Google Play Console.",
+      "If a screenshot includes test accounts, real users, private data, or unauthorized brands, redact it before use.",
+      "If no result appears, check that the URL is not empty, the uploaded file is PNG/JPG/WebP, browser file reading is allowed, and the selected input source matches your data.",
+      "Before real submission, review the latest platform dimensions, review policies, trademark or copyright permissions, privacy content, copy claims, and readability on target devices.",
+    ],
+    resultGuidanceHeading: "How to use the downloaded listing images",
+    useCaseVisualAlt:
+      "Product and design team arranging app store listing assets, screenshot boards, feature graphics, colors, and export folders.",
+    resultGuidanceBody: [
+      "Use PNG as a direction image or review image. First confirm whether the first screenshot explains the core user benefit clearly.",
+      "Hand the SVG wrapper to a designer when the team needs prompt traceability, final product screens, brand fonts, store whitespace, or localized variants.",
+      "Do not blindly reuse one image across App Store and Google Play. Portrait screenshots, iPad shots, and feature graphics need separate composition checks.",
+      "If a generated image feels crowded, remove small labels, secondary features, and long subheadlines before adding more decoration.",
+      "Before uploading to a real store console, check the latest official specs and review guidance for size, content, privacy, trademark, copyright, and exaggerated claims.",
+    ],
+    useCasesHeading: "Use cases",
+    useCaseItems: [
+      "Indie builders preparing first App Store or Google Play listing assets and needing a fast visual direction.",
+      "Growth teams comparing ASO screenshot, benefit-led creative, and feature graphic styles before launch.",
+      "Product teams turning new-version UI screenshots into store update assets for release planning or campaign review.",
+      "Designers receiving a rough product brief and generating a low-fidelity direction before final artboards.",
+      "Remote or outsourced teams aligning on copy, composition, and brand colors with PNG/SVG files.",
+      "Launch teams checking whether app icons, store screenshots, and social assets use the same visual language.",
+    ],
+    faqHeading: "FAQ",
+    faqItems: [
+      {
+        question: "Does this tool crawl the product URL automatically?",
+        answer:
+          "It fetches public title, description, OG metadata, headings, and a short page summary to infer product benefits and screenshot copy. Logged-in, blocked, or anti-scraping pages may fail.",
+      },
+      {
+        question: "Are uploaded UI screenshots stored on a server?",
+        answer:
+          "When UI screenshot mode is selected, the screenshot is sent to the image task as a reference. Do not upload real user data, unredacted admin screens, customer information, or unauthorized brand assets.",
+      },
+      {
+        question: "Can the generated PNG go straight into App Store or Google Play?",
+        answer:
+          "It can be used for upload preview or team review, but before publishing you still need to check the latest platform dimensions, content policy, privacy, trademark, and copyright requirements.",
+      },
+      {
+        question: "Why export SVG as well as PNG?",
+        answer:
+          "The SVG is a handoff wrapper for the generated image. It preserves the image reference, dimensions, and prompt metadata so a designer can review and refine the direction.",
+      },
+      {
+        question: "Can I use it without a real product screenshot?",
+        answer:
+          "No. Upload real UI screenshots first. Product URL or product name can add context, but cannot replace real product screens.",
+      },
+      {
+        question: "Does this check the latest store review rules?",
+        answer:
+          "No. It generates visual results and does not connect to App Store Connect, Google Play Console, or live policy APIs. Review official store guidance before submission.",
+      },
+    ],
+    ctaPrimary: "Prepare App Icons",
+    ctaSecondary: "Back to all tools",
+    ctaHint:
+      "Store screenshots are usually reviewed together with the app icon. If the icon package is not ready yet, prepare app icon assets first and keep the listing visuals consistent.",
+  },
+} as const;
+
+export default appStoreScreenshotGenerator;

package/src/i18n/messages/en/tools/build-in-public-story-generator.ts

@@ -0,0 +1,229 @@
+const buildInPublicStoryGenerator = {
+  meta: {
+    title: "Build-in-Public Story Generator",
+    description: "Enter this week's product progress, GTM assumptions, signals, and feedback ask to generate transparent build-in-public drafts for Indie Hackers, Reddit, X, and LinkedIn.",
+    intro: "Turn real Tomako GTM progress into community-acceptable public storytelling: stage, assumption, action, signal, uncertainty, and feedback ask instead of promotional copy.",
+    category: "Community growth tools",
+    keywords: [
+      "build in public story generator",
+      "build in public post generator",
+      "build in public twitter thread",
+      "build in public reddit post",
+      "Indie Hackers post template",
+      "founder progress update",
+    ],
+    inputSignal: "Stage + progress + GTM hypothesis + signal",
+    outputSignal: "Platform drafts + authenticity review",
+    boundarySignal: "Review prototype; no auto-posting or growth promise",
+  },
+  examples: [
+    {
+      label: "GTM hypothesis update",
+      input: "Product: Tomako; stage: beta; this week tested whether Reddit and Indie Hackers are better for early feedback; signal: 3 founders replied that channel choice hurts more than post copy.",
+      expectedOutput: "Indie Hackers long post, Reddit discussion post, X thread, LinkedIn update, plus promo-risk, evidence-gap, and public-boundary checks.",
+    },
+  ],
+  guide: {
+    heroVisualAlt:
+      "Founder progress, GTM assumptions, metrics, and open questions organized into transparent community story material.",
+    workspaceHeading: "Generate transparent build-in-public updates with evidence and questions",
+    workspaceHint:
+      "Enter your product stage, weekly progress, Tomako GTM hypothesis, current signals, and feedback ask. The prototype returns platform drafts plus an authenticity review.",
+    workspaceBadge: "Review prototype",
+    outputs: "What you get from the generator",
+    outputItems: [
+      {
+        title: "Story angle",
+        body: "Decide whether this week should lead with stage, assumption, experiment, signal, or uncertainty instead of packaging learning as success.",
+      },
+      {
+        title: "Four platform drafts",
+        body: "Generate an Indie Hackers long post, Reddit discussion post, X thread, and LinkedIn progress update from the same material.",
+      },
+      {
+        title: "Authenticity review",
+        body: "Flag promotional language, evidence gaps, oversharing risk, and community-contract issues before you post.",
+      },
+      {
+        title: "Sharper feedback ask",
+        body: "Turn vague asks into a specific question the community can actually respond to.",
+      },
+    ],
+    supportHeading: "Use it for public learning notes, not generic social posts",
+    supportVisualAlt:
+      "Product progress, assumptions, and signals becoming a clear public learning note.",
+    supportItems: [
+      "Useful for indie makers, early SaaS teams, developer tools, AI products, and small teams validating GTM channels.",
+      "Especially useful after Tomako has produced channel choices, launch plans, or growth assumptions and you need to explain the learning publicly.",
+      "The input can be rough, but it needs real progress and a real feedback question. Otherwise the output will sound like promotion.",
+      "The result is a draft and review aid. It does not auto-post, guarantee acquisition, or replace community judgment.",
+    ],
+    platformHeading: "Same source material, different community contracts",
+    platformVisualAlt:
+      "One build-in-public source story adapted into a long post, discussion post, and thread.",
+    platformItems: [
+      "Indie Hackers can carry the full context: background, assumption, numbers, learning, and a founder ask.",
+      "Reddit needs less promotion, the question near the top, and a clear reason the post is asking for judgment.",
+      "X threads should break the story into stage, action, signal, and uncertainty, not slogans.",
+      "LinkedIn can emphasize decision quality and learning, but it should not read like a company announcement.",
+    ],
+    boundaryHeading: "Check what should not be public before posting",
+    boundaryVisualAlt:
+      "A public post review sheet with flags for promotional wording, missing proof, and sensitive information.",
+    boundaryItems: [
+      "Do not reveal customer names, sensitive revenue, private roadmap, private community screenshots, or identifiable user feedback.",
+      "Metrics can be shared as ranges, relative movement, or sample sizes. If you do not have data, say it is a qualitative signal.",
+      "Tomako's GTM strategy should be framed as an input to your hypothesis, not as validated market truth.",
+      "If the ending is only a signup link or heavy CTA, it stops being build-in-public and becomes an ad.",
+    ],
+    whyTomakoHeading: "Why this belongs in Tomako instead of a generic post generator",
+    whyTomakoItems: [
+      {
+        title: "It starts from GTM assumptions",
+        body: "Generic tools ask for platform and tone. This asks for stage, channel hypothesis, signal, and uncertainty.",
+      },
+      {
+        title: "It preserves open questions",
+        body: "Good build-in-public writing is not perfectly polished. It shows what you are still trying to learn.",
+      },
+      {
+        title: "It adapts the social contract",
+        body: "Reddit, Indie Hackers, X, and LinkedIn do not accept the same framing with different lengths.",
+      },
+      {
+        title: "It reviews before publishing",
+        body: "The result flags copy that feels promotional, claims without evidence, and details that should stay private.",
+      },
+    ],
+    reviewHeading: "Treat the result as a pre-publish review sheet",
+    reviewVisualAlt:
+      "A public story draft with evidence, risk, and feedback-question review markers.",
+    reviewItems: [
+      "Remove absolute conclusions that do not have evidence.",
+      "Keep at least one failure, hesitation, or unresolved question.",
+      "Separate metrics, user feedback, and Tomako assumptions instead of blending them into promo copy.",
+      "Review the Reddit version especially hard for self-promotion tone.",
+      "Before copying, confirm which numbers, customers, roadmap items, and internal decisions should stay private.",
+    ],
+    standardHeading: "A good build-in-public tool should be specific and restrained",
+    standardVisualAlt:
+      "A transparent public progress post standard card with stage, signal, and question markers.",
+    standardItems: [
+      "Quality: output should have a real story structure, not product claims rewritten in social tone.",
+      "Trust: it should distinguish facts, assumptions, metrics, qualitative signals, and unresolved questions.",
+      "Ease of use: the first version should need only stage, weekly progress, and a feedback ask, not a complete growth report.",
+      "Platform fit: platform drafts should change the social contract, not only the character count.",
+      "Safety: it should warn about oversharing, customer privacy, roadmap leaks, and self-promotion risk.",
+    ],
+    faq: "FAQ",
+    faqItems: [
+      {
+        question: "Does this post to X, Reddit, or LinkedIn for me?",
+        answer:
+          "No. It creates drafts and a review checklist. You still edit manually and post according to each community's rules.",
+      },
+      {
+        question: "Can I use it without real metrics?",
+        answer:
+          "Yes, but the post should say it is a qualitative observation or unvalidated hypothesis. Do not invent momentum.",
+      },
+      {
+        question: "How is this different from a normal AI post generator?",
+        answer:
+          "Normal tools usually start from platform and tone. This starts from stage, GTM hypothesis, evidence, what worked or did not, and the feedback question.",
+      },
+      {
+        question: "Is this review version connected to a live Agent?",
+        answer:
+          "Not yet. This is a deterministic frontend prototype to validate the interaction and output structure. Before publishing, the team should decide whether to upgrade it to Agent/Skill Result output.",
+      },
+    ],
+    ctaHint:
+      "If you do not have a public GTM hypothesis yet, compare cold-start channels first. If you already have rough social copy, adapt it to each platform next.",
+    ctaPrimary: "Adapt existing social assets",
+    ctaSecondary: "Choose cold-start channels",
+  },
+  widget: {
+    formTitle: "Public progress brief",
+    formHint:
+      "Use real progress, not only product claims. The output keeps uncertainty and evidence gaps visible so the post reads like a learning note.",
+    productNameLabel: "Product name",
+    productNamePlaceholder: "Tomako",
+    stageLabel: "Current stage",
+    productContextLabel: "Product context",
+    productContextPlaceholder:
+      "Tomako is an AI GTM OS for indie makers that turns product context into channel strategy, launch assets, and growth actions.",
+    thisWeekLabel: "What actually happened this week",
+    thisWeekPlaceholder:
+      "Example: We used Tomako to rank cold-start channels and learned that Reddit is better for asking a specific judgment question, while Product Hunt is not ready yet.",
+    feedbackAskLabel: "What do you want feedback on this week?",
+    feedbackAskPlaceholder:
+      "Example: Should an early tool position as a GTM workspace, or as a set of sharper launch tools?",
+    advancedTitle: "Add GTM strategy, signals, and public boundaries",
+    gtmStrategyLabel: "GTM hypothesis from Tomako",
+    gtmStrategyPlaceholder:
+      "Example: Prioritize Reddit and Indie Hackers for feedback quality, delay Product Hunt, and use public learning posts to test positioning.",
+    metricsLabel: "Metrics or signals",
+    metricsPlaceholder:
+      "Example: 3 founders replied that channel choice hurts more than copy generation; 1 Reddit-style draft felt too self-promotional.",
+    uncertaintyLabel: "What is still uncertain",
+    uncertaintyPlaceholder:
+      "Example: Not sure whether build-in-public is an acquisition channel or mainly a trust and learning mechanism.",
+    boundaryLabel: "Public boundary",
+    generate: "Generate public story drafts",
+    status: {
+      idle: "Draft preview",
+      done: "Story ready",
+      error: "Needs better input",
+    },
+    previewItems: [
+      "Indie Hackers, Reddit, X, and LinkedIn drafts",
+      "Promo tone, evidence gap, and public-risk review",
+      "Copyable Markdown export",
+    ],
+    workspaceVisualAlt:
+      "Rough progress notes, evidence signals, and feedback questions organized into public build-in-public drafts.",
+    stages: {
+      idea: "Idea validation",
+      prototype: "Prototype validation",
+      beta: "Beta testing",
+      launched: "Early launched version",
+      postLaunch: "Post-launch learning",
+    },
+    boundaries: {
+      open: "Share stage and non-sensitive metrics directly",
+      blurMetrics: "Use ranges or relative movement for metrics",
+      avoidRoadmap: "Do not reveal unreleased roadmap",
+      customerSafe: "Anonymize all customer and user feedback",
+    },
+    channels: {
+      indieHackers: "Indie Hackers",
+      reddit: "Reddit",
+      xThread: "X Thread",
+      linkedin: "LinkedIn",
+    },
+    errors: {
+      validation: {
+        title: "Add the minimum public progress brief",
+        body: "Product name, product context, real weekly progress, and a specific feedback ask are required.",
+      },
+      weakInput: {
+        title: "Use real progress, not placeholder text",
+        body: "The input is too short or looks like a test. Add what you did, what signal you saw, and what is still uncertain.",
+      },
+    },
+    resultReady: "Generated public story pack",
+    copied: "Copied",
+    copy: "Copy Markdown",
+    download: "Download",
+    reset: "Reset",
+    primaryRisk: "Primary posting risk",
+    recommendedLead: "Recommended lead",
+    evidenceGaps: "Evidence gaps",
+    authenticityIssues: "Authenticity review",
+    communityFit: "Community fit principles",
+    reviewChecklist: "Pre-publish review",
+  },
+} as const;
+
+export default buildInPublicStoryGenerator;