manixh

# Portfolio Build Prompt (paste this into your AI coding agent)

You are building/updating a developer portfolio. This project ships with spec files that are the **single source of truth**. You must follow them exactly — do not invent architecture, components, content structure, or design choices of your own. If something is not covered by the spec files, ask before assuming.

## Step 1 — Read the spec files first (mandatory, in this order)

Before writing or editing any code, read these files fully if they exist in the project root:

1. `AGENTS.md` — your operating manual: what you're allowed to keep/replace and the exact build steps
2. `ARCHITECTURE.md` — tech stack, folder structure, routing, data flow, build process
3. `COMPONENTS.md` — every reusable component, its props, variants, and usage examples
4. `CONTENT_SCHEMA.md` — the data schema and exactly where every piece of personal content must live
5. `DESIGN.md` — visual system: colors, type, spacing, layout rules
6. `LICENSE` — note it and move on, no action needed

Do not skip any of these, do not skim, and do not proceed to Step 2 until you've read all that are present. If any of these files are **missing**, stop and tell me which ones are missing instead of guessing their contents.

## Step 2 — Detect project state

Check the current folder and report back:

- **Existing project detected** (there's already code beyond the spec files — e.g. `src/`, `package.json`, existing components): treat this as an update. You must reuse and adapt the existing structure/content wherever it already satisfies `ARCHITECTURE.md` and `COMPONENTS.md`, and only change what's needed to bring it into compliance with the spec files. Do not rewrite working code from scratch "for cleanliness." List what you intend to change and why, mapped to a specific spec file.
- **Fresh/empty project**: treat this as a new build from the spec files.

## Step 3 — Gather missing information (only if needed)

Cross-check `CONTENT_SCHEMA.md` against what already exists in the project:

- If personal content (name, bio, projects, skills, links, images, etc.) required by `CONTENT_SCHEMA.md` already exists in the project (e.g. in a data file, CMS folder, or config), extract and reuse it — don't ask for things you can already find.
- For anything required by `CONTENT_SCHEMA.md` that is genuinely missing, ask me directly, as a single consolidated list of questions grouped by schema section (e.g. "Profile", "Projects", "Skills", "Social links"). Don't ask one question at a time. Don't ask about anything not required by the schema.
- If `DESIGN.md` exposes any theme-level choices (color mode, accent color, font pairing, etc.), ask about those in the same batch.

## Step 4 — Confirm before building

Once you have everything you need, output a short build plan before touching any files:

- Which files/components you will create, edit, or leave untouched
- Which sections of `CONTENT_SCHEMA.md` will be populated with what data
- Any assumptions you're making, explicitly flagged as assumptions

Wait for my explicit "yes/go/confirmed" before writing any code. Do not start building on your own initiative, even if you're confident.

## Step 5 — Build strictly to spec

Once confirmed:

- Follow `ARCHITECTURE.md` exactly for folder structure, routing, and data flow — don't introduce a different framework, state approach, or file layout.
- Use only the components and variants defined in `COMPONENTS.md`. If you need a component it doesn't define, stop and ask rather than inventing one.
- Populate content exactly where `CONTENT_SCHEMA.md` says it must live — don't hardcode personal content inline in components if the schema defines a data layer.
- Apply `DESIGN.md` precisely (colors, spacing, type scale, breakpoints) rather than default framework styling.
- Follow every explicit instruction in `AGENTS.md`, including what to preserve vs. replace.

## Step 6 — Self-check before you tell me you're done

Before reporting completion, verify and fix:

- Project installs and builds cleanly with no errors or warnings (run the actual install/build/lint commands from `ARCHITECTURE.md`)
- No broken imports, unused files, or dead code left behind
- No missing content fields vs. `CONTENT_SCHEMA.md`
- No component used outside the variants/props defined in `COMPONENTS.md`
- Responsive behavior and design tokens match `DESIGN.md`
- No console errors in dev mode

If any check fails, fix it yourself before reporting — don't hand me a broken build.

## Step 7 — Final report

Summarize: what was built/changed, which files were touched, any assumptions made, and any spec gaps you had to ask about. Do not describe features or structure that aren't actually in the spec files.

---

**Golden rule for the whole task:** if the spec files say it, build it that way. If the spec files don't say it, ask — never improvise architecture, components, content placement, or design on your own judgment.