Skip to content

samber/dev-event-organizer-skills / skills/business-event-formats

business-event-formats

Verified

Choose which company-run event shape to run - invite-only dinner, executive summit, single-city user conference, multi-city roadshow, or a floor-primary trade-show event - plus how its program is sourced and what shape its floor takes. Also owns the business-oriented activity layer any conference can run beside its program for sponsors (hiring corner, hands-on product feedback session, opt-in demo space, matchmaking). Use whenever a company weighs a user conference against a roadshow or a summit, asks what kind of event to put on for developers, customers or partners, or asks whether to run its own floor or exhibit on someone else's, or an organizer asks what to offer sponsors beyond talks, even if they only say "we want to do an event". Format catalog only. Do NOT use for track count or session mix - use samber/dev-event-organizer-skills@event-format-selection; for floor operations use samber/dev-event-organizer-skills@event-booth-experience; for goals and budget use samber/dev-event-organizer-skills@corporate-event-strategy.

references/vendor-conference-precedents.md

View on GitHub
# Company-run conference precedents, and what does not transfer

Two things live here: named companies describing their own events in their own words, and a note on which parts of the corporate-events-industry material behind these shapes carry over to a developer audience.

Contents: how to read these precedents, the precedents themselves, the community-pole contrast, and the transposition note.

## How to read them

These are descriptions, not templates. Each company's shape works because of an installed base, a launch cadence and a budget that its words do not mention and you do not have.

Import the reasoning: why the shape was chosen, and what it was chosen instead of. Leave the surface alone. Copying a named company's shape without its constraints is a failure mode the skill body lists for that reason.

The set as a whole shows one pattern: at the company-run pole, the _shape_ is a commercial decision and the _language_ is a community one. Every company below describes its event in the vocabulary of practitioners, builders or users rather than of sales. That is a positioning move, and `samber/dev-event-organizer-skills@event-positioning` owns what it entitles an event to claim. It is noted here only because it explains why these self-descriptions read the way they do.

## The precedents

- **HashiCorp - HashiConf.** HashiCorp calls it "our flagship user conference" (hashicorp.com). The company also runs a smaller spin-off, HashiDays, positioned as "one-day, single-track, deeply technical, and community-focused": a company-run event deliberately borrowing the single-track identity usually associated with independent conferences.

  One company running both a flagship and a smaller, tighter format is the clearest published example that these shapes compose rather than compete. Whether a company should run more than one is `samber/dev-event-organizer-skills@event-portfolio-strategy`'s question, not this skill's.

- **AWS - re:Invent.** Launched in 2012 as "its first global customer and partner conference" (press materials). Present-day self-description from the company's own FAQ: "five days in Las Vegas with 2,200+ sessions". The launch framing names customers _and_ partners in the same breath, which is the split the floor-shape menu turns on: a floor exists for the partner half of that sentence.
- **GitHub - Universe.** Calls itself "the world's fair of software" (github.blog). A fair is a floor metaphor, not a stage metaphor, chosen by a company whose event has both.
- **Salesforce - Dreamforce.** The first edition, in 2003, drew "just over 1,000 registered attendees" and carried a product launch at the same event. Treat this attendance figure as indicative of scale rather than as a verified number, and do not use it to size anything. The shape carried a launch from its first, small edition: a user conference does not need scale to do the job the shape exists for.
- **swyx (Netlify) on company-sponsored conferences.** "Company sponsored conferences are often around a certain architecture" (swyx.io). It names the structural consequence of the company-supplied and mixed rungs on the program-sourcing menu: content organized around one architecture, whether or not the attendee uses that company's product.

## The community-pole contrast

One principle is worth carrying, because it marks the boundary the program-sourcing menu's delete rule enforces. Community conferences state the ban outright: "no product and/or vendor sales pitches" is CNCF's wording. A company-run event is not bound by that rule, which is exactly why the posture has to be chosen deliberately rather than inherited. `samber/dev-event-organizer-skills@event-format-selection` owns the community-pole side of this contrast; nothing here restates its ladder.

## Transposition note: what does not carry over

The shape vocabulary this skill catalogs (roadshow, executive summit, roundtable, invite-only dinner, floor-primary event) comes from **corporate B2B marketing and the trade-show industry**. Its _structure_ transposes: the shapes are real, the invitation models are real, and the trade between reach and account depth is real in both domains. Four things do not transpose, and a recommendation that carries them across is wrong in a way that is hard to see.

1. **The measurement frame.** That material measures these shapes in pipeline attribution against an enterprise buying committee. This collection's reader is measured on developer adoption, and the two do not convert. Route measurement to `samber/dev-event-organizer-skills@corporate-event-strategy` instead of importing an attribution model.
2. **The assumed buyer.** Those shapes were designed around a line-of-business executive who authorises a purchase without ever using the product. Developer-led adoption inverts that hierarchy: the person who decides in practice is often the person the seniority-gated guest list excludes. This is the single biggest reason an executive summit underperforms when copied straight across.
3. **The content norms.** An enterprise-buyer audience expects a product pitch and is not offended by one. A developer audience discounts it, and the community pole bans it outright. This is why the program-sourcing menu's default is mixed with labelled company slots rather than company-supplied.
4. **Every number.** No cost, headcount, city count, attendance figure or conversion rate from that material survives the move: different audiences, different geographies, different years. The skill body states no such figure for this reason, and neither should a deliverable built from it.

What is left after those four are removed is the shape catalog itself, which is why this skill is a catalog and not a playbook. Every effort, value, compliance and efficiency ordering in the skill body is argued from those shapes' mechanics and contestable on its own terms.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall