> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/docs/extensions/trend-finder/creator-lens.md).

# Trend Finder Creator Lens

This guide explains the local profile that tells Trend Finder what useful means for the current operator.

## Creator Lens

Creator Lens is the local profile that tells Trend Finder what "useful" means for this operator.

| Field       | Meaning                                                                                 |
| ----------- | --------------------------------------------------------------------------------------- |
| Audience    | Who the opportunity should matter to.                                                   |
| Format      | The kinds of output the operator wants to create.                                       |
| Goal        | The job Trend Finder should optimize for.                                               |
| Topic focus | Up to eight focus phrases used to bias analysis and fallback scoring.                   |
| Risk level  | `safe`, `balanced`, or `experimental`, used as a signal for how early/aggressive to be. |
| Competitors | Up to 15 public competitor or adjacent-channel names used for public evidence matching. |

The default lens is:

```
Audience: AI vibe-coders, creators, and automators
Format: tutorials, workflows, newsletters, product ideas, and experiments
Topic focus: AI agents, automation, coding tools, creator workflows
Goal: find early topics worth creating useful content about
Risk level: balanced
```

Creator Lens affects the system in these ways:

* It is included in the AI trend analyst prompt.
* It influences AI-produced `nicheFit`, `creatorPotential`, `creatorAngle`, hooks, questions, and optional watchlist reasons.
* It influences deterministic fallback `whyNow`, `creatorAngle`, hooks, audience questions, novelty, niche fit, and creator potential.
* It is used in the watchlist creator-fit reason text.
* It gives the analyst and fallback composer context for contrarian, plain-language, and ready-title angle-pack fields.
* It lets the collector flag public YouTube channel-title matches against saved competitor names.
* It is stored in generated Trend Finder payloads and private snapshots.

Creator Lens does not immediately rescore the already-rendered payload. Edits are browser drafts until saved. Saving posts the lens to the local loopback Creator Lens bridge, which writes `creator-lens.json` inside the Trend Finder extension cache. The next Trend Finder run loads that saved lens.

Browser drafts persist under localStorage key `ai-os.trend-finder.creator-lens.v1`. The browser migrates legacy `findtrend.trend-finder.creator-lens.v1` and `claude-os.trend-finder.creator-lens.v1` values when present. Saved file-backed config uses the local `/__trend_finder_creator_lens` bridge, which is loopback-only and token-gated.

Creator Lens also does not directly select source adapters or mutate reviewed source configuration in the current implementation. It influences analysis, fallback topic shaping, score factors, creator copy, and watchlist reasons after sources have been collected.

The run button saves unsaved Creator Lens edits first, then requests the local aggregate refresh. If the browser is offline, edits can remain in local browser draft storage, but they cannot affect collector output until saved and rerun.

## Competitor Names

Competitors are public channel or adjacent-creator names, not URLs, private accounts, handles that require authenticated scraping, or source adapter configuration. The browser draft parser and script-side cache parser both normalize whitespace, dedupe by a case-insensitive key, cap names at 80 characters, and cap the list at 15 entries. Invalid values surface safe validation messages such as "public channel names only" and do not echo private paths or raw input back to the UI.

Competitor matching is collect-time behavior. After a saved lens is loaded, the collector compares the normalized competitor list with reviewed public YouTube channel-title entities that are already allowed by the YouTube source review. Matching evidence receives a bounded `competitorMatch` object and UI chip. Trend Finder does not collect private competitor feeds, crawl competitor pages, or widen source coverage because a competitor name was entered.

Saving competitors follows the same save/rerun rule as other Creator Lens fields. Browser edits are drafts until saved through the loopback Creator Lens bridge. The next Trend Finder run loads the saved file-backed lens, applies competitor matching during collection, and passes the competitor list to AI or fallback angle generation.

In AI mode, risk level is a prompt signal. In deterministic fallback mode, it also has explicit numeric effects: `experimental` gives higher fallback novelty and a larger niche-fit bonus than `balanced`, while `safe` gives the smallest fallback niche-fit bonus.

## Angle-Pack Output

Trend Finder now publishes an angle pack per topic when AI or fallback output can provide it:

| Field             | Meaning                                                       |
| ----------------- | ------------------------------------------------------------- |
| `creatorAngle`    | Existing creator-facing angle grounded in the topic evidence. |
| `contrarianAngle` | A bounded "what most people are missing" angle.               |
| `plainExplainer`  | A plain-language explanation suitable for creator copy.       |
| `suggestedTitle`  | A ready-to-use title or hook line.                            |

The angle pack is rendered on trend cards, Brief, and static Brief export. Fallback copy uses the lens audience, format, topic focus, risk level, and competitor matches without claiming an AI analyst ran.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/docs/extensions/trend-finder/creator-lens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.