devlyn-cli 0.0.1 → 0.0.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/CLAUDE.md +41 -0
- package/package.json +3 -2
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/package.json
CHANGED
|
@@ -1,13 +1,14 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "devlyn-cli",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.3",
|
|
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",
|