メニュー
Analyzes legacy ORM models (Mongoose, Sequelize) to extract schemas, validations, and relationships. Use when reverse-engineering a legacy data layer for a modern rewrite.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Enforces data governance by verifying Knowledge Catalog Aspects before recommending BigQuery tables.
Ensures the game has a fun easter egg that turns the screen black and white, sepia or gameboy monotone colours. Use when creating or modifying a game.
Ensures platformer games have polished movement, responsive controls, and balanced jump mechanics. Use ONLY when the game type is "platformer".
Guides the creation of a new game and is the high-level orchestrator skill that MUST be invoked first. Use when tasked with creating a new game.
Arcade game must have a retro asthetic. Use when creating or modifying a game to ensure that the game looks retro and maintains a consistent look and feel with all games.
Game will always use the same control scheme/buttons and mapping of the gamepad and keyboard. Use when creating or modifying a game.
| name | auditing-data-models |
| description | Analyzes legacy ORM models (Mongoose, Sequelize) to extract schemas, validations, and relationships. Use when reverse-engineering a legacy data layer for a modern rewrite. |
Analyze the legacy data layer to extract schemas, validation rules, and entity relationships. Produce a blueprint for a modern, type-safe data access layer (e.g., Zod + Native MongoDB).
Reverse-engineer the legacy application's database models to ensure data integrity and structural parity in the modernized system.
Copy this checklist and track your progress:
Task Progress:
- [ ] Step 1: Locate the Models
- [ ] Step 2: Analyze Entity Schemas
- [ ] Step 3: Map Relationships & Hooks
- [ ] Step 4: Generate Data_Models.md
Search the legacy codebase for database model definitions (e.g., app/models/, db/models/). Identify the Primary Entities and their corresponding source files.
For each database model, extract:
String, ObjectId, Date).Date.now).user.authenticate(password)) or computed properties that will need to be ported to the utility layer.pre('save'), post('remove')) that perform side-effects like cascading deletes or password hashing.Compile findings into docs/legacy-audit/Data_Models.md. Additionally, identify specific data-integrity stress-tests (e.g., "Attempt to load a legacy record missing the email field to check if the new Zod schema handles it gracefully"). Append these probes to docs/verification/Verification_Plan.md.