Ryan Heltemes

Capture how a market actually describes its problem, in its own words, and record which rooms it gathers in.

Read a product's own repo, data, and artifacts, then write the three supply-side files the rest of the system needs.

Read real captured analytics and grade a campaign into what moved, what stayed flat, and what to prune.

Grade research you didn't gather, a chatbot dump or someone else's summary, into usable files, and find what it left out.

Run a repeatable audit of how an AI assistant answers a literal buyer question about your product, and write down what it got wrong.

The front door to reconnaissance and measurement: state the floors, then route to one of five live sub-skills.

Installs and runs a linter that blocks claim-shaped language with no source, and keeps a five-state register of what you may actually say.

Check and record per-account trust in each community before spending any of it, because standing doesn't transfer between rooms.

Sort marketing assets by whether a platform could take them away, and build the ones it can't first.

Track few numbers honestly, separate durable signal from noise, and kill the activity that produced nothing.

A pre-send checklist with a hard default: the deliverable is a paste block for a human, not an automated send.

Track every rented channel and, just as importantly, the ones you ruled out and why, so the same debate doesn't run twice.

The front door to asset and claim discipline: sort what you own from what you rent, and route to six focused sub-skills.

Design attention-getting work that survives the carry test: would a stranger pass it on, with your name still attached?

Turn one substantial piece into many standalone cuts, where every cut has to make sense to someone who never saw the source.

Judge whether attention already in motion can be ridden, instead of trying to manufacture it from nothing.

Paste-ready copy in which every factual sentence traces to a cleared claim, written for a room whose rules were read first.

One self-contained printable strategy document, assembled only from the pack, with every line traceable to its source file.

Derive the one claim, one verifier, and one citation that make an AI assistant select your product and defend the choice.

A sequenced no-budget campaign where each of five stages stays closed until its gate is met, and the plan says what would open it.

A daily marketing briefing built only from what you already captured, capped at three things, with stale inputs flagged rather than used.

Find a room that already has your audience, and pay for standing in it with something genuinely useful rather than a pitch.

Find the angle a funded competitor can't follow you onto, and write it down as two sections an agent can act on.

The front door to a no-budget marketing doctrine: pick fights you can win, stage everything for a human, and route to ten focused sub-skills.

Make the changelog entry part of landing the change, not a reconstruction at the end of the sprint. Two tiers so a small repo does not carry enterprise ceremony.

Catches cross-cutting duplication that file-size and modularity audits structurally cannot see. One canonical accessor per concept, plus a reverse pass for orphaned data.

Keep a change contained to its bounded unit. Carries the silent-deletion trap and the residue trap, the two ways refactors break things nobody mentioned.

Fires at the moment an agent adds to an existing file: state the file's size first, change only what traces to the request, write nothing speculative.

Bounded labeled sections, intent summaries, why-comments instead of what-comments, and naming that documents. Readability as structure, not cosmetics.

Keep units cohesive and right-sized while guarding the monolith cliff and the thousand-tiny-files cliff at the same time.

Answer does this already exist, and where, cheaply and without guessing. Builds a durable index and checks for twins by question, not just by name.

Orient inside the existing structure first, then turn the request into a short design doc with named modules, explicit interfaces, and a verify-stepped build sequence.

Prompt authorship for image and animation generators. Six principles, a legibility tell that explains the mush, and a four-move fix ordered strongest first.

Turn the contradiction you keep apologizing for into the thing you lead with. For products carrying two opposed truths where picking a side kills it.

Say the same thing to a different reader without the meaning moving. Carries a drift catalog, a fidelity ledger, and a reversal test.

Triage a music library without playing it, and catch a voiceover the music is burying. Returns cut points, splice plans, and a measured mix verdict.

Prose discipline with teeth: a banned-word catalog, a hard em-dash ceiling, a coherence pass, and an edit mode that protects your voice instead of rewriting it.

Set a project up to stay clean from the start instead of bolting discipline on later. The entry point that routes to eight focused sub-skills.