devlyn-cli 0.2.0 → 0.2.1
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 +23 -1
- package/package.json +2 -2
package/CLAUDE.md
CHANGED
|
@@ -6,6 +6,15 @@
|
|
|
6
6
|
- Follow commit conventions in `.claude/commit-conventions.md`
|
|
7
7
|
- Follow design system in `docs/design-system.md` for UI/UX work if exist
|
|
8
8
|
|
|
9
|
+
## Error Handling Philosophy
|
|
10
|
+
|
|
11
|
+
**No silent fallbacks.** Handle errors explicitly and show the user what happened.
|
|
12
|
+
|
|
13
|
+
- **Default behavior**: When something fails, display a clear error state in the UI (error message, retry option, or actionable guidance). Do NOT silently fall back to default/placeholder data.
|
|
14
|
+
- **Fallbacks are the exception, not the rule.** Only use fallbacks when it is a widely accepted best practice (e.g., fallback fonts in CSS, CDN failover, graceful image loading with placeholder). If unsure, handle the error explicitly instead.
|
|
15
|
+
- **Never hide failures.** The user should always know when something went wrong. A visible error with a retry button is better UX than silently showing stale/default data.
|
|
16
|
+
- **Pattern**: `try { doThing() } catch (error) { showErrorUI(error) }` — NOT `try { doThing() } catch { return fallbackValue }`
|
|
17
|
+
|
|
9
18
|
## Investigation Workflow
|
|
10
19
|
|
|
11
20
|
When investigating bugs, analyzing features, or exploring code:
|
|
@@ -39,6 +48,19 @@ The full design-to-implementation pipeline:
|
|
|
39
48
|
|
|
40
49
|
For complex features, use the Plan agent to design the approach before implementation.
|
|
41
50
|
|
|
51
|
+
## Vibe Coding Workflow
|
|
52
|
+
|
|
53
|
+
The recommended sequence after writing code:
|
|
54
|
+
|
|
55
|
+
1. **Write code** (vibe coding)
|
|
56
|
+
2. `/simplify` → Quick cleanup pass (reuse, quality, efficiency)
|
|
57
|
+
3. `/devlyn.review` → Thorough solo review with security-first checklist
|
|
58
|
+
4. `/devlyn.team-review` → Multi-perspective team review (for important PRs)
|
|
59
|
+
5. `/devlyn.clean` → Periodic codebase-wide hygiene
|
|
60
|
+
6. `/devlyn.update-docs` → Keep docs in sync
|
|
61
|
+
|
|
62
|
+
Steps 4-6 are optional depending on the scope of changes. `/simplify` should always run before `/devlyn.review` to catch low-hanging fruit cheaply.
|
|
63
|
+
|
|
42
64
|
## Documentation Workflow
|
|
43
65
|
|
|
44
66
|
- **Sync docs with codebase**: Use `/devlyn.update-docs` to clean up stale content, update outdated info, and generate missing docs
|
|
@@ -56,7 +78,7 @@ For complex features, use the Plan agent to design the approach before implement
|
|
|
56
78
|
|
|
57
79
|
- **Codebase cleanup**: Use `/devlyn.clean` to detect and remove dead code, unused dependencies, complexity hotspots, and tech debt
|
|
58
80
|
- **Focused cleanup**: Use `/devlyn.clean [category]` for targeted sweeps (dead code, deps, tests, complexity, hygiene)
|
|
59
|
-
- **Periodic maintenance sequence**: `/devlyn.clean` → `/devlyn.update-docs` → `/devlyn.review`
|
|
81
|
+
- **Periodic maintenance sequence**: `/devlyn.clean` → `/simplify` → `/devlyn.update-docs` → `/devlyn.review`
|
|
60
82
|
|
|
61
83
|
## Context Window Management
|
|
62
84
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "devlyn-cli",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.1",
|
|
4
4
|
"description": "Claude Code configuration toolkit for teams",
|
|
5
5
|
"bin": {
|
|
6
6
|
"devlyn": "bin/devlyn.js"
|
|
@@ -24,4 +24,4 @@
|
|
|
24
24
|
"type": "git",
|
|
25
25
|
"url": "git+https://github.com/fysoul17/devlyn-cli.git"
|
|
26
26
|
}
|
|
27
|
-
}
|
|
27
|
+
}
|