ctxr-cli 0.4.1 → 0.6.0

package/templates/skills/ctxr-land.md

@@ -1,24 +1,38 @@
 The land half of the session lifecycle, after review. `ctxr-submit` is the other half; `ctxr-session-lifecycle`
 covers what surrounds both and is not repeated here.
 
-1. Name the target — `--branch <name>` or `--pr <n>` — rather than letting it fall back to the current
-   checkout: the checkout you are standing in is as likely to be the canonical clone on
+1. Name the target explicitly — a branch name or a pull-request number — rather than relying on whichever
+   checkout you happen to be standing in: that checkout is as likely to be the canonical clone on
    `__DEFAULT_BRANCH__`, which has no session to infer, as the session itself. Never land
    `__DEFAULT_BRANCH__` itself; a pull request whose head is `__DEFAULT_BRANCH__` is refused too.
-2. Run `ctxr session land` (add `--yes` only when you already have explicit approval from elsewhere in
-   this conversation; otherwise let it prompt). It reads the pull request's state, gates the merge behind
-   an explicit confirmation, merges with `--merge-method` (default squash), confirms the forge reports
-   merged, and fast-forwards `__DEFAULT_BRANCH__` in the store's canonical clone — whichever checkout you
-   ran it from, including a session worktree. A clone on another branch or one that cannot fast-forward
-   is reported, never forced.
-3. Conflicting or unknown mergeability stops the command; follow `ctxr-session-lifecycle`'s conflict
-   playbook, then retry — a retry re-reads state and performs only what remains.
-4. Add `--reap` to remove the session worktree in the same run, once it is clean and merged — and run it
-   from outside that worktree, since no command can remove the directory it is running from (`git worktree
-   list` names the canonical clone first). Otherwise run `ctxr session reap` afterward, or leave cleanup to
-   whoever owns the worktree.
-5. Report exactly what the command reported — merged or not, synced or not (with why not), reaped or not
-   (with why not). Never claim a merge or a cleanup the command itself did not confirm.
+2. Read state before any side effect: `gh pr view <target> --json number,url,title,state,mergeable,headRefName`.
+   Refuse if the head branch is `__DEFAULT_BRANCH__`, or if the target you named doesn't match the head
+   branch this reports. A closed pull request stops here — report it, do nothing further.
+3. Check mergeability. `MERGEABLE` proceeds to the gate below. `UNKNOWN` re-queries once (`gh pr view`
+   again) before treating it as still unknown. `CONFLICTING` or still-`UNKNOWN` after the re-query stops
+   the command — follow `ctxr-session-lifecycle`'s conflict playbook, then retry from step 1; a retry
+   re-reads state and performs only what remains.
+4. Gate: merging is an external side effect, and plan consent is not fire consent. Present the pull
+   request's number, title, and url; wait for an explicit go (already having explicit approval from
+   elsewhere in this conversation satisfies this — don't ask twice).
+5. Merge: `gh pr merge <number> --squash` (or `--merge` / `--rebase` if the operator asked for a different
+   method). Then re-read state (`gh pr view` again) to confirm the forge reports `MERGED` — never claim a
+   merge from the merge command's exit code alone; a transport error can arrive after the merge already
+   succeeded.
+6. Synchronize the default branch in the store's canonical clone — the repository's main worktree, not
+   necessarily the checkout you're running this from. From the canonical clone: `git fetch origin` then
+   `git merge --ff-only origin/__DEFAULT_BRANCH__`. If that clone is on another branch, or the fast-forward
+   fails (diverged from origin), report exactly that and stop — never check it out, reset it, or force the
+   merge to make it comply.
+7. Reclaim the worktree: see `ctxr-session-lifecycle`'s Reclaiming section (`ctxr session list` to scope,
+   then `git worktree remove` / `git branch -d`) — run it from outside the worktree being removed. This is
+   the default action, not an optional extra: nothing sweeps up afterward, so a worktree left here is left
+   indefinitely. Skip it only for a reason you can name — you are standing inside it, it is not yours to
+   reclaim, or the operator asked you to leave it — and report that reason in step 8.
+8. Report exactly what happened — merged or not, synced or not (with why not), reclaimed or not (with why
+   not). Never claim a merge or a cleanup you did not confirm yourself.
 
-Never merge by hand (a raw forge-CLI merge, the forge's web UI on this agent's behalf): `ctxr session land`
-is the only merge path, so every landing leaves the same audit trail and passes through the same gate.
+Merging with `gh pr merge` (step 5) is the mechanism, not a shortcut around one: the pull request and its
+merge commit are the audit trail. What step 4's gate protects against is merging without having actually
+read the state in steps 2-3 first, or without an explicit go — never skip the read, the mergeability check,
+or the confirmation to save a round trip.

package/templates/skills/ctxr-organize-audit.md

@@ -1,7 +1,7 @@
 1. Run `ctxr lint` for the full health report — orphan notes, broken links, uningested inbox material,
    catalog gaps. It always exits 0; its findings are observations for judgment, never a block.
 2. Run `ctxr doctor` for the invariants that DO block: catalog coverage, fail-closed visibility, hook
-   health, and more. Address doctor's failures before `ctxr session submit`; it runs the same checks.
+   health, and more. Address doctor's failures before `ctxr-submit`; it runs the same checks.
 
 ## Placement review
 

package/templates/skills/ctxr-publish.md

@@ -0,0 +1,79 @@
+Turn store content into a shareable HTML page for a subject — a store subtree, a single note, a
+concept whose sources aren't co-located, or everything a named context admits. The gate below is the
+one step no convention can enforce by itself; everything else here is a decision procedure, not a
+mechanism.
+
+## 1. Does this earn a page over a note?
+
+Reach for a page when the reader needs to compare options side by side, see spatial structure, manipulate
+something, navigate non-linearly, or share a link — and the store's own notes genuinely can't. A page
+costs several times the effort of the markdown it's drawn from; don't build one to restate a note in a
+different font. If a note would do the job, the note is the deliverable.
+
+## 2. Name the subject, let the selector produce the set
+
+`ctxr publish gather` resolves a subject to its source notes — never a hand-picked list, which is how a
+walled note slips in unnoticed:
+
+- `--under <prefix>` — a store subtree
+- `--note <path>` — a single note
+- `--entity <name>` — every note linking to a concept, the same enumeration `ctxr rollup gather` uses
+- `--as <context>` — everything a named context can see
+
+## 3. Gate before copying anything out
+
+`ctxr publish gather --audience <audience>` evaluates every resolved note through the same tri-state
+disclosure verdict `ctxr check` uses, and reports the worst verdict in the set. Run it FIRST, before
+reading a single note for content:
+
+- **DENY** notes contribute nothing — not a title, not a count, not a paraphrase.
+- **ASK** stops the build; name the note to the operator and wait.
+- Only **ALLOW** content may be quoted or summarized into the page.
+
+Never infer a verdict from a note's resolved visibility on your own — an external audience's verdict
+requires an explicit tag or a human answer, not an inference from how widely a note is already visible.
+
+## 4. Fix the identity once
+
+`ctxr publish new <slug>` creates the page's folder. A slug starting with a date (`YYYY-` or
+`YYYY-MM-DD-`) is reserved for a frozen snapshot — never used for a page you intend to keep updating.
+The command refuses to overwrite an existing folder; if one already exists for this subject, edit its
+files directly rather than re-running `publish new` — a rename or an overwrite breaks any link already
+handed out.
+
+## 5. Choose the form, then delegate the craft
+
+Pick the shape the content actually needs — a status board, a timeline, a side-by-side comparison, an
+explainer with a live demo — not a rendering of the source notes in reading order. Contexture ships no
+renderer of its own: for visual direction, load the `frontend-design` skill this store carries by
+default (or whichever design-focused skill it's configured or installed instead), and follow it for the
+actual HTML, CSS, and visual language. If a sibling page already exists, read its stylesheet and
+inherit its palette and type scale before inventing a new one.
+
+## 6. Verify the output invariants
+
+`ctxr publish check <path>` runs the mechanical half of the checklist — no external network address,
+a viewport meta tag, at least one print rule, a provenance line, a sibling README, balanced tags, and
+valid syntax in every embedded script. It exits non-zero naming every failing check; fix all of them
+before reporting the page as ready. It answers only what's derivable from the file itself — the DO-test
+in step 1, the form choice in step 5, and factual accuracy stay judgment calls, not checker output.
+
+## 7. It's a page, not a note
+
+The published-pages location is excluded from retrieval by default — a page never becomes a source for
+anything else the store retrieves, and it never carries the visibility field (that would falsely signal
+it's indexed). Confirm with `ctxr lint` after landing.
+
+## 8. Provenance and drift
+
+The source notes are the fact of record. When a fact changes, change the note first, then the page —
+and grep the page for every place that fact was echoed (a summary line, a total, a status badge) before
+declaring the update done; a page that repeats a number in three places goes stale in all three if only
+one is touched.
+
+## 9. Landing
+
+A page's files are ordinary tracked content — they land via `ctxr-submit` like any other change. If a
+change also touches a derived artifact in the sense `ctxr-derived-artifacts` covers (catalog, graph,
+generated document sections), follow that skill's check-before-build discipline for those separately;
+a published page is authored content, not something `ctxr-derived-artifacts` rebuilds.

package/templates/skills/ctxr-session-capture.md

@@ -1,6 +1,11 @@
 End-of-session capture: propose what the session produced that is durable, write only what is approved.
 The approval gate is what keeps the blast radius low — nothing is written without it.
 
+A session produces durable material in two shapes, and they go to different places: a **fact** about
+what happened is a note; a **rule** for how future work should go is a convention, and belongs in this
+store's house conventions at `__HOUSE_CONVENTIONS_PATH__`, which is inlined into AGENTS.md and so loads
+at the start of every session. One pass proposes both.
+
 ## When
 
 Fires on the user's own closing utterance ("done", "ship it", "that's all", a sign-off) or an explicit
@@ -25,6 +30,29 @@ scratch work that landed on no decision.
 
 Unsure → propose (the user can decline).
 
+## What is a convention
+
+A convention is a rule for future work. The test that separates it from a note: a note records that
+something happened, a convention changes what happens next. "We chose Postgres, because X" is a note.
+"Name migrations with the date first, because they sort" is a convention.
+
+The default answer is NO — a store that gains a convention every session ends with a bloated,
+self-contradicting document nobody reads. Propose one only when all four hold:
+
+- It is a rule for future work, not a fact about past work.
+- It applied more than once, or the user stated it as a correction.
+- It is store-wide. A rule about one folder belongs in that folder's `README.md`, not here.
+- It is not already in the shipped baseline — read that file first. Restating contexture's own
+  behavior as a house rule is the most likely way to get this wrong.
+
+Propose REMOVALS on the same bar: a convention the session contradicted, or that no longer matches how
+work actually goes, is worse than none — it teaches the next agent something false. The inlined section
+also has a hard ceiling (`harness.convention_max_bytes`), so growth-only is not a maintenance strategy.
+
+Each entry states the rule, why it exists, and how to apply it. The Why is not decoration: without the
+observation that earned it, no future reader can tell whether a rule still holds or whether a one-off
+calcified, so it never gets retired.
+
 ## Proposal — ONE message, empty proposal omitted
 
 ```
@@ -32,6 +60,12 @@ Unsure → propose (the user can decline).
 - A1  path: <layer>/<location>/<Title>.md
       visibility: <value> — <one-line rationale; `ctxr note resolve` on a sibling shows the default>
       sketch: bullets
+
+### House conventions
+- C1  add · <section> — <the rule, as an imperative>
+      why: <what goes wrong without it — the observation this session produced>
+      apply: <what to do concretely>
+- C2  remove · <the rule, quoted> — <what contradicted it>
 ```
 
 Secret-marker pass: any item whose content looks like a credential gets `⚠ suspected-secret:` on its
@@ -59,7 +93,16 @@ Then run `ctxr session capture --proposal <file>`. It validates and writes every
 one bad path never blocks the rest. These note commits ride the session pull request
 (`ctxr-session-lifecycle`).
 
+Approved conventions are a direct edit to `__HOUSE_CONVENTIONS_PATH__`, never the YAML above: `ctxr
+session capture` writes NOTES — it takes a path, a visibility, and a body, and stamps the visibility
+field — and a guidance file is not a note and carries no visibility. Edit it under the matching
+section, then run `ctxr update` so AGENTS.md re-inlines it, and stage BOTH in the same commit: a staged
+guidance change without a matching staged AGENTS.md regeneration fails `doctor --staged` and the
+pre-commit hook refuses it. If the file does not exist yet (a store migrated in from before it was
+seeded), say so in the proposal and create it with the approved entries — never unasked.
+
 ## Report from actual writes
 
 Report exactly what the command reported — wrote / appended / refused (with reason) / skipped, by ID —
-never from the proposal itself. A refused item is surfaced prominently with its reason.
+never from the proposal itself. A refused item is surfaced prominently with its reason. For conventions,
+report the section each entry landed in or was removed from, and that `ctxr update` re-inlined them.

package/templates/skills/ctxr-session-lifecycle.md

@@ -35,4 +35,23 @@ time regardless — sequence those.
 
 ## Reclaiming
 
-__RECLAIMING_STEP__
+Scope with `ctxr session list` — it reports every worktree and branch this store recognizes as a session,
+whichever checkout you run it from. Reclaiming is always an explicit go, never automatic; never claim a
+worktree or branch was removed without having run the command yourself.
+
+Establish that the pull request actually merged before removing anything, and get that from the forge —
+`gh pr view <branch> --json state` reporting `MERGED` — not from git. If the store squash-merges (GitHub's
+default), the squashed commit is not the branch's tip, so git's ancestry test calls a landed branch
+unmerged forever: `git log <default>..<branch>` never empties and `git branch -d` never succeeds. Reading
+a refusal there as "unmerged work" strands every session the store has ever landed.
+
+With `MERGED` confirmed: `git worktree remove <path>`, then `git branch -d <branch>` — run from outside
+that worktree (no command can remove the directory it is running from — `git worktree list` names the
+canonical clone first). Leave the worktree removal unforced: it refuses on uncommitted work, and that
+refusal is real, so stop and look rather than reaching for `--force`. If `git branch -d` refuses on a
+pull request the forge says is merged, that is the squash case above, and `git branch -D` is the correct
+finish — the forge, not the ancestry graph, is what established the work is safe.
+
+To deliberately discard a session instead — abandoning unmerged work — `git worktree remove --force <path>`
+then `git branch -D <branch>`. State plainly, before running it, that this destroys any uncommitted or
+unmerged work in that worktree; it needs its own explicit go, distinct from the merged-and-clean case above.

package/templates/skills/ctxr-submit.md

@@ -13,14 +13,18 @@ a session, the conflict playbook, sequencing several pull requests) and is not r
    staged set matches the intended unit. Derived artifacts under the cache paths never stage.
 4. One coherent unit per pull request. If the session produced two disjoint units, say so and ask
    whether to split.
-5. Fire gate: `ctxr session submit` commits, pushes, and opens the pull request — an external side
-   effect, and plan consent is not fire consent. Present the branch, the title, and what rides it; wait
-   for an explicit go before running it.
-6. Run: `ctxr session submit --branch "<name>" --title "<title>" --body "<why / what changed /
-   verification / follow-ups>"`. Name a real branch with `--branch` — never let a generated name reach
-   the forge. It runs the full store validation first; fix a failure, never bypass it. If no forge is
-   reachable it still pushes and prints the manual pull-request instructions.
-7. Verify before any retry: a transport error can arrive AFTER the push or the pull-request open already
-   succeeded. Before retrying anything, `git ls-remote origin <branch>` and the forge's pull-request list
-   for the branch — never replay a push or a pull-request open blindly.
-8. Hand off: report the pull request, then point at `ctxr-land` for after review.
+5. Validate: run `ctxr doctor` (store scope, not `--staged` — a session's job is to leave the whole store
+   healthy, not merely pass one commit's gate). Fix a failure; never bypass it, and never proceed past it.
+6. Commit: `git commit -m "<message>"`, describing the unit staged in step 3.
+7. Name the branch: if it still carries a generated name, `git branch -m "<name>"` before pushing — never
+   let a generated name reach the forge.
+8. Run: `git push -u origin "<branch>"`, then `gh pr create --base __DEFAULT_BRANCH__ --title "<title>" --body
+   "<why / what changed / verification / follow-ups>"`. Do not stop to confirm first — the request to
+   submit is the consent for both, and `ctxr doctor` in step 5 is the gate on this path. If `gh` has no
+   reachable GitHub remote for this repository, `git push` still succeeds on its own — report the pushed
+   branch and give the operator the manual pull-request instructions instead of retrying `gh`.
+9. Verify before any retry: a transport error can arrive AFTER the push or the pull-request open already
+   succeeded. Before retrying anything, `git ls-remote origin <branch>` and `gh pr list --head <branch>` —
+   never replay a push or a pull-request open blindly.
+10. Hand off: report the pull request, then point at `ctxr-land` for after review — landing is a separate
+    decision and keeps its own explicit confirmation.

package/templates/vendor/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 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

package/templates/vendor/frontend-design/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: frontend-design
+description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
+license: Complete terms in LICENSE.txt
+---
+
+# Frontend Design
+
+Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify.
+
+## Ground it in the subject
+
+If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout.
+
+## Design principles
+
+For web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option.
+
+Typography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content.
+
+Structure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them.
+
+Leverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated.
+
+Match complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well.
+
+Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.
+
+## Process: brainstorm, explore, plan, critique, build, critique again
+
+For calibration: AI-generated design right now clusters around three looks: (1) a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. Just like a human designer who's hired, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.
+
+Work in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system with color, type, layout, and signature. Color: describe the palette as 4–6 named hex values. Type: the typefaces for 2+ roles (a characterful display face that's used with restraint, a complementary body face, and a utility face for captions or data if needed). Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Signature: the single unique element this page will be remembered by that embodies the brief in an appropriate way.
+
+Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan exactly and deriving every color and type decision from it.
+
+When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and a element-based selector like .cta). This can happen often with paddings/margins between sections.
+
+Try to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them.
+
+## Restraint and self-critique
+
+Spend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.
+
+## More on writing in design
+
+Words appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.
+
+Write from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever.
+
+Use active voice as default. A control should say exactly what happens when it's used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.
+
+Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.
+
+Keep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.

package/templates/vendor/frontend-design/provenance.json

@@ -0,0 +1,7 @@
+{
+  "source": "anthropics/skills",
+  "subpath": "skills/frontend-design",
+  "ref": "53048666b05b4799081517d00e09e0a2dd688678",
+  "license": "Apache-2.0",
+  "sha256": "1608ea77fbb6fc30d13a97d12cfa8ebf31358d40f0dd97beed24829d6b3f45dd"
+}

package/dist/adapters/forge/github.d.ts

@@ -1,12 +0,0 @@
-import type { ForgeAdapter, PullRequestLifecycleState, PullRequestMergeability } from './types.js';
-/** GitHub's own vocabulary, normalized to the adapter interface's small unions — kept pure and exported so tests exercise the mapping without a subprocess. */
-export declare function mapPullRequestState(ghState: string): PullRequestLifecycleState;
-export declare function mapMergeability(ghMergeable: string): PullRequestMergeability;
-/**
- * The reference forge adapter, shelling out to `gh` (same tool, same
- * pattern as `git` itself) rather than a token-based REST client — simpler
- * to implement correctly, and consistent with how every other git-adjacent
- * operation in this codebase is invoked.
- */
-export declare const githubForgeAdapter: ForgeAdapter;
-//# sourceMappingURL=github.d.ts.map

package/dist/adapters/forge/github.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"github.d.ts","sourceRoot":"","sources":["../../../src/adapters/forge/github.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,YAAY,EAAE,yBAAyB,EAAE,uBAAuB,EAAoB,MAAM,YAAY,CAAC;AAMrH,+JAA+J;AAC/J,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,MAAM,GAAG,yBAAyB,CAW9E;AAED,wBAAgB,eAAe,CAAC,WAAW,EAAE,MAAM,GAAG,uBAAuB,CAW5E;AAWD;;;;;GAKG;AACH,eAAO,MAAM,kBAAkB,EAAE,YAkDhC,CAAC"}

package/dist/adapters/forge/github.js

@@ -1,76 +0,0 @@
-import { execFile } from 'node:child_process';
-import { promisify } from 'node:util';
-const execFileAsync = promisify(execFile);
-const PR_NUMBER_RE = /\/pull\/(\d+)/;
-/** GitHub's own vocabulary, normalized to the adapter interface's small unions — kept pure and exported so tests exercise the mapping without a subprocess. */
-export function mapPullRequestState(ghState) {
-    switch (ghState) {
-        case 'OPEN':
-            return 'open';
-        case 'MERGED':
-            return 'merged';
-        case 'CLOSED':
-            return 'closed';
-        default:
-            throw new Error(`Internal error: unrecognized GitHub pull request state "${ghState}".`);
-    }
-}
-export function mapMergeability(ghMergeable) {
-    switch (ghMergeable) {
-        case 'MERGEABLE':
-            return 'mergeable';
-        case 'CONFLICTING':
-            return 'conflicting';
-        case 'UNKNOWN':
-            return 'unknown';
-        default:
-            throw new Error(`Internal error: unrecognized GitHub mergeable status "${ghMergeable}".`);
-    }
-}
-/**
- * The reference forge adapter, shelling out to `gh` (same tool, same
- * pattern as `git` itself) rather than a token-based REST client — simpler
- * to implement correctly, and consistent with how every other git-adjacent
- * operation in this codebase is invoked.
- */
-export const githubForgeAdapter = {
-    id: 'github',
-    kind: 'forge',
-    interfaceVersion: 2,
-    async isAvailable(cwd) {
-        try {
-            // `gh auth status` alone only proves SOME host has stored credentials —
-            // it says nothing about whether THIS repo's remote is even a GitHub
-            // remote. `gh repo view` fails unless the current repo's remote
-            // resolves to a real, reachable GitHub repository, which is the
-            // actual question `session submit` needs answered.
-            await execFileAsync('gh', ['repo', 'view'], { cwd });
-            return true;
-        }
-        catch {
-            return false;
-        }
-    },
-    async openPullRequest(input) {
-        const { stdout } = await execFileAsync('gh', ['pr', 'create', '--head', input.branch, '--base', input.baseBranch, '--title', input.title, '--body', input.body], { cwd: input.cwd });
-        const url = stdout.trim();
-        const match = PR_NUMBER_RE.exec(url);
-        return { url, number: match?.[1] ? Number(match[1]) : null };
-    },
-    async pullRequest(cwd, ref) {
-        const { stdout } = await execFileAsync('gh', ['pr', 'view', ref, '--json', 'number,url,title,state,mergeable,headRefName'], { cwd });
-        const data = JSON.parse(stdout);
-        return {
-            number: data.number,
-            url: data.url,
-            title: data.title,
-            state: mapPullRequestState(data.state),
-            mergeable: mapMergeability(data.mergeable),
-            headBranch: data.headRefName,
-        };
-    },
-    async mergePullRequest(cwd, number, method) {
-        await execFileAsync('gh', ['pr', 'merge', String(number), `--${method}`], { cwd });
-    },
-};
-//# sourceMappingURL=github.js.map