Orchestrate app launch preparation - SEO, screenshots, personas, ads, articles, landing pages
Orchestrates complete app launch preparation including SEO, screenshots, personas, ads, articles, and landing pages. Use `/post-dev run` after development to generate all marketing materials automatically.
/plugin marketplace add mwguerra/claude-code-plugins/plugin install post-development@mwguerra-marketplaceThis skill is limited to using the following tools:
This skill enables comprehensive post-development preparation for app launches, including marketing materials, SEO, and content generation.
Use this skill when:
/pd-seo)/pd-screenshots)/pd-personas)/pd-ads)/pd-articles)/pd-landing)/post-dev init --base-url http://localhost:3000
/post-dev run
/post-dev run --task seo
/post-dev status
.post-development/
├── post-development.json # Master plan
├── seo/
│ ├── pages/ # SEO data per page
│ └── assets/ # Favicon, OG image specs
├── screenshots/
│ ├── desktop/
│ ├── tablet/
│ └── mobile/
├── personas/
│ ├── personas/ # Individual persona files
│ ├── strategies/ # Marketing strategies
│ └── cta/ # CTA collections
├── ads/
│ ├── instagram/
│ ├── facebook/
│ ├── linkedin/
│ └── twitter/
├── articles/
│ ├── article-1/
│ ├── article-2/
│ └── article-3/
└── landing-pages/
└── [persona-name]/
Tasks run in dependency order:
seo → no dependenciesscreenshots → no dependenciespersonas → depends on seoads → depends on personas, screenshotsarticles → depends on personas, screenshotslanding → depends on personas, screenshots, articlesnpm install -D playwright)# 1. Initialize project
/post-dev init --base-url http://localhost:3000
# 2. Run everything
/post-dev run
# 3. Or run tasks individually
/post-dev seo
/post-dev screenshots
/post-dev personas
/post-dev ads
/post-dev articles
/post-dev landing
# 4. Check progress anytime
/post-dev status
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.