Interactive Resume — W4C project template

A W4C project template for building a personal CV site out of interactive modules. Creating a project from it generates a copy of this repository in your namespace and starts the Startup Creator agent (w4c-startup), which turns the survey answers and the module list into a planned build and files it on the project board.

This repository is a brief, not a finished site: it ships the specification, the module list and the project metadata; the Startup Creator drives the build and hands each layer to the right specialist. Read SPEC.md for the full contract — the modules, the content model, the flows, the non-functional requirements and the acceptance criteria the work is checked against.

What ships in this repository

Path	Purpose
README.md	This file: how the template is wired and how to work in the project.
SPEC.md	The product specification and acceptance criteria — the contract to work against.
.w4c/template.json	Template manifest: identity, dev-server startup conditions, starter prompt, module list (templates only).
.w4c/fields.json	Field schema — the survey questions the template and each module ask (see below).
.w4c/project.json	Project metadata committed with the repository.
.w4c/README.md	The .w4c/ folder contract, including the field-schema format.
.w4c/preview.svg	Catalog thumbnail for the template picker.
.w4c/boards/roadmap.json	The layer → task seed the Startup Creator materialises as board cards.

The template ships no diagrams/ or workflows/ folders and only a board element: a personal site does not need an architecture diagram or automation to ship, so the board files the focused layer set (plan, design, frontend, content & SEO, deploy, quality).

Modules

Each module is one screen/section of the built site. They are declared as pages in .w4c/template.json, and each may ask its own survey questions (see below):

Module	What it builds
hero-intro	Animated intro: avatar, name, headline, tagline, CTAs.
timeline-experience	Expandable experience/education timeline.
skills-matrix	Filterable skills grouped by category, with proficiency.
project-showcase	Case-study cards with a detail dialog and tech tags.
recommendations	Quote carousel with authors, roles and companies.
resume-download	Print stylesheet plus a downloadable PDF/DOCX CV.
contact-cta	Validated contact form and an availability badge.

Every module is selected in the create-project dialog; the modules you keep become board cards with their own brief, so the build starts from an explicit list instead of an implicit route list.

Survey questions — .w4c/fields.json

The template's identity and preference questions, and the extra questions a module asks, are declared in the repository's field-schema file .w4c/fields.json (the path can be overridden with the manifest's fieldsSchema). The server folds them into the create-project dialog:

• fields[] — template-level questions (name, headline, links, profile links, stack, theme, accent colour, …), merged with any inline fields in .w4c/template.json.
• pages.<module-id>[] — questions asked only while that module is selected (e.g. timeline-experience asks for the timeline layout and whether to include education).

The format is documented in .w4c/README.md. Answers become {{token}}s in the starter prompt and in each module's prompt, and are stored on the project so the agent never has to guess.

profileLinks accepts several URLs (one per line) and is the one field with a side effect: the starter prompt hands them to the Web Researcher agent, which reads each URL and seeds the resume with the person's real profile — current role, experience, skills, projects and public contact links — instead of placeholder content. links are only the links displayed on the built site. Both are optional; when profileLinks is empty (or a page cannot be read) the build proceeds from the other survey answers.

Build order

Work top-down, one layer at a time, and verify each stage before the next (details in SPEC.md §8): research the profile links (Web Researcher) → scaffold → content model → hero → timeline → skills → showcase → recommendations → print/PDF → contact → quality.

Working rules

• Content over chrome: real experience, skills and case studies beat placeholder blocks.
• Motion is an enhancement — honour prefers-reduced-motion and keep the site usable without it.
• The printed/PDF CV is a first-class output, not an afterthought.
• One concern per commit, conventional messages (feat:, fix:, chore:, docs:, test:).
• Never commit secrets.
• Keep docs/PLAN.md, the board and .w4c/project.json in sync as the project evolves.