ITECHDEV-MX
- 37 skills
- 0 followers
- 9 hours ago last updated
- ▌ Page Cro · itechdev-mx bundleWhen the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
- ▌ SEO Audit · itechdev-mx bundleWhen the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
- ▌ Copywriting · itechdev-mx bundleWhen the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
- ▌ Email Sequence · itechdev-mx bundleWhen the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
- ▌ Pricing Strategy · itechdev-mx bundleWhen the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.
- ▌ Analytics Tracking · itechdev-mx bundleWhen the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
- ▌ Product Marketing Context · itechdev-mxWhen the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing-context.md` that all other skills reference for product, audience, and positioning context.
- ▌ Autoplan · itechdev-mxEngineering plan from the reframed + strategically-aligned request. Decomposes into tasks, identifies skills/recipes that apply, lists affected packages, estimates effort. Position 2 in story-creation pipelines.
- ▌ Sdd Flow · itechdev-mxSpec-Driven Development workflow for AriaCore. Trigger: When user requests SDD or multi-phase implementation planning.
- ▌ Skillify · itechdev-mxCapture a workflow you just ran ad-hoc and turn it into a draft SKILL.md file under skills/_drafts/. Lowers the barrier from "I did this once" to "we have a skill for this" so repeated patterns graduate into the catalog instead of dying as tribal knowledge. Inspired by oh-my-claudecode/skillify.
- ▌ Branch Pr · itechdev-mxPR creation workflow for AriaCore following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
- ▌ Server API · itechdev-mxAPI contract guardrails for AriaCore server changes. Trigger: Any route, handler, payload, or status code modification.
- ▌ Plugin Thin · itechdev-mxAdapter boundary rules for plugin integrations. Trigger: Changes in plugin scripts/hooks for Claude, OpenCode, Gemini, or Codex.
- ▌ Tui Quality · itechdev-mxBubbletea/Lipgloss quality rules for AriaCore TUI. Trigger: Changes in model, update, view, navigation, or rendering.
- ▌ UI Elements · itechdev-mxCreation rules for AriaCore UI elements, pages, cards, metrics, and detail flows. Trigger: Adding or changing dashboard UI components or connected browsing flows.
- ▌ Office Hours · itechdev-mxReframe a client request before any planning happens. Asks the user forcing questions, identifies the real product hiding inside the ask, and outputs a structured rewrite that the rest of the chain consumes. First step in story-creation pipelines.
- ▌ Story Writer · itechdev-mxFinal agent in the story-creation chain. Consumes office-hours, ceo-plan, eng-plan and emits a Connextra-format user story with Gherkin acceptance criteria. Persists the result both to disk (/Historias/<slug>/3-story.md) and to ARIA memory as a story-typed observation.
- ▌ Ab Test Setup · itechdev-mx bundleWhen the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
- ▌ Backlog Triage · itechdev-mxBacklog triage protocol for AriaCore: audit open issues and PRs, classify each item, infer maintainer ideology from comments, and produce an actionable disposition report. Trigger: Auditing open issues or PRs, triaging the backlog, reviewing contributor submissions as a maintainer, or applying triage to any GitHub repo.
- ▌ Business Rules · itechdev-mxProduct and business-rule guardrails for AriaCore. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
- ▌ Commit Hygiene · itechdev-mxCommit and branch naming standards for AriaCore contributors, enforced by GitHub rulesets. Trigger: Any commit creation, review, or branch cleanup.
- ▌ Cultural Norms · itechdev-mxCultural and collaboration norms for AriaCore contributors and agents. Trigger: Starting substantial work, reviewing changes, or defining team conventions.
- ▌ Dashboard Htmx · itechdev-mxHTMX and templ interaction rules for the AriaCore dashboard. Trigger: Any change to htmx attributes, partial updates, forms, or server-rendered browser UI.
- ▌ Docs Alignment · itechdev-mxDocumentation alignment rules for AriaCore. Trigger: Any code or workflow change that affects user or contributor behavior.
- ▌ Issue Creation · itechdev-mxIssue creation workflow for AriaCore following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
- ▌ Pr Review Deep · itechdev-mxDeep technical review protocol for AriaCore pull requests. Trigger: Reviewing any external or internal contribution before merge.
- ▌ Memory Protocol · itechdev-mxPersistent memory discipline for AriaCore contributors. Trigger: Decisions, bugfixes, discoveries, preferences, or session closure.
- ▌ Plan Ceo Review · itechdev-mxStrategic alignment pass over a reframed request. Cross-references the reframe against company strategy, current quarter priorities, and rejected alternatives. Decides whether the work fits NOW, LATER, or NEVER. Position 1 in story-creation pipelines.
- ▌ Visual Language · itechdev-mxVisual language rules for AriaCore surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change.
- ▌ Testing Coverage · itechdev-mxTDD and coverage standards for AriaCore. Trigger: When implementing behavior changes in any package.
- ▌ Project Structure · itechdev-mxRepository structure and placement rules for AriaCore. Trigger: Creating files, packages, handlers, templates, styles, or tests in this repo.
- ▌ Story Orchestrator · itechdev-mxCoordinator agent-skill that drives the multi-agent story-creation chain (office-hours → plan-ceo-review → autoplan → story-writer). Loads each child skill, supplies the previous artifact(s) as input, invokes the sub-agent, and short-circuits when plan-ceo-review returns LATER or NEVER. Lives at position-less (orchestrator role, not part of the chain itself).
- ▌ Gentleman Bubbletea · itechdev-mxBubbletea TUI patterns for Gentleman.Dots installer. Trigger: When editing Go files in installer/internal/tui/, working on TUI screens, or adding new UI features.
- ▌ Competitor Profiling · itechdev-mx bundleWhen the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.
- ▌
- ▌ Architecture Guardrails · itechdev-mxArchitecture guardrails for AriaCore across local store, cloud sync, dashboard, and plugins. Trigger: Any change that affects system boundaries, ownership, state flow, or cross-package responsibilities.
- ▌ Aria Core Memory · itechdev-mxALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to aria-core proactively. Do NOT wait for the user to ask.