Vibecode Frase
track this build5 steps, step by step0%KINDA · weekend project
A content-brief generator over SERP pages and an LLM is reachable, but Frase's workflow combines SERP retrieval, scoring, editor UX, AI-search tracking, and reporting.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Frase. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Frase indie build ## Goal Build the smallest trustworthy replacement for the core Frase workflow for one developer or a tiny team. ## Scope Retrieve top pages, summarize topics/questions/headings, generate a brief, score a draft against terms, and export to a doc. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - SERP data pipeline - optimization scoring - team workflows - AI-search tracking - editor polish - reporting If those capabilities are essential, use Danswer/Onyx instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a content-brief generator to replace Frase. Requirements: - A Node CLI: `brief "<keyword>"` writes ./briefs/<keyword-slug>.md. - Fetch the top 10 results for the keyword from Serper.dev (key in .env). - Scrape each result with Playwright plus Readability: title, H2/H3 outline, word count, and any questions found on the page. - Send the aggregate to an LLM (key in .env) to produce the brief: suggested title and angle, a target outline, questions to answer, terms competitors cover, and a word-count range. - `score <draft.md> "<keyword>"` re-checks my draft against the brief: which terms and questions are covered or missing, with a plain coverage percentage. - Cache scraped pages in ./cache/ keyed by URL so re-runs cost nothing. - Flat files only, no database; no accounts, no telemetry, the only network calls are the SERP API, page fetches, and the LLM. - Out of scope: an editor UI, rank tracking, team workflows. Briefs are Markdown, I write in my own editor. - README: which keys to get and the rough per-brief cost of the SERP API. ## Required capabilities - SERP/search API - web parser - LLM API - document/editor UI - scoring logic - hosted backend ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Frase. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Frase indie build ## Goal Build the smallest trustworthy replacement for the core Frase workflow for one developer or a tiny team. ## Scope Retrieve top pages, summarize topics/questions/headings, generate a brief, score a draft against terms, and export to a doc. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - SERP data pipeline - optimization scoring - team workflows - AI-search tracking - editor polish - reporting If those capabilities are essential, use Danswer/Onyx instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a content-brief generator to replace Frase. Requirements: - A Node CLI: `brief "<keyword>"` writes ./briefs/<keyword-slug>.md. - Fetch the top 10 results for the keyword from Serper.dev (key in .env). - Scrape each result with Playwright plus Readability: title, H2/H3 outline, word count, and any questions found on the page. - Send the aggregate to an LLM (key in .env) to produce the brief: suggested title and angle, a target outline, questions to answer, terms competitors cover, and a word-count range. - `score <draft.md> "<keyword>"` re-checks my draft against the brief: which terms and questions are covered or missing, with a plain coverage percentage. - Cache scraped pages in ./cache/ keyed by URL so re-runs cost nothing. - Flat files only, no database; no accounts, no telemetry, the only network calls are the SERP API, page fetches, and the LLM. - Out of scope: an editor UI, rank tracking, team workflows. Briefs are Markdown, I write in my own editor. - README: which keys to get and the rough per-brief cost of the SERP API. ## Required capabilities - SERP/search API - web parser - LLM API - document/editor UI - scoring logic - hosted backend ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Frase. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Frase product brief ## Problem A content-brief generator over SERP pages and an LLM is reachable, but Frase's workflow combines SERP retrieval, scoring, editor UX, AI-search tracking, and reporting. ## Product outcome Retrieve top pages, summarize topics/questions/headings, generate a brief, score a draft against terms, and export to a doc. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - SERP/search API - web parser - LLM API - document/editor UI - scoring logic - hosted backend ## Explicit non-goals for v1 - SERP data pipeline - optimization scoring - team workflows - AI-search tracking - editor polish - reporting ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a content-brief generator to replace Frase. Requirements: - A Node CLI: `brief "<keyword>"` writes ./briefs/<keyword-slug>.md. - Fetch the top 10 results for the keyword from Serper.dev (key in .env). - Scrape each result with Playwright plus Readability: title, H2/H3 outline, word count, and any questions found on the page. - Send the aggregate to an LLM (key in .env) to produce the brief: suggested title and angle, a target outline, questions to answer, terms competitors cover, and a word-count range. - `score <draft.md> "<keyword>"` re-checks my draft against the brief: which terms and questions are covered or missing, with a plain coverage percentage. - Cache scraped pages in ./cache/ keyed by URL so re-runs cost nothing. - Flat files only, no database; no accounts, no telemetry, the only network calls are the SERP API, page fetches, and the LLM. - Out of scope: an editor UI, rank tracking, team workflows. Briefs are Markdown, I write in my own editor. - README: which keys to get and the rough per-brief cost of the SERP API. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Frase capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Frase indie build ## Goal Build the smallest trustworthy replacement for the core Frase workflow for one developer or a tiny team. ## Scope Retrieve top pages, summarize topics/questions/headings, generate a brief, score a draft against terms, and export to a doc. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - SERP data pipeline - optimization scoring - team workflows - AI-search tracking - editor polish - reporting If those capabilities are essential, use Danswer/Onyx instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a content-brief generator to replace Frase. Requirements: - A Node CLI: `brief "<keyword>"` writes ./briefs/<keyword-slug>.md. - Fetch the top 10 results for the keyword from Serper.dev (key in .env). - Scrape each result with Playwright plus Readability: title, H2/H3 outline, word count, and any questions found on the page. - Send the aggregate to an LLM (key in .env) to produce the brief: suggested title and angle, a target outline, questions to answer, terms competitors cover, and a word-count range. - `score <draft.md> "<keyword>"` re-checks my draft against the brief: which terms and questions are covered or missing, with a plain coverage percentage. - Cache scraped pages in ./cache/ keyed by URL so re-runs cost nothing. - Flat files only, no database; no accounts, no telemetry, the only network calls are the SERP API, page fetches, and the LLM. - Out of scope: an editor UI, rank tracking, team workflows. Briefs are Markdown, I write in my own editor. - README: which keys to get and the rough per-brief cost of the SERP API. ## Required capabilities - SERP/search API - web parser - LLM API - document/editor UI - scoring logic - hosted backend ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Frase product brief ## Problem A content-brief generator over SERP pages and an LLM is reachable, but Frase's workflow combines SERP retrieval, scoring, editor UX, AI-search tracking, and reporting. ## Product outcome Retrieve top pages, summarize topics/questions/headings, generate a brief, score a draft against terms, and export to a doc. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - SERP/search API - web parser - LLM API - document/editor UI - scoring logic - hosted backend ## Explicit non-goals for v1 - SERP data pipeline - optimization scoring - team workflows - AI-search tracking - editor polish - reporting ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a content-brief generator to replace Frase. Requirements: - A Node CLI: `brief "<keyword>"` writes ./briefs/<keyword-slug>.md. - Fetch the top 10 results for the keyword from Serper.dev (key in .env). - Scrape each result with Playwright plus Readability: title, H2/H3 outline, word count, and any questions found on the page. - Send the aggregate to an LLM (key in .env) to produce the brief: suggested title and angle, a target outline, questions to answer, terms competitors cover, and a word-count range. - `score <draft.md> "<keyword>"` re-checks my draft against the brief: which terms and questions are covered or missing, with a plain coverage percentage. - Cache scraped pages in ./cache/ keyed by URL so re-runs cost nothing. - Flat files only, no database; no accounts, no telemetry, the only network calls are the SERP API, page fetches, and the LLM. - Out of scope: an editor UI, rank tracking, team workflows. Briefs are Markdown, I write in my own editor. - README: which keys to get and the rough per-brief cost of the SERP API. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Frase capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
They pay because writers need a repeatable research/editor workflow, not a pile of scraped pages.
xSERP data pipeline
xoptimization scoring
xteam workflows
xAI-search tracking
xeditor polish
xreporting
share on X ↗"I just replaced Frase ($49/mo) with one prompt"
Frase pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| starter | $49/workspace | $39/workspace | 1 seat; 1 site; 10 articles/month; 50 page audits/month; 3 Frase Guard pages. |
| professional | $129/workspace | $103/workspace | 3 seats; 5 sites; 40 articles/month; 250 page audits/month; 15 Frase Guard pages. |
| scale | $299/workspace | $239/workspace | 5 seats; 10 domains; 100 articles/month; 1,000 page audits/month; 50 Frase Guard pages. |
| enterprise | custom | — | Custom sites, seats, article volume, audit volume, governance, security, and support. |
free tierno free tier (7-day trial only)
billingmonthly + annual (about 20% lower on annual billing)
hidden costsExtra seats cost $29/month; optional article/audit overages can add usage charges, but public unit rates are not disclosed. FraseCMS paid hosting starts at $19/month after its free 100,000-pageview/25 GB level.
verified 2026-08-14 · source ↗
Vibecode Frase
Kinda. The core of Frase is buildable in a weekend with the prompt on this page, but there are real gaps: SERP data pipeline, optimization scoring. Read the honest list above before committing.
How much does Frase cost?
Frase costs about $49/month (Starter, checked 2026-07-30), which is $588 per year.
What do I lose by replacing Frase?
Honestly: SERP data pipeline; optimization scoring; team workflows; AI-search tracking; editor polish; reporting. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Frase?
Yes: Danswer/Onyx (Open-source enterprise search/answering app; not a Frase clone, but prior art for retrieva). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.