Implement and route HitKeep contributions through the repository-owned hk developer platform. Use for any HitKeep code, UI, API, database, analytics-feature, seed, screenshot, documentation, integration, or release-preparation change, as well as setup, local development, builds, smoke tests, and contributor workflow discovery.
Operate HitKeep safely in isolated Git worktrees. Use when inspecting workspace state, resolving ports or URLs, starting or stopping development services, coordinating concurrent agents or QA runs, reusing active runs, reading bounded logs, or preparing a secret-free handoff.
Plan, execute, investigate, and report HitKeep quality gates through hk. Use while iterating, before calling contributor work complete, when choosing change-aware versus PR-parity versus exhaustive validation, when CI parity matters, or when investigating a failed or asynchronous gate.
Maintain HitKeep dashboard localization. Use whenever a contributor adds or changes user-visible dashboard text, Transloco keys, locale JSON files, PrimeNG locale behavior, language switching, translated labels, localized layout, date/number/duration formatting, or supported dashboard languages.
Analyze HitKeep AI visibility data. Use for AI crawler fetches, AI-referred visits, assistant names or families, citation yield, resource types, top paths, fetch failures, Search Console context, GPTBot, ClaudeBot, ChatGPT, Claude, Perplexity, AI search, or whether assistants are discovering and sending traffic to a site.
Official parent skill for analyzing HitKeep data through HitKeep MCP and official docs. Use for broad traffic, event, ecommerce, Web Vitals, AI visibility, Search Console, opportunity, tracking-health, MCP setup, or analytics-surface questions; use a narrower HitKeep analytics skill when the task clearly matches one.
Analyze HitKeep ecommerce and conversion data. Use for revenue, orders, average order value, products, sources, ecommerce funnels, conversion changes, UTM performance, acquisition quality, or aggregate city, provider, and ASN context.
Verify HitKeep tracking setup and automatic event collection. Use when installation status, missing pageviews or events, WordPress or script installs, automatic outbound clicks, downloads, form submissions, hostname mismatches, blockers, consent, CSP, or the difference between tracker failure and analytics interpretation is in question.