@mohammadhprp/system-prompt 0.12.0 → 0.12.2

package/framework/skills/jira-cli/references/commands-detailed.md

@@ -0,0 +1,268 @@
+# Jira CLI Detailed Command Reference
+
+Complete flag and option reference for the `jira` CLI. All list flags are POSIX-compliant and combine freely.
+
+## Table of Contents
+
+- [Global Options](#global-options)
+- [Issue List](#issue-list)
+- [Issue Create](#issue-create)
+- [Issue Edit](#issue-edit)
+- [Issue Assign](#issue-assign)
+- [Issue Move (Transition)](#issue-move-transition)
+- [Issue View](#issue-view)
+- [Issue Link / Unlink](#issue-link--unlink)
+- [Issue Clone](#issue-clone)
+- [Issue Delete](#issue-delete)
+- [Issue Comment](#issue-comment)
+- [Issue Worklog](#issue-worklog)
+- [Epic](#epic)
+- [Sprint](#sprint)
+- [Releases, Projects, Boards, Other](#releases-projects-boards-other)
+
+## Global Options
+
+```bash
+jira --version              # Print version
+jira init                   # Interactive config wizard (run once)
+jira me                     # Print the current logged-in user
+jira open [KEY-1]           # Open project or issue in browser
+jira completion --help      # Shell completion setup (Bash/Zsh)
+```
+
+- `-c, --config <file>` — use an alternative config file (or `JIRA_CONFIG_FILE` env var)
+- `-p, --project <KEY>` — override the configured project on list/create commands
+
+## Issue List
+
+```bash
+jira issue list [flags]
+```
+
+| Flag | Description |
+| --- | --- |
+| `-a, --assignee <user>` | Filter by assignee; `x` = unassigned; use `$(jira me)` for yourself |
+| `-r, --reporter <user>` | Filter by reporter |
+| `-s, --status <status>` | Filter by status; prefix with `~` for "not" (e.g. `-s~Done`) |
+| `-y, --priority <priority>` | Filter by priority (e.g. `High`) |
+| `-t, --type <type>` | Filter by issue type (e.g. `Bug`) |
+| `-l, --label <label>` | Filter by label; repeatable |
+| `-w, --watching` | Issues you are watching |
+| `-R, --resolution <value>` | Filter by resolution (e.g. `"Won't do"`, `Fixed`) |
+| `--history` | Issues you recently interacted with |
+| `--created <value>` | Relative window: `-7d`, `-1h`, `week`, `month` |
+| `--updated <value>` | Same value format as `--created` |
+| `--created-before <value>` | e.g. `-24w` |
+| `--updated-before <value>` | Same format |
+| `-q, --jql <query>` | Raw JQL within the project context |
+| `--order-by <field>` | Order by field (e.g. `rank`, `created`) |
+| `--reverse` | Reverse sort order |
+| `--plain` | Non-interactive table output (use in scripts) |
+| `--table` | Table view for explorer commands (epic/sprint) |
+| `--raw` | Raw JSON output |
+| `--csv` | CSV output |
+| `--columns <list>` | Comma-separated columns to display |
+| `--no-headers` | Omit the header row (for `awk`/parsing) |
+
+Examples:
+
+```bash
+# Assigned to me, high priority, open, created this month
+jira issue list -a$(jira me) -yHigh -sopen --created month
+
+# Unassigned issues created this week
+jira issue list -ax --created week
+
+# Not Done, created before 24 weeks ago, assigned to someone
+jira issue list -s~Done --created-before -24w -a~x
+
+# Issues I reported this week, oldest first
+jira issue list -r$(jira me) --created week --reverse
+```
+
+## Issue Create
+
+```bash
+jira issue create [flags]
+```
+
+| Flag | Description |
+| --- | --- |
+| `-t, --type <type>` | Issue type (required) |
+| `-s, --summary <text>` | Summary/title (required) |
+| `-b, --body <text>` | Description; supports GitHub- and Jira-flavored Markdown |
+| `-y, --priority <value>` | Priority |
+| `-l, --label <label>` | Label; repeatable |
+| `-P, --parent <KEY>` | Attach to an epic (or parent in next-gen projects) |
+| `--fix-version <value>` | Fix version |
+| `--custom "key=value"` | Set custom fields; repeatable |
+| `--template <file\|->` | Load description from file or stdin |
+| `--no-input` | Skip all interactive prompts |
+
+```bash
+# Minimal non-interactive creation
+jira issue create -tTask -s"Summary" -b"Description" --no-input
+
+# Description piped from stdin
+echo "Description" | jira issue create -s"Summary" -tTask --no-input
+
+# Story attached to EPIC-42 with labels and fix version
+jira issue create -tStory -s"Summary" -PEPIC-42 -lbackend --fix-version v2.0 --no-input
+```
+
+## Issue Edit
+
+```bash
+jira issue edit ISSUE-1 [flags]
+```
+
+Accepts the same field flags as create (`-s`, `-b`, `-y`, `-l`, `-C` component, `--fix-version`). Prefix a value with `-` to remove it:
+
+```bash
+# Remove label p2, add p1; swap fix version v1.0 for v2.0
+jira issue edit ISSUE-1 --label -p2 --label p1 --fix-version -v1.0 --fix-version v2.0 --no-input
+```
+
+## Issue Assign
+
+```bash
+jira issue assign ISSUE-1 <user>
+jira issue assign ISSUE-1 $(jira me)   # assign to self
+jira issue assign ISSUE-1 default      # default assignee
+jira issue assign ISSUE-1 x            # unassign
+```
+
+A partial name ("suffix") may prompt for selection if it matches multiple users.
+
+## Issue Move (Transition)
+
+```bash
+jira issue move ISSUE-1 <status> [flags]
+```
+
+| Flag | Description |
+| --- | --- |
+| `--comment <text>` | Comment added during the transition (workflow must allow it) |
+| `-R, --resolution <value>` | Set resolution while moving (e.g. `Fixed`) |
+| `-a, --assignee <user>` | Reassign while moving |
+
+```bash
+jira issue move ISSUE-1 "In Progress"
+jira issue move ISSUE-1 Done -RFixed -a$(jira me) --comment "Completed"
+```
+
+The status name must match the workflow exactly (case-sensitive). Run `jira issue move` with no arguments to pick from valid transitions interactively.
+
+## Issue View
+
+```bash
+jira issue view ISSUE-1 [--comments <n>]
+```
+
+Renders the description as Markdown in the terminal (pager: `less` by default). `--comments 5` shows the 5 most recent comments.
+
+## Issue Link / Unlink
+
+```bash
+jira issue link ISSUE-1 ISSUE-2 <link-type>   # e.g. Blocks, Relates, Duplicates
+jira issue unlink ISSUE-1 ISSUE-2
+jira issue link remote ISSUE-1 <url> "<text>" # add a remote web link
+```
+
+## Issue Clone
+
+```bash
+jira issue clone ISSUE-1 [flags]
+```
+
+| Flag | Description |
+| --- | --- |
+| `-s, -y, -a, -l, -C` | Override summary, priority, assignee, labels, components on the clone |
+| `-H, --replace "find:replace"` | Case-sensitive text replacement in summary and description |
+
+```bash
+jira issue clone ISSUE-1 -s"Modified summary" -yHigh -a$(jira me)
+jira issue clone ISSUE-1 -H"find me:replace with me"
+```
+
+## Issue Delete
+
+```bash
+jira issue delete ISSUE-1 [--cascade]
+```
+
+`--cascade` also deletes all subtasks.
+
+## Issue Comment
+
+```bash
+jira issue comment add ISSUE-1 "Comment body" [flags]
+```
+
+| Flag | Description |
+| --- | --- |
+| `--internal` | Mark as an internal (restricted) comment |
+| `--template <file\|->` | Load comment from file or stdin |
+
+```bash
+echo "Comment from stdin" | jira issue comment add ISSUE-1
+```
+
+The positional body takes precedence over `--template` when both are given.
+
+## Issue Worklog
+
+```bash
+jira issue worklog add ISSUE-1 "<time>" [flags]
+```
+
+Time is positional and accepts values like `"10m"`, `"2h"`, `"2d 3h 30m"`.
+
+```bash
+jira issue worklog add ISSUE-1 "2d 3h 30m" --comment "Implementation" --no-input
+```
+
+## Epic
+
+```bash
+jira epic list [EPIC-KEY] [issue-list-flags]   # list epics, or issues in an epic
+jira epic list EPIC-1 -ax -yHigh --table --plain
+jira epic create -n"Epic name" -s"Summary" -yHigh -lbug -b"Description" --no-input
+jira epic add EPIC-1 ISSUE-1 ISSUE-2           # up to 50 issues at once
+jira epic remove ISSUE-1 ISSUE-2               # up to 50 issues at once
+```
+
+`epic list` supports all `issue list` filter flags except issue type. `epic create` requires `-n/--name`.
+
+## Sprint
+
+```bash
+jira sprint list [SPRINT_ID] [flags]
+```
+
+| Flag | Description |
+| --- | --- |
+| `--current` | Issues in the current active sprint |
+| `--prev` | Issues in the previous sprint |
+| `--next` | Issues in the next planned sprint |
+| `--state <list>` | e.g. `future,active` |
+| `--table` | Table view (default is explorer) |
+
+```bash
+jira sprint list --current -a$(jira me) --table --plain
+jira sprint list --state future,active --table --plain
+jira sprint list SPRINT_ID -yHigh --table --plain   # all issue filters supported
+jira sprint add SPRINT_ID ISSUE-1 ISSUE-2           # up to 50 issues at once
+```
+
+Only the 25 most recent sprints are shown. Get sprint IDs from `jira sprint list`.
+
+## Releases, Projects, Boards, Other
+
+```bash
+jira release list [--project KEY]   # project versions; feature must be enabled on the instance
+jira project list                   # all accessible projects
+jira board list                     # boards in the configured project
+jira open                           # open project in browser
+jira open ISSUE-1                   # open issue in browser
+```

package/framework/skills/jira-cli/references/quick-reference.md

@@ -0,0 +1,111 @@
+# Jira CLI Quick Reference
+
+Condensed cheat sheet. Use `--plain` (or `--table`, `--raw`, `--csv`) and `--no-input` when running non-interactively.
+
+## Setup
+
+```bash
+jira init                  # one-time config wizard (Cloud/Local, auth, project, board)
+export JIRA_API_TOKEN=...  # Jira Cloud API token
+export JIRA_AUTH_TYPE=bearer  # only for on-premises PAT auth
+jira me                    # verify auth and current user
+```
+
+## List Issues
+
+```bash
+jira issue list --plain
+jira issue list -a$(jira me) --plain                          # assigned to me
+jira issue list -r$(jira me) --created week --plain           # reported by me this week
+jira issue list -w --plain                                    # watching
+jira issue list --history                                     # recently interacted
+jira issue list -yHigh -s"To Do" --created month -lbackend --plain
+jira issue list -ax --created week --plain                    # unassigned
+jira issue list -s~Done --plain                               # status is not Done
+jira issue list -q "summary ~ cli" --plain                    # raw JQL
+```
+
+Filter flags: `-a` assignee (`x` = unassigned), `-r` reporter, `-s` status (`~` = not), `-y` priority, `-l` label (repeatable), `-t` type, `-w` watching, `-R` resolution, `--created`/`--updated` (`-7d`, `-1h`, `week`, `month`), `--created-before`/`--updated-before`, `--order-by <field> --reverse`.
+
+## Output Modes
+
+```bash
+jira issue list --plain --columns key,summary,status --no-headers   # TSV, no header
+jira issue list --raw        # JSON
+jira issue list --csv        # CSV
+```
+
+## Create / Edit / Assign
+
+```bash
+jira issue create -tBug -s"Summary" -b"Body" -yHigh -lbug --no-input
+jira issue create -tStory -s"Summary" -PEPIC-42 --no-input              # attach to epic
+echo "Body" | jira issue create -s"Summary" -tTask --no-input           # body via stdin
+jira issue edit ISSUE-1 -s"New summary" --no-input
+jira issue edit ISSUE-1 --label -p2 --label p1 --no-input               # "-" removes
+jira issue assign ISSUE-1 "Jon Doe"
+jira issue assign ISSUE-1 $(jira me)                                    # self
+jira issue assign ISSUE-1 default                                       # default assignee
+jira issue assign ISSUE-1 x                                             # unassign
+```
+
+## Transition
+
+```bash
+jira issue move ISSUE-1 "In Progress"
+jira issue move ISSUE-1 Done -RFixed -a$(jira me) --comment "Done"
+```
+
+Status name must match the workflow exactly.
+
+## Comments / Links / Worklog
+
+```bash
+jira issue comment add ISSUE-1 "Comment body"
+jira issue comment add ISSUE-1 "Internal note" --internal
+jira issue link ISSUE-1 ISSUE-2 Blocks
+jira issue unlink ISSUE-1 ISSUE-2
+jira issue link remote ISSUE-1 https://example.com "Example text"
+jira issue worklog add ISSUE-1 "2d 3h 30m" --comment "Note" --no-input
+```
+
+## Clone / Delete
+
+```bash
+jira issue clone ISSUE-1 -s"New summary" -a$(jira me)
+jira issue clone ISSUE-1 -H"find:replace"          # replace text in summary/description
+jira issue delete ISSUE-1 --cascade                # also deletes subtasks
+```
+
+## Epics
+
+```bash
+jira epic list --table --plain
+jira epic list EPIC-1 --table --plain              # issues in an epic
+jira epic create -n"Name" -s"Summary" -b"Body" --no-input
+jira epic add EPIC-1 ISSUE-1 ISSUE-2               # up to 50
+jira epic remove ISSUE-1 ISSUE-2                   # up to 50
+```
+
+## Sprints
+
+```bash
+jira sprint list --current --table --plain
+jira sprint list --prev --table --plain
+jira sprint list --next --table --plain
+jira sprint list --state future,active --table --plain
+jira sprint list SPRINT_ID -yHigh --table --plain  # issue filters work here too
+jira sprint add SPRINT_ID ISSUE-1 ISSUE-2          # up to 50
+```
+
+## Projects, Boards, Misc
+
+```bash
+jira project list
+jira board list
+jira release list --project KEY
+jira open ISSUE-1          # open in browser
+jira me                    # current user
+jira issue list -pXYZ ...  # override configured project
+jira issue list -c ./config.yaml ...   # alternative config file
+```

package/framework/skills/jira-cli/references/troubleshooting.md

@@ -0,0 +1,114 @@
+# Jira CLI Troubleshooting
+
+Common `jira` CLI error scenarios and solutions.
+
+## Table of Contents
+
+- [Command not found](#command-not-found)
+- [Authentication errors (401/403)](#authentication-errors-401403)
+- [Configuration problems](#configuration-problems)
+- [Command hangs in scripts](#command-hangs-in-scripts)
+- [Transition errors](#transition-errors)
+- [Empty or wrong issue lists](#empty-or-wrong-issue-lists)
+- [Epic or issue creation fails on-premises](#epic-or-issue-creation-fails-on-premises)
+- [Custom fields not applied](#custom-fields-not-applied)
+- [Multiple Jira instances or projects](#multiple-jira-instances-or-projects)
+- [View command pager issues](#view-command-pager-issues)
+
+## Command not found
+
+**Symptom:** `command not found: jira`
+
+**Fix:**
+1. Install jira-cli: download a binary from the [releases page](https://github.com/ankitpokhrel/jira-cli/releases), or use Homebrew (`brew install ankitpokhrel/jira-cli/jira-cli`)
+2. Verify: `jira --version`
+
+## Authentication errors (401/403)
+
+**Symptom:** API errors like `GET .../myself: 401 Unauthorized` or 403 on every command.
+
+**Fix:**
+1. Verify the token is exported: `echo "${JIRA_API_TOKEN:?not set}"`
+2. Jira Cloud: use an API token from https://id.atlassian.com/manage-profile/security/api-tokens (your email is the login; basic auth is the default)
+3. On-premises with a Personal Access Token: set `JIRA_AUTH_TYPE=bearer`
+4. On-premises with login credentials: export the password as `JIRA_API_TOKEN` (basic auth, the default)
+5. Re-check with `jira me`
+6. Tokens can also be supplied via `.netrc` or `keychain` instead of the environment variable
+
+## Configuration problems
+
+**Symptom:** `Please select installation type`, or prompts for server/project on every command.
+
+**Fix:**
+1. Run `jira init` and complete the wizard (installation type Cloud/Local, auth type, login, project, board)
+2. To start over, re-run `jira init` and answer the regeneration prompt
+3. Confirm the config path with `jira --help`; override it per command with `-c /path/to/config.yaml` or `JIRA_CONFIG_FILE`
+
+## Command hangs in scripts
+
+**Symptom:** `jira issue list` (and other list commands) never returns in CI or non-interactive shells.
+
+**Cause:** list and create commands open an interactive TUI by default.
+
+**Fix:**
+1. Add `--plain` (or `--table`, `--raw`, `--csv`) to list commands
+2. Add `--no-input` and all required flags to create/edit/move/assign commands
+3. Pipe bodies via stdin instead of letting them prompt: `echo "Body" | jira issue create -s"Summary" -tTask --no-input`
+
+## Transition errors
+
+**Symptom:** `jira issue move ISSUE-1 "Done"` fails or reports an unknown transition.
+
+**Fix:**
+1. Status names are case-sensitive and must match the workflow exactly (e.g. `"In Progress"`, not `in progress`)
+2. Run `jira issue move` with no arguments to list valid transitions for the issue
+3. If a workflow field (comment, resolution, assignee) is rejected during a move, the Jira workflow does not allow it on that transition — drop the flag or ask an admin to enable it
+
+## Empty or wrong issue lists
+
+**Symptom:** `jira issue list` returns nothing, or issues from the wrong project.
+
+**Fix:**
+1. The CLI is scoped to the project/board chosen during `jira init` — re-run `jira init` to change it
+2. Target another project for a single command: `jira issue list -pXYZ --plain`
+3. Reset filters one at a time to isolate the culprit (`-a`, `-s`, `--created`, ...)
+4. Sprint views only show the 25 most recent sprints; older sprints are not listed
+
+## Epic or issue creation fails on-premises
+
+**Symptom:** Creation fails or misbehaves on a non-English Jira Server/Data Center installation.
+
+**Cause:** older Jira APIs do not return untranslated issue type names.
+
+**Fix:** manually fill `epic.name`, `epic.link`, and `issue.types.*.handle` fields in the generated config file.
+
+## Custom fields not applied
+
+**Symptom:** `--custom "key=value"` appears to be ignored or errors.
+
+**Fix:**
+1. Custom fields must be configured in the generated config file to map names to field IDs
+2. See the jira-cli discussion on custom fields for the exact config format
+3. Validate the value type matches the field (text, option, user, ...)
+
+## Multiple Jira instances or projects
+
+**Symptom:** Need to work against two servers or project contexts.
+
+**Fix:**
+1. Generate a config per context with `jira init`
+2. Switch with `jira issue list -c ./other_config.yaml` or `export JIRA_CONFIG_FILE=./other_config.yaml`
+
+## View command pager issues
+
+**Symptom:** `jira issue view` output is truncated or opens an unwanted pager.
+
+**Fix:** `view` uses `less` by default; pipe output (`jira issue view ISSUE-1 | cat`) or configure a custom pager when embedding in scripts.
+
+## mtls authentication issues
+
+**Symptom:** Certificate errors with auth type `mtls`.
+
+**Fix:**
+1. Re-run `jira init`, select installation type `Local`, auth type `mtls`, and provide the CA cert, client key, and client cert
+2. If `JIRA_API_TOKEN` is set, it is used together with `mtls`

package/framework/styles/README.md

@@ -6,8 +6,11 @@ A curated catalog of design system references from [Refero Styles](https://style
 
 | Style | Description | Preview |
 | --- | --- | --- |
-| [Linear](./linear/README.md) | Midnight precision instrument — near-black surfaces, acid-lime accent, tight Inter typography. | ![Linear preview](https://images.refero.design/styles/refero.design/image/eee18c0c-a85f-4a66-83f6-f9f38d284825.jpg) |
-| [Raycast](./raycast/README.md) | Midnight command center, coral neon — almost-black canvas, warm coral brand accent, glass navigation. | ![Raycast preview](https://images.refero.design/styles/refero.design/image/ee40e139-0b24-47a0-9ea0-98372d317c5b.jpg) |
+| [Factory](./factory/README.md) | Terminal war room — stark black canvas, light figure-ground cards, and restrained orange/green data signals. | ![Factory preview](./factory/assets/preview.jpg) |
+| [Huly](./huly/README.md) | Midnight observatory — violet-to-coral aurora hero, dark productivity surfaces, and pill-shaped controls. | ![Huly preview](./huly/assets/preview.jpg) |
+| [Linear](./linear/README.md) | Midnight precision instrument — near-black surfaces, acid-lime accent, tight Inter typography. | ![Linear preview](./linear/assets/preview.jpg) |
+| [Notion](./notion/README.md) | Warm paper notebook — off-white canvas, editorial typography, blue primary action, and playful accent panels. | ![Notion preview](./notion/assets/preview.jpg) |
+| [Raycast](./raycast/README.md) | Midnight command center, coral neon — almost-black canvas, warm coral brand accent, glass navigation. | ![Raycast preview](./raycast/assets/preview.jpg) |
 
 ## How Styles Are Organized
 
@@ -15,7 +18,9 @@ Each style entry follows this structure:
 
 ```text
 styles/<style-name>/
-└── README.md       # Full design system reference: palette, typography, spacing, components, tokens
+├── README.md       # Concise style overview and implementation guidelines
+├── DESIGN.md       # Full design system reference: palette, typography, spacing, components, tokens
+└── assets/         # Preview images and other style assets, when provided
 ```
 
 ## How to Use a Style
@@ -32,4 +37,4 @@ All styles are sourced from [Refero Styles](https://styles.refero.design/) — a
 ## Related Repository Areas
 
 - [`skills/`](../skills/) contains task-specific procedures for AI coding agents.
-- [`references/standards/`](../references/standards/) contains canonical engineering rules.
+- [`references/standards/`](../references/standards/) contains canonical engineering rules.