协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
suede-free-tools【开发与工程】Suede-affiliated engineering-as-marketing strategy for selecting, scoring, and scoping calculators, graders, generators, and other free interactive tools. Use when the user wants a lead, link, education, or product-adoption asset with a measurable path to the paid product. NOT FOR: downloadable lead assets (use suede-lead-magnets), implementation of …
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Suede uses engineering as marketing when a genuinely useful tool can create qualified discovery and a natural bridge to the paid product. Select, score, and scope the smallest maintainable calculator, grader, generator, or utility whose output earns attention rather than merely capturing it.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before designing a tool strategy, understand:
Business Context - What's the core product? Who is the target audience? What problems do they have?
Goals - Lead generation? SEO/traffic? Brand awareness? Product education? What is one lead worth (LTV and close rate from this source)?
Resources - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion? Timeline?
Existing Behavior - What tools or manual workarounds does the audience use today? How are leads generated now?
Populate all four terms before calling the go/no-go, and show the arithmetic:
State every rate you assumed and where it came from. If a term cannot be sourced, say which one and mark the go/no-go unresolved rather than filling it in.
| Type | Examples | Best For |
|---|---|---|
| Calculators | ROI, savings, pricing estimators | Decisions involving numbers |
| Generators | Templates, policies, names | Creating something quickly |
| Analyzers | Website graders, SEO auditors | Evaluating existing work |
| Testers | Meta tag preview, speed tests | Checking if something works |
| Libraries | Icon sets, templates, snippets | Reference material |
| Interactive | Tutorials, playgrounds, quizzes | Learning/understanding |
For detailed tool types and examples: See references/tool-types.md
What problems does your audience Google? - Search query research, common questions
What manual processes are tedious? - Spreadsheet tasks, repetitive calculations
What do they need before buying your product? - Assessments, planning, comparisons
What information do they wish they had? - Data they can't easily access, benchmarks
| Approach | Pros | Cons |
|---|---|---|
| Fully gated | Maximum capture | Lower usage |
| Partially gated | Balance of both | Common pattern |
| Ungated + optional | Maximum reach | Lower capture |
| Ungated entirely | Pure SEO/brand | No direct leads |
The gating trade-off itself (per-field conversion cost and how to frame the
exchange) is owned by suede-lead-magnets. Use its gating tables when deciding
what to ask for; the table above only covers where the gate sits in a tool.
Tool landing page: "[thing] calculator", "[thing] generator", "free [tool type]"
Supporting content: "How to [use case]", "What is [concept]"
Free tools attract links because:
When: Unique concept, core to brand, high strategic value, have dev capacity
Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow When: Speed to market, limited dev resources, testing concept
When: Something good exists, white-label available, not core differentiator
Account creation, saving results, advanced features, perfect design, every edge case
Rate each factor 1-5:
| Factor | Score |
|---|---|
| Search demand exists | ___ |
| Audience match to buyers | ___ |
| Uniqueness vs. existing | ___ |
| Natural path to product | ___ |
| Build feasibility | ___ |
| Maintenance burden (inverse) | ___ |
| Link-building potential | ___ |
| Share-worthiness | ___ |
25+: Strong candidate | 15-24: Promising | <15: Reconsider
Anchors for the three decisive factors: score these against the anchor, not on impression, and cite the evidence used:
| Factor | 1 | 3 | 5 |
|---|---|---|---|
| Search demand exists | No query with measurable volume | A query family in the hundreds of searches/month | A head term in the thousands/month |
| Build feasibility | Needs a data pipeline, licensed data, or an ongoing integration | Two to four engineer-weeks with known components | One engineer-week, one screen, no backend state |
| Maintenance burden (inverse) | Depends on data refreshed on a schedule or a third-party API | Occasional content or dependency updates | Static computation, nothing to refresh |
Return exactly these sections:
Name and the one-sentence job it does for the user.
The filled table with a score per factor, the total, and the verdict band. For the three anchored factors, name the evidence behind the score.
Two explicit lists: In (what v1 does) and Out (what is deliberately deferred). No item appears in both.
Which option from Gating Options, and the trade-off accepted in one line.
The single target query for the tool page, plus the supporting-content query.
The two or three usage events the tool must emit (use, complete, capture) so
suede-analytics can read the funnel. This skill does not define the metrics
plan itself.
suede-lead-magnets for downloadable assets and suede-site-alchemy for the public conversion surface.suede-seo-audit for search validation and suede-analytics for usage measurement.suede-emails for the post-capture lifecycle sequence.suede-content-strategy for the supporting content around the tool page.suede-ads and suede-social for tool distribution and launch promotion.suede-ab-testing to design and evaluate tests on the tool page or its gate.