Further Reading for Devin
Tutorials, documentation and walkthroughs for designing with Devin, as listed in the published guide.
How to design interfaces with Devin in OpenDesign: a multi-step build delegated and handed back, one docs-section task from brief to reviewed file, and the limits to know before you start.
“A docs section delivered
while I review something else.”
THREE WAYS INTO THIS DEVIN GUIDE
This guide: brief, references, design rules and a reviewed HTML result.
Read this guide SETUPHere is the full path from a clean machine to a Devin for Terminal that can build and verify UI.
Go to setup COMPARISONHow Devin differs from Codex, Claude Code, Cursor for design work, and when to choose another workflow.
See the comparisonOne Complete Devin Design Task
A single task, shown end to end: the brief and constraints you hand over, the artifact that comes back, and the checks you still run before it is done. The interface below is an illustrative example built for this page, not a recorded Devin run.
BriefDesign the getting-started section of a developer docs site: navigation, an article with a callout and code, and an on-this-page rail. Hand the whole section back as one reviewable file. Desktop and phone.
data-od-id hooksWrite the brief, select the design system and define the acceptance criteria.
Plans the layout, writes the HTML, CSS and JavaScript and revises it on request.
Provides the design system and skill, renders the preview and stores every version as a file in the project.
Visual hierarchy, spacing on the 8px grid, both breakpoints and every interaction are checked before handoff.
Three columns on the 8px grid; the article measure stays under 72 characters.
Title, callout, then steps; the accent marks the active navigation item only.
Navigation becomes a sheet; the on-this-page rail folds into a jump menu.
Copy the code, jump to a heading, open the navigation sheet.
Fit
Compatibility
This guide covers Devin as connected through the OpenDesign desktop app. Published references checked on 6 September 2026.
Devin for Terminal is the command-line version of Devin, Cognition’s autonomous AI software engineer. It runs as a local coding agent with access to your codebase, tools, and environment, planning and executing multi-step tasks on its own. This page is about designing interfaces with Devin through OpenDesign, not about Devin’s own interface. OpenDesign’s setup notes list the available agents.
Devin (Cognition) account — account-based sign-in, not BYOK. Authenticate with your Devin (Cognition) account — credentials stay with your agent on your machine. This page does not promise a quota or price.
Check the download page for desktop builds. The Node.js and pnpm requirements in the source quickstart apply to running from source, not to installing a desktop package. Minimum compatible Devin version: not verified here.
Follow the connection instructions shown by your installed version, then run a small task. Confirm that Devin handled it and that the artifact opens. A download alone does not establish a working connection.
Start with the desktop app
Download first, complete the Devin setup for your installed version, then check a small result. You do not need to build OpenDesign from source to follow this path.
Choose the package for your computer, install it and open the app.
Download OpenDesignFollow the Devin instructions in your installed version. Authenticate with your Devin (Cognition) account — credentials stay with your agent on your machine.
Devin documentation# 1. Install Devin for Terminal
curl -fsSL https://cli.devin.ai/install.sh | bash
# 2. Start it in your project and sign in on first run
cd your-project
devin # sign in with your Devin (Cognition) accountFrom the Devin setup notes in the published guide; check the vendor documentation for the current command.
Use a small brief so you can judge the whole loop, including one revision.
Build a settings screen with a profile form and a save confirmation. Use my design rules. Check it at desktop and mobile widths.
To run OpenDesign from source, follow the technical quickstart instead.
The Devin design workflow
The same docs page task, followed from brief to verified file. Each step lists what you provide, what Devin does, what OpenDesign contributes and what you check.
Plain language, three to six lines. Name the audience, the job of the screen and the platforms.
A design system and a few hard rules. This is what separates on-brand output from a generic look.
Devin writes a self-contained HTML file: layout, styles, interactions and stable hooks.
The file renders inside OpenDesign at the widths you asked for. This is where the design is judged.
data-od-id targets for comments and edits.Request changes by pointing at elements in the preview. Every revision is a new file; nothing is overwritten silently.
Resources
Tutorials, documentation and walkthroughs for designing with Devin, as listed in the published guide.
The artifact types Devin can produce in OpenDesign, one skill per type.
Brand tokens and components to bind before Devin generates anything.
Starting points for decks, landing pages and product screens.
Limitations
FAQ
Start with a small task, judge the round trip, then bring the real brief. Choose the option that matches your setup; the page does not detect it.