Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

nexus-marketing-growth

Estrelas6

Forks0

Atualizado2 de março de 2026 às 20:05

Guidelines for generating marketing copy, Reddit posts, Hacker News launches, and growth strategies for Project Nexus. Use this skill when asked to write public-facing content, launch announcements, or analyze product-market fit.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

MAX-786

MAX-786/project-nexus

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de pesquisa de mercado e especialistas em marketingNegócios e Operações Financeiras·SOC 13-1161

SKILL.md

readonly

name	nexus-marketing-growth
description	Guidelines for generating marketing copy, Reddit posts, Hacker News launches, and growth strategies for Project Nexus. Use this skill when asked to write public-facing content, launch announcements, or analyze product-market fit.

Project Nexus: Marketing & Growth Protocol

1. The Source of Truth (Mandatory First Step)

Action: Before writing ANY marketing content, you MUST read the README.md file in the project root to understand the current, live feature set. Do not hallucinate features that have not been built yet. If a feature is in the PRD but not the README, clearly label it as "Coming Soon" or "On the Roadmap."

2. Core Messaging Pillars (What to Emphasize)

Privacy & Control (BYOK): "Your Second Brain. Not Big Tech's." Emphasize that users bring their own API keys and own their database.
Frictionless Capture: No context switching. Save and summarize without leaving the video or article.
The Graph: It’s not a digital graveyard; it auto-links concepts visually.
Active Recall: Saving is useless without remembering. Highlight the gamified Tinder-style spaced repetition.

3. Brand Tone & Voice

Authentic & Humble: We are building in public. Acknowledge that this is an early prototype/MVP. Ask for feedback, do not demand adoption.
Anti-Marketing Fluff: Avoid words like "Revolutionary," "Game-changing," or "Ultimate." Developers and productivity nerds hate corporate speak.
Technical Transparency: Be open about the stack (Next.js, Supabase, pgvector, Plasmo) and the challenges of building it.

4. Platform-Specific Playbooks

A. Reddit (e.g., r/opensource, r/selfhosted, r/productivity, r/PKMS)

Format: Start with a clear, relatable problem statement. "I was tired of saving 100 links a week and never reading them..."
Rule: Do not write a sales pitch. Frame the post as a "Show and Tell" or a request for genuine architectural/feature feedback.
Content: Include a GitHub link, invite people to roast the code, and explicitly ask if they would use a self-hosted version vs. a managed cloud version.

B. Hacker News (Show HN)

Format: Deeply technical. Explain how the vector search works and why you chose the BYOK model.
Rule: Anticipate skepticism about LLM costs and data privacy. Address them proactively in the first comment.

C. Build-in-Public (X / Twitter / LinkedIn)

Format: Short, visual milestones. "Today I got the React Flow nodes auto-linking based on vector similarity."
Rule: Always include a screenshot, GIF, or a code snippet showing the feature in action.

5. Community Engagement

When generating responses to hypothetical user comments, default to thanking them for the feedback, agreeing with valid critiques, and adding their suggestions to the open-source issue tracker.

Mais deste repositório

mesmo repositório

nexus-docs-manager

MAX-786/project-nexus

Rules for creating, updating, and managing project documentation. Use this skill when analyzing Git commits, updating the README, writing API specs, or acting as the Technical Writer for Project Nexus.

2026-03-096

nexus-github-cli

MAX-786/project-nexus

Act as an autonomous project manager and lead developer. Use the GitHub CLI (`gh`) to orchestrate the entire development lifecycle: tracking tasks on Project Boards, organizing Sprints via Milestones, documenting progress via Issue Comments, and executing code changes via Pull Requests.

2026-03-046

nexus-code-quality

MAX-786/project-nexus

Rules for ESLint, Prettier, and TypeScript strictness. Use this skill when writing new files, refactoring code, or debugging build failures caused by type errors.

2026-03-046

nexus-deployments

MAX-786/project-nexus

Deployment protocols for Vercel (Next.js Web App), Chrome Web Store packaging (Plasmo Extension), and Supabase production migrations. Use this when setting up CI/CD, preparing a release, or configuring deployment environment variables.

2026-03-046

nexus-git-workflow

MAX-786/project-nexus

Guidelines for Git branching, commit messages (Conventional Commits), and Pull Request structures. Use this skill when asked to commit code, create a branch, or write a PR description.

2026-03-046

nexus-nextjs-dev

MAX-786/project-nexus

Guidelines for writing Next.js App Router frontend code, using Shadcn UI, and TailwindCSS for Project Nexus. Use this when creating or modifying UI components, pages, or client/server interactions.

2026-03-026

name	nexus-marketing-growth
description	Guidelines for generating marketing copy, Reddit posts, Hacker News launches, and growth strategies for Project Nexus. Use this skill when asked to write public-facing content, launch announcements, or analyze product-market fit.

Project Nexus: Marketing & Growth Protocol

1. The Source of Truth (Mandatory First Step)

Action: Before writing ANY marketing content, you MUST read the README.md file in the project root to understand the current, live feature set. Do not hallucinate features that have not been built yet. If a feature is in the PRD but not the README, clearly label it as "Coming Soon" or "On the Roadmap."

2. Core Messaging Pillars (What to Emphasize)

Privacy & Control (BYOK): "Your Second Brain. Not Big Tech's." Emphasize that users bring their own API keys and own their database.
Frictionless Capture: No context switching. Save and summarize without leaving the video or article.
The Graph: It’s not a digital graveyard; it auto-links concepts visually.
Active Recall: Saving is useless without remembering. Highlight the gamified Tinder-style spaced repetition.

3. Brand Tone & Voice

Authentic & Humble: We are building in public. Acknowledge that this is an early prototype/MVP. Ask for feedback, do not demand adoption.
Anti-Marketing Fluff: Avoid words like "Revolutionary," "Game-changing," or "Ultimate." Developers and productivity nerds hate corporate speak.
Technical Transparency: Be open about the stack (Next.js, Supabase, pgvector, Plasmo) and the challenges of building it.

4. Platform-Specific Playbooks

A. Reddit (e.g., r/opensource, r/selfhosted, r/productivity, r/PKMS)

Format: Start with a clear, relatable problem statement. "I was tired of saving 100 links a week and never reading them..."
Rule: Do not write a sales pitch. Frame the post as a "Show and Tell" or a request for genuine architectural/feature feedback.
Content: Include a GitHub link, invite people to roast the code, and explicitly ask if they would use a self-hosted version vs. a managed cloud version.

B. Hacker News (Show HN)

Format: Deeply technical. Explain how the vector search works and why you chose the BYOK model.
Rule: Anticipate skepticism about LLM costs and data privacy. Address them proactively in the first comment.

C. Build-in-Public (X / Twitter / LinkedIn)

Format: Short, visual milestones. "Today I got the React Flow nodes auto-linking based on vector similarity."
Rule: Always include a screenshot, GIF, or a code snippet showing the feature in action.

5. Community Engagement

When generating responses to hypothetical user comments, default to thanking them for the feedback, agreeing with valid critiques, and adding their suggestions to the open-source issue tracker.