agentleFS
NickKostovnyNickKostovny/marketing-playbooks/skills/hamming-taste-principles/SKILL.md

hamming-taste-principles

Skill0 starsChanged 2 months agoMITView on GitHub

Apply these aspirational taste principles whenever Nick is writing, briefing, reviewing, or evaluating marketing content for Invert — blog posts, LinkedIn posts, landing pages, ad copy, email sequences, case studies, video scripts, or any piece representing Invert to bioprocessing practitioners. Trigger alongside content-proportion-check on the same signals: "review this," "does this sound right," "draft a post about," "write a brief for," "here's the copy," "help me write," "landing page," "blog post," "content review," or any moment where marketing language is being produced or evaluated. Also trigger when Nick shares practitioner feedback, customer quotes, or evidence from conversations — these may confirm or invalidate the hypotheses tracked in this skill. This skill is hypothesis-grade: its principles are informed by Hamming's "You and Your Research" but have NOT been validated with Invert's ICP. Treat them as taste heuristics to test, not positioning truths to assert.

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Instead of "save 40% of time on data review," connect the time saved to what it enables: more runs, deeper characterization, catching the …

    line 44
  2. Distinctive:

    Do not imply practitioners are currently doing unimportant work

    line 49
  3. Distinctive:

    Do not romanticize the individual hero scientist — bioprocessing is collaborative and institutional

    line 50
  4. Distinctive:

    Do not use Hamming's language directly (e.g., "first-class work") — it would read as borrowed prestige

    line 51
  5. Distinctive:

    When describing time savings, connect them forward: saved time in this step compounds into deeper analysis in the next step, which …

    line 66
  6. Distinctive:

    Do not promise exponential results or use "compound interest" as marketing copy

    line 69
  7. Distinctive:

    Do not imply practitioners are currently underperforming — the compounding is about what's newly *possible*, not what was previously wrong

    line 70
  8. Distinctive:

    Don't frame regulatory requirements or institutional processes as problems to solve — frame them as the context within which better work …

    line 83
  9. Distinctive:

    When describing how Invert works within existing workflows, treat the constraints as given and respected, not as legacy burdens

    line 84
  10. Distinctive:

    If Invert enables something new, describe it as "possible within the existing constraints" rather than "possible despite them"

    line 85
  11. Distinctive:

    Do not minimize real frustrations practitioners have with their constraints

    line 88
  12. Distinctive:

    Do not suggest practitioners should be grateful for limitations

    line 89
  13. Distinctive:

    Do not claim Invert makes people smarter or better scientists

    line 108
  14. Distinctive:

    Evidence that would invalidate: If the primary value stories are about speed and reporting rather than about seeing something new.

    line 113
  15. Distinctive:

    Do not frame this as "Invert writes your reports for you" — that diminishes the practitioner's contribution

    line 127
  16. Distinctive:

    Evidence that would invalidate: If reporting/communication features are low on the value stack and practitioners primarily value Invert for …

    line 132

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hamming Taste Principles

These principles are extracted from Richard Hamming's 1986 talk "You and Your Research." They represent an aspirational emotional register for Invert's marketing — a hypothesis about what would resonate with bioprocessing practitioners who care about doing meaningful work.

Status: Hypothesis-grade. None of these principles have been validated with practitioners. They inform taste and tone — they do not override the instrument positioning, proportion checks, or language authenticity requirements in the existing marketing skills. If a principle here conflicts with content-proportion-check or brand-marketing-framework, those skills win.


How This Skill Relates to the Existing System

content-proportion-check governs what claims are made and whether they're grounded. It is the quality gate. Nothing in this skill relaxes that gate.

brand-marketing-framework governs what kind of marketing Invert should do. The instrument positioning is settled and validated. This skill does not replace it.

This skill adds a hypothesis-grade layer about emotional register — the aspirational qualities that the best Invert content might have if these principles hold up. Think of it as a set of flavors to experiment with, not rules to follow.


The Principles

1. Important Work Over Safe Work

Hamming observed that the difference between scientists who produced great work and those who didn't often came down to whether they chose important problems or safe ones. He didn't mean "Nobel Prize problems" — he meant problems where a reasonable attack existed and the stakes justified the effort.

The taste hypothesis: Practitioners who use Invert are trying to do work that matters — not just get through the day. Content that acknowledges this aspiration (without flattering or romanticizing it) will land differently than content that sells efficiency for its own sake.

What this looks like in practice:

  • Instead of "save 40% of time on data review," connect the time saved to what it enables: more runs, deeper characterization, catching the signal you'd otherwise miss
  • Frame Invert's value in terms of what the practitioner can now do that they couldn't before, not just what they no longer have to do
  • Acknowledge that practitioners make real choices about where to invest their attention — and that those choices matter

What this does NOT mean:

  • Do not imply practitioners are currently doing unimportant work
  • Do not romanticize the individual hero scientist — bioprocessing is collaborative and institutional
  • Do not use Hamming's language directly (e.g., "first-class work") — it would read as borrowed prestige

Evidence that would validate: Practitioners describing their motivation in terms of doing better science, not just operational speed. Customer conversations where someone says the equivalent of "now I can focus on what actually matters."

Evidence that would invalidate: Practitioners describing their motivation purely in operational or compliance terms. If the ICP's primary frame is "get the report done" rather than "understand the process better," this principle doesn't apply.

2. Compound Returns on Capability

Hamming's compound interest metaphor: small differences in effort and capability accumulate dramatically over time. The person who works 10% harder doesn't produce 10% more — they produce disproportionately more because knowledge and opportunity build on each other.

The taste hypothesis: Invert's value compounds. It isn't a one-time efficiency gain — it's a capability that makes each subsequent analysis faster, each subsequent insight more accessible. Content that communicates this compounding quality will resonate more than content that sells a static ROI.

What this looks like in practice:

  • Frame adoption as a trajectory, not a transaction: what does month 6 with Invert look like versus month 1?
  • Emphasize how visibility into data creates a "prepared mind" — the practitioner who has already seen the patterns is the one who notices when something is off
  • When describing time savings, connect them forward: saved time in this step compounds into deeper analysis in the next step, which compounds into better decisions downstream

What this does NOT mean:

  • Do not promise exponential results or use "compound interest" as marketing copy
  • Do not imply practitioners are currently underperforming — the compounding is about what's newly possible, not what was previously wrong

Evidence that would validate: Customer stories where usage deepened over time — practitioners finding new applications, using Invert in ways they didn't initially expect, building on earlier analyses.

Evidence that would invalidate: Adoption patterns that are flat — practitioners use Invert for a specific task and don't expand usage. If value is transactional rather than compounding, this principle is wrong.

3. Constraints as Catalysts

Hamming repeatedly showed that limitations — not enough programmers, not enough computing power, not the right department — forced creative reframing that produced better outcomes. His own invention of automatic programming came from not getting the resources he wanted.

The taste hypothesis: Bioprocessing practitioners work under real constraints — regulatory requirements, limited analytical resources, institutional processes. Content that frames Invert as thriving within constraints (rather than eliminating them) will feel more credible than content that promises liberation from them.

What this looks like in practice:

  • Don't frame regulatory requirements or institutional processes as problems to solve — frame them as the context within which better work happens
  • When describing how Invert works within existing workflows, treat the constraints as given and respected, not as legacy burdens
  • If Invert enables something new, describe it as "possible within the existing constraints" rather than "possible despite them"

What this does NOT mean:

  • Do not minimize real frustrations practitioners have with their constraints
  • Do not suggest practitioners should be grateful for limitations
  • This is about tone, not about denying that some workflows are genuinely painful

Evidence that would validate: Practitioners describing Invert as fitting into how they already work — extending capability rather than requiring workflow overhaul.

Evidence that would invalidate: Practitioners primarily valuing Invert because it removes a hated constraint. If the emotional register is "finally, I don't have to do X anymore" rather than "now I can do Y within the same system," this principle needs adjustment.

4. The Prepared Mind

Hamming paraphrased Pasteur: "Luck favors the prepared mind." The scientists who made breakthroughs weren't just lucky — they had been thinking about the right problems long enough to recognize the answer when it appeared.

The taste hypothesis: Invert's deepest value isn't automation — it's preparation. By giving practitioners better, faster visibility into their data, it prepares their mind to see what matters. The practitioner who catches the unexpected trend, the anomalous signal, the process deviation — they catch it because they were already looking with the right tool.

What this looks like in practice:

  • This principle reinforces the instrument positioning directly: an instrument prepares the scientist to see
  • Emphasize discovery moments — the thing the practitioner noticed that they wouldn't have seen otherwise
  • Frame Invert's analytical capabilities in terms of what they reveal, not what they compute

What this does NOT mean:

  • Do not claim Invert makes people smarter or better scientists
  • The insight belongs to the practitioner. Invert prepared the conditions; the practitioner did the seeing.

Evidence that would validate: One customer case already partially validates this — the scientist discovered an unexpected data error because Invert let him see his data in a new way. More examples like this would confirm the principle.

Evidence that would invalidate: If the primary value stories are about speed and reporting rather than about seeing something new. If practitioners don't describe "aha moments," the prepared mind framing doesn't match their experience.

5. Communicate So Others Can Build

Hamming insisted that doing great work wasn't enough — you had to communicate it so others could build on top of it. He distinguished between work that advanced the field and work that was a dead end because no one could follow it.

The taste hypothesis: One of Invert's underappreciated values is communication — it helps practitioners present their findings internally (to leadership, to cross-functional teams, to regulators) in ways that are clear and actionable. This is not a minor efficiency gain; it's the difference between work that influences decisions and work that stays in a notebook.

What this looks like in practice:

  • Content that acknowledges the communication burden practitioners carry — the reports, the presentations, the cross-site alignment
  • Frame Invert's reporting and visualization capabilities as helping practitioners get credit for and build on their own work
  • The customer slide (all data, all results, one mention of the tool) is the template — the practitioner presented their work, and it was clear enough that leadership could act on it

What this does NOT mean:

  • Do not frame this as "Invert writes your reports for you" — that diminishes the practitioner's contribution
  • The communication is the practitioner's; Invert enables the clarity

Evidence that would validate: Practitioners describing internal presentation or reporting as a significant part of how they use Invert. Stories where Invert-generated outputs influenced organizational decisions.

Evidence that would invalidate: If reporting/communication features are low on the value stack and practitioners primarily value Invert for analysis alone.


Validation Tracker

Each principle carries a status. Update these as evidence accumulates.

PrincipleStatusLast ReviewedKey Evidence
Important Work Over Safe WorkUNTESTED—None yet
Compound Returns on CapabilityUNTESTED—None yet
Constraints as CatalystsUNTESTED—None yet
The Prepared MindPARTIALLY SUPPORTED—Customer discovery story
Communicate So Others Can BuildUNTESTED—None yet

Status definitions:

  • UNTESTED — No practitioner evidence for or against
  • PARTIALLY SUPPORTED — Some evidence, not yet conclusive
  • VALIDATED — Consistent practitioner evidence confirms this resonates
  • INVALIDATED — Practitioner evidence contradicts the hypothesis
  • RETIRED — Invalidated or absorbed into another skill

When this skill fires, check the tracker. If a principle has been sitting at UNTESTED for more than 3 months, surface that to Nick as a prompt: "This principle hasn't been tested yet — is there a low-cost way to validate it?" If a principle hits VALIDATED, consider promoting it into content-proportion-check or brand-marketing-framework where it has more weight. If it hits INVALIDATED, flag it for removal.


When Practitioner Evidence Appears

If Nick shares customer quotes, interview notes, sales call summaries, or any practitioner feedback, scan it against these five principles. Look for language that either supports or contradicts the hypotheses. Surface the connection explicitly: "This quote from the MSAT engineer maps to the Prepared Mind principle — they're describing exactly the kind of discovery moment the hypothesis predicts."

Equally important: surface contradictions. If a practitioner describes their motivation in purely operational terms and shows no sign of the aspirational register these principles assume, say so. The skill is only useful if it's honest about what it finds.


What This Skill Is NOT

  • It is not a positioning document. The instrument positioning is established and validated. This skill does not change or replace it.
  • It is not a content style guide. It does not govern word choice, sentence structure, or formatting.
  • It is not a filter that blocks content. It's an aspirational layer — content can ship without hitting any of these notes. But the best content might hit one or two of them naturally.
  • It is not a license to romanticize. Every principle here can be executed badly by flattering the reader or inflating the claim. The proportion check still applies.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

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.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.