In Episode 1, we established a seven-step workflow for building projects with AI. The video above applies that workflow to a real portfolio website from initial requirements through implementation and review. This written companion helps you follow the build without treating the video as a list of commands to copy blindly. Use it to make your own product decisions, give the coding agent useful context, and verify the finished website yourself. What you will build The project is a focused personal portfolio that explains: who you are what you build which projects demonstrate your work how someone can contact or follow you Your version may need different sections. The important part is to define the purpose and audience before choosing the layout or asking an agent to write code. Step 1: Write the portfolio requirements Start by describing the outcome rather than the visual style alone. Keep the first version narrow. A clear homepage, projects area, about information, and working contact path are more valuable than several unfinished screens. Step 2: Turn the brief into small tasks Ask the agent to divide the work into independently testable outcomes. A practical order is: establish the visual tokens and shared page shell build accessible desktop and mobile navigation create the homepage content sections add reusable project cards and project details add the about and contact destinations add metadata, sitemap, and sharing information run responsive, accessibility, and production checks Each task should state what changes, what must remain unchanged, and how the result will be verified. Step 3: Resolve content and design decisions Before implementation, answer the questions that would materially change the site: Is the site meant to attract employers, clients, collaborators, or an audience? Which projects have enough evidence to publish? Which links and calls to action currently work? Are real photographs and screenshots available? Does the site need a contact form, or is an external contact link sufficient? Which features are explicitly excluded from launch? This prevents the agent from filling gaps with generic copy or fabricated proof. Step 4: Implement using reusable content Store repeated project and tutorial information as structured content rather than duplicating it inside page components. Then the homepage, listing pages, metadata, and related-content sections can share the same source of truth. Ask the agent to implement one scoped task at a time: Review each result before moving to the next layer. Step 5: Test the portfolio as a visitor Check the experience at common phone and desktop widths. At minimum, verify: the header and mobile menu work with touch and keyboard input text does not overflow or become too small project links open the correct destinations images have useful alternative text and stable dimensions buttons have visible hover and focus states empty or unavailable sections remain hidden no broken links, console errors, or failed application requests appear pages expose accurate titles, descriptions, canonical URLs, and indexable content A successful production build is necessary, but it is not a replacement for navigating the actual interface. Step 6: Review and refine Look at the website from a first-time visitor's perspective. The opening screen should quickly answer three questions: Who is this person? What do they build or teach? Where can I see evidence? Give the agent precise feedback when something misses the mark. Name the route, component, current behavior, intended behavior, and anything that must remain unchanged. Then rerun the affected tests. Step 7: Complete the release review Before deployment, review both the public experience and the implementation: confirm every published claim and link remove placeholders and unused routes check security headers and error handling confirm secrets are not present in the client bundle or repository verify forms, analytics, and external integrations independently build the exact commit intended for release keep a rollback path and verify the public routes after deployment Track the final state accurately: implemented, tested, committed, pushed, and deployed are separate milestones. Reuse the workflow for your own project The portfolio is only the first applied build in this series. Reuse the same sequence for another project: AI makes each stage faster when the goal and constraints are clear. You still own the product decisions and the evidence that the result works.