Cypress docs
Continuous fullstack delivery loops — orchestrates frontend, backend, and quality subagents (behaviour drivers, engineers, UI/UX specialist, code/security reviewers, architects) in a test → diagnose → fix → review → secure → re-test cycle until the work is production-ready
npx -y skills add jgamaraalv/delivery-loop --skill cypress-docsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Search and extract Cypress information from official documentation (docs.cypress.io, cypress.io); prefer LLM markdown under /llm/* and refuse unverified API or behavior claims.
SKILL.md
1.9 KB, as published. Nobody here has run it
Cypress Documentation
Retrieve accurate, verifiable Cypress information by treating the official docs as the source of truth — never memory.
Core rules
- Search before you claim. Never assert "Cypress can / cannot…" from memory — search the docs first, retrying with alternate terminology before concluding a feature is missing.
- Prefer the LLM-optimized docs. On
docs.cypress.io, fetch/llms.txt, then read the Markdown mirror under/llm/*— every page has one (e.g.…/app/faq→…/llm/markdown/app/faq.md). Fall back to the HTML page only if the/llmversion is incomplete. - Primary sources only: https://docs.cypress.io and https://www.cypress.io (plus
/changelog/and the cypress.io blog for version/update questions). - Never invent. If the docs can't verify a claim, say "I could not verify this in Cypress docs," offer the closest documented alternative, and never guess an API, signature, or default. Prefer "unknown" over incorrect.
- Be version-aware. Use the version if given, else assume latest stable; when behavior differs by version, call it out explicitly.
References
Read on demand (progressive disclosure):
references/search-strategy.md— query-type → doc-section routing table, the/llm/*→ standard → changelog → blog search flow, error-message routing, and/llms.txtauto-discovery · read when locating the right doc page.references/extraction-rules.md— how to extract commands / concepts / configuration, response style and confidence annotation, caching, safety rules, and a worked example · read when structuring an answer from a fetched page.