القائمة
Use when starting any conversation involving marketing, branding, product launches, positioning, content creation, or go-to-market strategy - routes to the correct marketing skill
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when executing an implementation plan with four or more independent tasks touching different files, via the experimental agent-teams flag — parallel implementer teammates plus continuous async reviewers. Higher token cost; requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Use when starting creative work — adding features, building components, adding functionality, modifying existing behavior, or any time the user describes a new idea or capability they want to build.
Use when adding, modifying, or removing database tables, columns, indexes, views, functions, or RLS policies — any schema change targeting a shared or production database
Use when facing two or more independent investigations or research tasks in the current session — debugging multiple unrelated failures, exploring different solution approaches, or running parallel reads. Not for executing implementation plans (use subagent-driven-development, agent-team-development, or tmux-parallel-development for those).
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
| name | using-globalcoder-marketing |
| description | Use when starting any conversation involving marketing, branding, product launches, positioning, content creation, or go-to-market strategy - routes to the correct marketing skill |
Entry point for the globalcoder-marketing plugin. Routes to the correct skill based on user intent.
Invoke relevant marketing skills BEFORE any response. If the user's task involves marketing, branding, launching, positioning, or content - check this routing table.
digraph routing {
rankdir=LR;
"User intent" [shape=doublecircle];
"Audience / market" [shape=box, label="market-research"];
"Buyer profiles" [shape=box, label="customer-personas"];
"Name / voice / brand" [shape=box, label="brand-identity"];
"Messaging / value prop" [shape=box, label="positioning-strategy"];
"Launch timeline / GTM" [shape=box, label="launch-plan"];
"Content planning" [shape=box, label="content-strategy"];
"Landing page" [shape=box, label="landing-page"];
"Email / social / ads" [shape=box, label="campaign-builder"];
"Post-launch review" [shape=box, label="launch-retrospective"];
"User intent" -> "Audience / market" [label="who's the market?"];
"User intent" -> "Buyer profiles" [label="who are we selling to?"];
"User intent" -> "Name / voice / brand" [label="what's our brand?"];
"User intent" -> "Messaging / value prop" [label="how do we position?"];
"User intent" -> "Launch timeline / GTM" [label="plan the launch"];
"User intent" -> "Content planning" [label="what content?"];
"User intent" -> "Landing page" [label="build landing page"];
"User intent" -> "Email / social / ads" [label="create campaigns"];
"User intent" -> "Post-launch review" [label="how did it go?"];
}
market-research → customer-personas → brand-identity → positioning-strategy → launch-plan → content-strategy → landing-page / campaign-builder → launch-retrospective
All skills also work standalone. Each reads upstream docs from docs/marketing/ if they exist.
Every skill that produces artifacts asks at the start:
What output depth for this session?
- Minimal - Markdown documents only
- Full - Markdown + code artifacts (structured data, templates, components)
This plugin works alongside globalcoder-workflow. Skills that produce actionable plans suggest:
"Use
globalcoder-workflow:writing-plansto break this into executable tasks."
No hard dependency. Suggestion only.