# AI use cases for Res (alextnetto/res) Repo: [alextnetto/res](https://github.com/alextnetto/res) | Use cases: 3 | Page: https://dedupedai.com/use-cases/alextnetto-res/ RES is an agent skill that studies a web SaaS product through the browser and writes a knowledge base of its screens, rules, data model, design tokens and production barriers for rebuilding it. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Turn a SaaS product into a build kit for your team: https://dedupedai.com/use-cases/alextnetto-res/rebuild-saas-from-browser-study/ - Find what blocks a clone from launching: https://dedupedai.com/use-cases/alextnetto-res/check-production-barriers-before-launch/ - Check a knowledge base and build its report and zip: https://dedupedai.com/use-cases/alextnetto-res/validate-and-package-knowledge-base/ ## How to turn a SaaS product into a build kit for your team with Res Repo: [alextnetto/res](https://github.com/alextnetto/res) | Difficulty: Intermediate | Time: 2 hours | Basis: From the README Have an agent study a web product in a trial account and hand back a report and a zip for rebuilding it. **Who it is for:** A product lead whose team relies on a web SaaS tool and needs to rebuild it or ship a similar product for a new market. **The problem:** Rebuilding a product from memory or screenshots misses screens, edge states, business rules and launch blockers, and the knowledge sits in one person's head. **The outcome:** A knowledge base with screens, rules with evidence, data model, design tokens and a build plan, plus REPORT.html for people and a handoff zip for a coding agent. ### Steps 1. In a terminal, run `claude plugin marketplace add alextnetto/res` 2. Run `claude plugin install res@res`, then start a new Claude Code session. 3. Create a trial account of the product with an email you own, and log in to it in a separate Chrome profile that your agent's browser tool uses. 4. Ask the agent to study the product for your market and scope, and to use the trial profile without asking you questions until it is done. 5. When the study ends, open REPORT.html and unzip the handoff zip for your coding agent, which starts from BUILD.md. ### Prompt to paste into your agent ```text Using the res skill from the alextnetto/res repo, study for the market through the trial browser profile, and do not ask me questions until finished. Expect a re-/ folder with REPORT.html and a handoff zip. Verify that REPORT.html links every rule and barrier ID and that sandbox/ledger.csv lists no writes left unresolved. ``` ### Caveat RES drives a real browser, so use it only on products you are allowed to study and prefer a trial account over your production login. Risk, reverse engineering: Studying a product's screens and rules may breach its terms, so check the product's terms and get legal advice before you rebuild it. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. 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/alextnetto-res/rebuild-saas-from-browser-study/ ## How to find what blocks a clone from launching with Res Repo: [alextnetto/res](https://github.com/alextnetto/res) | Difficulty: Intermediate | Time: 2 hours | Basis: From the README Get a ranked list of integrations, licenses and approvals a rebuilt product would need before launch. **Who it is for:** A founder or product manager planning a launch in a regulated or integration-heavy market who needs to know what could stop them before writing code. **The problem:** Launch blockers such as partner approvals, certifications and distribution gatekeepers often surface late, when lead times are already too long. **The outcome:** clone/barriers.md with each barrier's category, the features it blocks, severity, market weight, lead time, cost source and a mitigation. ### Steps 1. Run `claude plugin marketplace add alextnetto/res` in a terminal, then `claude plugin install res@res`. 2. In your charter, name the target market and say that production barriers are a priority. 3. Let the agent finish the study, which includes a first barrier scan during recon. 4. Open clone/barriers.md in the knowledge base and sort the entries by severity and lead time. 5. Assign an owner to each barrier that blocks a feature you plan to launch with. ### Prompt to paste into your agent ```text Using the res skill in the alextnetto/res repo, study with a charter focused on production barriers for the market, and do not ask me questions. Expect clone/barriers.md inside re-/. Verify that every barrier lists severity, lead time and a mitigation with a source ID. ``` ### Caveat The barrier list is built from public documents and observed behavior, so confirm lead times and costs with the named gatekeeper before you plan around them. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. 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/alextnetto-res/check-production-barriers-before-launch/ ## How to check a knowledge base and build its report and zip with Res Repo: [alextnetto/res](https://github.com/alextnetto/res) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Run the RES scripts to validate, render and package a study without starting a new agent session. **Who it is for:** An engineer or reviewer who already has a knowledge base folder and needs to confirm it is complete before sharing it with developers. **The problem:** A knowledge base with broken IDs or missing evidence can mislead the people or coding agents who rebuild from it. **The outcome:** A passing check, a generated REPORT.html and a handoff zip ready to send. ### Steps 1. Clone the repo with `git clone https://github.com/alextnetto/res.git` and change into the Res folder. 2. Create a new knowledge base with `node skills/reverse-engineering-saas/scripts/init-kb.mjs --product "Acme CRM" --git`, replacing the product name with yours. 3. Validate the folder with `node skills/reverse-engineering-saas/scripts/check-kb.mjs re-acme-crm`, using your own folder name. 4. Render the report with `node skills/reverse-engineering-saas/scripts/build-report.mjs re-acme-crm`. 5. Package the handoff with `node skills/reverse-engineering-saas/scripts/pack-kb.mjs re-acme-crm`. ### Prompt to paste into your agent ```text In the res repo, run skills/reverse-engineering-saas/scripts/check-kb.mjs on the folder re-, fix any reported problems, then run build-report.mjs and pack-kb.mjs on the same folder. Expect a passing check, REPORT.html and a zip in the knowledge base folder. Verify that the check reports no failures before packing. ``` ### Caveat The scripts need Node.js 22 or later, and the example folder name acme-crm must be replaced with the folder your init step created. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. 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/alextnetto-res/validate-and-package-knowledge-base/