Intro
Module 6 stress-tests agent workflows on tougher projects: crafting migration agents to modernize legacy Java and pairing with Figma’s MCP so designs flow straight into production-ready UI code.Video lesson
Key takeaways
- Start complex efforts by validating agent understanding—have it profile the codebase/version and restate functionality before transformations.
- Let agents draft the playbook: generate migration instructions (Java 6→17) with structure for analysis, build config, code changes, testing, and reporting, then reuse them in a custom agent.
- Package the migration agent with clear inputs (repo path, target version) and required tools so repeated runs stay predictable; review its summary after each execution.
- Expect multiple passes: inspect branches, rerun tests, and iterate on errors until both code and specs compile cleanly on the new runtime.
- For design-to-code flows, install the Figma MCP, share the design URL, and confirm the agent pulls layout context via
getDesignContext. - Ask the agent to scaffold the project (React/Vite) and render the UI; provide precise feedback (colors, layout, assets) and let it re-query Figma to fetch exact imagery.
- Use MCP-enabled tools whenever external context is needed (Figma, etc.); richer context leads to fewer manual fixes and higher-fidelity outputs.