@tydung26/product-kit 1.3.1 → 1.4.0
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/README.md +4 -8
- package/package.json +1 -1
- package/skills/naming/SKILL.md +66 -0
package/README.md
CHANGED
|
@@ -5,10 +5,6 @@ Product engineer skills kit for Claude Code, Antigravity, and OpenCode AI assist
|
|
|
5
5
|
## Install
|
|
6
6
|
|
|
7
7
|
```bash
|
|
8
|
-
# pnpm
|
|
9
|
-
pnpm add -g @tydung26/product-kit
|
|
10
|
-
|
|
11
|
-
# npm
|
|
12
8
|
npm install -g @tydung26/product-kit
|
|
13
9
|
```
|
|
14
10
|
|
|
@@ -46,10 +42,10 @@ pkit doctor # Diagnose installation issues
|
|
|
46
42
|
|
|
47
43
|
## Install Paths
|
|
48
44
|
|
|
49
|
-
| Tool | Global
|
|
50
|
-
| ---------------------- |
|
|
51
|
-
| Claude Code + OpenCode | `~/.claude/skills/<skill>/`
|
|
52
|
-
| Antigravity | `~/.gemini/antigravity/skills/<skill>/` | `.agent/skills/<skill>/`
|
|
45
|
+
| Tool | Global | Project |
|
|
46
|
+
| ---------------------- | --------------------------------------- | ------------------------- |
|
|
47
|
+
| Claude Code + OpenCode | `~/.claude/skills/<skill>/` | `.claude/skills/<skill>/` |
|
|
48
|
+
| Antigravity | `~/.gemini/antigravity/skills/<skill>/` | `.agent/skills/<skill>/` |
|
|
53
49
|
|
|
54
50
|
## License
|
|
55
51
|
|
package/package.json
CHANGED
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: "pkit:naming"
|
|
3
|
+
description: >
|
|
4
|
+
Generate product/project name suggestions across multiple naming styles.
|
|
5
|
+
Use when user says "name my product", "name my app", "suggest a product name",
|
|
6
|
+
"I need a name for my project/tool/service". For software products only.
|
|
7
|
+
license: MIT
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Naming
|
|
11
|
+
|
|
12
|
+
Interview the user and propose **product names** across 8 naming styles. This skill is for naming software products, apps, tools, APIs, and services — not general naming tasks.
|
|
13
|
+
|
|
14
|
+
**⚠️ ONLY for naming/renaming software products, apps, tools, APIs, or services.**
|
|
15
|
+
Do NOT use for: naming people/pets/companies/teams, branding exercises, or domain research.
|
|
16
|
+
|
|
17
|
+
## Usage
|
|
18
|
+
|
|
19
|
+
```
|
|
20
|
+
/pkit:naming <optional context>
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Workflow
|
|
24
|
+
|
|
25
|
+
### Step 1 — Interview
|
|
26
|
+
|
|
27
|
+
Use `AskUserQuestion` with up to 4 questions at once:
|
|
28
|
+
|
|
29
|
+
1. What does this project do? (1-sentence pitch)
|
|
30
|
+
2. Who is the audience? (developers, consumers, enterprise, internal team)
|
|
31
|
+
3. What personality/feel? (serious, playful, minimal, bold, technical, approachable)
|
|
32
|
+
4. Any keywords, domain concepts, or technologies central to it?
|
|
33
|
+
|
|
34
|
+
If answers are thin, ask a follow-up batch:
|
|
35
|
+
|
|
36
|
+
1. Any hard constraints? (must be pronounceable, short, avoid certain words)
|
|
37
|
+
2. Any names you already like or dislike — and why?
|
|
38
|
+
|
|
39
|
+
### Step 2 — Generate Names
|
|
40
|
+
|
|
41
|
+
Propose **exactly 3 names per style** across all 6 styles (18 total).
|
|
42
|
+
|
|
43
|
+
Per name format: `**Name** — one-line reason it fits (5–10 words)`
|
|
44
|
+
|
|
45
|
+
| Style | Approach | Example |
|
|
46
|
+
| ------------------ | ----------------------------------- | ------------------------------ |
|
|
47
|
+
| **Descriptive** | Says exactly what it does | `product-kit`, `file-sync` |
|
|
48
|
+
| **Portmanteau** | Blend 2 relevant words | `Snapchat`, `DevKit` |
|
|
49
|
+
| **Brandable** | Invented/abstract, memorable | `Notion`, `Vercel`, `Supabase` |
|
|
50
|
+
| **Metaphor** | Abstract concept mirroring essence | `Forge`, `Anchor`, `Tide` |
|
|
51
|
+
| **Greek / Latin** | Classical roots, timeless authority | `Hermes`, `Aether`, `Kairos` |
|
|
52
|
+
| **Simple / Plain** | Common everyday words, zero jargon | `Quick`, `Base`, `Core`, `Kit` |
|
|
53
|
+
|
|
54
|
+
### Step 3 — Follow-up
|
|
55
|
+
|
|
56
|
+
End with:
|
|
57
|
+
|
|
58
|
+
> "Want more in a specific style, or variations on any of these?"
|
|
59
|
+
|
|
60
|
+
## Rules
|
|
61
|
+
|
|
62
|
+
- **Product names only** — for software, apps, tools
|
|
63
|
+
- If user asks to name something non-product (person, pet, etc.), politely redirect: "This skill is for product naming — try `/pkit:naming` with a product concept."
|
|
64
|
+
- **Names only** — no domain checks, no trademark lookups, no availability
|
|
65
|
+
- Group output by style with a `##` heading per style
|
|
66
|
+
- If user provides very little context, state your assumptions briefly and proceed
|