Updated 1d ago
by llopresto87
Cypress
CYPRESS (Contextual Yield Protocol for Routed Expert Seed Systems) — a project- and vendor-agnostic multi-agent seed for AI coding tools. Drop it into any repo to give agents a large number of per-role expert team, named protocols, a progressive-discovery knowledge graph, and spec- and test-driven discipline by default.
103 GitHub stars (103)
+60 in 20 days
| Period | New stars |
|---|---|
| Sep 27 | 0 |
| Sep 28 | 0 |
| Sep 29 | 0 |
| Sep 30 | 0 |
| Oct 1 | 0 |
| Oct 2 | +1 |
| Oct 3 | +15 |
| Oct 4 | +27 |
| Oct 5 | +5 |
| Oct 6 | +5 |
| Oct 7 | +2 |
| Oct 8 | +1 |
| Oct 9 | +2 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | +1 |
| Oct 14 | +1 |
| Oct 15 | 0 |
| Oct 16 | 0 |
- 15 skills (15 skills found in its SKILL.md files)
- 5 forks (5 forks)
- 1d ago last update (Last updated 1d ago)
Install
Skills CLI
npx skills add llopresto87/Cypress
Asks which skills and agents to install. Just one: npx skills add llopresto87/Cypress --skill adopt-existing — add -g for every project.
Claude Code
git clone https://github.com/llopresto87/Cypresscp -r "Cypress/skills/adopt-existing" ~/.claude/skills/
Copies the adopt-existing skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add llopresto87/Cypress
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
adopt-existing
Source-first growth of an existing single- or multi-repository project into CYPRESS's unified docs/graph knowledge system. Use from initialize when code already exists, or for a graph refresh after material code changes. Scout executable evidence, model subsystem nodes, build project-specific architecture/product/API/data/dependency/prompt/operations leaves, connect them for progressive discovery…
skills/adopt-existing/SKILL.md on GitHub (opens in a new tab) -
adr-writer
Author an Architecture Decision Record that captures a non-obvious technical choice — its context, the decision, the consequences, the rejected alternatives, and the reversibility cost. Use whenever a non-trivial dependency is picked, a framework is chosen, a one-way door is opened, two specialists disagree and the orchestrator must pick, or anyone in a future session would ask "why did we do thi…
skills/adr-writer/SKILL.md on GitHub (opens in a new tab) -
brainstorm-internal
The divergence technique CYPRESS applies to itself, with no user in the loop — generating genuinely distinct options against evidence already in hand, stating what would have to be true for each, and naming the one fact that would kill each. Use when a choice is the session's to make and the user has nothing to add to it - filling grill.md §7, assembling an ADR's rejected alternatives, choosing b…
skills/brainstorm-internal/SKILL.md on GitHub (opens in a new tab) -
brainstorm-socratic
The Socratic questioning technique that converges a vague goal — question selection, one-to-three-per-turn pacing, the reflect-every-two-answers cadence, the nine-question hard cap, and the eight-point convergence checklist that defines "converged". This is the USER-FACING of the brainstorm protocol's two modes — use it when the decision is the owner's to make; when it is the session's own, the m…
skills/brainstorm-socratic/SKILL.md on GitHub (opens in a new tab) -
context-router
Resolve the minimum set of knowledge-graph nodes needed for a task before reading any source file. Use at the START of every non-trivial task once a project has a knowledge graph — when changing a subsystem, tracing a bug, planning work, answering a question about how something works, or onboarding. This is the mechanism that keeps a large or multi-repo codebase inside a context window: it decide…
skills/context-router/SKILL.md on GitHub (opens in a new tab) -
grill-planner
The authoring discipline for the project's plan-of-record at docs/graph/plans/grill.md — what a worker filling any section carries, and the audit that says whether the plan is still consistent with the specs, the wiki, and the decisions. Use whenever a brief produces or updates grill.md, or grill.md needs a consistency pass. The pass itself (which section, which owner, in which order) is protocol…
skills/grill-planner/SKILL.md on GitHub (opens in a new tab) -
holistic-editing
The discipline for any change, fix, refactor, or review whose unit of work is larger than a trivial one-liner. Use whenever you edit existing code or a knowledge page — the unit of work is the whole file or module, never the smallest diff that satisfies the request. A change is complete only when the file reads as if the requirement had existed from the beginning: no bolted-on functions, no _v2 w…
skills/holistic-editing/SKILL.md on GitHub (opens in a new tab) -
humanizer
Draft or revise prose a person will read (documentation, README text, ADR and spec bodies, runbooks, pull-request descriptions, commit messages, delivery summaries, briefs and reports for the owner) so it reads as deliberate writing by a competent author, without changing what it says. Use when a draft came out of a model and shows the tells (empty contrasts, staged openers, one-line closers, for…
skills/humanizer/SKILL.md on GitHub (opens in a new tab) -
knowledge-graph
Build and maintain the project's knowledge graph — a tiered set of nodes under docs/graph/ that lets an agent load only the few facts a task needs instead of the whole codebase. Use when adopting a project, when a fact changes, when a node grows too large, or when a task should have matched a node's triggers and didn't. Enforces one home per fact (dedup), honest per-node budgets, cite-don't-fabri…
skills/knowledge-graph/SKILL.md on GitHub (opens in a new tab) -
library-wiki
Maintain a project-local, version-pinned wiki of every external dependency. Use whenever a new library is being added, an existing one is being upgraded, an idiom for using a library is being adopted, a pitfall is being discovered, or a wiki page is missing for code that already uses a library. The wiki is the source of truth this project consults BEFORE writing code that touches a library; agent…
skills/library-wiki/SKILL.md on GitHub (opens in a new tab) -
research-and-ingest
Find authoritative sources on the web (or via documentation MCP servers like Context7/DeepWiki), download or snapshot them when allowed, normalize them into clean Markdown, and stage them for the library-wiki. Use whenever a new library/spec/API/standard is being added, a wiki page is stale, an ADR needs current evidence, or a behavior best practice needs verification. Always prefer official upst…
skills/research-and-ingest/SKILL.md on GitHub (opens in a new tab) -
spec-author
Write an executable specification under docs/graph/specs/ that turns a clear goal into testable contracts. Use whenever a feature, endpoint, job, significant function, or AI interaction needs a contract that the tester can encode and the implementer can satisfy. Coordinates product (§3, §9), architect (§4, §6, §7), and tester (§10 testability review) into a single signed-off document. Specs are t…
skills/spec-author/SKILL.md on GitHub (opens in a new tab) -
test-first
The test-SHAPING technique applied inside the test-first protocol — pick the lowest test level that exercises the behavior (unit, integration, contract, e2e, golden, property-based, evaluation), name the test after the spec contract, and assert one outcome per test. The workflow itself (entry conditions, RED-GREEN-REFACTOR-COMMIT gates, variants, exceptions) is the test-first protocol.
skills/test-first/SKILL.md on GitHub (opens in a new tab) -
toolcraft
Doctrine (kernel §3.8) — when an operation will recur across independent sessions, the unit of work is a durable, tested, cataloged tool, not a throwaway script. Defines what counts as a durable tool, what stays disposable, the procedure sibling (a project skill), and the fail-closed rule that a task is incomplete until a durable tool is cataloged or recorded absent. AUTHORING a tool is agent.too…
skills/toolcraft/SKILL.md on GitHub (opens in a new tab) -
validate-knowledge
Prove that a knowledge base actually works before trusting it — after building or adopting docs, a knowledge graph, or a wiki, verify it can orient a fresh agent and resist false premises. Use at the end of an adoption, after a large docs change, or before relying on the graph to route work. Two methods: clean-context test agents answering known-answer and adversarial questions, and enforcement t…
skills/validate-knowledge/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.