Scaffold Application Slice

Prompt file imported from anisbouhadida/medz-explorer (.github/prompts/scaffold-application-slice.prompt.md). Copyright stays with the author.

Scaffold a focused Angular application slice for this workspace using the user's arguments as the brief.

Follow the repo conventions in application instructions and, when tests are created or updated, testing instructions.

Expect the arguments to describe the slice name and intended behavior, such as a page, feature component, layout section, route-backed flow, or shared application-facing service.

When carrying out the task:

• Start from the closest existing feature or layout pattern in src/app instead of inventing a new structure.
• Create or update only the files needed for that slice.
• Prefer standalone Angular components, inject(), signals, computed(), and rxResource() when async UI state is involved.
• Reuse shared domain types from src/app/shared/model and shared API services from src/app/shared/service/api before adding new local abstractions.
• Keep component logic in .ts, markup in .html, and styling in .css.
• If routing is required, wire it in the existing route structure in a lazy-load-friendly way.
• Preserve the Medz Ivory visual direction from DESIGN.md and the existing Angular Material plus Tailwind stack.
• Add or update targeted specs when the new slice changes user-visible behavior or introduces new logic.

In the final response:

• Briefly state what was added or changed.
• Mention the key files that define the new slice.
• Note any assumptions, open questions, or follow-up work that still matters.