domain

Included with Lifetime

$97 forever

Document domain knowledge including entities, processes, and ubiquitous language

General

What this skill does

# Domain Knowledge

Document domain knowledge systematically using the domain-knowledge skill.

## CRITICAL: NO ASSUMPTIONS ALLOWED

**NEVER make assumptions about the domain.** This command exists to trigger dialogue with the user, NOT to create documentation independently.

**STOP and ASK when:**
- You don't know what entities exist
- You don't know attributes or data types
- You don't know how entities relate
- You don't know process steps
- You're uncertain about ANY detail

## Workflow

Ask the user what they want to do:

1. **Document entity** - Create or update an entity in `docs/domains/[domain]/entities/`
2. **Document process** - Create or update a process in `docs/domains/[domain]/processes/`
3. **Add glossary term** - Add a term to `docs/domains/[domain]/glossary/`
4. **View domain** - Show existing domain documentation

### For All Options

1. First check if `docs/domains/` directory exists
2. Ask which domain area this belongs to (or create new)
3. Follow the dialogue-first approach from the skill
4. Create documentation only after user confirms details

### Documentation Structure

```
docs/domains/
└── [domain-name]/
└── [subdomain-name]/
├── entities/
│ ├── _overview.md
│ └── {entity}.md
├── processes/
│ ├── _overview.md
│ └── {process}.md
└── glossary/
├── _overview.md
└── {term}.md
```

## Example Dialogue

```
User: "Document the Order entity"

GOOD Response:
"I'll help document the Order entity. First some questions:

1. Which domain does Order belong to? (e.g., 'ecommerce', 'sales')
2. What attributes does an Order have?
3. What are the data types for each?
4. How does Order relate to other entities?
5. What states can an Order be in?

I'll only document what you tell me."
```

## Remember

- **Dialogue first, documentation second**
- **Verify, don't assume**
- Mark unknowns with `# TODO:` or `# QUESTION:`
- Use Mermaid diagrams for visualization
- Keep files focused - one entity/process/term per file

## Resources

- For detailed templates and examples, see [domain-guide.md](domain-guide.md)

Files: 2

Size: 10.4 KB

Complexity: 14/100

Category: General

Source: https://github.com/smidigstorm/storm-claude-marketplace/tree/main/plugins/pm-domain-knowledge/skills/domain

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts