Skip to content

Tohuhono/Oberon / .agents/skills/domain-modeling

domain-modeling

Verified

Build and sharpen Oberon's domain model. Use when discussing codebase terminology, editing .agents/CONTEXT.md, or recording or revisiting an ADR.

Domain Modeling

Actively build and sharpen Oberon's domain model as you design. This is the active discipline: challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. (Merely reading CONTEXT.md for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)

During the session

Challenge against the glossary

When the user uses a term that conflicts with CONTEXT.md, surface the difference. For example, distinguish the composed Adapter from a Plugin adapter.

Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. For example, distinguish a Playground from a Starter app, or an Oberon config from Site state.

Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

Cross-reference with code

When the user states how something works, check whether the code and public documentation agree. Surface contradictions before recording a term or decision.

Update CONTEXT.md inline

When a term is resolved, update CONTEXT.md immediately. Use the table format in CONTEXT-FORMAT.md.

Keep definitions and aliases in the glossary. Put behavior and API contracts in the public documentation linked from ARCHITECTURE.md, and durable decision rationale in ADRs. The glossary is not a plan or a record of implementation details.

Offer ADRs sparingly

Only offer to create an ADR when all three are true:

  1. Hard to reverse: the cost of changing your mind later is meaningful
  2. Surprising without context: a future reader will wonder "why did they do it this way?"
  3. The result of a real trade-off: there were genuine alternatives and you picked one for specific reasons

If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.

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: 471kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall