BUILD FROM FIGMA FRAME LINKS

Implement these Figma screens in the current Angular project:
[PASTE FRAME LINKS]

Use the remote Figma MCP connection to inspect the actual frames, components, variables, layout, and available visual references before writing code.

Requirements:
- Use Angular, TypeScript, separate HTML templates, and SCSS. Follow this repository's Angular version and conventions.
- Reuse existing components; extract repeated UI into shared components.
- Match Figma typography, spacing, colors, icons, assets, and states.
- Match the 1920px desktop design; adapt to 1440px, 1024px, 768px, and 390px. Identify any responsive behavior you infer.
- Use Grid/Flexbox and shared SCSS design tokens.
- Use real assets saved in the project, not temporary asset URLs.
- Include semantic HTML, labeled controls, keyboard interaction, and visible focus states.
- Preserve the original Figma screens. Do not modify the Figma file.
- Implement one screen first for visual review before expanding.
- Run the project build and check responsive layouts against Figma.
- Report changed files, missing assets, assumptions, and remaining visual or functional gaps.
If MCP access fails, explain what is missing instead of guessing.

============================================================

BUILD FROM THE SELECTED FIGMA FRAME

Use figma-desktop MCP to inspect the currently selected frame in Figma. First confirm its name and dimensions.

Implement the selected screen in this Angular project.

Requirements:
- Use Angular, TypeScript, separate HTML templates, and SCSS. Follow this repository's Angular version and conventions.
- Reuse existing components; extract repeated UI into shared components.
- Match Figma typography, spacing, colors, icons, assets, and states.
- Match the 1920px desktop design; adapt to 1440px, 1024px, 768px, and 390px. Identify any responsive behavior you infer.
- Use Grid/Flexbox and shared SCSS design tokens.
- Use real assets saved in the project, not temporary asset URLs.
- Include semantic HTML, labeled controls, keyboard interaction, and visible focus states.
- Preserve the original Figma screens. Do not modify the Figma file.
- Implement one screen first for visual review before expanding.
- Run the project build and check responsive layouts against Figma.
- Report changed files, missing assets, assumptions, and remaining visual or functional gaps.
If MCP access fails, explain what is missing instead of guessing.