@funnycode/myclaude 0.1.70 → 0.1.72

package/seed/marketplaces/ecc/commands/marketing-campaign.md

@@ -1,129 +1,129 @@
----
-description: Plan and execute a full marketing campaign. Accepts a product brief and returns positioning, landing page copy, email sequence, social posts, ad variants, video scripts, and a content calendar. Can also review existing copy for conversion quality.
-allowed_tools: ["Read", "Grep", "Glob", "WebSearch", "WebFetch", "Write"]
----
-
-# /marketing-campaign
-
-Plan and execute a marketing campaign from brief to full content suite.
-
-## Usage
-
-```
-/marketing-campaign                          # Prompt for brief interactively
-/marketing-campaign [product brief]          # Full campaign from inline brief
-/marketing-campaign copy [type]              # Single deliverable only
-/marketing-campaign review [file-or-brief]   # Copy audit for conversion and brand consistency
-```
-
-## What It Does
-
-1. **Research** — Profiles the target audience and maps competitors before writing anything
-2. **Positioning** — Locks the campaign angle and tone profile first
-3. **Copy production** — Generates the full content suite in the right order (landing page → emails → social → ads → video scripts → calendar)
-4. **Review** — Gates all output through a conversion and brand consistency checklist
-
-## Modes
-
-### Full Campaign Mode
-
-Provide a product brief containing:
-- Product name and description
-- Target audience (specific, not generic)
-- Core problem the product solves
-- Core benefit / outcome
-- Tone guidance
-- Channels required
-- Launch goal or timeline
-
-The agent returns all campaign deliverables in order, with a copy review summary at the end.
-
-### Single Deliverable Mode
-
-```
-/marketing-campaign copy landing-page
-/marketing-campaign copy email-sequence
-/marketing-campaign copy social-posts
-/marketing-campaign copy ads
-/marketing-campaign copy video-scripts
-```
-
-Requires positioning to be defined first. Run full mode or provide the angle before requesting a single deliverable.
-
-### Copy Review Mode
-
-```
-/marketing-campaign review path/to/copy.md
-/marketing-campaign review "paste copy here"
-```
-
-Returns a structured audit against:
-- 5-second clarity test (above-fold copy)
-- CTA quality (specific, earned, one per piece)
-- Brand tone consistency
-- Claim specificity and supportability
-- Platform-native fit
-- Cross-channel consistency
-
-## Brief Template
-
-```markdown
-Product: [name]
-Description: [1-3 sentences on what it does]
-Audience: [who, specifically]
-Problem: [the specific pain the product solves]
-Benefit: [the outcome the user gets]
-Tone: [adjectives + what to avoid]
-Channels: [landing page, email, LinkedIn, X, ads, video]
-Goal: [launch, waitlist, signups, awareness — and timeline]
-```
-
-## Output Location
-
-When saving campaign assets, the convention is `.claude/campaigns/{campaign-name}/`:
-
-```
-.claude/campaigns/product-launch/
-├── positioning.md
-├── landing-page.md
-├── email-sequence.md
-├── social-posts.md
-├── ad-copy.md
-├── video-scripts.md
-└── content-calendar.md
-```
-
-Confirm the save location before writing files.
-
-## Examples
-
-```
-/marketing-campaign Build a 7-day launch campaign for an AI career platform for UK university students.
-```
-
-```
-/marketing-campaign copy landing-page
-```
-
-```
-/marketing-campaign review .claude/campaigns/the-key/landing-page.md
-```
-
-## Agent Delegation
-
-This command invokes:
-- `marketing-agent` — campaign planning and copy production
-- `brand-voice` — voice capture when tone needs locking across multiple outputs
-- `content-engine` — platform-native social content production
-- `crosspost` — multi-platform distribution
-- `market-research` — deep audience or competitive intelligence
-
-## Related Commands
-
-- `/plan` — Strategic planning before a campaign
-- `/plan-prd` — Product requirements document before briefing a campaign
-- `/code-review` — Review code behind a landing page implementation
-
----
-
-*Part of [Everything Claude Code](https://github.com/affaan-m/everything-claude-code)*
+---
+description: Plan and execute a full marketing campaign. Accepts a product brief and returns positioning, landing page copy, email sequence, social posts, ad variants, video scripts, and a content calendar. Can also review existing copy for conversion quality.
+allowed_tools: ["Read", "Grep", "Glob", "WebSearch", "WebFetch", "Write"]
+---
+
+# /marketing-campaign
+
+Plan and execute a marketing campaign from brief to full content suite.
+
+## Usage
+
+```
+/marketing-campaign                          # Prompt for brief interactively
+/marketing-campaign [product brief]          # Full campaign from inline brief
+/marketing-campaign copy [type]              # Single deliverable only
+/marketing-campaign review [file-or-brief]   # Copy audit for conversion and brand consistency
+```
+
+## What It Does
+
+1. **Research** — Profiles the target audience and maps competitors before writing anything
+2. **Positioning** — Locks the campaign angle and tone profile first
+3. **Copy production** — Generates the full content suite in the right order (landing page → emails → social → ads → video scripts → calendar)
+4. **Review** — Gates all output through a conversion and brand consistency checklist
+
+## Modes
+
+### Full Campaign Mode
+
+Provide a product brief containing:
+- Product name and description
+- Target audience (specific, not generic)
+- Core problem the product solves
+- Core benefit / outcome
+- Tone guidance
+- Channels required
+- Launch goal or timeline
+
+The agent returns all campaign deliverables in order, with a copy review summary at the end.
+
+### Single Deliverable Mode
+
+```
+/marketing-campaign copy landing-page
+/marketing-campaign copy email-sequence
+/marketing-campaign copy social-posts
+/marketing-campaign copy ads
+/marketing-campaign copy video-scripts
+```
+
+Requires positioning to be defined first. Run full mode or provide the angle before requesting a single deliverable.
+
+### Copy Review Mode
+
+```
+/marketing-campaign review path/to/copy.md
+/marketing-campaign review "paste copy here"
+```
+
+Returns a structured audit against:
+- 5-second clarity test (above-fold copy)
+- CTA quality (specific, earned, one per piece)
+- Brand tone consistency
+- Claim specificity and supportability
+- Platform-native fit
+- Cross-channel consistency
+
+## Brief Template
+
+```markdown
+Product: [name]
+Description: [1-3 sentences on what it does]
+Audience: [who, specifically]
+Problem: [the specific pain the product solves]
+Benefit: [the outcome the user gets]
+Tone: [adjectives + what to avoid]
+Channels: [landing page, email, LinkedIn, X, ads, video]
+Goal: [launch, waitlist, signups, awareness — and timeline]
+```
+
+## Output Location
+
+When saving campaign assets, the convention is `.claude/campaigns/{campaign-name}/`:
+
+```
+.claude/campaigns/product-launch/
+├── positioning.md
+├── landing-page.md
+├── email-sequence.md
+├── social-posts.md
+├── ad-copy.md
+├── video-scripts.md
+└── content-calendar.md
+```
+
+Confirm the save location before writing files.
+
+## Examples
+
+```
+/marketing-campaign Build a 7-day launch campaign for an AI career platform for UK university students.
+```
+
+```
+/marketing-campaign copy landing-page
+```
+
+```
+/marketing-campaign review .claude/campaigns/the-key/landing-page.md
+```
+
+## Agent Delegation
+
+This command invokes:
+- `marketing-agent` — campaign planning and copy production
+- `brand-voice` — voice capture when tone needs locking across multiple outputs
+- `content-engine` — platform-native social content production
+- `crosspost` — multi-platform distribution
+- `market-research` — deep audience or competitive intelligence
+
+## Related Commands
+
+- `/plan` — Strategic planning before a campaign
+- `/plan-prd` — Product requirements document before briefing a campaign
+- `/code-review` — Review code behind a landing page implementation
+
+---
+
+*Part of [Everything Claude Code](https://github.com/affaan-m/everything-claude-code)*

package/seed/marketplaces/ecc/commands/model-route.md

@@ -1,30 +1,30 @@
----
-description: Recommend the best model tier for the current task based on complexity, risk, and budget.
----
-
-# Model Route Command
-
-Recommend the best model tier for the current task by complexity and budget.
-
-## Usage
-
-`/model-route [task-description] [--budget low|med|high]`
-
-## Routing Heuristic
-
-- `haiku`: deterministic, low-risk mechanical changes
-- `sonnet`: default for implementation and refactors
-- `opus`: architecture, deep review, ambiguous requirements
-
-## Required Output
-
-- recommended model
-- confidence level
-- why this model fits
-- fallback model if first attempt fails
-
-## Arguments
-
-$ARGUMENTS:
-- `[task-description]` optional free-text
-- `--budget low|med|high` optional
+---
+description: Recommend the best model tier for the current task based on complexity, risk, and budget.
+---
+
+# Model Route Command
+
+Recommend the best model tier for the current task by complexity and budget.
+
+## Usage
+
+`/model-route [task-description] [--budget low|med|high]`
+
+## Routing Heuristic
+
+- `haiku`: deterministic, low-risk mechanical changes
+- `sonnet`: default for implementation and refactors
+- `opus`: architecture, deep review, ambiguous requirements
+
+## Required Output
+
+- recommended model
+- confidence level
+- why this model fits
+- fallback model if first attempt fails
+
+## Arguments
+
+$ARGUMENTS:
+- `[task-description]` optional free-text
+- `--budget low|med|high` optional

package/seed/marketplaces/ecc/commands/multi-backend.md

@@ -1,162 +1,162 @@
----
-description: Run a backend-focused multi-model workflow for APIs, algorithms, data, and business logic.
----
-
-# Backend - Backend-Focused Development
-
-Backend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Codex-led.
-
-## Usage
-
-```bash
-/backend <backend task description>
-```
-
-## Context
-
-- Backend task: $ARGUMENTS
-- Codex-led, Gemini for auxiliary reference
-- Applicable: API design, algorithm implementation, database optimization, business logic
-
-## Your Role
-
-You are the **Backend Orchestrator**, coordinating multi-model collaboration for server-side tasks (Research → Ideation → Plan → Execute → Optimize → Review).
-
-**Collaborative Models**:
-- **Codex** – Backend logic, algorithms (**Backend authority, trustworthy**)
-- **Gemini** – Frontend perspective (**Backend opinions for reference only**)
-- **Claude (self)** – Orchestration, planning, execution, delivery
-
----
-
-## Multi-Model Call Specification
-
-**Call Syntax**:
-
-```
-# New session call
-Bash({
-  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend codex - \"$PWD\" <<'EOF'
-ROLE_FILE: <role prompt path>
-<TASK>
-Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
-Context: <project context and analysis from previous phases>
-</TASK>
-OUTPUT: Expected output format
-EOF",
-  run_in_background: false,
-  timeout: 3600000,
-  description: "Brief description"
-})
-
-# Resume session call
-Bash({
-  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend codex resume <SESSION_ID> - \"$PWD\" <<'EOF'
-ROLE_FILE: <role prompt path>
-<TASK>
-Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
-Context: <project context and analysis from previous phases>
-</TASK>
-OUTPUT: Expected output format
-EOF",
-  run_in_background: false,
-  timeout: 3600000,
-  description: "Brief description"
-})
-```
-
-**Role Prompts**:
-
-| Phase | Codex |
-|-------|-------|
-| Analysis | `~/.claude/.ccg/prompts/codex/analyzer.md` |
-| Planning | `~/.claude/.ccg/prompts/codex/architect.md` |
-| Review | `~/.claude/.ccg/prompts/codex/reviewer.md` |
-
-**Session Reuse**: Each call returns `SESSION_ID: xxx`, use `resume xxx` for subsequent phases. Save `CODEX_SESSION` in Phase 2, use `resume` in Phases 3 and 5.
-
----
-
-## Communication Guidelines
-
-1. Start responses with mode label `[Mode: X]`, initial is `[Mode: Research]`
-2. Follow strict sequence: `Research → Ideation → Plan → Execute → Optimize → Review`
-3. Use `AskUserQuestion` tool for user interaction when needed (e.g., confirmation/selection/approval)
-
----
-
-## Core Workflow
-
-### Phase 0: Prompt Enhancement (Optional)
-
-`[Mode: Prepare]` - If ace-tool MCP available, call `mcp__ace-tool__enhance_prompt`, **replace original $ARGUMENTS with enhanced result for subsequent Codex calls**. If unavailable, use `$ARGUMENTS` as-is.
-
-### Phase 1: Research
-
-`[Mode: Research]` - Understand requirements and gather context
-
-1. **Code Retrieval** (if ace-tool MCP available): Call `mcp__ace-tool__search_context` to retrieve existing APIs, data models, service architecture. If unavailable, use built-in tools: `Glob` for file discovery, `Grep` for symbol/API search, `Read` for context gathering, `Task` (Explore agent) for deeper exploration.
-2. Requirement completeness score (0-10): >=7 continue, <7 stop and supplement
-
-### Phase 2: Ideation
-
-`[Mode: Ideation]` - Codex-led analysis
-
-**MUST call Codex** (follow call specification above):
-- ROLE_FILE: `~/.claude/.ccg/prompts/codex/analyzer.md`
-- Requirement: Enhanced requirement (or $ARGUMENTS if not enhanced)
-- Context: Project context from Phase 1
-- OUTPUT: Technical feasibility analysis, recommended solutions (at least 2), risk assessment
-
-**Save SESSION_ID** (`CODEX_SESSION`) for subsequent phase reuse.
-
-Output solutions (at least 2), wait for user selection.
-
-### Phase 3: Planning
-
-`[Mode: Plan]` - Codex-led planning
-
-**MUST call Codex** (use `resume <CODEX_SESSION>` to reuse session):
-- ROLE_FILE: `~/.claude/.ccg/prompts/codex/architect.md`
-- Requirement: User's selected solution
-- Context: Analysis results from Phase 2
-- OUTPUT: File structure, function/class design, dependency relationships
-
-Claude synthesizes plan, save to `.claude/plan/task-name.md` after user approval.
-
-### Phase 4: Implementation
-
-`[Mode: Execute]` - Code development
-
-- Strictly follow approved plan
-- Follow existing project code standards
-- Ensure error handling, security, performance optimization
-
-### Phase 5: Optimization
-
-`[Mode: Optimize]` - Codex-led review
-
-**MUST call Codex** (follow call specification above):
-- ROLE_FILE: `~/.claude/.ccg/prompts/codex/reviewer.md`
-- Requirement: Review the following backend code changes
-- Context: git diff or code content
-- OUTPUT: Security, performance, error handling, API compliance issues list
-
-Integrate review feedback, execute optimization after user confirmation.
-
-### Phase 6: Quality Review
-
-`[Mode: Review]` - Final evaluation
-
-- Check completion against plan
-- Run tests to verify functionality
-- Report issues and recommendations
-
----
-
-## Key Rules
-
-1. **Codex backend opinions are trustworthy**
-2. **Gemini backend opinions for reference only**
-3. External models have **zero filesystem write access**
-4. Claude handles all code writes and file operations
+---
+description: Run a backend-focused multi-model workflow for APIs, algorithms, data, and business logic.
+---
+
+# Backend - Backend-Focused Development
+
+Backend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Codex-led.
+
+## Usage
+
+```bash
+/backend <backend task description>
+```
+
+## Context
+
+- Backend task: $ARGUMENTS
+- Codex-led, Gemini for auxiliary reference
+- Applicable: API design, algorithm implementation, database optimization, business logic
+
+## Your Role
+
+You are the **Backend Orchestrator**, coordinating multi-model collaboration for server-side tasks (Research → Ideation → Plan → Execute → Optimize → Review).
+
+**Collaborative Models**:
+- **Codex** – Backend logic, algorithms (**Backend authority, trustworthy**)
+- **Gemini** – Frontend perspective (**Backend opinions for reference only**)
+- **Claude (self)** – Orchestration, planning, execution, delivery
+
+---
+
+## Multi-Model Call Specification
+
+**Call Syntax**:
+
+```
+# New session call
+Bash({
+  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend codex - \"$PWD\" <<'EOF'
+ROLE_FILE: <role prompt path>
+<TASK>
+Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
+Context: <project context and analysis from previous phases>
+</TASK>
+OUTPUT: Expected output format
+EOF",
+  run_in_background: false,
+  timeout: 3600000,
+  description: "Brief description"
+})
+
+# Resume session call
+Bash({
+  command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend codex resume <SESSION_ID> - \"$PWD\" <<'EOF'
+ROLE_FILE: <role prompt path>
+<TASK>
+Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
+Context: <project context and analysis from previous phases>
+</TASK>
+OUTPUT: Expected output format
+EOF",
+  run_in_background: false,
+  timeout: 3600000,
+  description: "Brief description"
+})
+```
+
+**Role Prompts**:
+
+| Phase | Codex |
+|-------|-------|
+| Analysis | `~/.claude/.ccg/prompts/codex/analyzer.md` |
+| Planning | `~/.claude/.ccg/prompts/codex/architect.md` |
+| Review | `~/.claude/.ccg/prompts/codex/reviewer.md` |
+
+**Session Reuse**: Each call returns `SESSION_ID: xxx`, use `resume xxx` for subsequent phases. Save `CODEX_SESSION` in Phase 2, use `resume` in Phases 3 and 5.
+
+---
+
+## Communication Guidelines
+
+1. Start responses with mode label `[Mode: X]`, initial is `[Mode: Research]`
+2. Follow strict sequence: `Research → Ideation → Plan → Execute → Optimize → Review`
+3. Use `AskUserQuestion` tool for user interaction when needed (e.g., confirmation/selection/approval)
+
+---
+
+## Core Workflow
+
+### Phase 0: Prompt Enhancement (Optional)
+
+`[Mode: Prepare]` - If ace-tool MCP available, call `mcp__ace-tool__enhance_prompt`, **replace original $ARGUMENTS with enhanced result for subsequent Codex calls**. If unavailable, use `$ARGUMENTS` as-is.
+
+### Phase 1: Research
+
+`[Mode: Research]` - Understand requirements and gather context
+
+1. **Code Retrieval** (if ace-tool MCP available): Call `mcp__ace-tool__search_context` to retrieve existing APIs, data models, service architecture. If unavailable, use built-in tools: `Glob` for file discovery, `Grep` for symbol/API search, `Read` for context gathering, `Task` (Explore agent) for deeper exploration.
+2. Requirement completeness score (0-10): >=7 continue, <7 stop and supplement
+
+### Phase 2: Ideation
+
+`[Mode: Ideation]` - Codex-led analysis
+
+**MUST call Codex** (follow call specification above):
+- ROLE_FILE: `~/.claude/.ccg/prompts/codex/analyzer.md`
+- Requirement: Enhanced requirement (or $ARGUMENTS if not enhanced)
+- Context: Project context from Phase 1
+- OUTPUT: Technical feasibility analysis, recommended solutions (at least 2), risk assessment
+
+**Save SESSION_ID** (`CODEX_SESSION`) for subsequent phase reuse.
+
+Output solutions (at least 2), wait for user selection.
+
+### Phase 3: Planning
+
+`[Mode: Plan]` - Codex-led planning
+
+**MUST call Codex** (use `resume <CODEX_SESSION>` to reuse session):
+- ROLE_FILE: `~/.claude/.ccg/prompts/codex/architect.md`
+- Requirement: User's selected solution
+- Context: Analysis results from Phase 2
+- OUTPUT: File structure, function/class design, dependency relationships
+
+Claude synthesizes plan, save to `.claude/plan/task-name.md` after user approval.
+
+### Phase 4: Implementation
+
+`[Mode: Execute]` - Code development
+
+- Strictly follow approved plan
+- Follow existing project code standards
+- Ensure error handling, security, performance optimization
+
+### Phase 5: Optimization
+
+`[Mode: Optimize]` - Codex-led review
+
+**MUST call Codex** (follow call specification above):
+- ROLE_FILE: `~/.claude/.ccg/prompts/codex/reviewer.md`
+- Requirement: Review the following backend code changes
+- Context: git diff or code content
+- OUTPUT: Security, performance, error handling, API compliance issues list
+
+Integrate review feedback, execute optimization after user confirmation.
+
+### Phase 6: Quality Review
+
+`[Mode: Review]` - Final evaluation
+
+- Check completion against plan
+- Run tests to verify functionality
+- Report issues and recommendations
+
+---
+
+## Key Rules
+
+1. **Codex backend opinions are trustworthy**
+2. **Gemini backend opinions for reference only**
+3. External models have **zero filesystem write access**
+4. Claude handles all code writes and file operations