# Install ShadCV in My Project

You are an AI coding agent with access to my workspace, filesystem, and terminal.

Your task is to install, integrate, customize, and verify **ShadCV**, an open-source resume solution built with React, Next.js, Tailwind CSS, and shadcn/ui.

Source repository: https://github.com/Hundemit/shadcv
## 1. Read the Project Instructions

First, inspect my workspace, read its project instructions, and identify the intended destination. A checkout of ShadCV alone is a standalone setup, even though it is a React application.

Clone the ShadCV repository into a safe, separate directory if it is not already available locally.

Before making any changes, read the repository's **AGENTS.md** and **README.md** in full.

These files contain the authoritative instructions for architecture, integration, dependencies, configuration, customization, PDF generation, and testing.

Follow the integration guide in AGENTS.md. Inspect the actual source code when documentation and implementation differ. Do not guess missing implementation details.

## 2. Choose the Appropriate Integration

ShadCV supports two approaches:

**Option A — Portable React Component**

If my workspace contains an existing React application and I only need the resume document, follow Path A in AGENTS.md to integrate ResumeDocument.

Reuse my application's existing routing, shadcn/ui components, Tailwind configuration, theme, and package manager wherever possible.

Keep the integration minimal and preserve existing functionality.

**Option B — Complete Next.js Website**

If there is no existing destination application, follow the standalone instructions in Path B of AGENTS.md. Use a separate checkout intended for customization, install the dependencies with the repository’s Node and pnpm versions, and run pnpm install --frozen-lockfile. The landing page is at / and the configured resume is at /template.

If I explicitly request the website features inside an existing Next.js application, follow the existing-app instructions in Path B and preserve its routes, providers and configuration.

If I have explicitly requested a particular approach, prioritize that choice.

Do not deploy or publish anything unless I explicitly request it.

## 3. Customize the Resume

Use resume information and assets I have explicitly provided or placed in the intended project.

If no information is available, use clearly fictional example data so the installation can proceed.

Never copy the source author's personal resume information, portrait, PDFs, or personal metadata into my customized resume.

For the complete website, follow the customization checklist in section 7 of AGENTS.md. Replace the demo content, metadata, social preview images and public assets before generating new downloads.

Preserve the project's applicable MIT license and copyright notices.

## 4. Implement and Verify

Perform the implementation directly using your available tools.

Follow the appropriate integration, installation, and verification procedures documented in AGENTS.md.

Install missing dependencies, resolve compatibility issues, and run the relevant checks.

For the standalone website, start the development server, verify /template, then run pnpm resume:export http://localhost:3000 with the actual loopback origin. Inspect the PDFs for every enabled language. Stop the dev server, then run pnpm check followed by pnpm test:browser. Install the Playwright browsers listed in AGENTS.md as needed. For an existing app, use its verification commands and adapt the export workflow if you integrated it.

Verify that the resume renders correctly on desktop and mobile, and confirm that the relevant features work.

Fix issues within scope without overwriting unrelated files or discarding existing changes.

## 5. Report the Result

Once finished, briefly provide:

- Which integration approach you selected and why.
- Which files and dependencies you changed.
- Where I can access the resume locally.
- Which checks passed or failed.
- What information, if any, I still need to provide.

**Important:** Do not stop after describing the installation process. Carry out the actual implementation, verify the result, and leave me with a working local setup. If required tools or repository access are unavailable, explain the blocker instead of pretending the installation succeeded.