geneseed 4.9.4 → 4.10.0

package/src/licenses/piomin-spring-boot.txt

@@ -0,0 +1,190 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+Copyright 2026 Piotr Mińkowski
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/src/licenses/superpowers.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Jesse Vincent
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/src/licenses/vibe-wise.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Noah Kim
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/src/skills/brainstorm/builder-check.md

@@ -1,5 +1,7 @@
 # {{SKILL}}: brainstorm — builder check
 
+{{CREDIT:superpowers:skills/brainstorming/builder-check-prompt.md}}
+
 The spec's author cannot read it cold: a re-read inherits the framing that wrote it. So a
 fresh reader does.
 

package/src/skills/brainstorm.md

@@ -3,6 +3,10 @@
 > {{DESC_BRAINSTORM}}
 <!-- aliases: grill-me -->
 
+{{CREDIT:superpowers:skills/brainstorming/SKILL.md}}
+
+{{CREDIT:mattpocock-skills:skills/productivity/grilling/SKILL.md}}
+
 **Trigger:** a new feature, behaviour change, or project arrives without a design, or the
 user says "brainstorm", "interview me" or "grill me". Also when goal, scope or success
 criteria are unstated ("let's design this", "clarify this first", "stress-test this plan"),

package/src/skills/codebase-design.md

@@ -3,6 +3,10 @@
 > {{DESC_CODEBASE_DESIGN}}
 <!-- aliases: domain-modeling -->
 
+{{CREDIT:mattpocock-skills:skills/engineering/codebase-design/SKILL.md}}
+
+{{CREDIT:mattpocock-skills:skills/engineering/domain-modeling/SKILL.md}}
+
 **Trigger:** the user asks "where should the seam go", how to make a module testable through
 its interface, or for a glossary term or ADR. Also designing or reshaping a module's interface,
 a design talk that keeps stumbling over ambiguous terms, or another {{SKILL}} needing this vocabulary.

package/src/skills/daydream/VENDOR.md

@@ -5,14 +5,14 @@ skill. It rides along in the rendered bundle and is exempt from Geneseed's autho
 gates (token, dead-link, hermeticity, skill counts) — it is listed in the
 generator's `VENDORED_SKILL_DIRS`.
 
-- **Upstream:** https://github.com/glebis/claude-skills/tree/main/daydream
-- **Commit:** f47170dee300dd3d5da2a1c3c708986faeea3d5a
-- **Author:** Gleb Kalinin
-- **License:** MIT (declared in `.claude-plugin/plugin.json`). The text is in `LICENSE`,
-  copied from upstream's root `LICENSE` as added in 93677f479f40ab43520883e7a6c954b755ab39ef
-  (the pinned commit predates the file; its copyright line covers 2025-2026).
+- **Upstream key:** daydream (repo, pinned commit, author and licence: `src/upstreams.json`)
+- **Credit:** {{CREDIT:daydream:daydream}}
 - **Inspired by:** Gwern's [LLM Daydreaming](https://gwern.net/ai-daydreaming)
 
+The licence (MIT, declared upstream in `.claude-plugin/plugin.json`) is in `LICENSE`, copied
+from upstream's root `LICENSE` as added in 93677f479f40ab43520883e7a6c954b755ab39ef (the
+pinned commit predates the file; its copyright line covers 2025-2026).
+
 ## Geneseed adaptation
 
 Vault resolution is adapted to read the harness's `geneseed-wiki.jsonc` knowledge-base
@@ -32,7 +32,7 @@ does not tell the model where a skill lives.
 
 To update, re-copy the upstream folder, re-apply the geneseed-wiki.jsonc adaptation, the
 frontmatter and the placeholder paths in `SKILL.md` / `instructions.md`, and
-bump the commit above.
+bump the `daydream` entry's `commit` in `src/upstreams.json`.
 
 `SKILL.md`'s frontmatter also carries `disable-model-invocation: true`, which upstream lacks: the
 skill is user-only (`/daydream`), so its description stays out of the model's always-on catalogue —

package/src/skills/debug.md

@@ -3,6 +3,10 @@
 > {{DESC_DEBUG}}
 <!-- aliases: ci-fix -->
 
+{{CREDIT:superpowers:skills/systematic-debugging/SKILL.md}}
+
+{{CREDIT:mattpocock-skills:skills/engineering/diagnosing-bugs/SKILL.md}}
+
 **Trigger:** a test fails, code crashes or prints a stack trace, or returns the wrong result — load this FIRST. Load it before reading code or investigating, not only before proposing a fix. Also when a CI run, pipeline job or pre-merge check is red ("CI is failing", "fix the build") — then start with the CI branch.
 
 **No fix without a root cause.** A change you cannot tie to a cause you understand is
@@ -12,7 +16,7 @@ The pressure to skip straight to a patch is highest exactly when this rule matte
 faster than thrashing; do not trade it away under pressure.
 
 ## Procedure
-1. **Build one command that goes red on *this* bug** before reading code for a theory. It asserts the user's exact symptom (not "didn't crash"), gives the same verdict every run, takes seconds and runs unattended; run it and show the output. Read the error and stack trace in full. For a flaky bug, raise the reproduction rate until it is debuggable. If you cannot build it, say so, list what you tried and ask for access or a captured artifact — no command, no hypothesis. Read `GLOSSARY.md` (or `CONTEXT.md`) and the ADRs in the area for the domain's vocabulary.
+1. **Build one command that goes red on *this* bug** before reading code for a theory. It asserts the user's exact symptom (not "didn't crash"), gives the same verdict every run, takes seconds and runs unattended; run it and show the output. If you forced the red by mutating code or a fixture, `diff` against a pristine copy to prove the mutation landed, then revert it. Read the error and stack trace in full. For a flaky bug, raise the reproduction rate until it is debuggable. If you cannot build it, say so, list what you tried and ask for access or a captured artifact — no command, no hypothesis. Read `GLOSSARY.md` (or `CONTEXT.md`) and the ADRs in the area for the domain's vocabulary.
 2. **Minimise, then isolate.** Cut inputs and steps one at a time until every remaining element is load-bearing. Then binary-search the cause — the code path, or for a regression the commit range with `git bisect` (the [git-history {{SKILL}}](git-history.md) carries the method). Change one variable at a time. Find the nearest working twin (a passing sibling test, the last green commit, the same call elsewhere) and list every difference, however small. For a bad value deep in the stack, trace it back caller by caller to where it was born, and fix there. In a multi-layer system (CI → build → sign, API → service → DB), instrument each boundary once to see *which* layer breaks before investigating inside it. For a performance regression, take a baseline measurement and bisect; don't log.
 3. **Rank 3–5 falsifiable hypotheses** ("if X is the cause, changing Y removes the bug") — list them in your reply, then test the top one without waiting. Cite the evidence for each as `file:line` or the exact log line. Proceed only on one that explains ALL the evidence — else gather more evidence, don't guess.
 4. Apply the smallest fix that addresses the root cause, not the symptom; resist fixing things the evidence doesn't implicate ({{LAW:one-intent-one-act}}). One change at a time — no bundled "while I'm here" edits.

package/src/skills/develop.md

@@ -2,6 +2,8 @@
 
 > {{DESC_DEVELOP}}
 
+{{CREDIT:mattpocock-skills:skills/engineering/tdd/SKILL.md}}
+
 **Trigger:** implementing a feature, fixing a bug, or changing code behaviour in a
 repo that has (or should have) a test suite — before writing implementation code.
 Covers both the test-first cycle (red → green → refactor) and the cover-alongside

package/src/skills/geneseed-code-review.md

@@ -2,6 +2,10 @@
 
 > {{DESC_CODE_REVIEW}}
 
+{{CREDIT:mattpocock-skills:skills/engineering/code-review/SKILL.md}}
+
+{{CREDIT:superpowers:skills/requesting-code-review/code-reviewer.md}}
+
 **Trigger:** reviewing changes before merge, or the user asks for a review — including "roast my code": same passes, findings unsoftened. Critiquing the user's own ask or plan is [roast-me](roast-me.md).
 
 ## Procedure
@@ -22,8 +26,8 @@
    kept apart, one axis's findings never mask the other's.
 5. Pass 1 — correctness: logic errors, edge cases, error handling, race
    conditions. Verify suspect behaviour by running tests, not by assuming.
-6. Pass 2 — quality: after `REVIEW.md`, the repo's documented standards (`CODING_STANDARDS.md`,
-   `CONTRIBUTING.md`) override. Then, as judgement calls and skipping what tooling enforces:
+6. Pass 2 — quality: after `REVIEW.md`, the repo's documented standards override: search the repo for every file that states how code
+   is written (`CODING_STANDARDS.md`, `CONTRIBUTING.md`, style or conventions docs), not one fixed path. Then, as judgement calls and skipping what tooling enforces:
    mysterious name, duplication, feature envy, data clumps, primitive obsession, repeated switches, shotgun surgery, divergent change, speculative generality, message chains, middle man, refused bequest, dead code, units that do too much.
 7. Pass 3 — spec fidelity: flag anything asked for but missing, present but never
    asked for, or implemented wrong — quoting the spec line for each. Where the spec is silent,

package/src/skills/git-history.md

@@ -3,6 +3,8 @@
 > {{DESC_GIT_HISTORY}}
 <!-- aliases: git-archaeology, git-rescue -->
 
+{{CREDIT:mattpocock-skills-frozen:skills/engineering/resolving-merge-conflicts/SKILL.md}}
+
 **Trigger:** something must be learned *from* the git history, or it needs repair.
 Learn: when a regression came in, who last touched a line and why, where a symbol or
 string entered. Repair: lost commits, a rebase/merge/reset gone wrong, a detached HEAD, a

package/src/skills/handoff.md

@@ -2,6 +2,8 @@
 
 > {{DESC_HANDOFF}}
 
+{{CREDIT:mattpocock-skills:skills/productivity/handoff/SKILL.md}}
+
 **Trigger:** the context window is filling, a session is ending mid-task, or work is passing to another agent or developer.
 
 ## Procedure

package/src/skills/learn-mode.md

@@ -4,6 +4,8 @@
 
 <!-- invocation: user -->
 
+{{CREDIT:vibe-wise:skills/learn/behavior.md}}
+
 **Trigger:** the user wants to *learn while building* rather than be handed finished code.
 Phrases: "learn mode", "turn on learning", "I want to understand what we build", "let me design it,
 you write it". Also "pause learning" / "resume learning" / "stop learn mode". To be taught a
@@ -11,8 +13,7 @@ topic outside a build, use the [teach {{SKILL}}](teach.md); to have knowledge te
 [quiz {{SKILL}}](quiz.md).
 
 The user is the engineer and owns the design; you write the code for the design they
-chose and understand. Learning and the user's control outrank build speed. The idea comes
-from [VibeWise](https://github.com/nykooi1/vibe-wise) (MIT); this is a rewrite, not a copy.
+chose and understand. Learning and the user's control outrank build speed.
 
 ## State — `.geneseed/learn.md`
 

package/src/skills/parallel-agents.md

@@ -2,6 +2,8 @@
 
 > {{DESC_PARALLEL_AGENTS}}
 
+{{CREDIT:superpowers:skills/subagent-driven-development/SKILL.md}}
+
 **Trigger:** two or more independent subtasks with no shared state or ordering between them — and a tool that can run subagents. The units run side by side and never see each other's work; when one agent must build on what the previous one produced, that is a relay — use [pipeline](pipeline.md).
 
 ## Procedure

package/src/skills/pipeline.md

@@ -2,6 +2,8 @@
 
 > {{DESC_PIPELINE}}
 
+{{CREDIT:superpowers:skills/subagent-driven-development/SKILL.md}}
+
 **Trigger:** [foreman mode](../modes/foreman.md) routes a triaged *substantial* task here; also directly invocable without that mode whenever the user asks to "run a pipeline" for a development, documentation, research, or review task. The crew is a relay, not a fan-out: its agents take turns in one worktree, each handed what the previous one produced — for independent subtasks run side by side, use [parallel-agents](parallel-agents.md).
 
 ## What it is

package/src/skills/plan.md

@@ -2,6 +2,10 @@
 
 > {{DESC_PLAN}}
 
+{{CREDIT:superpowers:skills/writing-plans/SKILL.md}}
+
+{{CREDIT:mattpocock-skills:skills/engineering/to-tickets/SKILL.md}}
+
 **Trigger:** a task with more than a couple of steps, or touching several files
 ({{DOCTRINE:plan-before-acting}}).
 

package/src/skills/prototype.md

@@ -2,6 +2,8 @@
 
 > {{DESC_PROTOTYPE}}
 
+{{CREDIT:mattpocock-skills:skills/engineering/prototype/SKILL.md}}
+
 **Trigger:** a design question needs a runnable answer — "does this state
 model feel right?" or "what should this look like?" — before committing to a
 real implementation.