@mohammadhprp/system-prompt 0.12.1 → 0.12.3

package/framework/skills/gitlab-mcp/references/issues.md

@@ -1,141 +0,0 @@
-# Issue Management
-
-## Create
-
-```
-create_issue
-  project_id: "my-group/my-project"
-  title: "Login page returns 500"
-  description: "Steps to reproduce..."
-  labels: "bug,critical"
-  assignee_ids: [123]
-  milestone_id: 5
-```
-
-## Read
-
-```
-get_issue         -> single issue details
-list_issues       -> project issues (default: created by current user)
-  scope: "all"    -> list ALL issues (not just current user's)
-  state: "opened" -> filter by state
-  labels: "bug"   -> filter by labels
-my_issues         -> issues assigned to current user across all projects
-```
-
-**Important**: `list_issues` defaults to showing only issues created by the current user.
-Pass `scope: "all"` to see all project issues.
-
-## Update
-
-```
-update_issue
-  project_id: "my-group/my-project"
-  issue_iid: 10
-  state_event: "close"    # or "reopen"
-  labels: "bug,resolved"
-  assignee_ids: [456]
-```
-
-### Patch-based description update (token-efficient)
-
-```
-update_issue_description_patch
-  project_id: "my-group/my-project"
-  issue_iid: 10
-  patch_type: "search_replace"  # or "unified_diff"
-  patch: |
-    <<<<<<< SEARCH
-    Status: In progress
-    =======
-    Status: Ready for review
-    >>>>>>> REPLACE
-  dry_run: false
-  create_note: true
-```
-
-Applies a small patch to the issue description without sending the full text.
-Reduces token usage for AI agents editing long descriptions.
-
-**Search/Replace format**:
-```
-<<<<<<< SEARCH
-text to find
-=======
-replacement text
->>>>>>> REPLACE
-```
-
-**Options**:
-- `dry_run: true` — preview changes without updating
-- `create_note: true` — add a comment summarizing the change after update
-- `allow_multiple: true` — allow multiple matches to all be replaced (search_replace only)
-
-**Error handling**:
-- Search text not found → fails with clear message
-- Multiple matches (without `allow_multiple`) → fails with count
-- Patch results in identical description → fails (no-op)
-- Unified diff doesn't match → fails
-
-## Delete
-
-```
-delete_issue   -> permanently delete (destructive, cannot be undone)
-```
-
-## Issue Links
-
-Link related issues:
-
-```
-create_issue_link
-  project_id: "my-group/my-project"
-  issue_iid: 10
-  target_project_id: "my-group/other-project"
-  target_issue_iid: 20
-  link_type: "relates_to"  # or "blocks", "is_blocked_by"
-```
-
-```
-list_issue_links   -> list all linked issues
-get_issue_link     -> get specific link details
-delete_issue_link  -> remove a link
-```
-
-## Discussions & Notes
-
-Add comments:
-
-```
-create_issue_note
-  project_id: "my-group/my-project"
-  issue_iid: 10
-  body: "Confirmed, this is a regression"
-  discussion_id: "abc123"   # optional: reply to existing thread
-```
-
-```
-update_issue_note         -> edit a comment
-list_issue_discussions    -> list all discussion threads
-```
-
-### Emoji reactions
-
-```
-list_issue_emoji_reactions       -> list reactions on an issue
-create_issue_emoji_reaction      -> add reaction to an issue
-delete_issue_emoji_reaction      -> remove reaction from an issue
-list_issue_note_emoji_reactions  -> list reactions on an issue note or thread reply
-create_issue_note_emoji_reaction -> add reaction to an issue note or thread reply
-delete_issue_note_emoji_reaction -> remove reaction from an issue note or thread reply
-```
-
-Generic note creation (works for both issues and MRs):
-
-```
-create_note
-  project_id: "my-group/my-project"
-  noteable_type: "Issue"    # or "MergeRequest"
-  noteable_iid: 10
-  body: "Note content"
-```

package/framework/skills/gitlab-mcp/references/merge-requests.md

@@ -1,120 +0,0 @@
-# Merge Request Workflow
-
-## Create
-
-```
-create_merge_request
-  project_id: "my-group/my-project"
-  title: "Add user authentication"
-  source_branch: "feature/auth"
-  target_branch: "main"
-  description: "Implements OAuth2 login flow"
-  assignee_id: 123
-  labels: "feature,auth"
-```
-
-## Read & Track
-
-```
-get_merge_request           -> full MR details (by IID or branch name)
-list_merge_requests         -> list with filters (state, labels, author, etc.)
-  - without project_id: current user's MRs across all projects
-  - with project_id: MRs in that project
-get_merge_request_conflicts -> check for merge conflicts
-list_merge_request_pipelines -> list pipelines attached to an MR
-```
-
-## Update
-
-```
-update_merge_request
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-  title: "Updated title"
-  state_event: "close"  # or "reopen"
-  assignee_ids: [123, 456]
-  labels: "feature,reviewed"
-```
-
-## Review & Approve
-
-See [code-review.md](code-review.md) for the full diff review workflow.
-
-```
-approve_merge_request       -> approve
-unapprove_merge_request     -> retract approval
-get_merge_request_approval_state -> check who approved, rules status
-```
-
-## Merge
-
-```
-merge_merge_request
-  project_id: "my-group/my-project"
-  mergeRequestIid: 42
-  should_remove_source_branch: true
-  squash: true
-  merge_when_pipeline_succeeds: true
-```
-
-**Warning**: `merge_merge_request` is destructive - cannot be undone.
-
-## Discussion Management
-
-### Threads (inline code comments)
-
-```
-create_merge_request_thread     -> new thread on a diff line
-resolve_merge_request_thread    -> mark thread resolved
-```
-
-### Notes (general comments)
-
-```
-create_merge_request_note       -> add comment
-get_merge_request_notes         -> list all comments
-update_merge_request_note       -> edit comment
-delete_merge_request_note       -> remove comment
-```
-
-### Discussion notes (replies in threads)
-
-```
-mr_discussions                         -> list all discussions
-create_merge_request_discussion_note   -> reply to thread
-update_merge_request_discussion_note   -> edit reply
-delete_merge_request_discussion_note   -> remove reply
-```
-
-### Draft notes (pending review)
-
-```
-create_draft_note          -> create pending comment
-list_draft_notes           -> see all drafts
-update_draft_note          -> edit before publishing
-delete_draft_note          -> discard
-publish_draft_note         -> publish single draft
-bulk_publish_draft_notes   -> publish all drafts at once
-```
-
-### Emoji reactions
-
-```
-list_merge_request_emoji_reactions       -> list reactions on an MR
-create_merge_request_emoji_reaction      -> add reaction to an MR
-delete_merge_request_emoji_reaction      -> remove reaction from an MR
-list_merge_request_note_emoji_reactions  -> list reactions on an MR note or thread reply
-create_merge_request_note_emoji_reaction -> add reaction to an MR note or thread reply
-delete_merge_request_note_emoji_reaction -> remove reaction from an MR note or thread reply
-```
-
-## Branch Comparison
-
-Compare without an existing MR:
-
-```
-get_branch_diffs
-  project_id: "my-group/my-project"
-  from: "main"
-  to: "feature/auth"
-```

package/framework/skills/gitlab-mcp/references/pipelines.md

@@ -1,67 +0,0 @@
-# Pipeline Operations
-
-> **Opt-in toolset**: Enable with `USE_PIPELINE=true` or `GITLAB_TOOLSETS=pipelines`
-
-## List & Inspect
-
-```
-list_pipelines             -> list pipelines with filters (status, ref, source)
-get_pipeline               -> pipeline details (status, duration, coverage)
-list_pipeline_jobs         -> all jobs in a pipeline
-list_pipeline_trigger_jobs -> trigger/bridge jobs (downstream pipelines)
-get_pipeline_job           -> single job details
-get_pipeline_job_output    -> job log output (supports pagination for large logs)
-```
-
-## Create & Control
-
-```
-create_pipeline            -> trigger new pipeline for a branch/tag
-  project_id: "my-group/my-project"
-  ref: "main"
-  variables: [{ key: "DEPLOY_ENV", value: "staging" }]
-```
-
-```
-retry_pipeline             -> retry all failed jobs in a pipeline
-cancel_pipeline            -> cancel running pipeline
-play_pipeline_job          -> run a manual job
-retry_pipeline_job         -> retry a single failed job
-cancel_pipeline_job        -> cancel a single running job
-```
-
-## Artifacts
-
-```
-list_job_artifacts         -> list files in a job's artifact archive
-get_job_artifact_file      -> get content of a single artifact file
-download_job_artifacts     -> download full artifact archive (zip) to local_path
-```
-
-## Deployments & Environments
-
-```
-list_deployments           -> list deployments with filters
-get_deployment             -> deployment details
-list_environments          -> list project environments
-get_environment            -> environment details
-```
-
-## Common Patterns
-
-### Check why a pipeline failed
-
-1. `list_pipelines` with `status: "failed"` -> get pipeline ID
-2. `list_pipeline_jobs` -> find failed job(s)
-3. `get_pipeline_job_output` -> read error logs
-
-### Retry failed pipeline
-
-1. `retry_pipeline` -> retries all failed jobs
-   OR
-2. `retry_pipeline_job` -> retry specific job only
-
-### Download test results
-
-1. `list_job_artifacts` -> find the test report file path
-2. `get_job_artifact_file` -> read the report content

package/framework/skills/gitlab-mcp/references/search.md

@@ -1,17 +0,0 @@
-# Code Search
-
-> **Opt-in toolset**: Enable with `GITLAB_TOOLSETS=search`
-
-Search requires GitLab advanced search or exact code search/Zoekt support on the target instance.
-
-## Scope
-
-```
-search_code          -> search code across all accessible projects
-search_project_code  -> search within one project
-search_group_code    -> search within one group
-```
-
-## Pattern
-
-Use the narrowest scope that can answer the question. Prefer `search_project_code` when the project is known, then broaden to group or instance-wide search only when needed.

package/framework/skills/gitlab-mcp/references/webhooks.md

@@ -1,32 +0,0 @@
-# Webhook Operations
-
-> **Opt-in toolset**: Enable with `GITLAB_TOOLSETS=webhooks`
-
-## List Webhooks
-
-Provide either `project_id` or `group_id`.
-
-```
-list_webhooks
-  project_id: "my-group/my-project"
-```
-
-## Inspect Recent Events
-
-GitLab exposes recent webhook events for the past 7 days.
-
-```
-list_webhook_events
-  project_id: "my-group/my-project"
-  webhook_id: 123
-  summary: true
-```
-
-Fetch full event details only after narrowing to the event ID.
-
-```
-get_webhook_event
-  project_id: "my-group/my-project"
-  webhook_id: 123
-  event_id: 456
-```

package/framework/skills/gitlab-mcp/references/work-items.md

@@ -1,50 +0,0 @@
-# Work Item Operations
-
-> **Opt-in toolset**: Enable with `GITLAB_TOOLSETS=workitems`
-
-Work items are GraphQL-based and cover issues, tasks, incidents, epics, objectives, requirements, tickets, and related hierarchy/status fields. Some status and custom field features require GitLab Premium/Ultimate.
-
-## Read
-
-```
-list_work_items              -> list work items with filters
-get_work_item                -> full details with status, hierarchy, type, labels, assignees, widgets
-list_work_item_notes         -> notes and discussions on a work item
-list_work_item_statuses      -> available statuses for a work item type
-list_custom_field_definitions -> custom field definitions for a work item type
-```
-
-## Create & Update
-
-```
-create_work_item
-  project_id: "my-group/my-project"
-  title: "Investigate checkout failure"
-  work_item_type: "issue"
-  description: "Steps to reproduce..."
-```
-
-```
-update_work_item             -> title, description, labels, assignees, state, parent, children, health, dates, custom fields
-convert_work_item_type       -> convert issue/task/incident/etc.
-move_work_item               -> move a work item to another project
-create_work_item_note        -> add a note, threaded reply, or internal note
-```
-
-## Emoji Reactions
-
-```
-list_work_item_emoji_reactions       -> list reactions on a work item
-create_work_item_emoji_reaction      -> add reaction to a work item
-delete_work_item_emoji_reaction      -> remove reaction from a work item
-list_work_item_note_emoji_reactions  -> list reactions on a work item note or thread reply
-create_work_item_note_emoji_reaction -> add reaction to a work item note or thread reply
-delete_work_item_note_emoji_reaction -> remove reaction from a work item note or thread reply
-```
-
-## Incident Timeline
-
-```
-get_timeline_events     -> list timeline events for an incident
-create_timeline_event   -> create an incident timeline event
-```

package/framework/skills/great-interface/SKILL.md

@@ -1,43 +0,0 @@
----
-name: great-interface
-description: >-
-  Build, explain, review, and refine product interfaces across accessibility, layout,
-  writing, typography, color, UI polish, holistic review, change review, and design variants.
-  Use when creating frontend interfaces, reviewing interface quality, explaining how an
-  interface works, or comparing UI directions.
----
-
-# Great Interface
-
-Use the domain references below as the sources of truth. Load the smallest set that covers
-the request, except for a holistic review, which loads every applicable review domain.
-
-## Build and refine
-
-- Accessibility: [better-accessibility.md](references/better-accessibility.md)
-- Layout: [better-layout.md](references/better-layout.md)
-- Writing: [better-writing.md](references/better-writing.md)
-- Typography: [better-typography.md](references/better-typography.md)
-- Colors: [better-colors.md](references/better-colors.md)
-- UI polish and motion: [better-ui.md](references/better-ui.md)
-
-## Review
-
-- Holistic screen or flow review: [better-interface.md](references/better-interface.md)
-- Change, branch, or pull request review: [interface-review.md](references/interface-review.md)
-
-## Explore alternatives
-
-- Explain how an interface or effect was built: [explain-interface.md](references/explain-interface.md)
-- Build and compare multiple UI directions: [variant.md](references/variant.md)
-
-## Ownership
-
-Do not duplicate rules across domains. Accessibility owns keyboard support, focus, ARIA,
-semantic structure, hit areas, announcements, and reduced motion. Layout owns grouping,
-spacing, responsive structure, and spatial RTL. Writing owns interface copy. Typography owns
-how text renders and wraps. Colors owns palette systems and color measurement. UI owns
-surfaces, icons, and visual motion. The review references own orchestration and reporting.
-
-When domains overlap, report or apply the rule in the owning domain and mention secondary
-effects only where useful.

package/framework/skills/great-interface/references/animations.md

@@ -1,205 +0,0 @@
-# Animations
-
-Interruptible transitions, press feedback and the restraint that decides whether to animate at all. Staged entrances and exits live in [enter-exit.md](enter-exit.md); icon swaps in [icon-transitions.md](icon-transitions.md).
-
-## Interruptible animations
-
-Users change intent mid-interaction. Animations that cannot be interrupted make the interface feel broken.
-
-### CSS transitions vs. keyframes
-
-| | CSS Transitions | CSS Keyframe Animations |
-| --- | --- | --- |
-| **Behavior** | Interpolate toward latest state | Run on a fixed timeline |
-| **Interruptible** | Yes, retargets mid-animation | No, restarts from beginning |
-| **Use for** | Interactive state changes (hover, toggle, open/close) | Staged sequences that run once (enter animations, loading) |
-| **Duration** | Fixed; retargets the value mid-flight, not the timeline | Fixed timeline, restarts from the beginning |
-
-```css
-/* Good: interruptible transition for a toggle */
-.drawer {
-  transform: translateX(-100%);
-  transition: transform 200ms ease-out;
-}
-.drawer.open {
-  transform: translateX(0);
-}
-
-/* Clicking again mid-animation smoothly reverses, no jank */
-```
-
-```css
-/* Bad: keyframe animation for interactive element */
-.drawer.open {
-  animation: slideIn 200ms ease-out forwards;
-}
-
-/* Closing mid-animation snaps or restarts, feels broken */
-```
-
-Prefer CSS transitions for interactive elements. Reserve keyframes for one-shot sequences.
-
-## Scale on press
-
-A subtle scale-down on click gives buttons tactile feedback. Always `scale(0.96)`, never below `0.95`, which feels exaggerated. Use CSS transitions so a release mid-press returns smoothly.
-
-Not every button needs it. Add a `static` prop that disables the scale where the motion would distract.
-
-### CSS example
-
-```css
-.button {
-  transition-property: scale;
-  transition-duration: 150ms;
-  transition-timing-function: ease-out;
-}
-
-.button:active {
-  scale: 0.96;
-}
-```
-
-### Tailwind example
-
-```tsx
-<button className="transition-transform duration-150 ease-out active:scale-[0.96]">
-  Click me
-</button>
-```
-
-### Motion example
-
-```tsx
-<motion.button whileTap={{ scale: 0.96 }}>
-  Click me
-</motion.button>
-```
-
-### Static prop pattern
-
-Extract the scale class into a variable and apply it conditionally on a `static` prop:
-
-```tsx
-const tapScale = "active:not-disabled:scale-[0.96]";
-
-function Button({ static: isStatic, className, children, ...props }) {
-  return (
-    <button
-      className={cn(
-        "transition-transform duration-150 ease-out",
-        !isStatic && tapScale,
-        className,
-      )}
-      {...props}
-    >
-      {children}
-    </button>
-  );
-}
-
-// Usage
-<Button>Click me</Button>           {/* scales on press */}
-<Button static>Submit</Button>       {/* no scale */}
-```
-
-## Skip animation on page load
-
-Use `initial={false}` on `AnimatePresence` to stop enter animations firing on first render. An element already in its default state animates on later state changes, not on page load.
-
-### When it works
-
-```tsx
-// Good: icon doesn't animate in on mount, only on state change
-<AnimatePresence initial={false} mode="popLayout">
-  <motion.span
-    key={isActive ? "active" : "inactive"}
-    initial={{ opacity: 0, scale: 0.25, filter: "blur(4px)" }}
-    animate={{ opacity: 1, scale: 1, filter: "blur(0px)" }}
-    exit={{ opacity: 0, scale: 0.25, filter: "blur(4px)" }}
-  >
-    <Icon />
-  </motion.span>
-</AnimatePresence>
-```
-
-Works well for icon swaps, toggles, tabs and segmented controls, anything with a default state on page load.
-
-### When it breaks
-
-Never use `initial={false}` where the component relies on its `initial` prop for a first-time enter animation, such as a staggered page hero or a loading state. Removing it skips the entire entrance.
-
-```tsx
-// Bad: initial={false} would skip the staggered page enter entirely
-<AnimatePresence initial={false}>
-  <motion.div initial="hidden" animate="visible" variants={...}>
-    ...
-  </motion.div>
-</AnimatePresence>
-```
-
-Verify the component still looks right on a full page refresh before applying this.
-
-## Suppress transitions on theme switch
-
-Flipping the theme changes `color`, `background-color`, `border-color` and `box-shadow` on nearly every element at once. Everything carrying a transition on those properties animates together, so the switch reads as a slow smear rather than an instant change. Disable transitions for the swap and restore them right after.
-
-Inject a stylesheet that turns off every transition, force a reflow so the new colors commit while it still applies, then drop it on the next frame:
-
-```tsx
-"use client";
-
-import { useEffect } from "react";
-
-export function DisableThemeTransitions() {
-  useEffect(() => {
-    const mql = window.matchMedia("(prefers-color-scheme: dark)");
-
-    const handleChange = () => {
-      const style = document.createElement("style");
-      style.append(
-        document.createTextNode(
-          "*,*::before,*::after{transition:none !important}"
-        )
-      );
-      document.head.append(style);
-
-      const _flushReflow = document.body.offsetHeight;
-
-      requestAnimationFrame(() => {
-        requestAnimationFrame(() => style.remove());
-      });
-    };
-
-    mql.addEventListener("change", handleChange);
-    return () => mql.removeEventListener("change", handleChange);
-  }, []);
-
-  return null;
-}
-```
-
-`document.body.offsetHeight` is read for its side effect, forcing a synchronous style flush so the new theme resolves while the override is still in the document and no transition starts. The nested `requestAnimationFrame` removes the override only after that paint, restoring transitions before the next interaction.
-
-That covers the OS-level change. An in-app toggle needs the same treatment around its own flip: apply the override, change the theme, flush, remove. `next-themes` ships this as `disableTransitionOnChange`.
-
-## Motion restraint
-
-Motion is a budget, not a garnish. Three rules decide whether an animation belongs at all:
-
-- **Give high-frequency interactions instant feedback instead of animation.** Every keystroke, every list-row hover, every tab switch in a work tool. Reserve expressive motion for infrequent moments (first load of a view, success states, empty states); high-frequency interactions get instant feedback or the subtlest possible transition (`opacity`/`background-color` at ≤150ms).
-- **Motion is never the only feedback channel.** Every state change an animation communicates stays visible when it doesn't run: a color change, an icon swap, a label. Users with reduced motion enabled and anyone who blinked still need to see what happened.
-- **Brief and precise beats prominent.** Where a shorter, smaller animation says the same thing, use it. When in doubt cut the duration, not the clarity.
-
-```css
-/* Good: high-frequency hover gets a minimal transition */
-.row:hover {
-  background-color: var(--surface-hover);
-  transition: background-color 100ms ease-out;
-}
-
-/* Bad: every hover replays a full entrance */
-.row:hover .row-icon {
-  animation: bounceIn 500ms;
-}
-```
-