# AI use cases for Cypress (llopresto87/Cypress) Repo: [llopresto87/Cypress](https://github.com/llopresto87/Cypress) | Use cases: 4 | Page: https://dedupedai.com/use-cases/llopresto87-cypress/ CYPRESS is an installer that copies instruction files, Markdown method files and small Python scripts into a code repository so an AI coding tool follows a written workflow for specs, tests and delegation. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Install the CYPRESS workflow into a repository: https://dedupedai.com/use-cases/llopresto87-cypress/install-workflow-into-repo/ - Build a knowledge graph of your codebase: https://dedupedai.com/use-cases/llopresto87-cypress/build-repo-knowledge-graph/ - Route a risky change through spec and failing test first: https://dedupedai.com/use-cases/llopresto87-cypress/route-risky-change-spec-first/ - Update the workflow without losing your edited files: https://dedupedai.com/use-cases/llopresto87-cypress/reinstall-without-losing-edits/ ## How to install the CYPRESS workflow into a repository with Cypress Repo: [llopresto87/Cypress](https://github.com/llopresto87/Cypress) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Copies the kernel, agent definitions and graph skeleton into your project with one installer command. **Who it is for:** A 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 problem:** Each 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 outcome:** Your project contains the kernel file, the .claude/ directory, docs/graph/ and an install stamp at .cypress/seed.json, ready for a first graph build. ### Steps 1. `git clone https://github.com/llopresto87/Cypress` 2. `./Cypress/install.sh claude-code --project-dir /path/to/your/project` 3. Read the last line of the installer output, which says the files are placed and the project's graph is not built yet. ### Prompt to paste into your agent ```text In the Cypress repo, run the installer for claude-code against the project at . 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 . ``` ### 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/llopresto87-cypress/install-workflow-into-repo/ ## How to build a knowledge graph of your codebase with Cypress Repo: [llopresto87/Cypress](https://github.com/llopresto87/Cypress) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Runs the one-time growth pass so later sessions open a few linked notes instead of rereading the code. **Who it is for:** A developer who has just installed CYPRESS into a repository and wants the first session to map the project for later sessions. **The problem:** A coding session that rereads the whole codebase spends its context window on code that is not relevant to the task at hand. **The outcome:** docs/graph/ holds short linked notes about your project, with the router index pointing to them and models.md naming the model for each kind of work. ### Steps 1. `./Cypress/install.sh claude-code --project-dir /path/to/your/project` 2. Open a session in your coding tool rooted at your project. 3. Paste `INSTALL_PROMPT.md` into the session to start the one-time growth pass. 4. Open docs/graph/models.md and name the model each host runs for each kind of work. ### Prompt to paste into your agent ```text In the Cypress repo, install the workflow into and start the growth pass in a Claude Code session there. Expected output: notes under docs/graph/ and a filled plant entry in docs/graph/index.md. Verify that the router index links to the notes the session created. ``` ### Caveat The README gives no figure for how long the growth pass takes, so the time above is an estimate and depends on the size of your repository. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/llopresto87-cypress/build-repo-knowledge-graph/ ## How to route a risky change through spec and failing test first with Cypress Repo: [llopresto87/Cypress](https://github.com/llopresto87/Cypress) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Sorts a change into a risk tier, then requires a specification and failing test before code for high-risk work. **Who it is for:** A developer about to change architecture or a contract in a shared repository who wants the AI session to slow down and write a spec first. **The problem:** An AI session can start editing code for a risky change before anyone has written down what the change should do. **The outcome:** For a T3 change, the session writes a specification and a failing test before the code, and separate reviewer workers check the result. ### Steps 1. Install the workflow with `./Cypress/install.sh claude-code --project-dir /path/to/your/project`. 2. Open a Claude Code session rooted at your project. 3. Describe the change and ask the session to classify it into a risk tier first. 4. For a T3 change, confirm the session wrote a specification and a failing test before any code edit. 5. Ask the reviewer worker to check the change against the written specification. ### Prompt to paste into your agent ```text In the Cypress-installed repo at , ask a Claude Code session to classify and then implement the change described in following the T3 process. Expected output: a specification file and a failing test committed or saved before the implementation. Verify that the failing test exists and fails before the code change is made. ``` ### Caveat The README says the tier choice and the order of spec and test are requested of the model, and no tool checks them, so you must verify the order yourself. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/llopresto87-cypress/route-risky-change-spec-first/ ## How to update the workflow without losing your edited files with Cypress Repo: [llopresto87/Cypress](https://github.com/llopresto87/Cypress) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Re-runs the installer so changed files are kept as timestamped copies before replacement. **Who it is for:** A developer who edited CYPRESS files in their repository and needs to reinstall or update the method without losing those edits. **The problem:** Re-running an installer can silently overwrite local changes to instruction files, so the team loses decisions made in those files. **The outcome:** Any file that differed from the new version is kept beside it as a timestamped copy, and matching files are left alone. ### Steps 1. `./Cypress/install.sh claude-code --project-dir /path/to/your/project` 2. Look in the project for timestamped copies of any file that differed. 3. Compare each copy with its replacement and move your edits into the new file by hand. 4. Check .cypress/seed.json for the version and options of the install. ### Prompt to paste into your agent ```text In the Cypress repo, re-run the claude-code installer against . Expected output: a list of files replaced, each with a timestamped copy of the old version. Verify that .cypress/seed.json shows the new install stamp and that each timestamped copy still exists. ``` ### Caveat The README says the install does not merge files, so any edits in the timestamped copies must be moved into the new versions by you. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/llopresto87-cypress/reinstall-without-losing-edits/