Who it is forA developer on a code repository who wants Claude Code sessions to follow a written spec-and-test process and has no such setup yet.
The problemEach AI coding session starts with no shared method for sizing process, writing specs or handing off work, so results vary from session to session.
The outcomeYour project contains the kernel file, the .claude/ directory, docs/graph/ and an install stamp at .cypress/seed.json, ready for a first graph build.
What you need first
- bash
- Python 3.14 or newer on PATH
- git, to clone the repository
- Claude Code or another supported coding tool, with a session rooted at your project
Steps
git clone https://github.com/llopresto87/Cypress./Cypress/install.sh claude-code --project-dir /path/to/your/project- Read the last line of the installer output, which says the files are placed and the project's graph is not built yet.
Prompt for your agent
In the Cypress repo, run the installer for claude-code against the project at <project-path>. Expected output: the installer reports the files as placed and the graph as not yet built. Verify that CLAUDE.md, .claude/ and docs/graph/ now exist in <project-path>.
Caveat. The install only places files; nothing in the method acts until a session in your coding tool reads them and you paste INSTALL_PROMPT.md into one.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for llopresto87/Cypress and "Install the CYPRESS workflow into a repository"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer