@super-hands/connect 0.1.14 → 0.1.16

package/client.mjs

@@ -41,11 +41,11 @@ function codexConfigBlock(args) {
 }
 
 // lib/connect-skill.ts
-var CONNECT_SKILL_VERSION = 9;
+var CONNECT_SKILL_VERSION = 11;
 var CONNECT_SKILL_DIR = MCP_SERVER_KEY;
 var CONNECT_SKILL_FILENAME = "SKILL.md";
 var VERSION_MARKER = `[//]: # (superhands-skill-version: ${CONNECT_SKILL_VERSION})`;
-var CONNECT_SKILL_DESCRIPTION = `Build UI the way this team has decided it should be built. Use BEFORE building, changing, or restyling any page, screen, view, form, or component \u2014 "build a page", "add a screen", "create a form", "make a dashboard", "redesign this", "new landing page" \u2014 and when asked how this product should look or behave. Reads the team's Standards and Playbooks from their Superhands MCP server.`;
+var CONNECT_SKILL_DESCRIPTION = `Build UI the way this team has decided it should be built. Use BEFORE building, changing, or restyling any page, screen, view, form, or component \u2014 "build a page", "add a screen", "create a form", "make a dashboard", "redesign this", "new landing page" \u2014 and when asked how this product should look or behave. Reads the team's build-time Instructions from their Superhands MCP server.`;
 var CONNECT_SKILL_CONTENT = `---
 name: ${CONNECT_SKILL_DIR}
 description: ${CONNECT_SKILL_DESCRIPTION}
@@ -56,11 +56,11 @@ ${VERSION_MARKER}
 # Superhands
 
 This machine is connected to the team's Superhands server over MCP (server
-key \`${MCP_SERVER_KEY}\`). It holds the team's **Instructions** in two kinds:
-their **Standards**, the decisions they have written about how their product
-should look and behave \u2014 the same decisions their engineers' pull requests are
-reviewed against \u2014 and their **Playbooks**, procedures they imported for their
-agents to follow.
+key \`${MCP_SERVER_KEY}\`). It holds the team's build-time **Instructions**:
+team-authored decisions, imported procedures, examples and conventions that all
+describe how agents should build in this product. Source labels tell you where
+an instruction came from and how to read it; they are not a choice about which
+half to follow.
 
 Before you build, change, or restyle any UI:
 
@@ -68,18 +68,18 @@ Before you build, change, or restyle any UI:
    you have been asked to build, in plain language \u2014 for example "a sign-in
    page with email and password and an error state", and
    \`skill_version: ${CONNECT_SKILL_VERSION}\` \u2014 the version of this file, so
-   the server can tell you when this file is out of date. Both sections come
+   the server can tell you when this file is out of date. The corpus comes
    back narrowed to that work, with everything not chosen still named.
    - Pass \`paths\` too, when you already know which files this work touches \u2014
      the handful you have open or are about to edit, repository-relative, for
-     example \`["app/marketing/pricing.tsx"]\`. The team writes down where each
-     Standard applies, and a path answers that far better than a description
+     example \`["app/marketing/pricing.tsx"]\`. The team writes down where
+     Instructions apply, and a path answers that far better than a description
      does. Leave it out if you do not know yet; it narrows nothing away.
    - If that tool is not available on this server, it is an older deployment:
      call \`superhands_get_guidance\` and \`superhands_get_skill\` instead,
      with the same \`intent\` \u2014 those two are older and take no \`paths\`.
 2. Plan against what comes back, and note which parts of your plan each set of
-   keys covers. The Playbooks section renders what to read first, then names
+   keys covers. The first answer renders what to read first, then names
    under **Reachable** the modules judged to matter to parts you have not
    started \u2014 those keys are what the next step asks with \u2014 and ends with an
    index of the modules it did **not** choose, for anything the selection
@@ -88,35 +88,40 @@ Before you build, change, or restyle any UI:
    defaults.
 3. As you start each part \u2014 the sidebar, then the table, then the form \u2014 call
    \`superhands_get_playbook_modules\` with the reachable keys covering the
-   part you are starting now. A key ending in \`*\` takes everything under
-   it, so \`better-ui/*\` is a whole skill and \`better-ui/SKILL#*\` is one
-   file. It runs no selection and makes no model call, so it is a plain, fast
-   lookup and it returns exactly what you named.
+   part you are starting now and \`part\` set to that part in a few words,
+   for example \`"the form's validation errors"\`. A key ending in \`*\` takes
+   everything under it, so \`better-ui/*\` is a whole skill and
+   \`better-ui/SKILL#*\` is one file. It runs no selection and makes no model
+   call, so it is a plain, fast lookup and it returns exactly what you named.
+   - **Expect to make this call several times in one task.** A contact form is
+     not one part: it is the form, then its inputs, then its buttons, then its
+     validation errors, then its loading and empty states. One read at the
+     start and nothing after it is the mistake this step exists to prevent.
    - Fetch each part's modules **when you reach that part**, not all of them at
      the start. These are instructions to follow, not facts to know, so modules
      for a part you are not building are a page of directions about the wrong
      thing sitting in your context while you work.
-   - The Standards from step 1 need no such loop. They are a short list of
-     constraints on the whole task, so one read at the start is the right read.
+   - Team-authored decision entries from step 1 need no such loop. They are
+     concise enough to stay in the opening brief, so one read at the start is
+     the right read.
    - If that tool is not available on this server, it is an older deployment:
      build from what step 1 already returned and skip this step. Do not ask
      for the whole library instead \u2014 that is the wall of text step 1 avoided.
-4. Build to what comes back. Apply both sections. Where imported Playbook text
-   directly contradicts a Standard, the Standard governs. Where a Standard
-   names a case it deliberately does not govern, your own judgment resumes
-   there.
+4. Build to what comes back. Use the selected Instructions together. When two
+   entries pull in different directions, prefer the more specific instruction,
+   preserve explicit exceptions, and call out any conflict you cannot honestly
+   resolve.
 5. When you have finished \u2014 not part-way through \u2014 send the files you wrote or
    changed with \`superhands_report_completed_build\`, naming the \`route\` if
    you know it. The team looks at what their agents build there; it records
    and does not review, so a failed report costs the work nothing.
-6. When you finish, say you followed the team's guidance \u2014 never that your
-   work passes it or was checked. Reading Instructions is not a review,
-   reporting a build is not a review, and nothing has looked at what you built.
+6. When you finish, say you followed the team's Instructions \u2014 never that your
+   work was checked. Reading Instructions is not a check, reporting a build is
+   not a review, and nothing has looked at what you built.
 
 If the tool answers \`no-instructions\` (or \`no-guidance\` from an older
 server), carry on with what you were asked for and mention that the team
-writes its Standards and imports its Playbooks on the Superhands Instructions
-page.
+adds its Instructions on the Superhands Instructions page.
 
 If the \`${MCP_SERVER_KEY}\` MCP server is not reachable in this session, say
 so rather than guessing at the team's decisions \u2014 it is configured on this

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@super-hands/connect",
-  "version": "0.1.14",
+  "version": "0.1.16",
   "description": "Connect the coding agents on this machine to your team's Superhands MCP server, refresh it later with `update` (no token needed), and take it back off again with `uninstall`. Writes each client's own config; reads no repository, uploads nothing.",
   "bin": {
     "superhands-connect": "client.mjs"