@mohammadhprp/system-prompt 0.12.0 → 0.12.2

package/framework/mcps/gitlab-mcp/troubleshooting.md

@@ -1,116 +0,0 @@
-# GitLab MCP Troubleshooting
-
-## Server won't start
-
-**Problem**
-
-The AI client reports that `gitlab` failed to start.
-
-**Cause**
-
-The client cannot run `zereight-mcp-gitlab`, Node.js is not installed, or the npm package is not installed globally.
-
-**Solution**
-
-- Run `zereight-mcp-gitlab` manually to verify the server starts.
-- Check Node.js is installed: `node --version` (requires >= 18).
-- Run `npm install -g @zereight/mcp-gitlab` to install globally.
-- If no global install, use `command: "npx"` with `args: ["-y", "@zereight/mcp-gitlab"]` instead.
-
-## Authentication errors
-
-**Problem**
-
-The server starts but returns authentication errors on tool calls.
-
-**Cause**
-
-The Personal Access Token is missing, expired, or has insufficient scopes.
-
-**Solution**
-
-- Verify the token is set in `GITLAB_PERSONAL_ACCESS_TOKEN` or passed via `--token`.
-- Confirm the token has the required scopes (`api` for full access, `read_api` for read-only).
-- Generate a new token in GitLab: **Settings → Access Tokens → Personal Access Tokens**.
-- Confirm the API URL is correct: `https://gitlab.com/api/v4` (SaaS) or `https://your-instance/api/v4` (self-hosted).
-
-## Configuration errors
-
-**Problem**
-
-The MCP server is not listed, or the client ignores the config file.
-
-**Cause**
-
-The config file is in the wrong location, the JSON is invalid, or the client expects a different configuration wrapper.
-
-**Solution**
-
-- Validate the JSON with `python -m json.tool <file>` or another JSON parser.
-- Confirm the client-specific config location in the client's documentation.
-- Keep the server name as `gitlab`.
-- Ensure environment variables are set correctly in the config.
-
-## Permission errors
-
-**Problem**
-
-Tools return 403 Forbidden or insufficient permissions.
-
-**Cause**
-
-The authenticated user does not have the required GitLab project or group permissions.
-
-**Solution**
-
-- Verify the user has at least Developer role in the target project or group.
-- Check if the project is in a subgroup that inherits different permissions.
-- Use `list_projects` to confirm which projects the token can access.
-
-## Rate limiting
-
-**Problem**
-
-Tools return 429 Too Many Requests errors.
-
-**Cause**
-
-GitLab API rate limits have been exceeded.
-
-**Solution**
-
-- Reduce the frequency of tool calls.
-- For self-hosted GitLab, check `gitlab.rb` rate limit settings.
-- Wait for the rate limit window to reset before retrying.
-
-## Version mismatch
-
-**Problem**
-
-Some tools are missing or behave differently than documented.
-
-**Cause**
-
-The installed npm package version is outdated.
-
-**Solution**
-
-- Update to the latest version: `npm update -g @zereight/mcp-gitlab`.
-- Check the installed version: `npm list -g @zereight/mcp-gitlab`.
-- Refer to the [CHANGELOG](https://github.com/zereight/gitlab-mcp/blob/main/CHANGELOG.md) for breaking changes.
-
-## Read-only mode blocking writes
-
-**Problem**
-
-Write tools return errors when `GITLAB_PERMISSION_MODE=readonly`.
-
-**Cause**
-
-Read-only mode explicitly blocks all create, update, and delete operations.
-
-**Solution**
-
-- Set `GITLAB_PERMISSION_MODE=modify` to allow updates while blocking deletes.
-- Set `GITLAB_PERMISSION_MODE=full` for unrestricted access.
-- Use `GITLAB_TOOLS` allow-list to enable specific write tools in read-only mode.

package/framework/mcps/jira-mcp/README.md

@@ -1,52 +0,0 @@
-# Jira MCP
-
-## Overview
-
-Jira MCP is a Model Context Protocol (MCP) server for interacting with self-hosted Jira instances using Personal Access Token (PAT) authentication. It provides tools for creating, reading, updating, and deleting issues, searching with JQL, managing comments and assignments, and inspecting projects.
-
-Official source:
-
-- [GitHub: edrich13/mcp-jira-server](https://github.com/edrich13/mcp-jira-server)
-
-## Features
-
-- Personal Access Token authentication for self-hosted Jira.
-- Create, read, update, and delete Jira issues.
-- Search issues using JQL (Jira Query Language).
-- Add and view comments.
-- Manage issue assignments.
-- List projects and issue types.
-- Transition issues between statuses.
-- Get current user information.
-
-## Supported AI Clients
-
-Jira MCP works with any MCP-compatible AI client. The server is started via `npx` and communicates over stdio.
-
-- OpenCode
-
-## When to Use
-
-Use Jira MCP when an AI coding agent needs to interact with a self-hosted Jira instance.
-
-Good fits:
-
-- Creating and updating Jira issues from an AI agent.
-- Searching for issues with JQL queries.
-- Adding comments and managing issue assignments.
-- Inspecting project metadata and issue types.
-- Tracking work and status transitions.
-
-Avoid using it with Jira Cloud (SaaS) — this server is designed for self-hosted Jira instances only.
-
-## Requirements
-
-- Node.js 18 or higher available on `PATH`.
-- A self-hosted Jira instance (e.g., `https://jira.domain.com`).
-- A Jira Personal Access Token with appropriate permissions.
-
-## Related Skills
-
-Relevant skills in this repository:
-
-- [`backend-best-practices`](../../skills/backend-best-practices/SKILL.md): backend best practices for debugging and testing.

package/framework/mcps/jira-mcp/capabilities.md

@@ -1,79 +0,0 @@
-# Jira MCP Capabilities
-
-## What It Can Do
-
-12 tools for interacting with self-hosted Jira instances.
-
-### Issues
-
-| Tool | Description |
-| --- | --- |
-| `jira_get_issue` | Get details of a specific issue by key (e.g. "PROJ-123") |
-| `jira_search_issues` | Search for issues using JQL with optional max results |
-| `jira_create_issue` | Create a new issue with project, summary, type, description, priority, assignee, labels, components, and custom fields |
-| `jira_update_issue` | Update an existing issue — summary, description, assignee, priority, labels, status, and custom fields |
-| `jira_delete_issue` | Delete an issue permanently |
-| `jira_assign_issue` | Assign an issue to a user |
-
-### Comments
-
-| Tool | Description |
-| --- | --- |
-| `jira_add_comment` | Add a comment to an issue |
-| `jira_get_comments` | Get all comments from an issue |
-
-### Projects
-
-| Tool | Description |
-| --- | --- |
-| `jira_get_projects` | List all available projects |
-| `jira_get_project` | Get details of a specific project |
-| `jira_get_issue_types` | Get available issue types for a project |
-
-### User
-
-| Tool | Description |
-| --- | --- |
-| `jira_get_current_user` | Get information about the currently authenticated user |
-
-## What It Cannot Do
-
-- It does not work with Jira Cloud (SaaS) — designed for self-hosted instances only.
-- It cannot authenticate with OAuth, API tokens, or cookie-based auth — PAT only.
-- It cannot create, update, or delete Jira projects.
-- It cannot manage Jira users, groups, or permissions.
-- It cannot access Jira boards, sprints, or agile features.
-- It cannot attach files to issues.
-- It cannot operate without a valid PAT and accessible Jira instance.
-
-## Best Practices
-
-- Never commit your PAT to version control. Use environment variables or client config files with restricted permissions.
-- Use tokens with minimal required permissions.
-- Set expiration dates for tokens and rotate them regularly.
-- Use `jira_get_issue_types` before creating issues to confirm valid types for the project.
-- Use `jira_get_current_user` first to verify authentication is working.
-- Use JQL with specific project keys to scope searches and reduce response size.
-- For Jira instances behind SSO proxies, set `JIRA_USER_AGENT` to a whitelisted value.
-
-## Common Workflows
-
-### Find and update issues
-
-1. Call `jira_search_issues` with a JQL query to find relevant issues.
-2. Call `jira_get_issue` on a specific key to read full details.
-3. Call `jira_update_issue` to change status, assignee, or priority.
-4. Call `jira_add_comment` to leave a note about the change.
-
-### Create a new issue
-
-1. Call `jira_get_projects` to list available projects.
-2. Call `jira_get_issue_types` for the target project.
-3. Call `jira_create_issue` with project key, summary, issue type, and optional fields.
-4. Call `jira_assign_issue` to assign it to a team member.
-
-### Track work progress
-
-1. Call `jira_search_issues` with `assignee = currentUser() AND status != Done`.
-2. Call `jira_get_issue` on each key to review details.
-3. Call `jira_update_issue` to transition statuses as work progresses.

package/framework/mcps/jira-mcp/configs/.env.example

@@ -1,2 +0,0 @@
-JIRA_BASE_URL=
-JIRA_PAT=

package/framework/mcps/jira-mcp/configs/opencode.json

@@ -1,13 +0,0 @@
-{
-  "mcp": {
-    "jira": {
-      "type": "local",
-      "enabled": true,
-      "command": ["npx", "-y", "mcp-jira-server"],
-      "environment": {
-        "JIRA_BASE_URL": "{env:JIRA_BASE_URL}",
-        "JIRA_PAT": "{env:JIRA_PAT}"
-      }
-    }
-  }
-}

package/framework/mcps/jira-mcp/install.md

@@ -1,94 +0,0 @@
-# Jira MCP Installation
-
-## Requirements
-
-- Node.js 18 or higher available on `PATH`.
-- A self-hosted Jira instance.
-- A Jira Personal Access Token.
-- An MCP-compatible AI client.
-
-## Creating a Personal Access Token
-
-1. Log in to your self-hosted Jira instance.
-2. Click your profile icon → **Profile** or **Account Settings**.
-3. Navigate to **Personal Access Tokens** or **Security**.
-4. Click **Create token**, give it a name, set an expiration date, and copy the token immediately.
-
-## Installation
-
-The server can be used directly with `npx` — no build step required.
-
-```bash
-npx -y mcp-jira-server
-```
-
-Or install globally:
-
-```bash
-npm install -g mcp-jira-server
-```
-
-## Configuration
-
-| Field | Value |
-| --- | --- |
-| Server name | `jira` |
-| Command | `npx` (or `mcp-jira-server` if installed globally) |
-| Args | `-y`, `mcp-jira-server` |
-| Env | `JIRA_BASE_URL`, `JIRA_PAT` |
-
-### Config file examples
-
-Use the examples in [`configs/`](./configs/) as client-specific starting points:
-
-| Client | Example | Typical location |
-| --- | --- | --- |
-| OpenCode | [`configs/opencode.json`](./configs/opencode.json) | OpenCode MCP configuration. |
-
-### OpenCode
-
-Copy [`configs/opencode.json`](./configs/opencode.json) into your OpenCode project root or user config directory, replace the placeholder URL and token, and restart the OpenCode agent.
-
-## Verification
-
-Run the MCP server command directly:
-
-```bash
-npx -y mcp-jira-server
-```
-
-Then verify from your AI client:
-
-- The `jira` MCP server is listed.
-- The server starts without errors.
-- Tools are visible to the agent.
-
-Recommended first prompt:
-
-```
-Get my current Jira user information
-```
-
-## Updating
-
-```bash
-npx -y mcp-jira-server@latest
-```
-
-Or update global install:
-
-```bash
-npm update -g mcp-jira-server
-```
-
-## Uninstalling
-
-1. Remove the MCP entry from AI client configuration files.
-2. Uninstall the package: `npm uninstall -g mcp-jira-server`.
-
-## Common Issues
-
-- **Server does not start**: run `npx -y mcp-jira-server` manually. Ensure Node.js >= 18 is installed.
-- **Authentication errors**: verify the PAT is valid and not expired. Confirm `JIRA_BASE_URL` has no trailing slash.
-- **Connection refused**: check if the Jira instance is accessible and the URL is correct.
-- **API requests redirect to SSO login**: your Jira may be behind a reverse proxy. Set `JIRA_USER_AGENT` to a whitelisted User-Agent string.

package/framework/mcps/jira-mcp/troubleshooting.md

@@ -1,113 +0,0 @@
-# Jira MCP Troubleshooting
-
-## Server won't start
-
-**Problem**
-
-The AI client reports that `jira` failed to start.
-
-**Cause**
-
-The client cannot run `npx`, Node.js is not installed, or the npm package is unavailable.
-
-**Solution**
-
-- Run `npx -y mcp-jira-server` manually to verify the server starts.
-- Check Node.js is installed: `node --version` (requires >= 18).
-- Check network access if the package has not been cached locally.
-- Ensure the config file contains the correct command and args.
-
-## Authentication errors
-
-**Problem**
-
-The server starts but returns authentication errors on tool calls.
-
-**Cause**
-
-The Personal Access Token is missing, expired, or has insufficient permissions.
-
-**Solution**
-
-- Verify `JIRA_PAT` is set correctly in the environment.
-- Confirm the token has not expired.
-- Generate a new token in Jira if needed.
-- Verify `JIRA_BASE_URL` is correct and has no trailing slash.
-
-## Connection refused
-
-**Problem**
-
-Tools return connection errors.
-
-**Cause**
-
-The Jira instance is not accessible from the current machine.
-
-**Solution**
-
-- Verify the Jira URL is reachable: `curl https://jira.domain.com`.
-- Check network connectivity and firewall rules.
-- Confirm the URL format: `https://jira.domain.com` (no trailing slash).
-
-## Configuration errors
-
-**Problem**
-
-The MCP server is not listed, or the client ignores the config file.
-
-**Cause**
-
-The config file is in the wrong location, the JSON is invalid, or the client expects a different configuration wrapper.
-
-**Solution**
-
-- Validate the JSON with `python -m json.tool <file>` or another JSON parser.
-- Confirm the client-specific config location in the client's documentation.
-- Keep the server name as `jira`.
-- Ensure environment variables are set correctly in the config.
-
-## API requests redirect to SSO login
-
-**Problem**
-
-API requests return HTML login pages instead of JSON responses despite a valid PAT.
-
-**Cause**
-
-The Jira instance is behind a reverse proxy (oauth2-proxy, nginx, etc.) that filters requests by User-Agent and redirects API clients to SSO login.
-
-**Solution**
-
-- Set the `JIRA_USER_AGENT` environment variable to a whitelisted User-Agent string.
-- Contact your system administrator to get the allowed User-Agent value.
-
-## "Issue type not found" errors
-
-**Problem**
-
-Creating an issue fails with "issue type not found".
-
-**Cause**
-
-The issue type name does not exist in the target project.
-
-**Solution**
-
-- Call `jira_get_issue_types` with the project key to list valid types.
-- Use an exact match from the returned list.
-
-## "Cannot find module" errors
-
-**Problem**
-
-The server fails with module resolution errors when using a source build.
-
-**Cause**
-
-Dependencies are not installed or the project is not built.
-
-**Solution**
-
-- Run `npm install` and `npm run build` in the project directory.
-- Use the `npx` command instead of a local build.

package/framework/skills/brand-guidelines/LICENSE.txt

@@ -1,202 +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
-
-   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 Anthropic, PBC.
-
-   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.