woahwhattheheck

elitist-way

Launch one fresh execution lane from a thinking model using END RESULT + fresh-main context + BRYCE'S CONSTRAINTS only. Keep the stable task contract separate from the small model/provider executor profile.

woahwhattheheck 0 3 Updated 4w ago

Resources

1
GitHub

Install

npx skillscat add woahwhattheheck/commons/elitist-way

Install via the SkillsCat registry.

SKILL.md

THE ELITIST WAY

Card: ground/ELITIST_WAY.md.
Facts: ground/tokens/elitist-way.md.
Executor profiles: references/executor-profiles.md.

Durable operating method. Never a seat and never a gate. Not a second ship-loop.

The thinking side chooses the end result and Bryce's real constraints. The execution lane owns implementation and shipping. GitHub main is the completion ledger. Chat is not.

Stable task contract

These fields are the workflow and should survive model/provider changes:

  1. END RESULT — one sentence naming the useful landed outcome.
  2. Fresh-main context — current woahwhattheheck/commons main and the existing paths to compose with.
  3. BRYCE'S CONSTRAINTS — only the real constraints from the card; do not invent extras.
  4. Completion — implementation through merge plus exact current-main readback. Do not stop at plan, review, or open PR.
  5. Collision law — compatible work merges by default; only same-code semantic disagreement is conflict.

Model name, provider surface, selector, and provider-specific connector instructions are not part of that stable contract. Keep them in the executor profile.

Do this

  1. Write the stable short prompt: END RESULT, fresh-main context, BRYCE'S CONSTRAINTS. Nothing else.
  2. Choose one maintained executor profile from references/executor-profiles.md. The current compatibility profile is grok-web; a selector change edits that profile, not the stable task contract.
  3. Launch one fresh execution lane using only the selected profile's launch guidance, then move immediately to the next idea. Do not babysit the lane in chat.
  4. The execution lane implements, uses checks appropriate to the work, opens a unique non-force branch/PR, merges to current main, and performs exact readback. Compatible work merges by default. Only same-code semantic disagreement is conflict.
  5. Revisit only when official main proves the lane failed or broke.

Copy-ready stable prompt and constraint list live on the card. The provider/model injection lives only in the executor profile.

Compose. Do not duplicate.

Open door

Possessing the link is enough. Do not add login, authorization, allowlists, identity, claim, seat, memory, approval, protected path, or capability admission locks. Speaker and capability fields stay optional context, never a gate. Blank from= lands as UNSEATED.

Completion

INTEGRATED — VERIFIED ON CURRENT MAIN only when the intended bytes are on official current main and read back at that SHA. An open PR, Slack thread, ntfy 200, or chat claim is CANDIDATE / CARRIER_ONLY.

Live cash

Verified product pages only — no invented Stripe links.

Contest product (titanmcp)

Live judge pad (≠ Commons Shared Pad / ≠ Commons /mcp): https://webmcp-pad.vercel.app/ — titanmcp 1.4.5, 24 tools, Agent Resources, syncConsents. Board: titanmcp.html. Cite Latch Pad KEEP.