claude-code-marketing-quickstart
matteotitta/claude-code-marketing-quickstart/CLAUDE.md
This is a marketing workspace for one company. Read this file first.
One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
matteotitta/claude-code-marketing-quickstart/CLAUDE.md
This is a marketing workspace for one company. Read this file first.
matteotitta/claude-code-marketing-quickstart/.claude/skills/competitor-research/SKILL.md
Researches one B2B SaaS competitor across 13 dimensions (company, product, ICP, pricing, reviews, content, launches, search and AI visibility, tech stack, hiring, go-to-market, social, paid ads) and writes a sourced dossier with an executive summary, a threat level, strengths and weaknesses, and a data gaps section. Run it once per competitor, then compare. Triggers: "competitor analysis", "competitor research on", "what is [competitor] doing", "compare us to", "competitive landscape", "battlecard prep". Run after /company-context and /icp-research. Not for researching your own company (use /company-context).
Often used withtov-guidelinesicp-research
matteotitta/claude-code-marketing-quickstart/.claude/skills/icp-research/SKILL.md
Builds an ideal customer profile from evidence: case studies, testimonials, customer logos, solutions pages, reviews and any sales notes you have. Produces market sizing layers, firmographic segments, a champion and an economic buyer persona, a negative ICP, intent signals, customer proof points and a voice-of-customer section in the buyers' own words, every claim sourced. Triggers: "ICP research", "ideal customer profile", "who are our customers", "customer segments", "buyer personas", "who should we target". Run after /company-context. Not for competitor analysis (use /competitor-research) or call transcript patterns (use /win-loss).
Often used withtov-guidelinescompetitor-research
matteotitta/claude-code-marketing-quickstart/.claude/skills/level/SKILL.md
Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity
matteotitta/claude-code-marketing-quickstart/.claude/skills/messaging/SKILL.md
Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).
matteotitta/claude-code-marketing-quickstart/.claude/skills/positioning/SKILL.md
Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).
matteotitta/claude-code-marketing-quickstart/.claude/skills/tov-guidelines/SKILL.md
Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).
matteotitta/claude-code-marketing-quickstart/context/CLAUDE.md
Every skill reads these folders before it writes anything. Fill them in this order: ICP, competitors, voice, positioning, messaging. Win-loss, founder POV, brand kit, funnel and goals are in the paid context plugin ($19.99, link in the README), when you want them. Keep one current file per topic (for example positioning.md) and date the research behind it (1026-competitor-acme.md). See ../example/pulse-analytics/context for a filled-in version.
matteotitta/claude-code-marketing-quickstart/outputs/CLAUDE.md
One folder per lane. Skills read context/ first and save here, named MMYY-topic.md.
matteotitta/genesys-skills/skills/research/brand-kit/SKILL.md
Extracts visual identity from screenshots (primary) or website URLs (fallback) and compiles into a DESIGN.md-format
matteotitta/genesys-skills/skills/research/company-context/SKILL.md
Gathers firmographics, traction signals, funding history, team composition, tech stack, hiring activity, and
matteotitta/genesys-skills/skills/research/competitor-research/SKILL.md
Performs deep 13-dimension competitor analysis with quantitative scoring rubric. Produces a competitor dossier
Often used withicp-research
matteotitta/genesys-skills/skills/research/customer-interviews/SKILL.md
Generates structured interview guides for five B2B SaaS research types: discovery, win/loss, churn, expansion,
matteotitta/genesys-skills/skills/research/expert-pov/SKILL.md
Extracts contrarian beliefs, market perspectives, and philosophical stances from founder interviews or questionnaire
matteotitta/genesys-skills/skills/research/funnel-strategy/SKILL.md
Maps a company''s GTM motion (PLG, SLG, or Hybrid) to concrete funnel stages with inputs, outputs, and qualification
matteotitta/genesys-skills/skills/research/icp-behavioural/SKILL.md
Creates synthetic buyer personas that simulate real purchase decisions, then runs those personas through website
matteotitta/genesys-skills/skills/research/icp-research/SKILL.md
Scrapes case studies, testimonials, and solutions pages from a target website to build structured ICP documentation.
matteotitta/genesys-skills/skills/research/marketing-team-tracker/SKILL.md
Maintains a curated roster of best-in-class marketing teams and harvests their most stealable plays on demand, each classified against five repeatable patterns (product-as-marketing, characters-and-series, community-as-distribution, weird-creative, pick-a-fight). Resolves each team's surfaces, scans for plays shipped since the last scan, ranks by engagement, and emits a dated marketing-plays brief plus an append-only swipe file and a living roster. Triggers: "track marketing teams", "marketing inspiration scan", "marketing swipe file", "what's X doing in marketing", "add X to the marketing tracker". Upstream: recommended signal-scan. Downstream: feeds content-strategy, marketing-ideas, thought-leadership, gtme-pulse, linkedin-weekly-content. NOT for competitor threat analysis (use /competitor-research), per-account buying signals (use /niche-signal), or one-off ideation from a brief (use /marketing-ideas).
matteotitta/genesys-skills/skills/research/read-book/SKILL.md
Reads a book or long PDF and extracts structured, reusable notes — chunks
matteotitta/genesys-skills/skills/research/signal-scan/SKILL.md
Produces a topic-agnostic "what happened in the last N days" signal brief for any person, company, product, technology, or market term — ranked by engagement (upvotes, likes, views, stars, market odds) rather than SEO. Resolves entities before searching, expands to peer communities, clusters the same story across surfaces, and fans out across Reddit, Hacker News, news/funding, GitHub, G2/Trustpilot/Product Hunt, and YouTube (with X/TikTok/Instagram/Polymarket behind credit-gated flags). Triggers: "what happened with X in the last 30 days", "recent activity on", "what's new with", "signal scan on", "last 30 days". Upstream: recommended company-context. Downstream: feeds competitor-research, gtme-pulse, content-strategy, client-discovery. NOT for internal decision history (use /think), session recall (use /recall), a deep static competitor dossier (use /competitor-research), or a curated newsletter from pre-collected links (use /gtme-pulse).
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.