agentsclimarketplace
Sign in

Marc principles

Skill meunomeebero/marc-principles

Apply a paraphrased 32-principle Marc Lou viral-product lens to product design, landing pages, dashboards, onboarding, pricing, naming, CTAs, social proof, demos, copy, and sharing. Use when the user mentions Marc principles, Mark principles, viral product, cognitive biases, vieses cognitivos, memorable or shareable design, one idea per screen, simplifying hierarchy, or asks for a product/CRO/design critique. Treat these as provocative heuristics, never as automatic policy: product evidence, accessibility, truth, ethics, and the host product's explicit strategy win conflicts.From its SKILL.md

Install
npx -y skills add meunomeebero/marc-principles

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 486 tokens by cl100k_base, as published. Nobody here has run it

Marc Product Principles

Use Marc Lou's viral-product article as a sharp clarity and distribution lens. Do not treat it as research, universal law, or permission for dark patterns.

Load

  1. Read decision-policy.md for precedence and trust rules.
  2. If the host project has a higher-authority product policy, load it and apply the stricter rule.
  3. Read principles.md for the 32 paraphrased checks.

Workflow

  1. Name the surface and funnel stage.
  2. State the user's current mental question in one sentence.
  3. Pick 3-5 relevant principles. Never force all 32 into one screen.
  4. Convert each principle into a concrete hierarchy, copy, interaction, or distribution decision.
  5. Run the precedence check: truth/legal/security/accessibility -> explicit product contract -> observed evidence -> user clarity -> Marc heuristic.
  6. Remove or hide something before adding visible scope.
  7. Attach one behavioral metric and one trust guardrail to each material change.
  8. For UI work, verify desktop/mobile, keyboard, reduced motion, contrast, empty/error/loading states, and one dominant action per decision moment.

Output Contract

## Marc Principles Review

| Surface | User question | Principle | Decision | Metric | Trust guardrail |
|---|---|---|---|---|---|

## Remove / Hide
- ...

## Keep / Strengthen
- ...

## Experiment
- Hypothesis:
- Primary metric:
- Guardrail metric:

Hard Rules

  • Never invent numbers, testimonials, scarcity, rankings, savings, or comparisons.
  • Never remove a free tool, add a hard paywall, remove subscriptions, or raise price solely because the article says so.
  • Never trade accessibility or comprehension for novelty, emotion, or virality.
  • Never use more emotional pressure than the value already demonstrated.
  • Preserve user autonomy. CTA clarity is direction, not coercion.
  • Prefer customer language, real product proof, and observed outcomes over adjectives.

Source

Marc Lou, "32 Principles of a Viral Product," 12 Jun 2026: https://x.com/marclou/status/2065385672991752210

This skill stores paraphrased decision heuristics, not the article text.

What ships with it: 8 files

15.6 KB alongside SKILL.md, 1 of them executable

agents/

references/

scripts/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.