Tohuhono/Oberon / .agents/skills/domain-modeling
domain-modeling
VerifiedBuild and sharpen Oberon's domain model. Use when discussing codebase terminology, editing .agents/CONTEXT.md, or recording or revisiting an ADR.
| File | Kind | Size |
|---|---|---|
| ADR-FORMAT.md | markdown | 2.7 KB |
| CONTEXT-FORMAT.md | markdown | 1.3 KB |
| SKILL.md | skill md | 2.3 KB |
| agents/openai.yaml | config | 101 B |
CONTEXT-FORMAT.md
View on GitHub# CONTEXT.md Format
Update [CONTEXT.md](../../CONTEXT.md) in place. Keep the existing sections and table format.
## Structure
```md
| Term | Definition | Aliases to avoid |
| ------------------ | ----------------------------------------- | ----------------------- |
| **Canonical term** | A short definition of the domain concept. | ambiguous name, synonym |
```
## Rules
- **Choose one name.** Put the canonical name in the first column and ambiguous alternatives in
"Aliases to avoid".
- **Keep definitions tight.** One or two sentences max. Define what it IS, not what it does.
- **Only include terms specific to this project's context.** General programming concepts (timeouts,
error types, utility patterns) don't belong even if the project uses them extensively. Before
adding a term, ask: is this a concept unique to this context, or a general programming concept?
Only the former belongs.
- **Use the existing groups.** Add terms to Runtime and integration, Content, or Project surfaces as
appropriate. Keep Invariants and Ambiguous terms consistent when a resolved term affects them.
- **Separate names from behavior.** Link to public documentation for behavior and contracts. Record
architectural rationale in `.agents/adr/`, not in glossary definitions.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |