根据本地外链 JSON 队列或批次队列，把当前项目发布到免费外链、目录、startup listing、AI tools 和 gallery 平台。用于需要 Codex 使用 @chrome 操作用户已登录的 Chrome、读取项目资料夹、按单个 JSON 或 30 条左右的 batch JSON 逐组处理、通过 subagent 调用 $humanizer 生成自然文案、填写平台提交表单、直接提交免费 listing 并更新队列状态的任务。
使用 Firecrawl 根据用户提供的项目落地页或产品 URL 抓取并保存本地项目资料文件夹。用于需要 Codex 获取网站摘要、页面 metadata、品牌 Logo、首屏截图和结构化 product 字段，并在当前项目下保存 profile.md、metadata.json、raw-firecrawl.json 和下载后的图片资产。
按 GoBackendFram 框架约定开发、配置、集成或审查 Go 后端功能.
Use for practical and strategic Google Ads work for any product: workflow diagnosis, first-launch readiness, landing page/material/copy prep, Keyword Planner usage, competitor/category research, Search campaign setup, ad groups, keywords, match types, responsive search ads, URL options/UTM, conversions, bidding, regions/languages, negatives, search-term analysis, daily optimization SOP, product/landing-page/onboarding/operations feedback loops, market expansion, growth experiments, and reviews from Google Ads CSVs, analytics screenshots, database funnels, or conversion screenshots. Use stored real Google Ads UI knowledge first; ask for screenshots/data only when needed. Never invent recommendations without evidence; separate evidence, inference, and hypotheses.
判断一个产品 idea 能否被 2-5 人小团队在 3 个月内做出 MVP。
Use when asked to analyze a live website, SaaS product, web app, landing page, competitor site, or AI tool, especially with logged-in UX, Google/OAuth login, pre-authenticated Chrome sessions, payment avoidance, SEO/keyword research, competitor comparison, feasibility scoring, or a Markdown report saved locally.
Use when collecting today's products from Product Hunt, BetaList, Uneed, DevHunt, Microlaunch, Peerlist Launchpad, Fazier, Startup Fame, There Is An AI For That, Futurepedia, Toolify, AIToolHunt, or TopAI.tools into per-site JSON files.
Use when the user wants a polished UI and references a well-known product, brand, or aesthetic such as Figma, Apple, Linear, Stripe, Notion, Airbnb, Tesla, or asks for a premium, beautiful, product-grade interface. Loads only the most relevant design reference docs from references/ and turns them into implementation constraints.