Agentic Design Workflows
Jump to Weekly Schedule ▾Designers work inside chains of software. This seminar teaches students to direct a coding agent — the course uses Claude Code as its example — to reshape those chains around their own practice. In the first half, each student builds, publishes, and maintains a personal website entirely through the agent, learning how to specify intent, give the agent lasting context, and check its work. In the second half, each student chooses their own project: a workflow, tool, or plugin that removes real friction from their design process. Lectures, guest lectures, and student precedent presentations frame AI as a design partner and as a subject of critique.
Coding agents shift the question from can I program this? to can I say precisely what I want? — a question designers are trained to answer. Specifying, iterating, reviewing, and critiquing are studio skills; the agent turns them into working software. This course treats that shift as both an opportunity and a subject of critical inquiry.
The course is built around the student's existing workflow rather than a new one. Each student starts from what they already use — Rhino, Grasshopper, Adobe, GIS, a sketchbook — and ends with an AI-assisted workflow they actually use, documented on a website they maintain themselves. The personal site is the first project because it is the most transferable: every designer needs a public portfolio, and running one through an agent teaches the full cycle — spec, build, version, publish, maintain — on material students care about.
One weekly session, run as a seminar with a lab component. From Week 2, each session opens with a student precedent presentation — an agent-built tool, workflow, plugin, or designer website, presented as a case study. A short lecture or demo follows, then desk crits, where students work with the instructor available for individual guidance.
Work is assessed on the quality of direction as much as the quality of output: clarity of specifications, rigor of verification, evidence of real use on studio work, and depth of reflection. A student who writes a precise spec, reads what came back, catches what is wrong with it, and says so, has done the work of this course.
AI Fluency. In Weeks 2–7, students work through Anthropic's free online course AI Fluency: Framework & Foundations (14 lessons, about four hours) as homework — roughly 40 minutes a week — and discuss each week's lessons in class. Its 4D framework — Delegation, Description, Discernment, Diligence — gives the seminar a shared vocabulary for working with agents. The completion certificate is due at the midterm. Enroll free through Anthropic Academy.
Lectures shared with LAAR 61400. Four of this course's lectures are also taught in Representation and Computation I, where they are compressed. Here they are taken slower and pushed further: Cybernetics and Design in particular is the theoretical and technical spine of Part I rather than a single week's overview. Students who have taken LAAR 61400 will recognize the decks and should expect the discussion to go past them.
Part I — The Managed Site (Weeks 1–7). Everyone builds the same kind of thing: a personal website, built and then run entirely through a coding agent. Students who already have a site extend it into an agent-managed one. Part I is where the shared vocabulary is built — what a script is, what a website is made of, what an agent reads before it acts, and how a design system is written down so an agent can follow it.
Part II — Choose Your Adventure (Weeks 8–13). Each student develops something useful to their own practice, in one of three tracks.
| Track | What it is | Examples |
|---|---|---|
| A | Workflow A repeatable routine the agent runs for you |
A Claude Code skill that turns a Rhino export into a presentation board; a batch pipeline that renames, encodes, and files project images |
| B | Tool / App A standalone script or small web app |
PNG silhouette → scaled CAD block; OpenStreetMap → layered figure-ground SVG; a precedent-library browser |
| C | Plugin An extension inside design software |
A Grasshopper Python component; a Blender add-on; an Illustrator or Photoshop script; a Figma plugin; an MCP connector between a design tool and Claude |
This course runs on a personal machine, not a lab machine — an agent needs install rights, a persistent project folder, and a signed-in account, none of which survive on a shared computer. Everything below is free except the agent subscription. Rhino 8 is needed from Week 2 on; its Grasshopper Python component is where this course first reads code.
Personal Laptop — required. Windows or macOS, with rights to install a coding agent and Git. Bring it to every session; the lab component assumes it. For hardware recommendations, refer to the SSA IT Student Handbook. Technical support: CCNY IT Service Desk — servicedesk@ccny.cuny.edu · 212 650 7878 · Mon–Fri 8:00 AM – 6:00 PM.
Accounts to create. GitHub (free) and Anthropic Academy (free, for the AI Fluency course). A personal domain is optional and costs roughly $10–15 a year; GitHub Pages gives you a public URL without one.
Coding-agent subscription — required. An active paid plan for the semester is a requirement of the course; students without one cannot complete the assignments. Budget roughly $80–100 in total.
Agentic AI — Course Stance. This course separates three kinds of knowledge:
- Button knowledge — which command does what, like Offset in AutoCAD. Easy to look up.
- Behavior — how a drawing or the ground responds to a move, like tighter contours shedding water faster. Learned by making.
- Judgment — whether the result is right for the site and the people who use it. Built through critique.
An AI agent is good at button knowledge, including its own: Claude can walk you through setting up an agentic workflow, such as connecting it to Rhino through MCP or starting a project in Claude Code. Class time therefore goes to behavior and judgment, which you need to direct an agent and check what it gives back.
CCNY Email. Communication happens via CCNY email. Students need to check and be responsive to their CCNY email.
This course is an elective in Topics in Computational Studies, open to students across the school's programs, and introduces the computational skills and thinking processes necessary for a student preparing for a career in the design professions. The course supports the mission of the Graduate Program in Landscape Architecture at the Bernard and Anne Spitzer School of Architecture of the City College of New York, which asserts that landscape architecture plays an essential role in connecting social justice to environmental design and the planning of landscape systems in the urban realm. The Graduate Program prepares students to be leaders in the field through innovative research and practice in urban ecological design, planning, and policymaking. This course teaches students responsive technologies and strategies to address issues of globalization, expanding urbanization, social and environmental justice, the transformation of land management practices in response to diminishing natural resources, and resilient adaptation to climate change.
- Agent literacy — Understand how coding agents work: what they read, what they act on, where they fail.
- Designers as tool-makers — Treat software as a design material; shape your own instruments instead of adapting practice to default tools.
- Workflow as a design object — See design practice as a sequence of steps that can be examined, measured, and redesigned.
- Critical AI practice — Situate AI-assisted design in questions of authorship, labor, dependence, and environmental and financial cost.
- Self-maintained professional presence — Own and sustain a public body of work on the web.
By the end of the course, students will be able to:
- Specify — Translate design intent into a written build specification an agent can execute.
- Build and publish — Build a personal website, keep its history with Git, and publish it to the web.
- Manage through context — Maintain that site through the agent using a project context file (CLAUDE.md), a documented design system, and reusable skills.
- Verify — Read what the agent wrote, check it by previewing, comparing versions, and testing on real inputs, and decide whether to accept, revise, or discard it.
- Audit and scope — Map your own design workflow, locate repetitive friction, and scope a useful intervention.
- Develop — Build and document a working workflow, tool, or plugin that connects to the software you already use.
- Articulate — Present and critically reflect on the role of AI in your practice.
Three things are made in this course, and ten milestones pace them.
- Agent-managed personal website — Live at a public URL, with a CLAUDE.md, a documented design system, at least one reusable skill or pipeline, full Git history, and a case-study page for the Part II project.
- AI workflow presentation — Ten minutes: the workflow before, the intervention, a live demonstration, evidence of use on real work, and a critical reflection on what was gained, lost, and handed over.
- Precedent presentation — One per student, at the start of a session in Weeks 2–13: an agent-built tool, workflow, plugin, or designer website, presented as a case study — what it does, how it was made, and what it suggests for design practice.
| ID | Milestone | Week |
|---|---|---|
| D1 | Workflow audit — a diagram of a recent project's workflow with friction points marked | 02 |
| D2 | BUILDSPEC.md for the personal site | 03 |
| D3 | CLAUDE.md + site design system | 04 |
| D4 | Site live at a public URL | 05 |
| D5 | One skill or pipeline + two projects published through it | 06 |
| D6 | Managed site v1 + Part II proposal (problem, current workflow, track, success criteria) + AI Fluency certificate | 07 |
| D7 | Project BUILDSPEC + repository | 08 |
| D8 | Prototype working on one real input | 09 |
| D9 | Tested on current studio work + peer feedback | 11 |
| D10 | Project case-study page live + presentation draft | 13 |
Four guest lectures over Zoom bring designers and researchers working at the intersection of design and computation into the seminar, in Weeks 5, 6, 10, and 12: Bradley Cantrell, Xun Liu, Afshin Ashari, and Phillip Fernberg.
Dates are set against the Spring 2027 academic calendar once it is published. Weeks 2–13 open with a student precedent presentation. AI Fluency lessons are watched before class in Weeks 2–7 (see AI Fluency).
Part I — The Managed Site
| Week | Topic | Tools | Work |
|---|---|---|---|
| 01 | From Tool Users to Tool Makers Course introduction; chat versus agent; a tour of agent-built precedents; machine setup; precedent presentation sign-up ▸ Lecture: A History of Computational Thinking |
Claude CodeGitGitHubRhino | Install and verify all of them. Pick your precedent slot. |
| 02 | Coding 101 — How a Machine Reads Instructions What a computer actually does; what a script is; the five moves — name, repeat, choose, bundle, read and write — built up inside a Grasshopper Python component, where the inputs you wire are the variables the code uses; tracing a loop by hand; reading an error ▸ Lecture: Coding 101 ▸ Workshop 01: Reading a Script |
RhinoGrasshopperPythonClaude Code | D1 due — workflow audit: one recent project drawn as a sequence of steps, with the friction marked AI Fluency: introduction; why AI fluency; the 4D framework |
| 03 | What a Website Is Made Of HTML, CSS, and JavaScript — what each does and how they make up a page; type, grid, and color as the design decisions an agent needs written down; planning a site in chat; writing BUILDSPEC.md ▸ Lecture: Web Coding Literacy ▸ Lecture: Graphic Design 101 (type, grid, color) |
HTMLCSSJavaScript | D2 due — BUILDSPEC.md for your site AI Fluency: generative AI fundamentals; capabilities and limitations |
| 04 | Agentic AI — Context Is Design The agent loop and what an agent can touch; every session starts blank; CLAUDE.md as the project's standards manual; the folder as structure; names are context; single source of truth; writing a design system the agent follows ▸ Lecture: Cybernetics and Design |
Claude CodeMarkdown | D3 due — CLAUDE.md + site design system AI Fluency: delegation; project planning and delegation |
| 05 | Design and Build Guest lecture (Zoom); first build in Claude Code; local preview; Git and GitHub Pages; domains and DNS; desk crits |
Claude CodeGitGitHub | D4 due — site live at a public URL AI Fluency: description; effective prompting techniques |
| 06 | Skills — Turning Instructions into Instruments Guest lecture (Zoom); turning repeated instructions into a reusable skill or pipeline; the image standard as a worked example; desk crits |
Claude CodePython | D5 due — one skill or pipeline, plus two projects published through it AI Fluency: discernment; the Description–Discernment loop |
| 07 | Midterm Review Site pin-up; Part II pitches to the room |
D6 due — managed site v1 + Part II proposal + AI Fluency certificate AI Fluency: diligence; conclusion; course quiz |
Part II — Choose Your Adventure
| Week | Topic | Tools | Work |
|---|---|---|---|
| 08 | Scoping the Useful Case studies across the three tracks; finding the smallest useful version; setting up project repositories |
GitGitHub | D7 due — project BUILDSPEC + repository |
| 09 | Connecting Agents to Design Software File formats as interfaces; the scripting environments inside Rhino, Grasshopper, Blender and Adobe; APIs; MCP connectors in practice |
RhinoGrasshopperMCPPython | D8 due — prototype working on one real input |
| 10 | Desk Crits Guest lecture (Zoom); testing your tool against current studio work |
Bring live studio files to test on | |
| 11 | Desk Crits — Peer Tool Swap Each student runs someone else's tool on their own work and reports back |
D9 due — tested on studio work + peer feedback | |
| 12 | Desk Crits — Refinement Guest lecture (Zoom); hardening the tool against real inputs; documentation |
Refinement against peer feedback | |
| 13 | Publishing the Work A project case-study page on your managed site; publishing the repository; presentation rehearsal |
GitHubClaude Code | D10 due — project page live + presentation draft |
| 14 | Final Review Presentations of AI workflows to invited critics |
Final due — agent-managed site + ten-minute workflow presentation |
All students are held to high and consistent standards. Work is considered on its own merits and in relationship to the work of others, to make clear distinctions across the range of work. The full range of the grading scale may be used. Grades are not negotiable. Design work is graded on the following criteria:
- Completeness — Assignments are complete and graphically legible.
- Technical Skills — Executed with appropriate method and proficiency across media.
- Accuracy and Presentation — Completed with precision and presented professionally.
- Effort and Concept — Iterates through multiple drafts; shows experimentation and improvement; concepts are articulated and well-developed.
- Participation — Engages in discussions and group work.
- Attendance — Consistent preparation and on-time presence.
| Grade | Explanation | Quality Points |
|---|---|---|
| A+ | Exceptional | 4.00 |
| A | Excellent | 4.00 |
| A− | 3.70 | |
| B+ | 3.30 | |
| B | Good | 3.00 |
| B− | 2.70 | |
| C+ | 2.30 | |
| C | Satisfactory | 2.00 |
| F | Failure / Unsuccessful Completion | 0.00 |
A grade of C is the lowest passing letter grade for graduate students. Students will not receive credit for this course if their final grade is below C (2.0). Per the Graduate Bulletin, a graduate student with a GPA below 3.0 cannot receive a Master's Degree. For program-specific information on grades, academic standing, probation, and dismissal, meet with the graduate student advisor.
Attendance
This course meets once a week; the day, time, and room are set against the Spring 2027 calendar. Attendance is required and is taken at all scheduled sessions.
Per CCNY policy on lateness and absence, no distinction is made between excused and unexcused absences, and an instructor may treat lateness as equivalent to absence. For non-clinical courses, the number of hours absent may not exceed twice the number of contact hours the course meets per week. An instructor has the right to drop a student for excessive absence, entering a grade of WU. A student may appeal to the Committee on Course and Standing.
Absence for religious observance or jury duty is an exception. Notify the instructor prior to an absence whenever possible, and append a doctor's note or other written proof where relevant.
Academic Integrity
Academic dishonesty is prohibited at CUNY and is punishable by penalties including failing grades, suspension, and expulsion. Plagiarism — presenting the words, drawings, ideas, or opinions of someone else as one's own — is a serious instance of academic dishonesty. All assignments must be the student's original work, produced for this class and no other. Any copying, even short excerpts, from another book, article, or Internet source, published or unpublished, without proper attribution or citation, will result in automatic failure of the course.
You will fail this course if you: (1) submit work used for another course; (2) copy material and submit it as your own without quotation and citation, or otherwise represent another's work as your own; (3) submit the same work as another student. Plagiarized work will be reported to the CCNY Academic Integrity Committee per the CUNY Policy on Academic Integrity.
Incompletes
Grades of "incomplete" (INC) are not given unless there is evidence of a medical or personal emergency. In such cases, instructor and student develop a contract to complete work by a specified date, per CCNY policy. This contract must be processed by the academic advisor and approved by the Program Director and the Chair's Office. Missed work due to illness must be explained with a physician's note.
Classroom Civility
All students are expected to participate in class discussions. Meaningful and constructive dialogue is encouraged; discussion should be civil, respectful, and relevant to the topic. This requires a willingness to listen, tolerance for different points of view, and mutual respect from all participants. Guest critics will be informed of this expectation for civility.
Use of Electronic Devices
Students are expected to engage in active learning during class time. Mobile phones, texting, and social media are distracting; please put handheld devices away and out of view during class. The appropriate use of laptops will be discussed. The instructor provides periodic breaks; personal devices may be used during these.
City College Library Research Support
The Spitzer School of Architecture's library is a shared resource and a necessary supplement to all research and design work. Direct questions to library staff or the Architecture Librarian.
nsanchez@ccny.cuny.edu
library.ccny.cuny.edu/architecture
AccessAbility Center (AAC)
The AAC facilitates equal access and coordinates reasonable accommodations and support services for students with disabilities while preserving academic standards. Students registered with the AAC should inform the instructor at the beginning of the semester. Faculty must receive an official accommodation memo before implementing accommodations.
212 650 5913 (TTY/TTD 212 650 8441)
disabilityservices@ccny.cuny.edu
ccny.cuny.edu/accessability
Health and Wellness Services
City College's Office of Health and Wellness Services offers free and confidential counseling.
212 650 8222 — counseling@ccny.cuny.edu
Office of Diversity and Compliance
City College complies with CUNY policies regarding discrimination. The College has resources to support students who have experienced sexual violence, intimate partner/domestic violence, gender- or race-based discrimination, harassment, or stalking. For confidential support, contact the Student Psychological Counselor / Confidential Advocate at 212 650 8905 or the Gender Resources Program at 212 650 8222. The Title IX Coordinator is Diana Cuozzo.
212 650 7330 — dcuozzo@ccny.cuny.edu
ccny.cuny.edu/affirmativeaction
Public Safety
For an emergency on campus, call Public Safety at 212 650 7777. Off campus, call 911.