modelgen-nosqllisted

Extract NoSQL document models from Agile user stories using Domain-Driven Design (DDD) principles. Produces Mermaid class diagrams showing document structure (embedded vs referenced), JSON schema examples per collection, and detailed model documentation per module. Use this skill whenever the user asks to extract a NoSQL module model, NoSQL document model, NoSQL schema, collection design, or document structure from user stories. Also trigger when the user provides user stories grouped by module and asks for NoSQL data modeling, document-oriented design, or embed-vs-reference analysis. Even if the user says "design my NoSQL collections" or "what documents do I need", this skill applies if the input contains structured Agile user stories with module groupings. Do NOT use this skill for RDBMS or relational schema extraction â€” use the modelgen-relational skill for that. Also trigger when the user says "update the model" or "upgrade the model" to incrementally evolve an existing NoSQL document model based on cha
rashidee/co2-skills · ★ 3 · AI & Automation · score 79

Install: claude install-skill rashidee/co2-skills

# NoSQL Model Generator Extract document-oriented NoSQL models from Agile user stories following a systematic DDD methodology. This skill is database-agnostic and produces generic document models applicable to MongoDB, Couchbase, DynamoDB, Firestore, CosmosDB, or any document-oriented NoSQL store. ## When to Use Trigger this skill when the user asks to: - Extract a NoSQL module model or document model - Design NoSQL collections or document structures from user stories - Perform embed-vs-reference analysis on entities - Generate document schemas from requirements - Update an existing NoSQL document model based on story changes - Upgrade the model to a new version - Detect and fix outdated/invalid model elements Do NOT use for RDBMS/relational schema extraction â€” use the modelgen-relational skill for that. ## Version Gate Before starting any work, resolve the application folder first (see Input Resolution below), then check `CHANGELOG.md` in the application folder (`<app_folder>/CHANGELOG.md`): 1. If `<app_folder>/CHANGELOG.md` does not exist, skip this check (first-ever execution for this application). 2. If `<app_folder>/CHANGELOG.md` exists, scan all `## vX.Y.Z` headings and determine the **highest version** using semantic versioning comparison. 3. Compare the requested version against the highest version: - If requested version **>=** highest version: proceed normally. - If requested version **<** highest version: **STOP immediately**. Print: `"Version {reque