ss-bs-discovering-domain-model

Inventory entities, lifecycles, and relationships from codebases into docs/DOMAIN.md.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-bs-discovering-domain-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-bs-discovering-domain-model
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/project-bootstrap/ss-bs-discovering-domain-model
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-bs-discovering-domain-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn an existing codebase and its data models into a clear, newcomer-friendly domain model document without guessing, ensuring the entities and their lifecycles are truly the load-bearing ones.

Core Features & Use Cases

  • Inventory and map domain shape from code: Scans schemas, ORM models, type definitions, test fixtures, and state machines to identify candidate domain entities and how they relate conceptually.
  • Interactive selection and clarification: Asks you to pick the ≤15 most important entities, confirm lifecycles, resolve relationship cardinality, and capture workflow exceptions the schema doesn’t reveal.
  • Atomic documentation output: Writes docs/DOMAIN.md (or your configured path) in a single, validated update.

Quick Start

Use the ss-bs-discovering-domain-model skill as part of ss-bs-bootstrapping-project to generate or refine your docs/DOMAIN.md by guiding the entity and lifecycle choices in an interactive flow.

Frequently Asked Questions about ss-bs-discovering-domain-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a domain model document from an existing codebase?

To generate a domain model document from an existing codebase, inventory schemas, ORM models, and test fixtures to identify candidate entities. The tool interactively guides you through selecting load-bearing entities, confirming lifecycles, and resolving relationship cardinality for the final document.

What is the best way to document entity lifecycles and relationship cardinality for a project?

Document entity lifecycles and relationship cardinality through an interactive workflow that extracts state machines from code and tests. You confirm lifecycle completeness and resolve cardinality rules, capturing workflow exceptions the schema does not reveal to ensure the conceptual model matches actual behavior.

Can I audit an existing DOMAIN.md file for drift against my current codebase?

Yes, you can audit an existing DOMAIN.md file for drift against your current codebase. The audit mode compares your documented domain model against current schema and behavior, interactively resolving any detected drift during the update process.

How do you bootstrap domain documentation when schema and behavior exist but domain framing is unclear?

Bootstrap domain documentation by running an interactive flow that inventories entities from code and tests to clarify domain framing. You select the top fifteen load-bearing entities, confirm their lifecycles, and write the output to docs/DOMAIN.md in a single validated update.

Does this domain modeling approach work without a fully defined database schema?

The domain modeling approach requires existing schema and behavior to function, as it scans data models, type definitions, and test fixtures to identify candidate entities. It applies when these elements exist but the conceptual domain framing remains unclear.