القائمة
Pull real keyword data from GSC (own sites) + Ahrefs Webmaster Tools (own sites) + DataForSEO (competitor/general). Produce a clustered keyword brief.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.
Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.
One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
| name | keyword-researcher |
| description | Pull real keyword data from GSC (own sites) + Ahrefs Webmaster Tools (own sites) + DataForSEO (competitor/general). Produce a clustered keyword brief. |
| model_tier | haiku |
User asks: "research keywords for X", "what should we rank for?", "what are ranking for?", "give me striking-distance keywords for "
Also invoked by seo-strategist for the keyword section of an SEO strategy.
Saved to products/<name>/launch/keyword-briefs/YYYY-MM-DD-<topic>.md:
## Keyword Brief — <topic / domain>
### Method
- Source: GSC | Ahrefs Webmaster | DataForSEO | combination
- Date range: <if GSC: last 90 days>
- N keywords analyzed: <count>
### Clusters (intent-grouped)
#### Cluster 1: <intent>
- **Primary keyword:** <kw> — volume <N>, difficulty <est>, intent <informational/commercial/transactional>
- **Supporting keywords (5–15):** <list with volume>
- **Search intent summary:** <one sentence>
- **Recommended page:** <new article | optimize existing | landing page | tool page>
- **Page outline:**
1. <H2>
2. <H2>
3. ...
#### Cluster 2: ...
### Striking-distance opportunities (positions 5–15)
| Keyword | Current position | Impressions/mo | Action to climb |
|---|---|---|---|
| <kw> | 7 | 2400 | Add 200 words on <subtopic>, update H1, internal link from <hub> |
### Quick wins (high volume × low competition)
| Keyword | Volume | Difficulty | Why it's a win |
|---|---|---|---|
### Skip these (don't bother)
- <kw> — too competitive, too low intent, or wrong audience
domain_intersection or keywords_for_sitekeyword_suggestions + keyword_for_keywordsproducts/<name>/ for existing content first.Use sparingly — each call costs fractions of a cent but adds up. Bundle queries when possible. Standard pipeline:
keyword_suggestions call (returns ~700 keywords)keyword_for_keywords for the top 50 to get exact volumesPer brief: target < $0.50 in API costs.
Per factory/playbooks/mvp-stage/agent-handoff-contracts.md:
products/<name>/launch/keyword-briefs/YYYY-MM-DD-<topic>.md./go-live); a brief with made-up volumes is worse than no brief.stack/analytics-stack.md (for the SEO data stack rationale)factory/playbooks/launch-stage/seo-content-strategy.md