메뉴
Drafts one human-sounding Quora answer per question for Google-indexed visibility. Applies blog-writing anti-AI voice, Quora SEO structure, catalog fact checks, and Reddit-style deep links. Use when the user finds a Quora question to answer or wants a reply polished before posting. Delivers a single copy-paste block, not campaign files.
| name | quora-replies |
| description | Drafts one human-sounding Quora answer per question for Google-indexed visibility. Applies blog-writing anti-AI voice, Quora SEO structure, catalog fact checks, and Reddit-style deep links. Use when the user finds a Quora question to answer or wants a reply polished before posting. Delivers a single copy-paste block, not campaign files. |
Read blog-writing skill first for voice and anti-AI rules. Borrow catalog checks and deep links from reddit-replies. Use blog FAQ + catalog for verified facts (same sources as Pinterest pins, but Quora is one answer per question, not a pin batch).
Do not create marketing/quora/ copy files unless the user explicitly asks to archive an answer.
| Channel | Unit of work | Output |
|---|---|---|
| Many pin images per blog | Files in marketing/pinterest/ | |
| One reply per thread | Copy-paste block in chat | |
| Quora | One tailored answer per question | Copy-paste block in chat |
Quora SEO comes from winning individual question pages in Google (and upvotes on Quora). You do not blast six variants of the same guide. You find a strong question, write the best answer for that exact title, post once, and move on. Related questions get separate answers rewritten for their wording, posted days apart, never copy-pasted.
Before drafting, sanity-check the thread:
| Signal | Why it matters |
|---|---|
| Google visibility | Search the question phrase on Google; if a Quora URL is on page 1, an answer here can rank for years. |
| Views + age | High views on an old question = proven search demand. Stale top answers (pre-2019 policy, no specs) = room to outrank. |
| Exact title match | Your opening must answer this question's words ("why ban" vs "best stroller" vs "wagons allowed" are three different answers). |
| Answer gap | Top answers vague, short, or outdated? That's your opening. |
| Duplicates | Pick the highest-traffic phrasing; answer there only. Do not paste the same text on five merged questions. |
Follow questions you answer so you can edit when Disney policy or catalog specs change. Edits refresh the thread; duplicate posts look like spam.
What Quora and Google reward on a single answer:
| Signal | What to do |
|---|---|
| Direct answer first | Sentence one answers the question. No preamble, no "great question." |
| Title keywords | Use the question's phrases naturally 2–3 times ("Disney World", "large strollers", "ban"). |
| Length with purpose | Competitive gear questions: 250–500 words. Narrow questions can be shorter. |
| Scannable structure | Short paragraphs. Bold 2–3 labels if the answer covers multiple rules or picks. |
| Authority link | One official source when relevant (Disney FAQ, AAP). Separate line, full URL. |
| First-hand voice | One concrete parent scene (bus line, gate check, hallway fold test). |
| Credentials | Set on your Quora profile (parent, gear comparison). Do not repeat "as founder of…" in every paragraph. |
| One BabyPickr link last | Blog guide when topic matches; browse deep link when the question names one product situation. |
What hurts you: link-first answers, identical walls of text across questions, fear bait ("RUIN your trip"), blog FAQ copy-pasted without rewriting for the question title.
Same discipline as reddit-replies, with Quora depth:
Never mention BabyPickr before step 5.
Purely emotional or opinion threads with no gear comparison ask: answer fully, no link. Add a link when the question asks what to buy, what fits, specs, or rent vs buy.
Same blog can back multiple Quora threads, but rewrite each time:
| Question type | Lead with | Usually skip |
|---|---|---|
| Why / policy | 2019 rule, crowd flow, what changed | Full ranked list of 12 strollers |
| Allowed / size limit | 31 × 52 numbers, fold-for-transit | Rent-vs-buy math |
| Wagons | Hard ban, separate from size rule | Singles recommendations |
| Best X | Situation split (flying vs driving), 2–3 picks | Long policy history |
| Rent vs buy | Math and trip length | Wagon tangent |
Pull verified stats from app/blog/{slug}/page.tsx FAQ and data/*.ts. Do not dump the whole guide into one answer.
| Rule | Detail |
|---|---|
| Domain | https://www.babypickr.com (config/seo-metadata.ts SITE_ORIGIN) |
| Prefer blog | https://www.babypickr.com/blog/{slug} when the guide matches the question |
| Browse | /?sortBy=portability&highlight={ASIN} for one-product threads; same param rules as reddit-replies |
| Format | Plain URL on its own line, or natural sentence with URL. No raw query-string dumps without context. |
Supported stroller params: space, budget, parentHeight, sortBy, highlight (ASIN). Not supported: features=travel, features=double.
Common blogs: Disney → best-strollers-disney-world; city → best-strollers-city-apartments; tall → best-strollers-tall-parents.
Self-promo tone: "I put together a stroller comparison site when we were planning our trip…" not "check out my website."
data/*.ts or blog copy tied to catalog only.asin: null (Nuna TRVL dubl): cite catalog specs; no highlight param.## headers; bold lead-ins work better on mobile.- [ ] Read the exact Quora question title + top existing answers
- [ ] Confirm it is worth answering (views, Google presence, gap in top answers)
- [ ] Read blog-writing anti-AI section
- [ ] Grep catalog for any product you will name
- [ ] Draft for THIS question only: direct answer → context → detail → source → one link
- [ ] Anti-AI pass: read aloud; cut dashes, triplets, marketing tone
- [ ] Deliver one copy-paste block in chat (like reddit-replies)
No tests unless catalog or browse URL behavior changes.
Deliver one copy-paste block per question. Outside the block, optional notes: suggested credential, whether to skip link, or "edit this answer in 2027 if Disney changes policy."
Do not by default create repo files, campaign folders, or multi-answer batches.
For before/after samples see examples.md.
Creates BabyPickr Pinterest pin images and posting copy for blog articles: 1000x1500 branded graphics, multiple pin angles per post, product rankings, curiosity hooks, and SEO-friendly titles/descriptions/tags/topics. Use when the user mentions Pinterest, pin images, pin marketing, social graphics for blogs, or wants posting copy for BabyPickr content.
Researches and scores the next BabyPickr blog topic using content gaps, catalog fit, Google autocomplete, Trends, and SERP intent. Produces a topic brief with title, slug, situations, and outline. Use when the user asks what blog to write next, SEO topic research, keyword research for guides, or Google Trends / autocomplete for content planning.
Writes and edits BabyPickr blog posts with a human parent voice, homepage-aligned layout/theme, and without common AI writing tells (no em dashes or double hyphens). Use when creating or revising blog articles, guides, roundup posts, SEO content under app/blog/, or when the user mentions blog posts, editorial voice, or sounding like AI.
Drafts human-sounding Reddit replies for BabyPickr founder posts in parenting gear subs (r/Buyingforbaby, r/beyondthebump, etc.). Verifies catalog facts, builds safe deep links, and applies blog-writing anti-AI voice rules. Use when the user wants to reply to a Reddit post, share babypickr.com on Reddit, or polish a comment before posting.
Designs and maintains BabyPickr's Smart Registry Checklist: tier-based budget envelopes (minimum / comfortable / premium), cross-page product selection, consumable Amazon slots, budget tracking, curated auto-picks, and print/export. Use when editing the new-parent checklist blog, lib/registry/*, checklist UI, browse-page "Add to checklist" flows, or integrating new catalog products into registry slot eligibility.
Maintains BabyPickr baby monitor journey filters, boost scoring, and catalog flags so journey answers rank the right monitor type for each parent situation. Use when adding or editing monitors in data/monitors.ts, lib/filters/monitors.ts, lib/monitorCapability.ts, lib/journeyStorage.ts (monitor paths), journey tests, or when journey combinations return zero or wrong monitors.