novahiz 0.2.2 → 0.2.5

package/bundled-skills/ads/references/platform-setup-checklists.md

@@ -1,277 +0,0 @@
-# Platform Setup Checklists
-
-Complete setup checklists for major ad platforms.
-
-## Contents
-- Google Ads Setup (Account Foundation, Conversion Tracking, Analytics Integration, Audience Setup, Campaign Readiness, Ad Extensions, Brand Protection)
-- Meta Ads Setup (Business Manager Foundation, Pixel & Tracking, Domain & Aggregated Events, Audience Setup, Catalog, Creative Assets, Compliance)
-- LinkedIn Ads Setup (Campaign Manager Foundation, Insight Tag & Tracking, Audience Setup, Lead Gen Forms, Document Ads, Creative Assets, Budget Considerations)
-- Twitter/X Ads Setup (Account Foundation, Tracking, Audience Setup, Creative)
-- TikTok Ads Setup (Account Foundation, Pixel & Tracking, Audience Setup, Creative)
-- Universal Pre-Launch Checklist
-
-## Google Ads Setup
-
-### Account Foundation
-
-- [ ] Google Ads account created and verified
-- [ ] Billing information added
-- [ ] Time zone and currency set correctly
-- [ ] Account access granted to team members
-
-### Conversion Tracking
-
-- [ ] Google tag installed on all pages
-- [ ] Conversion actions created (purchase, lead, signup)
-- [ ] Conversion values assigned (if applicable)
-- [ ] Enhanced conversions enabled
-- [ ] Test conversions firing correctly
-- [ ] Import conversions from GA4 (optional)
-
-### Analytics Integration
-
-- [ ] Google Analytics 4 linked
-- [ ] Auto-tagging enabled
-- [ ] GA4 audiences available in Google Ads
-- [ ] Cross-domain tracking set up (if multiple domains)
-
-### Audience Setup
-
-- [ ] Remarketing tag verified
-- [ ] Website visitor audiences created:
-  - All visitors (180 days)
-  - Key page visitors (pricing, demo, features)
-  - Converters (for exclusion)
-- [ ] Customer match lists uploaded
-- [ ] Similar audiences enabled
-
-### Campaign Readiness
-
-- [ ] Negative keyword lists created:
-  - Universal negatives (free, jobs, careers, reviews, complaints)
-  - Competitor negatives (if needed)
-  - Irrelevant industry terms
-- [ ] Location targeting set (include/exclude)
-- [ ] Language targeting set
-- [ ] Ad schedule configured (if B2B, business hours)
-- [ ] Device bid adjustments considered
-
-### Ad Extensions
-
-- [ ] Sitelinks (4-6 relevant pages)
-- [ ] Callouts (key benefits, offers)
-- [ ] Structured snippets (features, types, services)
-- [ ] Call extension (if phone leads valuable)
-- [ ] Lead form extension (if using)
-- [ ] Price extensions (if applicable)
-- [ ] Image extensions (where available)
-
-### Brand Protection
-
-- [ ] Brand campaign running (protect branded terms)
-- [ ] Competitor campaigns considered
-- [ ] Brand terms in negative lists for non-brand campaigns
-
----
-
-## Meta Ads Setup
-
-### Business Manager Foundation
-
-- [ ] Business Manager created
-- [ ] Business verified (if running certain ad types)
-- [ ] Ad account created within Business Manager
-- [ ] Payment method added
-- [ ] Team access configured with proper roles
-
-### Pixel & Tracking
-
-- [ ] Meta Pixel installed on all pages
-- [ ] Standard events configured:
-  - PageView (automatic)
-  - ViewContent (product/feature pages)
-  - Lead (form submissions)
-  - Purchase (conversions)
-  - AddToCart (if e-commerce)
-  - InitiateCheckout (if e-commerce)
-- [ ] Conversions API (CAPI) set up for server-side tracking
-- [ ] Event Match Quality score > 6
-- [ ] Test events in Events Manager
-
-### Domain & Aggregated Events
-
-- [ ] Domain verified in Business Manager
-- [ ] Aggregated Event Measurement configured
-- [ ] Top 8 events prioritized in order of importance
-- [ ] Web events prioritized for iOS 14+ tracking
-
-### Audience Setup
-
-- [ ] Custom audiences created:
-  - Website visitors (all, 30/60/90/180 days)
-  - Key page visitors
-  - Video viewers (25%, 50%, 75%, 95%)
-  - Page/Instagram engagers
-  - Customer list uploaded
-- [ ] Lookalike audiences created (1%, 1-3%)
-- [ ] Saved audiences for common targeting
-
-### Catalog (E-commerce)
-
-- [ ] Product catalog connected
-- [ ] Product feed updating correctly
-- [ ] Catalog sales campaigns enabled
-- [ ] Dynamic product ads configured
-
-### Creative Assets
-
-- [ ] Images in correct sizes:
-  - Feed: 1080x1080 (1:1)
-  - Stories/Reels: 1080x1920 (9:16)
-  - Landscape: 1200x628 (1.91:1)
-- [ ] Videos in correct formats
-- [ ] Ad copy variations ready
-- [ ] UTM parameters in all destination URLs
-
-### Compliance
-
-- [ ] Special Ad Categories declared (if housing, credit, employment, politics)
-- [ ] Landing page complies with Meta policies
-- [ ] No prohibited content in ads
-
----
-
-## LinkedIn Ads Setup
-
-### Campaign Manager Foundation
-
-- [ ] Campaign Manager account created
-- [ ] Company Page connected
-- [ ] Billing information added
-- [ ] Team access configured
-
-### Insight Tag & Tracking
-
-- [ ] LinkedIn Insight Tag installed on all pages
-- [ ] Tag verified and firing
-- [ ] Conversion tracking configured:
-  - URL-based conversions
-  - Event-specific conversions
-- [ ] Conversion values set (if applicable)
-
-### Audience Setup
-
-- [ ] Matched Audiences created:
-  - Website retargeting audiences
-  - Company list uploaded (for ABM)
-  - Contact list uploaded
-- [ ] Lookalike audiences created
-- [ ] Saved audiences for common targeting
-
-### Lead Gen Forms (if using)
-
-- [ ] Lead gen form templates created
-- [ ] Form fields selected (minimize for conversion)
-- [ ] Privacy policy URL added
-- [ ] Thank you message configured
-- [ ] CRM integration set up (or CSV export process)
-
-### Document Ads (if using)
-
-- [ ] Documents uploaded (PDF, PowerPoint)
-- [ ] Gating configured (full gate or preview)
-- [ ] Lead gen form connected
-
-### Creative Assets
-
-- [ ] Single image ads: 1200x627 (1.91:1) or 1080x1080 (1:1)
-- [ ] Carousel images ready
-- [ ] Video specs met (if using)
-- [ ] Ad copy within character limits:
-  - Intro text: 600 max, 150 recommended
-  - Headline: 200 max, 70 recommended
-
-### Budget Considerations
-
-- [ ] Budget realistic for LinkedIn CPCs ($8-15+ typical)
-- [ ] Audience size validated (50K+ recommended)
-- [ ] Daily vs. lifetime budget decided
-- [ ] Bid strategy selected
-
----
-
-## Twitter/X Ads Setup
-
-### Account Foundation
-
-- [ ] Ads account created
-- [ ] Payment method added
-- [ ] Account verified (if required)
-
-### Tracking
-
-- [ ] Twitter Pixel installed
-- [ ] Conversion events created
-- [ ] Website tag verified
-
-### Audience Setup
-
-- [ ] Tailored audiences created:
-  - Website visitors
-  - Customer lists
-- [ ] Follower lookalikes identified
-- [ ] Interest and keyword targets researched
-
-### Creative
-
-- [ ] Tweet copy within 280 characters
-- [ ] Images: 1200x675 (1.91:1) or 1200x1200 (1:1)
-- [ ] Video specs met (if using)
-- [ ] Cards configured (website, app, etc.)
-
----
-
-## TikTok Ads Setup
-
-### Account Foundation
-
-- [ ] TikTok Ads Manager account created
-- [ ] Business verification completed
-- [ ] Payment method added
-
-### Pixel & Tracking
-
-- [ ] TikTok Pixel installed
-- [ ] Events configured (ViewContent, Purchase, etc.)
-- [ ] Events API set up (recommended)
-
-### Audience Setup
-
-- [ ] Custom audiences created
-- [ ] Lookalike audiences created
-- [ ] Interest categories identified
-
-### Creative
-
-- [ ] Vertical video (9:16) ready
-- [ ] Native-feeling content (not too polished)
-- [ ] First 3 seconds are compelling hooks
-- [ ] Captions added (most watch without sound)
-- [ ] Music/sounds selected (licensed if needed)
-
----
-
-## Universal Pre-Launch Checklist
-
-Before launching any campaign:
-
-- [ ] Conversion tracking tested with real conversion
-- [ ] Landing page loads fast (<3 sec)
-- [ ] Landing page mobile-friendly
-- [ ] UTM parameters working
-- [ ] Budget set correctly (daily vs. lifetime)
-- [ ] Start/end dates correct
-- [ ] Targeting matches intended audience
-- [ ] Ad creative approved
-- [ ] Team notified of launch
-- [ ] Reporting dashboard ready

package/bundled-skills/ads/references/rsa-output-spec.md

@@ -1,88 +0,0 @@
-# Google RSA Output Spec
-
-When the user requests Google Ads RSAs (Responsive Search Ads), output MUST comply with these platform limits and structural requirements. Do not output any RSA that violates them.
-
-## Hard limits per RSA (enforce before responding)
-
-- **Headlines:** exactly **15** per RSA, each **≤ 30 characters** (count characters, including spaces). Render as `1. ... (NN chars)` so the reader can verify.
-- **Descriptions:** exactly **4** per RSA, each **≤ 90 characters**.
-- **Paths:** up to 2 path fields, each **≤ 15 characters**.
-- **Final URL:** present, https.
-- **Pinning:** state any pinned positions explicitly. Default = unpinned unless user asks.
-- **Per-account guardrail:** Google enforces **3 RSAs max per ad group**. When the user asks for >3, group them by ad group.
-
-## Required sidecar artifacts (always include with RSA request)
-
-1. **Ad group structure**, labeled `Ad group structure:` — list each ad group with its theme, target keywords (match types), and which RSAs map to it.
-2. **Negative keyword list**, labeled `Negative keywords:` — minimum **8** entries, group-level vs campaign-level called out.
-3. **Sitelinks** (≥ 4), **Callouts** (≥ 4 ≤25 chars), **Structured snippets** if relevant.
-
-## Medical / CFM compliance (when product context indicates pt-BR medical practice)
-
-If `.agents/product-marketing.md` indicates a Brazilian medical practice (CFM-regulated), the following terms are **forbidden** in headlines, descriptions, sitelinks, and callouts:
-
-- Superlatives: `#1`, `melhor`, `o melhor`, `melhor do brasil`, `top`, `referência`
-- Outcome promises: `garantido`, `garantia`, `cura`, `cura definitiva`, `100%`, `resultado garantido`, `livre da dor`
-- Comparative claims vs other doctors/clinics
-
-Use neutral framing: `atendimento`, `consulta`, `avaliação`, `segunda opinião`, `agende sua consulta`, `tire suas dúvidas`. Geo modifier (`Porto Alegre`, `POA`, `Zona Sul POA`) required where the prompt specifies a region.
-
-## Output ORDER (mandatory — emit in this order to avoid truncation)
-
-1. **Ad group structure** (short)
-2. **Negative keywords** (≥8, MANDATORY — emit BEFORE RSAs so it isn't dropped if output runs long)
-3. **Sitelinks** (≥4)
-4. **Callouts** (≥4)
-5. **RSA1, RSA2, RSA3** (largest section, last — safe to truncate gracefully)
-
-## Output template (mandatory shape)
-
-```
-Ad group structure:
-- AG1 [theme]: keywords (match types) → RSA1, RSA2
-- AG2 [theme]: ...
-
-Negative keywords:
-  Campaign-level:
-    - <kw>
-    - <kw>
-    (≥4 here)
-  Ad-group level:
-    - AG1: <kw>, <kw>
-    - AG2: <kw>, <kw>
-    (≥4 more here — TOTAL ≥8 entries)
-
-Sitelinks (≥4):
-  - <title (≤25)> | <desc1 (≤35)> | <desc2 (≤35)> | URL
-
-Callouts (≥4, each ≤25 chars):
-  - <callout>
-
-RSA1 — [ad group name]
-  Final URL: https://...
-  Path1: ...   Path2: ...
-  Headlines (15, each ≤30 chars):
-    1. <headline> (NN chars)
-    ...
-    15. <headline> (NN chars)
-  Descriptions (4, each ≤90 chars):
-    1. <description> (NN chars)
-    ...
-    4. <description> (NN chars)
-  Pinning: H1=none; H2=none; ...   (or explicit pins)
-
-RSA2 — ...
-RSA3 — ...
-```
-
-## Self-check before responding
-
-Before sending the output, run this checklist mentally:
-
-- [ ] Each RSA has exactly 15 headlines, exactly 4 descriptions.
-- [ ] Every headline is ≤30 chars; every description is ≤90 chars. Character counts printed.
-- [ ] Negative keyword list labeled and ≥8 entries.
-- [ ] Ad group structure labeled.
-- [ ] If medical (CFM): no forbidden superlative/outcome words; geo modifier present where required; language is pt-BR.
-
-If any check fails, rewrite before responding. Do not ship partial RSAs.

package/bundled-skills/agent-device/SKILL.md

@@ -1,20 +0,0 @@
----
-name: agent-device
-description: Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
----
-
-# agent-device
-
-For a normal app-driving task, start immediately. Do not probe first with `--help`, `--version`, `devices`, `appstate`, `snapshot`, or `screenshot`:
-
-```bash
-agent-device open <app> --foreground
-```
-
-That starts the session and returns the initial interactive snapshot with `@refs`.
-
-Loop: act with `press|click|fill|longpress <target> ... --settle`, `scroll <direction> --settle`, or `back --settle`; continue from the printed diff, verify the named expectation (`wait text "..."`, `is`, `get`, or `find`), then run `agent-device close`.
-
-Copy refs byte-for-byte: `@e12`, `@e12~s4` — keep the `@` and any `~sN`. Prefer current refs, then `id`/`label`/`role` selectors; coordinates are a last resort. If snapshot reports sparse/AX-unavailable, its refs and selectors are invalid: run `agent-device screenshot`, inspect the image, use coordinates, then retry `snapshot -i` after navigating. Otherwise run `snapshot -i` only when the diff lacks the next target.
-
-Error output includes corrective hints; follow them instead of re-planning. Only when the task is specialized (for example gestures, scripting, TV, macOS, remote, or debugging) or a command shape is unclear, run `agent-device help <topic>`. `agent-device --help` lists topics, but is not a startup step.