القائمة
Use when creating a landing page - guides copy, page structure, CTA strategy, and optionally generates code using the project's UI framework
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | landing-page |
| description | Use when creating a landing page - guides copy, page structure, CTA strategy, and optionally generates code using the project's UI framework |
Create landing page copy, structure, and CTA strategy. In full mode, generates actual code using the project's existing UI framework.
Announce at start: "I'm using the landing-page skill to build the page."
Step 1: Context gathering
docs/marketing/positioning-strategy.md (primary input - value prop, messaging matrix)Step 2: Scoping questions (one at a time)
Step 3: Draft section by section
Present each section for validation before moving to next:
Step 4: Write output
docs/marketing/landing-page.md with all copy blocks and page structureStep 5: Handoff
globalcoder-marketing:campaign-builder to drive traffic to the pageUse 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