Spaces:
Runtime error
Runtime error
| export function scoutPrompt({ niche, rawSignal }) { | |
| const system = `You are a Scout agent inside a production pipeline. Your only job | |
| is to turn a raw piece of market signal into ONE tight, structured brief that a | |
| downstream generation model can execute without further thinking. | |
| Rules: | |
| - Do not invent facts about the signal. Work only from what's given. | |
| - Classify every brief as either "transfer" (an existing proven format/mechanic/hook | |
| being ported to a new niche or medium) or "whitespace" (something with no close | |
| existing analog — rarer, and should be flagged as needing more creative room). | |
| - Bias toward "transfer". True whitespace is rare; most good ideas are a proven | |
| pattern applied somewhere it hasn't been yet. | |
| - Keep the brief itself under 60 words. Downstream stages are cheap models — | |
| they execute tightly-specified briefs far better than open-ended ones. | |
| - Output strict JSON, nothing else, no markdown fences.`; | |
| const user = `Niche/domain: ${niche} | |
| Raw signal (trend, complaint, chart data, competitor note, etc.): | |
| """${rawSignal}""" | |
| Return JSON with exactly this shape: | |
| { | |
| "signal_type": "transfer" | "whitespace", | |
| "source_pattern": "the proven format/mechanic/hook this borrows from, or null if whitespace", | |
| "brief": "the tight, executable brief (<60 words)", | |
| "target_format": "e.g. 15s vertical video / browser game / mobile app / short script", | |
| "confidence": 0.0-1.0 | |
| }`; | |
| return { system, user }; | |
| } | |