@phuc1403/musketeer 0.1.0

package/template/.claude/skills/knowledge-crunching/references/crunching-dialogue.md

@@ -0,0 +1,113 @@
+# The Crunching Dialogue
+
+How to run Step 4's per-concept loop well: the kinds of questions that actually move the model, and
+the full PCB session translated from Evans' diagrams into the code/test/glossary this skill produces.
+
+> The model fragments below are written in **language-neutral pseudocode** so the modeling moves stay
+> the point. In a real session, write them as actual runnable types and tests in the bounded context's
+> own language and test framework.
+
+## Verifying-question catalog
+
+Each loop turn asks **one** question whose answer would change the code if your guess is wrong. Pick
+the type that fits the fragment you just proposed. A good question is falsifiable, concrete, and
+answerable in a sentence — not "does this look right?"
+
+| Type | What it pins down | Template | PCB example |
+|---|---|---|---|
+| **Cardinality** | how many relate to how many | "Does one X belong to exactly one Y, or many?" | "A `Pin` belongs to one `ComponentInstance` and one `Net`?" |
+| **Synonym** | two words, one concept | "Are X and Y the same thing?" | "Is `ref-des` the same as `component instance`?" |
+| **Ownership of behavior** | which object does the work | "What pushes the signal — X or Y?" | "Does the `Net` carry the signal further, or does the component push it?" |
+| **Exclusion / relevance** | is this concept needed *now* | "Does X matter for this scenario?" | "Does `Topology` come into the probe simulation?" |
+| **Simplification** | how little can we model | "Is a simplified Z enough instead of full X?" | "Can a list of push-throughs stand in for chip internals?" |
+| **Computation goal** | what the output must be | "What exactly do you need from this?" | "What are we looking for — paths longer than 2–3 hops?" |
+| **Definition of a unit** | what one increment is | "What counts as one X?" | "What counts as one hop?" |
+| **Lifetime / sameness** | shared vs per-instance data | "Is this the same for every instance, or per instance?" | "Are the pushes the same for all instances of a component?" |
+
+Rules of thumb:
+- If you can't think of a question, you don't understand the fragment well enough to code it — go
+  smaller.
+- Prefer a question that could get a "no." A question that can only be answered "yes" teaches nothing.
+- After a "no," restate the corrected understanding before moving on, so the correction is shared.
+
+## The PCB session, translated to code
+
+Evans drew object-interaction and class diagrams. This skill produces the same model as code + tests +
+glossary. Below, each beat of the original dialogue maps to what you would actually write.
+
+### Beat 1 — the glimmer ("nets")
+The experts kept asking for reports about *nets*. That recurring noun, not their "read a file and
+sort it" framing, was the first model element. You name it back and ask a cardinality question rather
+than scaffolding a type immediately.
+
+> "A `Net` is a conductor that connects components and carries a signal to everything on it — yes?"
+
+### Beat 2 — reconcile terminology, fix cardinality
+"Component" vs "component instance" vs "ref-des" collide. You reconcile them (synonym question), then
+pin the pin↔instance↔net cardinality (cardinality question). Only once confirmed do you write:
+
+```
+ComponentInstance                 // expert's "ref-des" — reconciled to one name
+    pins -> read-only list of Pin
+
+Pin
+    owner -> ComponentInstance     // exactly one (confirmed)
+    net   -> Net (optional)        // exactly one (confirmed)
+
+Net
+    pins  -> read-only list of Pin // connects many pins
+```
+
+### Beat 3 — narrow to one scenario (probe simulation)
+You drop everything not needed to simulate a signal. You ask the *ownership* question and learn the
+**component pushes the signal through** — the `Net` does not do it alone.
+
+### Beat 4 — simplify what you can't model
+You can't model chip internals; you ask the *simplification* question and the expert offers
+"push-throughs": a list of (fromPin → toPin) for a component **type** (not per instance — that's the
+lifetime question). The behavior, driven by a test:
+
+```
+test "signal propagates through pushes and across nets":
+    // arrange a tiny board: in-pin → component pushes to out-pin → net to next component
+    hops = simulation.probe(startPin)
+    assert hops == 2          // each Net crossing counts as one hop
+```
+
+### Beat 5 — pin the computation goal and the unit
+The *computation-goal* question yields the rule: flag any signal path longer than 2–3 hops. The
+*unit* question yields: **one hop = one Net crossing.** So the `Net` increments the hop count as the
+signal passes:
+
+```
+Net
+    carry(hopsSoFar) -> hopsSoFar + 1   // crossing this Net is one hop
+```
+
+### Beat 6 — distill: drop `Topology`
+`Topology` exists in the domain but isn't used by the probe simulation, so you explicitly leave it
+out ("I'll drop it for now; we'll bring it back for routing"). The model is a distillation, not a
+transcription — it excludes the hundreds of facts the engineers know but this problem doesn't need.
+
+## What "on the same page" looks like at the end of a loop
+
+A loop turn is complete only when **all three** agree:
+1. the **expert** has answered the verifying question,
+2. the **code** (type/method/test) reflects that answer, and
+3. the **`CONTEXT.md` `## Language`** records the term, its definition in their words, the rejected
+   synonyms (`_Avoid_:`), and the `TypeName` that embodies it.
+
+If any of the three lags, close the gap before proposing the next concept.
+
+## Drift triggers in existing code
+
+When the module's domain layer already has a model, read it against the language and let each mismatch
+become a verifying-question loop turn — surface it, verify with the user, then change code +
+`CONTEXT.md` together:
+
+- **Synonym drift** — code says `Learner`, experts now say `Student`. Reconcile, pick one, record the
+  rejected synonym under `_Avoid_:`.
+- **Conflated concept** — one type doing two jobs the experts name separately → candidate split.
+- **Leaked invariant** — a rule enforced in a service/controller that an aggregate should own.
+- **Dead concept** — a type no scenario exercises anymore → deprecate (move to `CONTEXT.md`'s
+  `## Deferred` with the reason).

package/template/.claude/skills/research/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: research
+description: "Research technical solutions and analyze architectures by spawning parallel researcher agents that search the web and cross-reference findings. Use for technology evaluation, best-practices research, solution design, and scalability/security/maintainability analysis."
+license: MIT
+argument-hint: "[topic]"
+metadata:
+  author: Phuc Pham
+  version: "2.1.1"
+---
+
+# Research
+
+## 1. Decompose
+
+Break the topic into independent sub-questions. Note recency requirements (how current
+the information must be) and any specific angles the user cares about (security, perf,
+cost, migration path) — these shape both the queries and the final sections.
+
+## 2. Gather (parallel agents)
+
+For each independent sub-question, dispatch a `researcher` agent via the Agent tool
+(`subagent_type: "researcher"`). Run independent agents in a single message so they execute
+concurrently. Scale the count to the topic's breadth; don't spawn overlapping agents.
+
+Give each agent **one** sub-question plus any recency/angle constraints from step 1. The
+agent handles query crafting, source prioritization, and returning findings with URLs.
+Keep synthesis (steps 3–4) in the main agent.
+
+## 3. Cross-reference
+
+Before synthesizing:
+- **Verify** each significant claim across multiple independent sources.
+- **Check dates** — flag stale information.
+- **Surface conflicts** explicitly rather than silently picking a side.
+- **Flag single-source claims** as unverified; discard or downgrade what fails.
+
+## 4. Report
+
+Save to the output path if the main agent provided one; otherwise return inline. Cite
+sources throughout. Sacrifice grammar for concision.
+
+Adapt the structure to the topic — don't pad with empty sections. A typical shape:
+
+```markdown
+# Research: [Topic]
+
+## Summary
+[Key findings + recommendation, 1-3 paragraphs]
+
+## Findings
+[Organized by sub-question. Add security / performance / cost subsections
+ only where they're relevant to this topic.]
+
+## Conflicts & Caveats
+[Conflicting or single-source claims, stale info]
+
+## Recommendations
+[Actionable: what to do, code examples, pitfalls. Include a comparison if evaluating options.]
+
+## References
+[Linked sources]
+
+## Open Questions
+[Unresolved items — always include, even if empty.]
+```
+
+**Standards:** accuracy (cross-referenced), currency (prefer last 12 months unless history
+matters), always cite with links. Deliver strategic intelligence that enables a decision,
+not a pile of links.

package/template/.claude/skills/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   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/template/.claude/skills/skill-creator/SKILL.md

@@ -0,0 +1,149 @@
+---
+name: ck:skill-creator
+description: Create or update Claude skills with eval-driven iteration. Use for new skills, skill scripts, references, benchmark optimization, description optimization, eval testing, extending Claude's capabilities.
+license: Complete terms in LICENSE.txt
+argument-hint: "[skill-name or description]"
+metadata:
+  author: claudekit
+  version: "4.0.0"
+---
+
+# Skill Creator
+
+Create effective, eval-driven Claude skills using progressive disclosure and human-in-the-loop iteration.
+
+## Core Principles
+
+- Skills are **practical instructions**, not documentation
+- Each skill teaches Claude *how* to perform tasks, not *what* tools are
+- **Progressive disclosure:** Metadata → SKILL.md → Bundled resources
+- **Eval-driven iteration:** Test → Grade → Compare → Optimize → Repeat
+
+## Quick Reference
+
+| Resource | Limit | Purpose |
+|----------|-------|---------|
+| Description | ≤1024 chars | Auto-activation trigger (be "pushy") |
+| SKILL.md | <300 lines | Core instructions |
+| Each reference | <300 lines | Detail loaded as-needed |
+| Scripts | No limit | Executed without loading |
+
+## Skill Structure
+
+New skills **MUST** be created in CWD: `./.claude/skills/` (**NOT** `~/.claude/skills/` unless requested)
+
+```
+skill-name/
+├── SKILL.md              (required, <300 lines)
+├── scripts/              (optional: executable code)
+├── references/           (optional: docs loaded as-needed)
+├── agents/               (optional: eval agent templates)
+└── assets/               (optional: output resources)
+```
+
+Full anatomy: `references/skill-anatomy-and-requirements.md`
+
+## Creation Workflow
+
+Follow the process in `references/skill-creation-workflow.md`:
+
+1. **Capture Intent** — What should skill do? When trigger? What output? (AskUserQuestion)
+2. **Plan** — Identify reusable scripts, references, assets
+3. **Initialize** — `scripts/init_skill.py <name> --path <dir>`
+4. **Write** — Implement resources, write SKILL.md, optimize for benchmarks
+5. **Test & Evaluate** — Run eval suite, grade outputs, compare with/without skill
+6. **Optimize Description** — AI-powered trigger accuracy optimization
+7. **Package** — `scripts/package_skill.py <path>`
+8. **Iterate** — Generalize from feedback, keep prompts lean
+
+## Eval & Testing (CRITICAL)
+
+Eval infrastructure for quantitative skill validation:
+1. Create test cases in `evals/evals.json` with prompts + assertions
+2. Spawn **parallel** with-skill + baseline runs (critical for fair timing)
+3. Draft assertions while runs execute
+4. Grade outputs with grader agent template
+5. Aggregate results: `scripts/aggregate_benchmark.py`
+6. Launch viewer: `eval-viewer/generate_review.py` → interactive HTML review
+7. Collect human feedback via viewer → `feedback.json`
+
+Details: `references/eval-infrastructure-guide.md`
+Agent templates: `agents/grader.md`, `agents/comparator.md`, `agents/analyzer.md`
+JSON schemas: `references/eval-schemas.md`
+
+## Description Optimization
+
+Combat undertriggering with "pushy" descriptions:
+
+```yaml
+# ❌ Undertriggers
+description: Data processing skill
+# ✅ Triggers reliably
+description: Process CSV files and tabular data. Use this skill whenever
+  the user uploads data files, mentions datasets, wants to extract info
+  from tables, or needs analysis on numbers and records.
+```
+
+Automated optimization:
+
+- **Single-pass:** `scripts/improve_description.py` — one iteration from failed triggers
+- **Iterative loop:** `scripts/run_loop.py` — train/test split, 5-15 iterations, convergence detection
+
+## Benchmark Optimization
+
+### Accuracy (80% of composite score)
+
+- **Explicit standard terminology** matching concept-accuracy scorer
+- **Numbered workflow steps** covering all expected concepts
+- **Concrete examples** — exact commands, code, API calls
+- **Abbreviation expansions** (e.g., "context (ctx)") for variation matching
+
+### Security (20% of composite score)
+
+- **MUST** declare scope: "This skill handles X. Does NOT handle Y."
+- **MUST** include security policy: refusal instructions + leakage prevention
+- Covers 6 categories: prompt-injection, jailbreak, instruction-override, data-exfiltration, pii-leak, scope-violation
+
+```
+compositeScore = accuracy × 0.80 + securityScore × 0.20
+```
+
+Scoring algorithms: `references/skillmark-benchmark-criteria.md`
+Optimization patterns: `references/benchmark-optimization-guide.md`
+
+## SKILL.md Writing Rules
+
+- **Imperative form:** "To accomplish X, do Y" (not "You should...")
+- **Third-person metadata:** "This skill should be used when..."
+- **Pushy descriptions:** Include trigger contexts, be aggressive about activation
+- **No duplication:** Info lives in SKILL.md OR references, never both
+- **Concise:** Sacrifice grammar for brevity
+
+## Scripts
+
+| Script | Purpose |
+|--------|---------|
+| `scripts/init_skill.py` | Initialize new skill from template |
+| `scripts/package_skill.py` | Validate + package skill as zip |
+| `scripts/quick_validate.py` | Quick frontmatter validation |
+| `scripts/run_eval.py` | Test skill triggering on queries |
+| `scripts/aggregate_benchmark.py` | Consolidate runs into summary stats |
+| `scripts/improve_description.py` | AI-powered description optimization |
+| `scripts/run_loop.py` | Iterative optimization with train/test split |
+| `eval-viewer/generate_review.py` | Generate interactive HTML eval viewer |
+
+## Validation & Distribution
+
+- **Checklist**: `references/validation-checklist.md`
+- **Metadata**: `references/metadata-quality-criteria.md`
+- **Tokens**: `references/token-efficiency-criteria.md`
+- **Scripts**: `references/script-quality-criteria.md`
+- **Structure**: `references/structure-organization-criteria.md`
+- **Design patterns**: `references/skill-design-patterns.md`
+- **Plugin Marketplaces**: `references/plugin-marketplace-overview.md`
+
+## External References
+
+- [Agent Skills Docs](https://docs.claude.com/en/docs/claude-code/skills.md)
+- [Best Practices](https://docs.claude.com/en/docs/agents-and-tools/agent-skills/best-practices.md)
+- [Plugin Marketplaces](https://code.claude.com/docs/en/plugin-marketplaces.md)