How do I install the Cypress Quick Start skill?

Run npx skillmds@latest add dekart-xyz/cypress-quick-start in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cypress Quick Start safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cypress Quick Start?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cypress Quick Start free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cypress Quick Start?

dekart-xyz (@dekart-xyz) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cypress Quick Start by dekart-xyz — Agent Skill

Name: Cypress Quick Start
Author: dekart-xyz

File contents

Cypress Quick Start Skill

Trigger

Use when asked to run, debug, reproduce, or verify Cypress E2E tests.

Required Environment Detail

This environment often has ELECTRON_RUN_AS_NODE=1 set globally. If not overridden, Cypress fails with bad option: --no-sandbox or --smoke-test. The Make targets clear it for Cypress.

Match the Cypress spec folder to its backend env file. Use the Make targets so lane settings load normally and only clone-local resources from .env take precedence:

make cypress-run ENV_FILE=.env.cloud SPEC="cypress/e2e/cloud/*.cy.js"

Only specs that call cy.stubGoogleOAuthToken(...) need DEV_REFRESH_TOKEN_INFO or DEV_REFRESH_TOKEN. DEV_REFRESH_TOKEN_INFO must include only profile/email scopes; DEV_REFRESH_TOKEN must include BigQuery and storage scopes. Specs that use cy.setDevClaimsEmail(...) need the backend started with DEKART_DEV_CLAIMS=1, but they do not need Google refresh tokens unless they also stub OAuth.

Standard Workflow

Ensure you are in repo root.
Start local Postgres with make up-and-down.
Start backend with the matching env file, for example make server .env.cloud.
Start the frontend with make client.
If Cypress binary is missing: npx cypress install
Run the requested spec:
- make cypress-run ENV_FILE=<env-file> SPEC="<spec-path>"
Report: pass/fail, failing assertion, artifact paths (video/screenshot).

Canonical Commands

Run cloud specs:
- backend: make server .env.cloud
- Cypress: make cypress-run ENV_FILE=.env.cloud SPEC="cypress/e2e/cloud/*.cy.js"
Run Google OAuth specs against local Vite:
- backend: make server .env.googleoauth
- Cypress: make cypress-run ENV_FILE=.env.googleoauth SPEC="cypress/e2e/google-oauth/*.cy.js"
Run one spec: make cypress-run ENV_FILE=.env.snowflake-s3 SPEC="cypress/e2e/snowflake-s3/layerOrderRerunRegression.cy.js"
Run all Snowflake S3 specs: make cypress-run ENV_FILE=.env.snowflake-s3 SPEC="cypress/e2e/snowflake-s3/*.cy.js"
Open interactive UI: make cypress-open ENV_FILE=<env-file>

Notes

Base and API URLs are derived in cypress.config.js from the clone-local ports in .env.
Layer-order regression spec: cypress/e2e/snowflake-s3/layerOrderRerunRegression.cy.js
Prefer local server instances (make server ...) for running local tests.

---name: cypress-quick-startdescription: Use this skill when running, debugging, reproducing, or validating Cypress E2E tests in this repo, including the required ELECTRON_RUN_AS_NODE override.---# Cypress Quick Start Skill## TriggerUse when asked to run, debug, reproduce, or verify Cypress E2E tests.## Required Environment DetailThis environment often has `ELECTRON_RUN_AS_NODE=1` set globally. If not overridden, Cypress fails with `bad option: --no-sandbox` or `--smoke-test`. The Make targets clear it for Cypress.Match the Cypress spec folder to its backend env file. Use the Make targets so lane settings load normally and only clone-local resources from `.env` take precedence:```bashmake cypress-run ENV_FILE=.env.cloud SPEC="cypress/e2e/cloud/*.cy.js"```Only specs that call `cy.stubGoogleOAuthToken(...)` need `DEV_REFRESH_TOKEN_INFO` or `DEV_REFRESH_TOKEN`. `DEV_REFRESH_TOKEN_INFO` must include only profile/email scopes; `DEV_REFRESH_TOKEN` must include BigQuery and storage scopes. Specs that use `cy.setDevClaimsEmail(...)` need the backend started with `DEKART_DEV_CLAIMS=1`, but they do not need Google refresh tokens unless they also stub OAuth.## Standard Workflow1. Ensure you are in repo root.2. Start local Postgres with `make up-and-down`.3. Start backend with the matching env file, for example `make server .env.cloud`.4. Start the frontend with `make client`.5. If Cypress binary is missing: `npx cypress install`6. Run the requested spec: - `make cypress-run ENV_FILE=<env-file> SPEC="<spec-path>"`7. Report: pass/fail, failing assertion, artifact paths (video/screenshot).## Canonical Commands- Run cloud specs: - backend: `make server .env.cloud` - Cypress: `make cypress-run ENV_FILE=.env.cloud SPEC="cypress/e2e/cloud/*.cy.js"`- Run Google OAuth specs against local Vite: - backend: `make server .env.googleoauth` - Cypress: `make cypress-run ENV_FILE=.env.googleoauth SPEC="cypress/e2e/google-oauth/*.cy.js"`- Run one spec: `make cypress-run ENV_FILE=.env.snowflake-s3 SPEC="cypress/e2e/snowflake-s3/layerOrderRerunRegression.cy.js"`- Run all Snowflake S3 specs: `make cypress-run ENV_FILE=.env.snowflake-s3 SPEC="cypress/e2e/snowflake-s3/*.cy.js"`- Open interactive UI: `make cypress-open ENV_FILE=<env-file>`## Notes- Base and API URLs are derived in `cypress.config.js` from the clone-local ports in `.env`.- Layer-order regression spec: `cypress/e2e/snowflake-s3/layerOrderRerunRegression.cy.js`- Prefer local server instances (`make server ...`) for running local tests.

Frequently asked questions

Cypress Quick Start