devlyn-cli 0.0.1 → 0.0.4
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/CLAUDE.md +41 -0
- package/README.md +106 -18
- package/bin/devlyn.js +9 -0
- package/package.json +4 -3
package/CLAUDE.md
ADDED
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# Project Instructions
|
|
2
|
+
|
|
3
|
+
## General
|
|
4
|
+
|
|
5
|
+
- Proactively use subagents and skills where needed
|
|
6
|
+
- Follow commit conventions in `.claude/commit-conventions.md`
|
|
7
|
+
- Follow design system in `docs/design-system.md` for UI/UX work if exist
|
|
8
|
+
|
|
9
|
+
## Investigation Workflow
|
|
10
|
+
|
|
11
|
+
When investigating bugs, analyzing features, or exploring code:
|
|
12
|
+
|
|
13
|
+
1. **Define exit criteria upfront** - Ask "What does 'done' look like?" before starting
|
|
14
|
+
2. **Checkpoint progress** - Use TodoWrite every 5-10 minutes to save findings
|
|
15
|
+
3. **Output intermediate summaries** - Provide "Current Understanding" snapshots so work isn't lost if interrupted
|
|
16
|
+
4. **Always deliver findings** - Never end mid-analysis; at minimum output:
|
|
17
|
+
- Files examined
|
|
18
|
+
- Key findings
|
|
19
|
+
- Remaining unknowns
|
|
20
|
+
- Recommended next steps
|
|
21
|
+
|
|
22
|
+
For complex investigations, use `/investigate` skill or spawn parallel Task agents to explore different areas simultaneously.
|
|
23
|
+
|
|
24
|
+
## Feature Development
|
|
25
|
+
|
|
26
|
+
1. **Plan first** - Always output a concrete implementation plan with specific file changes before writing code
|
|
27
|
+
2. **Track progress** - Use TodoWrite to checkpoint each phase
|
|
28
|
+
3. **Test validation** - Write tests alongside implementation; iterate until green
|
|
29
|
+
4. **Small commits** - Commit working increments rather than large changesets
|
|
30
|
+
|
|
31
|
+
For complex features, use the Plan agent to design the approach before implementation.
|
|
32
|
+
|
|
33
|
+
## Debugging Workflow
|
|
34
|
+
|
|
35
|
+
Use `/devlyn.resolve` for systematic bug fixing with test-driven validation.
|
|
36
|
+
|
|
37
|
+
## Communication Style
|
|
38
|
+
|
|
39
|
+
- Lead with **objective data** (popularity, benchmarks, community adoption) before personal opinions
|
|
40
|
+
- When user asks "what's popular" or "what do others use", provide data-driven answers
|
|
41
|
+
- Keep recommendations actionable and specific
|
package/README.md
CHANGED
|
@@ -1,43 +1,131 @@
|
|
|
1
|
+
<div align="center">
|
|
2
|
+
|
|
1
3
|
# devlyn-cli
|
|
2
4
|
|
|
3
|
-
Claude Code
|
|
5
|
+
**A shared configuration toolkit for Claude Code — standardize AI-powered workflows across your team and projects.**
|
|
6
|
+
|
|
7
|
+
[](https://www.npmjs.com/package/devlyn-cli)
|
|
8
|
+
[](https://opensource.org/licenses/MIT)
|
|
9
|
+
|
|
10
|
+
</div>
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
## Why devlyn-cli?
|
|
15
|
+
|
|
16
|
+
[Claude Code](https://docs.anthropic.com/en/docs/claude-code) is powerful out of the box, but teams need **consistent workflows** — shared commands, proven prompts, commit conventions, and reusable skills.
|
|
17
|
+
|
|
18
|
+
devlyn-cli installs a curated `.claude/` configuration into any project, giving your team:
|
|
19
|
+
|
|
20
|
+
- Battle-tested slash commands for debugging, code review, UI design, and more
|
|
21
|
+
- Reusable AI agent skills for investigation and prompt engineering
|
|
22
|
+
- Product and feature spec templates
|
|
23
|
+
- Commit message conventions
|
|
24
|
+
|
|
25
|
+
Zero dependencies. One command. Works with any project.
|
|
4
26
|
|
|
5
|
-
##
|
|
27
|
+
## Quick Start
|
|
6
28
|
|
|
7
29
|
```bash
|
|
8
|
-
# 새 프로젝트에 .claude 설정 설치
|
|
9
30
|
npx devlyn-cli
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
That's it. The interactive installer walks you through the setup.
|
|
10
34
|
|
|
11
|
-
|
|
35
|
+
```bash
|
|
36
|
+
# Non-interactive mode (for CI/CD)
|
|
12
37
|
npx devlyn-cli -y
|
|
13
38
|
|
|
14
|
-
#
|
|
39
|
+
# Update to the latest config
|
|
15
40
|
npx devlyn-cli@latest
|
|
41
|
+
|
|
42
|
+
# List all available commands and templates
|
|
43
|
+
npx devlyn-cli list
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
## What Gets Installed
|
|
47
|
+
|
|
48
|
+
```
|
|
49
|
+
your-project/
|
|
50
|
+
├── .claude/
|
|
51
|
+
│ ├── commands/ # 9 slash commands
|
|
52
|
+
│ ├── skills/ # 3 reusable AI skills
|
|
53
|
+
│ ├── templates/ # Document templates
|
|
54
|
+
│ └── commit-conventions.md # Commit message standards
|
|
55
|
+
└── CLAUDE.md # Project-level instructions
|
|
16
56
|
```
|
|
17
57
|
|
|
18
|
-
##
|
|
58
|
+
## Commands
|
|
19
59
|
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
60
|
+
Slash commands are invoked directly in Claude Code conversations (e.g., `/devlyn.resolve`).
|
|
61
|
+
|
|
62
|
+
| Command | Description |
|
|
63
|
+
|---|---|
|
|
64
|
+
| `/devlyn.resolve` | Systematic bug fixing with root-cause analysis and test-driven validation |
|
|
65
|
+
| `/devlyn.review` | Post-implementation code review — security, quality, best practices |
|
|
66
|
+
| `/devlyn.ui` | Generate 5 distinct UI style explorations from a spec or reference image |
|
|
67
|
+
| `/devlyn.feature-spec` | Transform product specs into implementable feature specifications |
|
|
68
|
+
| `/devlyn.product-spec` | Generate or incrementally update product spec documents |
|
|
69
|
+
| `/devlyn.discover-product` | Scan a codebase to generate feature-oriented product documentation |
|
|
70
|
+
| `/devlyn.recommend-features` | Prioritize top 5 features to build next based on value and readiness |
|
|
71
|
+
| `/devlyn.design-system` | Design system reference and guidance |
|
|
72
|
+
| `/devlyn.handoff` | Create structured handoff docs for context window transitions |
|
|
73
|
+
|
|
74
|
+
## Skills
|
|
75
|
+
|
|
76
|
+
Skills are triggered automatically based on conversation context.
|
|
77
|
+
|
|
78
|
+
| Skill | Description |
|
|
79
|
+
|---|---|
|
|
80
|
+
| `investigate` | Parallel code exploration with structured progress checkpoints |
|
|
81
|
+
| `prompt-engineering` | Claude prompt optimization based on Anthropic best practices |
|
|
82
|
+
| `feature-gap-analysis` | Identify missing features by comparing against baselines or competitors |
|
|
83
|
+
|
|
84
|
+
## Templates
|
|
85
|
+
|
|
86
|
+
| Template | Description |
|
|
87
|
+
|---|---|
|
|
88
|
+
| `template-product-spec.md` | Comprehensive product specification template |
|
|
89
|
+
| `template-feature.spec.md` | Feature specification template |
|
|
90
|
+
| `prompt-templates.md` | Reusable prompt snippets for common tasks |
|
|
24
91
|
|
|
25
92
|
## Optional Skill Packs
|
|
26
93
|
|
|
27
|
-
|
|
94
|
+
During installation, you can choose to add third-party skill packs:
|
|
28
95
|
|
|
29
96
|
```bash
|
|
30
|
-
# Vercel
|
|
97
|
+
# Vercel — React, Next.js, and React Native best practices
|
|
31
98
|
npx skills add vercel-labs/agent-skills
|
|
32
99
|
|
|
33
|
-
# Supabase
|
|
100
|
+
# Supabase — Supabase integration patterns
|
|
34
101
|
npx skills add supabase/agent-skills
|
|
35
102
|
```
|
|
36
103
|
|
|
37
|
-
##
|
|
104
|
+
## How It Works
|
|
38
105
|
|
|
39
|
-
|
|
106
|
+
1. Run `npx devlyn-cli` in your project
|
|
107
|
+
2. The CLI copies the config files into `.claude/`
|
|
108
|
+
3. Claude Code automatically reads `.claude/commands` and `.claude/skills`
|
|
109
|
+
4. Invoke commands like `/devlyn.resolve` in your Claude Code session
|
|
110
|
+
|
|
111
|
+
The installation is **idempotent** — run it again at any time to update to the latest config.
|
|
112
|
+
|
|
113
|
+
## Requirements
|
|
114
|
+
|
|
115
|
+
- Node.js 18+
|
|
116
|
+
- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) CLI
|
|
117
|
+
|
|
118
|
+
## Contributing
|
|
119
|
+
|
|
120
|
+
Contributions are welcome! Feel free to open an issue or submit a pull request.
|
|
121
|
+
|
|
122
|
+
1. Fork the repository
|
|
123
|
+
2. Create your branch (`git checkout -b feat/my-feature`)
|
|
124
|
+
3. Commit your changes following the included [commit conventions](config/commit-conventions.md)
|
|
125
|
+
4. Push to the branch (`git push origin feat/my-feature`)
|
|
126
|
+
5. Open a Pull Request
|
|
127
|
+
|
|
128
|
+
## License
|
|
129
|
+
|
|
130
|
+
[MIT](LICENSE) — Donut Studio
|
|
40
131
|
|
|
41
|
-
```bash
|
|
42
|
-
npx devlyn-cli@latest
|
|
43
|
-
```
|
package/bin/devlyn.js
CHANGED
|
@@ -290,6 +290,15 @@ async function init(skipPrompts = false) {
|
|
|
290
290
|
const targetDir = getTargetDir();
|
|
291
291
|
log('\n📁 Installing core config to .claude/', 'green');
|
|
292
292
|
copyRecursive(CONFIG_SOURCE, targetDir, targetDir);
|
|
293
|
+
|
|
294
|
+
// Copy CLAUDE.md to project root
|
|
295
|
+
const claudeMdSrc = path.join(__dirname, '..', 'CLAUDE.md');
|
|
296
|
+
const claudeMdDest = path.join(process.cwd(), 'CLAUDE.md');
|
|
297
|
+
if (fs.existsSync(claudeMdSrc)) {
|
|
298
|
+
fs.copyFileSync(claudeMdSrc, claudeMdDest);
|
|
299
|
+
log(' → CLAUDE.md', 'dim');
|
|
300
|
+
}
|
|
301
|
+
|
|
293
302
|
log('\n✅ Core config installed!', 'green');
|
|
294
303
|
|
|
295
304
|
// Skip prompts if -y flag or non-interactive
|
package/package.json
CHANGED
|
@@ -1,13 +1,14 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "devlyn-cli",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.4",
|
|
4
4
|
"description": "Claude Code configuration toolkit for teams",
|
|
5
5
|
"bin": {
|
|
6
6
|
"devlyn": "bin/devlyn.js"
|
|
7
7
|
},
|
|
8
8
|
"files": [
|
|
9
9
|
"bin",
|
|
10
|
-
"config"
|
|
10
|
+
"config",
|
|
11
|
+
"CLAUDE.md"
|
|
11
12
|
],
|
|
12
13
|
"keywords": [
|
|
13
14
|
"claude",
|
|
@@ -22,4 +23,4 @@
|
|
|
22
23
|
"type": "git",
|
|
23
24
|
"url": "git+https://github.com/fysoul17/devlyn-cli.git"
|
|
24
25
|
}
|
|
25
|
-
}
|
|
26
|
+
}
|