matteotitta
- 169 skills
- 0 followers
- 13 hours ago last updated
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ PPTX · matteotittaBrand-agnostic PowerPoint renderer. Applies any client's brand kit (or Genesys's own kit) to a slide outline and produces a styled.pptx. Resolves brand via a 5-layer waterfall (--brand-kit-path → client kit → Genesys kit → gdrive-config → fallback). Reads the FULL DESIGN.md token surface — colors, typography, spacing, rounded, components, signature elements, presentation guidance, voice overrides — and applies them through a 12-type slide grammar bound to a locked grid system. Inherits the design library at composition time: impeccable banned-pattern guards, design-reviewer scoring phases, quantitative budgets (≤2 brand colors per slide, ≤2 font weights per slide, one primary per slide). Same render code path produces a ClientCo deck, an ClientCo deck, or a Genesys deck — only the resolved BrandConfig differs. Takes outlines from /sales-deck, /proposal, /webinar, /product-launch, /case-study, or authored manually. NOT for: writing the outline (that's the upstream author skills), Google Slides (use create-slid
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Team Hiring · matteotittaGenerate the canonical Genesys hiring artefacts end-to-end. Mode A produces the sourcing 3-pack (JD + interview process + LinkedIn hiring post) plus an optional public careers page. Mode B produces per-batch operational artefacts (interview hub per role per sprint) and per-candidate Stage-1 outputs (scorecard from Granola transcript + advance email or decline note). Calibrated to a specific client (or Genesys-internal) context. Pulls voice, positioning, traction, ICP, team structure, and brand rules from the client's CLAUDE.md + locked PMM artefacts. Layers best-practice patterns from category-leading companies per role type (Nooks / Apollo / 11x / Clay for outbound; Linear / Vercel / Notion for PMM; Anthropic for technical roles). Produces markdown files in the client's team-hiring/ folder. Triggers Mode A: "create JD for", "hire a {role}", "hiring 3-pack", "team hiring sprint", "careers page", "SDR JD", "AE JD". Triggers Mode B: "build interview hub for {role}", "score this interview", "stage 1 scorecard fo
- ▌
- ▌
- ▌ Consultation · matteotittaInteractive consultation-elicitation loop that turns a vague client or internal ask into a sharp, reviewed spec plus a copy-paste handoff prompt. Interrogates the ask one question at a time, maps gaps on a four-quadrant Known/Unknown board (living consultation doc), drafts a planning-doctrine spec, routes the adversarial review through /premortem, and emits a delimited handoff for a fresh execution session. Triggers: "scope this", "help me think through", "turn this into a spec", "consultation", "what do we actually need for X". Feeds into client-proposals and execution skills. Do NOT use for discovery-CALL prep (use client-discovery), for producing the proposal doc itself (use client-proposals), or for validating a business idea (use business-brainstorm).
- ▌
- ▌
- ▌
- ▌ Genesys Design · matteotittaGenerate well-branded Genesys visual assets — LinkedIn covers, Substack "skill of the week" covers, 1080×1350 carousels, infographics, and web mocks — for production or throwaway prototypes. Bundles the full Genesys design system: colors_and_type.css tokens (ink #181723, paper #FAFFF9, mint/teal #BAFDFF, lavender #939BED, violet #6400D7, General Sans Bold display), self-contained UI-kit HTML templates, the licensed General Sans family, brand assets, and impeccable-derived craft references (banned patterns, scoring rubric, quality library, post-render checklist). The CSS binding of the canonical brand kit at projects/genesys/brand/0626-brand-kit.md. Triggers: /genesys-design, "make a Genesys LinkedIn cover", "Genesys carousel", "Genesys infographic", "brand this in Genesys style".
- ▌ Help Center · matteotittaGenerates Intercom-bound help-center / knowledge-base articles for tech products organized by researched canonical collection taxonomy (getting-started, account, integrations, settings, advanced, troubleshooting, etc.). Produces a persona × collection × article matrix per product, with markdown bodies + screenshot placeholders, plus a one-shot Intercom Articles API JSON export. Triggers on "help center", "knowledge base", "user documentation", "Intercom articles", "product docs", "FAQ articles". NOT for marketing/SEO content (use aeo-content or website-copy) and NOT for onboarding emails (use email-nurture or lifecycle-marketing — but help-center articles are the link target those emails point to).
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Contract Redline · matteotittaApplies tracked-changes redlines + margin comments to a supplier-hostile client contract (DOCX), producing a properly-marked review document for the counterparty's legal team. Translates an objection email into per-clause redlines with proposed counter-language and rationale comments authored as Matteo Tittarelli. Saves the redlined.docx to Downloads, uploads to the client's Drive folder, and drafts a Gmail reply. Used pre-signature in client engagements when the counterparty sends standard boilerplate that needs amendments before signing. Triggers: "redline this contract", "add comments to the contract as redlines", "redline the agreement and send back", "track-changes on the contract".
- ▌
- ▌
- ▌
- ▌ Product UI Frames · matteotittaProduce brand-bound HTML video compositions rendered to MP4 via the Hyperframes engine. Use when the brief asks for a video, motion clip, animated explainer, lower-third, b-roll, social cut, or website-to-video. Takes a brand-kit (Genesys, client, or course DESIGN.md) as required input and synthesizes a Hyperframes-compatible palette + typography + house-style at composition time, so the same template renders three visibly distinct videos for three brand-kits. Produces an `index.html` source + an MP4 output. Triggers: "create a video", "render a clip", "make an explainer", "animate this", "video version of", "turn this site into a video". Downstream: linkedin-content, newsletter, sales-enablement-asset, youtube-scripts. Not for: static images (use linkedin-infographics), web prototypes (use vibe-coding), or Figma motion (use figma-prototype).
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Metadata Lint · matteotitta<!-- Sourced from ibelick/ui-skills (MIT). https://github.com/ibelick/ui-skills/blob/main/skills/fixing-metadata/SKILL.md. See../../../meta/catalog/design-reviewer/NOTICE.md for the MIT attribution block. -->
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Sales Tracks · matteotittaCreates persona-specific sales pitch tracks for live discovery and demo conversations. Each track combines a story arc that empathises with persona pain and JTBD, a capability/differentiator/benefit pitch sequence sourced from product-messaging, embedded objection handlers mined from win-loss-analysis transcripts, and a competitive anchor matrix that positions against each priority competitor for THAT specific persona. Consumes the full PMM foundational research stack: icp-research + icp-behavioural + positioning + product-messaging + competitor-research + win-loss-analysis + tov-guidelines + expert-pov + brand-kit. Outputs ship as per-persona markdown pages and optionally publish to Notion as a sales playbook the rep scans before a call. Triggered by "sales tracks", "pitch playbook", "talk track for [persona]", "sales playbook", "pitch deck for [persona]".
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌