Prompt file imported from Lai-Huyy/Shop-bandoan (.codex/prompts/design-feature.md). Copyright stays with the author.

Design a Shop-bandoan Feature

Name: design-feature
Author: Lai-Huyy

Design [feature] for Shop-bandoan without modifying code.

Read AGENTS.md, all relevant docs, backend/prisma/schema.prisma, the closest
existing module (auth, health, or restaurants), backend/src/app.module.ts, and
the current tests. Inspect git status but do not alter existing work.

Answer explicitly:
- Which existing module/service owns part of the problem?
- Should [feature] extend it or become a new module?
- Is a Prisma model, field, relation, enum, index, or migration truly needed?
- Does the persistence policy require a repository like RestaurantRepository?
- What new coupling, authorization, transaction, soft-delete/ownership, API,
  data-migration, and compatibility risks are introduced?

Propose routes beneath /api/v1, DTOs, response data inside the global envelope,
access policy, expected Swagger metadata, exception behavior, test plan, exact
file plan, documentation impact, and migration/rollback strategy when relevant.

Do not invent restaurant-product ownership, a frontend application, payment
behavior, or a database relation that is not supported by an approved rule.
Do not implement, commit, or push.

{ "prompt": "# Design a Shop-bandoan Feature\n\n```text\nDesign [feature] for Shop-bandoan without modifying code.\n\nRead AGENTS.md, all relevant docs, backend/prisma/schema.prisma, the closest\nexisting module (auth, health, or restaurants), backend/src/app.module.ts, and\nthe current tests. Inspect git status but do not alter existing work.\n\nAnswer explicitly:\n- Which existing module/service owns part of the problem?\n- Should [feature] extend it or become a new module?\n- Is a Prisma model, field, relation, enum, index, or migration truly needed?\n- Does the persistence policy require a repository like RestaurantRepository?\n- What new coupling, authorization, transaction, soft-delete/ownership, API,\n data-migration, and compatibility risks are introduced?\n\nPropose routes beneath /api/v1, DTOs, response data inside the global envelope,\naccess policy, expected Swagger metadata, exception behavior, test plan, exact\nfile plan, documentation impact, and migration/rollback strategy when relevant.\n\nDo not invent restaurant-product ownership, a frontend application, payment\nbehavior, or a database relation that is not supported by an approved rule.\nDo not implement, commit, or push.\n```", "variables": [], "notes": "Read AGENTS.md, all relevant docs, backend/prisma/schema.prisma, the closest existing module (auth, health, or restaurants), backend/src/app.module.ts, and the current tests. Inspect git status but do not alter existing work.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/Lai-Huyy/Shop-bandoan", "path": ".codex/prompts/design-feature.md", "ref": "9892163e46d063287188d85a0d7afee8c45fc7f5", "url": "https://github.com/Lai-Huyy/Shop-bandoan/blob/9892163e46d063287188d85a0d7afee8c45fc7f5/.codex/prompts/design-feature.md", "key": "Lai-Huyy/Shop-bandoan/.codex/prompts/design-feature.md" } } }

design-feature

About

Design a Shop-bandoan Feature

Use it

Manifest

Reviews