@groupby/ai-dev 0.2.0 → 0.2.3

package/toolsets/rzlv-flow/resources/sync-state-format.md

@@ -113,6 +113,7 @@ Confluence mirror files use this frontmatter:
 sync:
   confluence_page_id: "123456789"          # Confluence page ID
   confluence_url: "https://..."            # Full page URL
+  confluence_title: "Page Title"           # Exact title as it appears in Confluence
   space: "ENG"                             # Confluence space key
   parent_page_id: "987654321"              # Parent page ID in Confluence
   last_synced: "2025-12-11T10:30:00Z"      # Last sync timestamp
@@ -126,6 +127,9 @@ source:
   jira_ticket: "PROJ-120"                  # Associated Jira ticket (optional)
   doc_type: "technical-architecture"       # overview | technical | decisions | strategic
   generated_from: "docs/jira/.../technical-architecture.md"  # Source _docs/ file
+  bmad_docs_referenced:                    # BMAD source docs used (traceability)
+    - "docs/jira/.../technical-architecture.md"
+  jira_initiative_key: "PROJ-100"          # Related Jira initiative (cross-linking)
 
   # Flexible mode fields (use instead of structured fields)
   # origin: "manual"                       # manual | context-analyst | other skill
@@ -207,3 +211,108 @@ Build a REST API endpoint for user authentication that accepts username/password
 - Uses existing `UserService` for credential validation
 - Token signing key stored in environment variables
 ```
+
+---
+
+## Complete Example: Synced Confluence Page (Structured Mode)
+
+This example shows a Confluence page mirror created via the `atlassian-orchestrator` skill from an epic's `_docs/` folder. The file lives at:
+
+```
+docs/confluence/rezolve/ENG/platform-initiative/user-authentication/technical-architecture/index.md
+```
+
+Note the **Leaf Bundle** pattern: the page is a directory (`technical-architecture/`) containing `index.md`, not a flat `.md` file. See `confluence-file-structure.md` for details.
+
+```yaml
+---
+sync:
+  confluence_page_id: "456789012"
+  confluence_url: "https://rezolve.atlassian.net/wiki/spaces/ENG/pages/456789012"
+  confluence_title: "Technical Architecture — User Authentication"
+  space: "ENG"
+  parent_page_id: "456789000"
+  last_synced: "2025-12-11T10:30:00Z"
+  version: 3
+  remote_updated: "2025-12-11T09:15:00Z"
+
+mode: "structured"
+
+source:
+  jira_ticket: "AIP-200"
+  doc_type: "technical-architecture"
+  generated_from: "docs/jira/rezolve/AIP/AIP-200-user-authentication/_docs/technical-architecture.md"
+  bmad_docs_referenced:
+    - "docs/jira/rezolve/AIP/AIP-200-user-authentication/_docs/technical-architecture.md"
+  jira_initiative_key: "AIP-100"
+
+orchestrator:
+  generated_at: "2025-12-08T14:00:00Z"
+  auto_sync: true
+---
+
+# Technical Architecture — User Authentication
+
+## Overview
+
+REST API authentication using JWT tokens with bcrypt password hashing and Redis-backed rate limiting.
+
+## Authentication Flow
+
+1. Client sends POST `/api/auth/login` with credentials
+2. Server validates against UserService
+3. On success: sign JWT with RS256, return token + expiry
+4. On failure: increment rate limiter, return 401
+
+## Technology Decisions
+
+- **JWT signing:** RS256 with rotating keys (see decisions.md)
+- **Rate limiting:** Redis sliding window, 5 req/min/IP
+- **Password storage:** bcrypt with cost factor 12
+```
+
+---
+
+## Complete Example: Synced Confluence Page (Flexible Mode)
+
+This example shows an ad-hoc page published to Confluence by a developer using the `confluence-publish` skill. The file lives at:
+
+```
+docs/confluence/rezolve/ENG/team-guides/onboarding-guide/index.md
+```
+
+```yaml
+---
+sync:
+  confluence_page_id: "789012345"
+  confluence_url: "https://rezolve.atlassian.net/wiki/spaces/ENG/pages/789012345"
+  confluence_title: "Developer Onboarding Guide"
+  space: "ENG"
+  parent_page_id: "789012000"
+  last_synced: "2025-12-12T14:00:00Z"
+  version: 1
+  remote_updated: "2025-12-12T14:00:00Z"
+
+mode: "flexible"
+
+source:
+  origin: "manual"
+  linked_jira: "AIP-300"
+---
+
+# Developer Onboarding Guide
+
+Welcome to the team! This guide covers local setup, tooling, and key workflows.
+
+## Local Setup
+
+1. Clone the monorepo
+2. Run `npm install` in the root
+3. Copy `.env.example` to `.env` and fill in values
+
+## Key Workflows
+
+- **Daily triage:** Use `jira-daily-triage` to start your day
+- **Ticket focus:** Use `jira-ticket-focus` to deep-load a ticket
+- **Wrap up:** Use `jira-wrap-sync` when finishing work
+```

package/toolsets/rzlv-flow/skills/jira-daily-triage/SKILL.md

@@ -40,9 +40,9 @@ Before executing, read these resource files for protocol and structure guidance:
   ```
   JQL: project = {PROJECT} AND sprint in openSprints()
   ```
-- Extract the sprint name and ID from the results.
-- If no open sprint is found, inform the user and continue without a sprint filter.
-- Store the active sprint name and ID for the session.
+- Extract the sprint name, ID, end date, and days remaining from the results.
+- If no open sprint is found, display: "No active sprint detected — Backlog mode" and continue without a sprint filter. In Backlog mode, skip sprint-scoped queries and show only the user's assigned tickets ordered by priority.
+- Store the active sprint name, ID, end date, and days remaining for the session.
 
 > **Note:** Sprint data may be stored in custom fields whose names vary by Jira instance. When using MCP to query sprint tickets, inspect the returned fields for sprint information (name, start/end dates, goal). If sprint details are missing from the default field set, request additional fields or use `'*all'` to retrieve all fields.
 
@@ -90,7 +90,12 @@ Present results using this structure:
 
 ```
 ## 🌅 Your Day — {date}
-**Project:** {PROJECT} | **Sprint:** {Sprint Name} ({X}/{Y} tickets complete)
+**Project:** {PROJECT} | **Sprint:** {Sprint Name} | **Ends:** {end_date} ({days_left} days left)
+**Sprint Progress:** {X}/{Y} tickets complete
+
+{IF NO SPRINT:}
+## 🌅 Your Day — {date}
+**Project:** {PROJECT} | **No active sprint detected — Backlog mode**
 
 ### 🔥 In Progress (Complete These First)
 | # | Ticket | Summary | Points | Days Active |
@@ -114,7 +119,10 @@ Present results using this structure:
 | 5 | PROJ-130 | Performance fix | 5 | Critical |
 
 ### ⚠️ Blockers & Flags
-- PROJ-120: Waiting on design review (3 days)
+- {TICKET-KEY}: {blocker description} ({n} days)
+- {TICKET-KEY}: {blocker description} ({n} days)
+{IF NO BLOCKERS:}
+✓ No blockers detected
 
 **Recommended Focus:** #1 PROJ-123 (continue in-progress work) or #2 PROJ-124 (fresh start)
 

package/toolsets/rzlv-flow/skills/jira-sprint-status/SKILL.md

@@ -30,7 +30,7 @@ Use MCP to find the active sprint:
 JQL: project = {PROJECT} AND sprint in openSprints()
 ```
 
-Extract the sprint name and ID. If no open sprint is found, inform the user and offer to report on a specific sprint or the full backlog.
+Extract the sprint name, ID, start date, end date, and sprint goal (if set). If no open sprint is found, inform the user and offer to report on a specific sprint or the full backlog.
 
 > **Note:** Sprint data may be stored in custom fields whose names vary by Jira instance. When using MCP to query sprint tickets, inspect the returned fields for sprint information (name, start/end dates, goal). If sprint details are missing from the default field set, request additional fields or use `'*all'` to retrieve all fields.
 
@@ -59,6 +59,16 @@ Calculate:
 - Overall completion percentage (done points / total points, or done count / total count)
 - Sprint velocity so far (points completed)
 
+### Step 4b: Calculate Velocity and Forecast
+
+Using the sprint start date, end date, and points completed so far:
+
+- **Days elapsed** — business days since sprint start
+- **Days remaining** — business days until sprint end
+- **Ideal velocity** — total points / total sprint days (points/day to finish on time)
+- **Actual velocity** — done points / days elapsed
+- **Forecast** — at current velocity, project whether the sprint will finish on time, ahead, or behind. If behind, estimate the shortfall: "May miss by {n} points"
+
 ### Step 5: Identify Risks
 
 Flag potential risks:
@@ -81,6 +91,11 @@ Filter tickets assigned to the current user:
 ```
 ## 📊 Sprint Status: {Sprint Name}
 **Project:** {PROJECT} | **Sprint:** {Sprint Name}
+**Ends:** {end_date} ({days_left} days left)
+{IF SPRINT GOAL SET:}
+**Goal:** {Sprint Goal}
+
+████████████░░░░░░░░ {percent}% Complete
 
 ### Progress
 | Status | Tickets | Story Points |
@@ -92,6 +107,11 @@ Filter tickets assigned to the current user:
 
 **Completion:** {percent}% by points ({done_pts}/{total_pts})
 
+### Velocity & Forecast
+- **Ideal:** {n} points/day
+- **Actual:** {n} points/day
+- **Forecast:** {On track | Ahead by {n} points | May miss by {n} points}
+
 ### Ticket Breakdown
 | # | Ticket | Summary | Status | Assignee | Points |
 |---|--------|---------|--------|----------|--------|
@@ -113,4 +133,11 @@ Filter tickets assigned to the current user:
 - **Completed:** {n} tickets ({pts} pts)
 - **In Progress:** {n} tickets ({pts} pts)
 - **Assigned (To Do):** {n} tickets ({pts} pts)
+
+---
+**Quick Actions:**
+1. View at-risk tickets in detail
+2. Focus on blocked items
+3. Generate standup update (summary for copy/paste)
+4. Export sprint data as markdown table
 ```

package/toolsets/rzlv-flow/skills/jira-ticket-focus/SKILL.md

@@ -25,7 +25,10 @@ Before executing, read these resource files — they are critical for correct be
 - If the user provides a **number** (e.g. "3"), look it up from the `numbered_ticket_list` stored in conversational context from a prior `jira-daily-triage` run.
 - If the user provides a **Jira key** (e.g. "PROJ-123"), use it directly.
 - If the key is **incomplete** (e.g. "123"), prepend the `confirmed_project` key from session context (e.g. "PROJ-123").
-- If neither a number mapping nor a project key is available, ask the user for the full ticket key.
+- If neither a number mapping nor a project key is available, attempt fallback detection:
+  1. **Git branch:** Check the current branch name for a `{PROJECT}-{n}` pattern (e.g. `feature/PROJ-123` → project is `PROJ`).
+  2. **Config file:** Check for a `.jira.json` file in the project root containing `{ "project": "PROJ", "instance": "rezolve" }`.
+  3. If neither yields a project key, ask the user for the full ticket key.
 
 ### Step 2: Fetch Ticket Details (FCMP Fetch Step)
 
@@ -35,6 +38,8 @@ Use `mcp_atlassian-rovo_fetch()` to retrieve:
 - Comments and recent history
 - Sprint information (use `active_sprint_name` from session context if available)
 - Linked Confluence documents (if any)
+- **Subtasks** — fetch all subtasks of the ticket via JQL: `parent = {TICKET-KEY} ORDER BY status ASC, priority DESC`
+- **Linked issues** — fetch linked issues (blocks, is blocked by, relates to)
 
 **Parent Epic detection** — check in this order:
 

package/toolsets/rzlv-flow/skills/jira-wrap-sync/SKILL.md

@@ -40,12 +40,23 @@ Before executing, read these resource files:
 - Map code changes to acceptance criteria where possible.
 - Summarize: files changed, insertions, deletions.
 
+**c) Acceptance criteria progress:**
+- Read the AC list from the ticket file.
+- Based on code changes and commit messages, infer which AC items have been completed.
+- Show checkbox progress:
+  ```
+  - [x] AC 1 — Completed (matches changes in auth-controller.ts)
+  - [x] AC 2 — Completed (matches changes in rate-limiter.ts)
+  - [ ] AC 3 — Not yet addressed
+  ```
+- Note: this is a best-effort inference. The user confirms the final state.
+
 ### Step 3: Draft Jira Comment
 
-Build a comprehensive comment covering both ticket updates and code progress:
+Build a comprehensive comment with the standardized prefix `[rzlv-flow Update]`:
 
 ```
-**Work Update:**
+[rzlv-flow Update]
 
 {IF TICKET FIELD CHANGES:}
 **Ticket Updates:**
@@ -61,22 +72,44 @@ Build a comprehensive comment covering both ticket updates and code progress:
 - {file1}: {brief description}
 - {file2}: {brief description}
 
-**AC Completed:** {X}/{Y}
-**Remaining:** {what's left}
+**Acceptance Criteria:**
+- [x] {completed AC 1}
+- [x] {completed AC 2}
+- [ ] {remaining AC 3}
+**Progress:** {X}/{Y} completed
 
 **Next Steps:** {suggested next action}
+
+Context: {optional PR link or Confluence doc link}
 ```
 
-### Step 4: FCMP Protocol (Before Any Sync)
+### Step 4: FCMP Preview (Prepare PUSH — Dry Run)
 
-Before executing any write operations, run the full FCMP cycle:
+Before executing any write operations, run the full FCMP cycle and present a dry-run preview:
 
 1. **FETCH** — Get the current ticket state from Jira via MCP.
 2. **COMPARE** — Check for remote changes since last sync (compare `sync.version` and `sync.remote_updated`).
 3. **MERGE** — If conflicts detected, show a diff of remote changes vs local changes and resolve with the user.
-4. Show the diff to the user and warn if conflicts exist.
+4. **Preview** — Show a dry-run diff of what will change if the user proceeds:
+
+```
+### FCMP Preview (Dry Run)
+{IF NO REMOTE CHANGES:}
+✓ Remote is unchanged since last sync — safe to push.
+
+{IF REMOTE CHANGES DETECTED:}
+⚠️ Remote changes detected since last sync:
+- {field}: {old_value} → {new_value}
+
+**Proposed local → remote changes:**
+- Description: {diff summary}
+- Story Points: {old} → {new}
+- Status: {current} (no change)
+
+Proceed with sync? (y/n)
+```
 
-Only proceed to the action menu after the FCMP cycle completes.
+Only proceed to the action menu after the FCMP preview is confirmed.
 
 ### Step 5: Present Multi-Select Action Menu
 

package/skills/skills/README.md

@@ -1,61 +0,0 @@
-# Skills
-
-This folder manages all skills, archived skills, and examples/instructions on using them.
-
-All skills in this `skills/library/` should represent _generally useful skills_ that might be used across teams.
-
-If any particular skill goes missing, note that it may have simply been archived (see [the archive](skills/archived/)) and may no longer be recommended for use. Ideally skills are not simply deleted from this repository, since others may be expecting them to be there.
-
-## Usage
-
-When developing a project, it is generally recommended to commit any skills you use to that codebase so that others may use them as well. Skills are stored as folders and can include many files, but need to include at least a SKILL.md file. Normal locations are:
-
-* **Claude Code**: `.claude/skills/<skill-name>/`
-* **Copilot**: `.github/skills/<skill-name>/`
-* **Codex**: `.agents/skills/<skill-name>/`
-  * Codex allows for storing skills in [many places](https://developers.openai.com/codex/skills#where-to-save-skills), including outside the repo.
-
-Note that each folder must contain a SKILL.md file, and may optionally contain other arbitrary files:
-* Other markdown files that describe processes
-* Script files that allow for deterministic coding
-* ...plus other resources required by either
-
-All of the above should be referenced directly by their SKILL.md file, with an explanation on when to read or use them.
-
-## Recommended usage
-
-However, to allow everyone to use skills regardless of their LLM client of choice, it can be valuable to do the following:
-
-* Store the skill folder in a place like `docs/ai/skills/<skill-name>/`
-* Reference the skill in the folder for each relevant client.
-
-For example:
-
-In `docs/ai/skills/frontend-design/SKILL.md`:
-
-```
----
-name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
----
-
-This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
-
-The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
-
-...
-```
-
-Then, in `.github/skills/frontend-design/SKILL.md` (and anywhere else needed):
-
-```
----
-name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
-license: Complete terms in LICENSE.txt
----
-
-See `docs/ai/skills/frontend-design/SKILL.md` and follow closely.
-```
-
-Note that we MUST include the skill boilerplate in any official skills location (eg. `.github/skills/`, etc.) to enable discovery and usage. We then copy the entire skill into `docs/ai/skills/` to leave it intact, though we don't technically need the boilerplate.

package/skills/skills/archived/README.md

@@ -1,3 +0,0 @@
-# Skills archive
-
-Any deprecated/archived skills should be moved here for discoverability purposes.

package/skills/skills/library/README.md

@@ -1,3 +0,0 @@
-# Skills library
-
-This folder contains skill folders that can be easily copied into project repos.

package/skills/skills/library/frontend-design/LICENSE.txt

@@ -1,177 +0,0 @@
-
-                                 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/skills/skills/library/frontend-design/SKILL.md

@@ -1,42 +0,0 @@
----
-name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
-license: Complete terms in LICENSE.txt
----
-
-This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
-
-The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
-
-## Design Thinking
-
-Before coding, understand the context and commit to a BOLD aesthetic direction:
-- **Purpose**: What problem does this interface solve? Who uses it?
-- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
-- **Constraints**: Technical requirements (framework, performance, accessibility).
-- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
-
-**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
-
-Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
-- Production-grade and functional
-- Visually striking and memorable
-- Cohesive with a clear aesthetic point-of-view
-- Meticulously refined in every detail
-
-## Frontend Aesthetics Guidelines
-
-Focus on:
-- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
-- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
-- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
-- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
-- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
-
-NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
-
-Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
-
-**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
-
-Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.