@jini-ai/agent-plugins 0.6.17 → 0.6.19

package/ui-ux-design/LICENSE

@@ -0,0 +1,201 @@
+                                 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 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 Support. 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 support.
+
+   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 2026 Open Design contributors
+
+   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/ui-ux-design/NOTICE

@@ -0,0 +1,14 @@
+Jini UI/UX Design Agent Plugin
+Copyright 2026 Leona Burime
+
+Portable skill sources remain at packages/agent-plugins/ui-ux-design.
+Originally assembled from AI-Dev-Shop's Web Design skill trees; the ADS-specific
+agent persona and routing implementation are not included.
+
+Source notes and attribution are retained in the generated skills tree, including
+skills/interface-design/ORIGINAL.md (Dammyjay93/interface-design) and
+skills/gstack-design/references/upstream-notes.md (garrytan/gstack).
+The skill references retain their original source links and attribution.
+
+This distribution does not include the provider-plugin aggregate or its Open SaaS
+Stripe adaptations. See LICENSE for the Apache License, Version 2.0.

package/ui-ux-design/README.md

@@ -0,0 +1,62 @@
+# `@jini-ai/agent-plugins/ui-ux-design`
+
+This plugin ships only as a subpath of `@jini-ai/agent-plugins`.
+
+Portable Agent Plugins payload containing seven design skills: UI/UX design, interface design,
+gstack design, frontend accessibility, Vercel web guidelines, shadcn/ui, and web compliance.
+Resolving this subpath reads only this plugin; it has no runtime or plugin dependencies.
+
+Resolve `@jini-ai/agent-plugins/ui-ux-design` with the host's package resolver. Its containing
+directory holds the payload. Copy that selected directory beneath the host's bundled-source root,
+then use `@jini-ai/agent-plugins/lifecycle` to seed it. That existing path packs the directory,
+verifies its digest, installs atomically, records activation and selects the bundled digest.
+Use the lifecycle's trusted installed-file readers for contributions. Host policy controls activation;
+installing this npm package grants no permission and preserves operator disablement on later boots.
+
+The npm version follows Jini's fixed release group. The inner `plugin.json` version (**0.6.2**)
+orders the plugin's own content releases; hosts refuse a lower one over an installed copy.
+The `./ui-ux-design/*` export exposes its raw assets for host staging.
+
+Sources ship in place from `packages/agent-plugins/ui-ux-design`: `plugin.json`, `mcp.json`, the
+complete skills tree (including references, examples and scripts), and the existing
+`com.anthropic.claude-code` extension. Tests, build output and caches are excluded. LICENSE and NOTICE retain provenance;
+no provider plugin or vendor SDK is included.
+
+## Host-neutral wording
+
+This is the one shared copy for every host. Its text names no host tools: it tells the agent to
+discover the host's tools, follow the host's permissions and explain a missing capability. The
+`shadcn-ui` frontmatter keeps `Bash` for coding hosts. A host that forbids shell use adds its own
+chat rules and strips that entry when it delivers the guidance, from its own overlay folder.
+
+## Upstream
+
+`skills/ui-ux-design/` is synced from AI-Dev-Shop's `skills/ui-ux-design/` (last sync: commit
+c10abee, 2026-10-30). Change guidance there first, then sync here, keeping the local host-neutral
+parts: the "Tool use and context" section and the "Read any supplied feature spec" bullet in
+`skills/ui-ux-design/SKILL.md`, the opening tool-discovery paragraph in `skills/shadcn-ui/SKILL.md`,
+and the `name`/`description` frontmatter in `skills/web-compliance/SKILL.md`.
+
+## Included skills
+
+Bundles the AI-Dev-Shop Web Design agent's full skill set (per its `agents/web-design/skills.md`
+persona and the `framework/routing/skills-registry.md` ownership mapping) into one portable plugin:
+
+- `ui-ux-design` — design-foundations (tokens, typography, spacing, breakpoints, component state
+  matrix) *and* first-impression polish, scanning hierarchy, conversion-focused visual signals —
+  one skill, not two. AI-Dev-Shop merged its former separate `ux-design` and `premium-ui` skills
+  into this single `ui-ux-design` skill; this sample tracks that merge instead of carrying the two
+  predecessor skills as stale copies (see git history for the 2026-08-12 consolidation).
+- `interface-design` — repeatable, memory-consistent visual systems for dashboards/admin panels/apps
+- `gstack-design` — manual four-mode workflow (consultation, shotgun, html, review)
+- `frontend-accessibility` — WCAG 2.1 AA checklist
+- `vercel-web-design-guidelines` — Vercel Web Interface Guidelines auditor
+- `shadcn-ui` — shadcn/ui (Radix + Tailwind) component discovery/integration guidance
+- `web-compliance` — legal/compliance checkpoints for public-facing UX flows
+
+Each skill directory is a verbatim copy of the corresponding `AI-Dev-Shop/skills/<name>/` tree —
+copied rather than referenced, because the whole point of a plugin is that it is self-contained and
+portable to a host that has never heard of AI-Dev-Shop. `AI-Dev-Shop/agents/web-design/skills.md`
+itself (the persona that composes these skills into one role) is not bundled — it is ADS-specific
+routing glue, not a portable skill.
+

package/ui-ux-design/com.anthropic.claude-code/hooks/hooks.json

@@ -0,0 +1,4 @@
+{
+  "$comment": "Example only, not real config. `com.anthropic.claude-code` follows the reverse-DNS convention Agent Plugins §8.2 describes (a client that controls a domain uses its reverse), but the spec publishes no namespace registry — this string is a plausible guess, not a confirmed/registered Claude Code identifier. The spec assigns no portable semantics to what's inside a client's own namespace directory in any case, so this file's shape is illustrative only.",
+  "hooks": []
+}

package/ui-ux-design/mcp.json

@@ -0,0 +1,4 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
+  "mcpServers": {}
+}

package/ui-ux-design/plugin.json

@@ -0,0 +1,26 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "ui-ux-design",
+  "version": "0.6.2",
+  "description": "UI/UX design, interface-design-system, accessibility, and shadcn/ui component skills bundled as one portable Agent Plugin.",
+  "extensions": {
+    "tovu": {
+      "displayName": "UI/UX Design",
+      "summary": "Helps the assistant design clean, accessible pages and components.",
+      "id": "jini/ui-ux-design",
+      "provides": [
+        "ui-design"
+      ]
+    }
+  },
+  "keywords": [
+    "design",
+    "ui",
+    "ux",
+    "ui-design",
+    "theme",
+    "page",
+    "website",
+    "layout"
+  ]
+}

package/ui-ux-design/skills/frontend-accessibility/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: frontend-accessibility
+version: 1.0.0
+last_updated: 2026-02-26
+description: WCAG 2.1 AA compliance guidance for frontend code review and E2E testing.
+---
+
+# Skill: Frontend Accessibility
+
+Accessibility is not a feature — it is a baseline quality requirement. A UI component that cannot be operated via keyboard or read by a screen reader is broken for a significant portion of users. This skill provides the WCAG 2.1 AA checklist that Code Inspection and QA/E2E agents use to catch violations before they ship.
+
+## WCAG 2.1 AA — What to Check in Code Inspection
+
+### Perceivable
+- All non-text content has a text alternative (`alt` on images, `aria-label` or `aria-labelledby` on icon buttons).
+- Color is not the only means of conveying information (error state must also have text or icon, not just red color).
+- Minimum contrast ratio: 4.5:1 for normal text, 3:1 for large text and UI components.
+- No content flashes more than 3 times per second.
+
+### Operable
+- All functionality accessible via keyboard (Tab, Shift+Tab, Enter, Space, Arrow keys).
+- Visible focus indicator on all interactive elements — never `outline: none` without a replacement.
+- Skip navigation link for pages with repeated navigation.
+- No keyboard traps — user can always Tab out of a component.
+
+### Understandable
+- Form inputs have associated `<label>` elements (not just placeholder text).
+- Error messages identify the field and describe the error — not just "invalid input".
+- Language attribute on `<html>` element.
+
+### Robust
+- Semantic HTML — use `<button>` for buttons, `<a>` for links, heading hierarchy (`<h1>` → `<h2>` → `<h3>`).
+- ARIA roles only when native HTML semantics are insufficient.
+- ARIA attributes used correctly — do not add `aria-label` to elements that already have visible text.
+
+## Common Violations to Flag in Code Inspection
+
+- `<div onClick>` instead of `<button>` — not keyboard accessible, no ARIA role.
+- `<img>` without `alt` attribute.
+- `<input>` without associated `<label>` (placeholder is not a label).
+- Interactive element with no visible focus state.
+- Hardcoded color values with insufficient contrast.
+- Error state communicated only via color change.
+
+## E2E Testing for Accessibility (axe-core integration)
+
+- Inject `@axe-core/playwright` in E2E tests.
+- Run `checkA11y()` after each page navigation and after dynamic content loads.
+- Configure to WCAG 2.1 AA ruleset.
+- Treat Critical and Serious violations as test failures.
+- Moderate violations are warnings — log but do not fail.
+
+## Keyboard Navigation Test Checklist
+
+- [ ] Can reach all interactive elements via Tab
+- [ ] Can activate buttons with Enter and Space
+- [ ] Can navigate dropdowns/menus with Arrow keys
+- [ ] Modals trap focus correctly (Tab stays inside modal while open)
+- [ ] Focus returns to trigger element when modal closes
+- [ ] Skip link present and functional on pages with navigation

package/ui-ux-design/skills/gstack-design/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: gstack-design
+version: 0.1.0
+last_updated: 2026-06-05
+description: Use when a user manually invokes gstack-inspired design workflows for product design consultation, visual variants, frontend implementation handoff, or UI design review.
+---
+
+# Skill: gstack Design
+
+Manual/slash-invoked domain skill adapted from gstack design workflows. This skill is not wired into the default pipeline.
+
+## Execution
+
+- Determine the user's requested design mode from the prompt or slash command arguments.
+- Select exactly one mode per invocation: `consultation`, `shotgun`, `html`, or `review`.
+- Read exactly one matching reference file from `references/` before taking action.
+- Do not load all references, chain modes, or silently expand into pipeline agent dispatch.
+- Preserve existing AI Dev Shop design rules, accessibility expectations, and project constraints.
+- If the user request spans multiple modes, ask which mode to run first.
+
+## Guardrails
+
+- Do not assume upstream-specific runtime services, generated boards, analytics hooks, or external binaries exist.
+- Do not implement code during `consultation`, `shotgun`, or `review` unless the user explicitly changes scope.
+- In `html` mode, treat "html" as a legacy shorthand for frontend implementation/prototype handoff; do not force raw HTML when the project has a framework.
+- Do not replace existing brand or design systems without explicit user approval.
+- Do not claim browser or screenshot evidence unless it was actually captured in the current host.
+
+## Output
+
+Return a concise design artifact for the selected mode:
+
+- selected mode and reference used
+- inputs inspected
+- recommendation or findings
+- open questions or approval gates
+- next action, if any
+
+## Reference
+
+Read exactly one reference based on intent:
+
+- `references/consultation.md` - new product direction, design system, brand/aesthetic proposal, or design strategy.
+- `references/shotgun.md` - multiple visual directions, option exploration, comparison, or taste feedback.
+- `references/html.md` - approved design to frontend implementation guidance or static prototype.
+- `references/review.md` - audit existing UI for hierarchy, spacing, accessibility, consistency, or AI slop.
+- `references/upstream-notes.md` - provenance only; do not load for normal execution unless reviewing upstream drift.
+
+## Failure Path
+
+- If no mode is clear, ask for one choice.
+- If required product context is missing, produce a bounded assumption list rather than inventing facts.
+- If a requested action conflicts with AI Dev Shop frontend/design guardrails, state the conflict and ask for approval before proceeding.

package/ui-ux-design/skills/gstack-design/references/consultation.md

@@ -0,0 +1,30 @@
+# Design Consultation
+
+## When
+
+Use for a new product surface, design direction, brand/aesthetic pass, or design-system proposal before implementation.
+
+## Workflow
+
+1. Gather product context: target users, core workflow, business goal, platform, existing brand, and UI constraints.
+2. Inspect existing UI or design artifacts when available before proposing a new direction.
+3. Identify the design problem in plain terms: what must be easier, clearer, faster, more trusted, or more memorable.
+4. Optionally research comparable products or patterns when the user asks for market/landscape awareness.
+5. Propose one primary design direction and one credible alternative.
+6. Define foundations only as far as needed: layout principles, typography direction, color role, spacing scale, motion posture, and component tone.
+7. Call out tradeoffs: implementation complexity, accessibility risk, brand risk, and where taste decisions need human input.
+
+## Output
+
+- Context summary
+- Recommended design direction
+- Alternative direction
+- Foundations and component implications
+- Decisions needed from the user
+- Suggested next mode: `shotgun`, `html`, or `review`
+
+## Guardrails
+
+- Do not invent user research or brand evidence.
+- Do not prescribe a full redesign when a smaller design repair would solve the problem.
+- Do not pick decorative visual trends over usability, accessibility, or product fit.

package/ui-ux-design/skills/gstack-design/references/html.md

@@ -0,0 +1,29 @@
+# Frontend Implementation Handoff
+
+## When
+
+Use after a design direction is approved and the user wants a frontend implementation plan, static prototype, or production handoff. The `html` mode name is legacy shorthand; it is not a raw HTML-only constraint.
+
+## Workflow
+
+1. Confirm the approved design source: consultation output, shotgun winner, screenshot, mockup, or user description.
+2. Detect the project frontend stack when a repo is present; prefer the existing framework and design system.
+3. Convert design intent into implementable structure: layout, components, states, tokens, responsive rules, and content hierarchy.
+4. If producing static HTML/CSS, keep it semantic, responsive, accessible, and clearly labeled as a prototype.
+5. If producing framework guidance, specify components, props, state handling, CSS strategy, and verification steps.
+6. Verify the result against the approved direction using browser evidence when browser automation is available.
+
+## Output
+
+- Implementation target and assumptions
+- Component/layout plan
+- Token and style notes
+- Accessibility and responsive checks
+- Prototype or implementation handoff
+- Verification checklist
+
+## Guardrails
+
+- Do not assume upstream-specific prototype tooling or generated design-board services exist.
+- Do not ignore the host app's current framework or design system.
+- Do not skip final visual verification when browser automation is available.

package/ui-ux-design/skills/gstack-design/references/review.md

@@ -0,0 +1,28 @@
+# Design Review
+
+## When
+
+Use to audit an existing UI for design quality, usability, accessibility, visual consistency, or AI-generated slop patterns.
+
+## Workflow
+
+1. Identify the target screen, flow, or component set.
+2. Inspect available evidence: screenshots, browser state, DOM, component code, design docs, or user reports.
+3. Audit hierarchy, spacing, alignment, typography, color contrast, responsive behavior, component states, loading/empty/error states, and interaction clarity.
+4. Look for common AI slop: generic gradients, meaningless decorative visuals, mismatched radii, low-density cards, vague copy, and inconsistent spacing.
+5. Classify findings as blocker, should-fix, or polish.
+6. Recommend the smallest design change that fixes the issue before proposing a broad redesign.
+
+## Output
+
+- Evidence inspected
+- Findings by severity
+- Specific recommended fixes
+- Accessibility and responsive notes
+- Follow-up mode if needed
+
+## Guardrails
+
+- Do not claim visual evidence without inspection.
+- Do not rewrite the product's visual direction unless the user asks.
+- Do not bury accessibility blockers under polish comments.

package/ui-ux-design/skills/gstack-design/references/shotgun.md

@@ -0,0 +1,33 @@
+# Design Shotgun
+
+## When
+
+Use when the user wants visual options, competing design directions, or a fast comparison before committing to one direction.
+
+## Workflow
+
+1. Confirm the target surface and constraints: product, audience, platform, existing UI, and non-negotiable brand or accessibility rules.
+2. Generate 3-6 meaningfully distinct directions. Avoid small variations of the same idea.
+3. For each direction, provide:
+   - name
+   - core idea
+   - visual language
+   - interaction posture
+   - accessibility and implementation tradeoffs
+4. Compare directions across brand fit, clarity, speed to build, accessibility, novelty, and maintenance cost.
+5. Ask the user for structured preference feedback: keep, reject, combine, or revise.
+6. Capture taste signals as explicit notes so the next mode can reuse them.
+
+## Output
+
+- Variant list
+- Comparison matrix
+- Recommended short list
+- Preference questions
+- Next step recommendation
+
+## Guardrails
+
+- Do not auto-select a final direction without user feedback.
+- Do not generate implementation code in this mode.
+- Do not present impossible or inaccessible designs as production-ready.

package/ui-ux-design/skills/gstack-design/references/upstream-notes.md

@@ -0,0 +1,23 @@
+# Upstream Notes
+
+## Source
+
+- Repo: `https://github.com/garrytan/gstack`
+- Local source: `/Users/la/Desktop/Multi-Agent Swarm Foundation/other-repos-to-learn-from/gstack`
+- Source commit: `cab774cc`
+- Adapted source files: `design-consultation/SKILL.md`, `design-shotgun/SKILL.md`, `design-html/SKILL.md`, `design-review/SKILL.md`
+
+## Kept
+
+- Product-context-first design consultation
+- Multiple visual directions before commitment
+- Structured comparison and taste feedback
+- Approved-design implementation/prototype handoff
+- UI review for hierarchy, spacing, accessibility, and AI slop
+
+## Stripped
+
+- Generated shared preambles and Claude-specific AskUserQuestion plumbing
+- Telemetry/config setup, taste databases, and local state scripts
+- gstack design daemon, comparison board binary, and Pretext runtime assumptions
+- Any hardcoded gstack install paths or external service requirements

package/ui-ux-design/skills/interface-design/ORIGINAL.md

@@ -0,0 +1,16 @@
+# Original Source Notes
+
+Imported from `Dammyjay93/interface-design`.
+
+Source characteristics:
+
+- plugin-oriented package for Claude Code
+- active command set under `.claude/commands`
+- source examples and system template under `reference/`
+- markdown-first design workflow centered on craft, memory, and consistency
+
+This repo normalizes that package into a single runtime skill with supporting material under `references/`.
+
+Source URL:
+
+- https://github.com/Dammyjay93/interface-design

package/ui-ux-design/skills/interface-design/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: interface-design
+version: 1.0.0
+last_updated: 2026-03-18
+description: Use when designing interfaces for dashboards, apps, tools, or admin panels where craft, memory, and consistency matter. Not for marketing sites.
+---
+
+# Skill: Interface Design
+
+Interface design here means deliberate visual systems, not generic UI output. Use this skill when the user wants a project-specific look and repeatable design decisions across sessions.
+
+## Scope
+
+- Use for product interfaces, internal tools, dashboards, admin panels, and workflow apps.
+- Do not use for marketing sites or copy-first landing pages.
+- Prefer this skill when the user wants a visual system rather than isolated component styling.
+
+## Load Strategy
+
+Read this file for the runtime contract. Open references only when you need the heavier material:
+
+- `references/system-template.md` for the `.interface-design/system.md` shape and token scaffold
+- `references/commands/init.md` for the build-first workflow
+- `references/commands/audit.md` for checking existing code against a system
+- `references/commands/extract.md` for deriving a system from existing code
+- `references/commands/status.md` for reporting the active design system
+- `references/commands/critique.md` for craft-focused review and rebuild guidance
+- `references/examples/system-precision.md` and `references/examples/system-warmth.md` for two concrete directions
+
+## Core Contract
+
+- Establish or load `.interface-design/system.md` before making repeated UI decisions.
+- Reuse spacing, radius, depth, and typography choices consistently.
+- State the design direction explicitly before building a component or screen.
+- Capture new stable patterns in `.interface-design/system.md` instead of letting them drift across files.
+
+## Practical Defaults
+
+- Keep the system tangible: direction, foundation, depth, tokens, patterns.
+- Prefer a small number of explicit design choices over a long list of vague principles.
+- When an existing interface already has a recognizable pattern set, preserve it and extend it rather than replacing it wholesale.