Community影像github.com

cbrock84/視覺內容

設計並引導承載內容的視覺資產——輪播、資訊圖表、引言圖、圖解及社群圖片,包含 AI 生成時的提示詞。用於將文字內容轉化為視覺格式、設計輪播或資訊圖表、製作社群圖片,或修正無法吸引目光的視覺。

視覺內容 是什麼?

這項技能「cbrock84/visual-content」提供了一套系統化的方法,用以將文字內容轉化為引人入勝的視覺資產,特別適用於社群媒體和內容行銷領域。它涵蓋了輪播、資訊圖表、引言圖和圖解等多種格式,並根據內容的內在結構(如序列、比較、單一主張)來決定最適合的視覺呈現方式。此技能不僅指導設計原則(如高對比度、行動裝置優先),還包含了 AI 圖像生成的提示詞撰寫規範,以確保生成的視覺資產符合品牌調性。支援的平台包括 Claude Code、Coder、Cursor 和 Codex 等 AI 代理,其核心價值在於幫助使用者避免常見的設計誤區,例如將一段文字簡單分割成多張投影片,而是創造出真正能抓住受眾注意力、促進互動的視覺內容。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/visual-content

Installed? Explore more 影像 skills: steipete/songsee, affaan-m/frontend-design, mattpocock/improve-codebase-architecture · View all 6 →

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

視覺內容 是做什麼的?

格式應隨內容形狀而變

  • 序列或流程 → 輪播。每張投影片一個步驟,一個想法。
  • 比較或關係 → 單一圖解。輪播會破壞需要同時觀看的關係。
  • 單一難忘的主張 → 引言圖。
  • 數量、趨勢或比例 → 圖表,並附帶一個訊息。
  • 包含超過約七個元素的事物 → 拆分為兩個視覺。

根據流行而非內容形狀選擇格式,正是許多輪播淪為一段文字切成十片的原因。

輪播

第一張投影片就是整個鉤子——將其視為標題,而非標題卡。每一張後續投影片都必須值得滑動,這意味著每一張的結尾都略顯不完整。

各投影片間使用一致的模板:相同的邊距、相同的位置、相同的色調。投影片間的變異會被解讀為錯誤。為它們編號,讓讀者知道需要投入多少。

最後一張投影片要讓想法落地。一張只說「追蹤以獲取更多」的最後一張投影片,浪費了唯一一張能確保所有完成閱讀者注意力的投影片。

資訊圖表和圖解

當圖解能呈現散文需要三段文字才能建立的關係時,它才有存在的價值。如果它只是重述文字,就刪掉它。

直接在元素上標註。圖例迫使讀者在大腦中記憶對應關係,同時還要看別處。剔除任何不承載意義的東西——裝飾性漸層、3D 效果以及資料上的陰影。

為實際情境而設計

絕大多數這類內容是在手機、動態消息中、以快速瀏覽的方式、在小螢幕上被觀看。在完成前,先以那個尺寸進行測試。如果標題在縮圖比例下無法閱讀,它就等於不存在。

主體與背景之間的高對比度是吸引目光的關鍵。細微差別是桌面端的奢侈。

圖像的生成位置

將提示詞寫成一份簡報:主體、構圖、光線、色調、氛圍以及負面限制。每張圖像只生成一個概念。然後檢查輸出是否正確渲染任何嵌入的文字,並符合品牌色調——生成圖像會偏移,偏離的品牌顏色比沒有品牌顏色更糟。

永遠不要

  • 在確定內容是序列、比較還是單一主張之前,就先選擇視覺格式。
  • 以完整尺寸設計最終會在縮圖尺寸下被觀看的內容。
  • 將承載關鍵資訊的內容單獨放在圖片中。圖片中的文字無法被搜尋、無法被翻譯,且對螢幕閱讀器不可見。

Individual skills in this repo

This repo contains 11 individual skills — each has its own dedicated page.

cbrock84/interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.

cbrock84/org-design

Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.

cbrock84/portfolio-governance

Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.

cbrock84/product-launch

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

cbrock84/program-management

Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.

cbrock84/project-delivery

Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.

cbrock84/retention

Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.

cbrock84/sales-enablement

Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.

cbrock84/tax

Structures the tax questions a growing business faces — corporate income, sales and use, payroll, nexus, and the obligations created by hiring or selling somewhere new. Use this to work out what a new state or country obligates you to, prepare for a tax filing or audit, understand sales tax on your product, or check what a remote hire or new market triggers.

cbrock84/unit-economics

Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.

cbrock84/video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

相關技能