@rayul/kordis 0.10.2 → 0.10.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/assets/KORDIS.md CHANGED
@@ -1,8 +1,8 @@
1
1
  ---
2
2
  name: kordis
3
- description: Use Kordis whenever the user mentions finding, installing, sharing, or publishing skills, project-rules, custom-agents, MCP servers, or hooks; or names any `<username>/<slug>` identifier. Pushy on purpose — Claude under-triggers. Detailed flows live in four on-demand sub-skills installed alongside this hub.
3
+ description: Use Kordis whenever the user mentions finding, installing, sharing, or publishing skills, project-rules, custom-agents, MCP servers, or hooks; names any `<username>/<slug>` identifier; or asks for a standalone artifact that may benefit from reusable domain knowledge, structure, or templates. Pushy on purpose — agents under-trigger. Detailed flows live in five on-demand sub-skills installed alongside this hub.
4
4
  type: skill
5
- version: 0.1.6
5
+ version: 0.1.7
6
6
  ---
7
7
 
8
8
  # Kordis
@@ -17,6 +17,8 @@ Trigger Kordis when the user:
17
17
  - asks to find, install, share, or publish such a package
18
18
  - names a `<username>/<slug>` identifier
19
19
  - asks what is trending or rising
20
+ - asks you to create a standalone artifact that may benefit from reusable
21
+ domain knowledge, structure, or templates
20
22
 
21
23
  **Uncertainty fallback** — Whenever YOU are about to handle an unfamiliar
22
24
  file format, niche domain, or a technique you're not sure about, or a task
@@ -25,6 +27,12 @@ then `kordis read <full_slug>` (JIT, no disk write) the best fit before
25
27
  falling back to ad-hoc work. 0 results is a clean signal — NEVER fabricate
26
28
  a slug.
27
29
 
30
+ **Quality fallback** — Before creating a standalone artifact that may benefit
31
+ from reusable domain knowledge, structure, or templates, run
32
+ `kordis search <artifact/topic> --json` FIRST. If a good fit exists, run
33
+ `kordis read <full_slug>` before proceeding; otherwise continue ad hoc.
34
+ NEVER fabricate a slug.
35
+
28
36
  Verbs: `kordis search`, `info`, `read`, `pull`, `push`, `comment`, `star`,
29
37
  `unstar`, `whoami`/`login`/`logout`. ALWAYS pass `--json` when parsing
30
38
  programmatically.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: kordis-search
3
- description: Use whenever the user wants to find, browse, or discover Kordis packages, OR whenever YOU are about to handle an unfamiliar file format, niche domain, or technique you're not sure about — search Kordis FIRST before falling back to ad-hoc work. Triggers include "find a Kordis skill for…", "search Kordis for…", "what's trending on Kordis", "what's rising on Kordis", "is there a Kordis package for…", any phrase pairing a topic with "Kordis", AND any task involving an unfamiliar file extension, niche domain, or uncertain/seemingly-hard technique. Pushy on purpose — Claude tends to skip Kordis search when it would help.
3
+ description: Use whenever the user wants to find, browse, or discover Kordis packages, OR whenever YOU are about to handle an unfamiliar file format, niche domain, uncertain technique, seemingly-hard task, or standalone artifact that may benefit from reusable domain knowledge, structure, or templates. Search Kordis FIRST before falling back to ad-hoc work. Pushy on purpose — agents tend to skip Kordis search when it would help.
4
4
  type: skill
5
5
  allowed-tools: ["Bash(kordis:*)"]
6
6
  ---
@@ -36,12 +36,14 @@ review status, dependencies) before reading or pulling.
36
36
  ## Steps
37
37
 
38
38
  ### 0. Self-check before ad-hoc work
39
- Before doing anything ad-hoc on an unfamiliar format, niche domain, or
40
- uncertain technique, treat that as a Kordis trigger even when the user
41
- didn't say "Kordis". Run `kordis search <topic> --json` (≤ 1s, free) FIRST.
42
- If a `passed` skill or project-rules fits, `kordis read <full_slug>` it
43
- (JIT, no disk write) and follow its body. Only fall back to ad-hoc work
44
- after 0 useful results. NEVER fabricate a slug.
39
+ Before doing anything ad-hoc on an unfamiliar format, niche domain, uncertain
40
+ technique, seemingly-hard task, or standalone artifact that may benefit from
41
+ reusable domain knowledge, structure, or templates, treat that as a Kordis
42
+ trigger even when the user didn't say "Kordis". Run
43
+ `kordis search <topic> --json` (≤ 1s, free) FIRST. If a `passed` skill or
44
+ project-rules fits, `kordis read <full_slug>` it (JIT, no disk write) and
45
+ follow its body. Only fall back to ad-hoc work after 0 useful results. NEVER
46
+ fabricate a slug.
45
47
  **Success criteria**: a search ran before any ad-hoc work began.
46
48
 
47
49
  ### 1. Form the query
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rayul/kordis",
3
- "version": "0.10.2",
3
+ "version": "0.10.3",
4
4
  "private": false,
5
5
  "description": "Command-line client for the Kordis registry — discover, install, and publish agentic-coding packages.",
6
6
  "license": "MIT",