Communitygithub.com

Kryhr/45-anti-slop-skills

Use this skill whenever building a case-study page, a portfolio, or a before/after gallery. Also use it when a user asks to "show our past work," "add a portfolio," or "add a before and after gallery." Covers structuring these pages to actually demonstrate results rather than present vague, unverifiable claims of quality.

45-anti-slop-skills 是什麼?

45-anti-slop-skills is a Claude Code agent skill that use this skill whenever building a case-study page, a portfolio, or a before/after gallery. Also use it when a user asks to "show our past work," "add a portfolio," or "add a before and after gallery." Covers structuring these pages to actually demonstrate results rather than present vague, unverifiable claims of quality.

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Kryhr/45-anti-slop-skills/tree/HEAD/skills/case-studies-portfolio

在你喜歡的 AI 中提問

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

說明文件

Case Studies and Portfolio

Why this matters

"We do great work" is a claim; a specific before-and-after with real numbers or a real transformation is evidence. Case studies and portfolios exist specifically to move a visitor from taking the business's word for it to seeing the actual result, which only works if the content is specific and real rather than a vague summary.

Do this

Case studies

Structure each case study around a real project with a genuine before/after or problem/result arc: what the client's situation was, what was actually done, and what the measurable or clearly observable outcome was. Use real numbers where they're genuinely available ("reduced average response time from 45 minutes to 12," not "significantly improved response time"), and name the client or project where permission allows; an anonymized case study is still usable but is weaker evidence than a named, verifiable one.

Before/after galleries

For businesses where visual transformation is the actual product (landscaping, renovation, aesthetics, detailing), a before/after gallery is often more persuasive than any written copy. Use real project photos, shot consistently (same angle/lighting where practical) so the comparison is genuinely legible, not photos that differ in framing or lighting in ways that make the "after" look better for reasons unrelated to the actual work.

  • Pair before/after images side by side or with a slider, clearly labeled, not left ambiguous about which is which.
  • Caption with real project context (location, scope, timeframe) where it adds credibility, not generic captions like "Before" and "After" with nothing else.

Portfolio pages

For a business whose work is inherently visual or project-based (design, development, construction), a portfolio should show real completed work with enough detail to demonstrate actual capability, not just a grid of thumbnails with no context. Link each portfolio piece to more detail (a mini case study, or the live result itself) where possible.

Never do this

  • Never present a case study or portfolio piece as real work that didn't actually happen, or with invented metrics.
  • Never use before/after photos shot under inconsistent conditions specifically to exaggerate the apparent transformation.
  • Never publish a portfolio grid with zero context, forcing the visitor to guess what they're even looking at.

Verification checklist

  • Every case study describes a real project with an actual, specific outcome
  • Metrics cited are real, not invented or exaggerated
  • Before/after photos are shot consistently enough for a fair comparison and clearly labeled
  • Portfolio pieces include enough real context to demonstrate actual capability, not just an unlabeled image grid

Individual skills in this repo

This repo contains 1 individual skill — each has its own dedicated page.

相關技能