tlc-claude-code 1.2.12 → 1.2.13

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.
Files changed (3) hide show
  1. package/deploy.md +45 -2
  2. package/package.json +1 -1
  3. package/tlc.md +19 -1
package/deploy.md CHANGED
@@ -88,11 +88,54 @@ Config saved to .tlc.json
88
88
 
89
89
  ### Process
90
90
 
91
- 1. **Read project info** from `.tlc.json` or `package.json`
91
+ 1. **Detect project state**:
92
+ - New project? Use info from `/tlc:new-project` or `/tlc:init`
93
+ - Existing TLC project? Read from `.tlc.json`
94
+ - Legacy project? Read from `package.json` + git remote
92
95
  2. **Ask for domain** if not configured
93
96
  3. **Generate webhook secret** (random 16 chars)
94
97
  4. **Output setup command** with all config embedded
95
- 5. **Save config** to `.tlc.json`
98
+ 5. **Save/update config** in `.tlc.json`
99
+
100
+ ### Upgrading Existing Projects
101
+
102
+ For projects already using TLC but without team features:
103
+
104
+ ```
105
+ > /tlc:deploy setup
106
+
107
+ TLC Dev Server Setup
108
+ ════════════════════════════════════════════════════════════════════
109
+
110
+ Detected existing TLC project: my-awesome-app
111
+ ✓ .tlc.json found
112
+ ✓ .planning/ directory exists
113
+ ✗ No deploy config yet
114
+
115
+ Adding team collaboration features...
116
+
117
+ Project: my-awesome-app
118
+ Repo: git@github.com:myorg/my-awesome-app.git
119
+
120
+ Enter your server domain: _
121
+ ```
122
+
123
+ The setup continues with the same flow - generates config, shows server command, DNS instructions, webhook config.
124
+
125
+ **What gets added to .tlc.json:**
126
+
127
+ ```json
128
+ {
129
+ "project": "my-awesome-app",
130
+ "testFrameworks": { ... }, // existing config preserved
131
+ "deploy": { // NEW: added by setup
132
+ "domain": "myapp.example.com",
133
+ "webhookSecret": "x7k9m2p4q8r1s5t3",
134
+ "dashboardUrl": "https://dashboard.myapp.example.com",
135
+ "configured": false
136
+ }
137
+ }
138
+ ```
96
139
 
97
140
  ```javascript
98
141
  // Config generation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tlc-claude-code",
3
- "version": "1.2.12",
3
+ "version": "1.2.13",
4
4
  "description": "TLC - Test Led Coding for Claude Code",
5
5
  "bin": {
6
6
  "tlc": "./bin/tlc.js",
package/tlc.md CHANGED
@@ -64,6 +64,23 @@ fi
64
64
  echo "✓ Synced"
65
65
  ```
66
66
 
67
+ ### Step 0b: Check for Team Features (Existing Projects)
68
+
69
+ For projects that existed before team features, check if dev server is configured:
70
+
71
+ ```bash
72
+ # Check if deploy config exists
73
+ deployDomain=$(jq -r '.deploy.domain // ""' .tlc.json)
74
+
75
+ if [ -z "$deployDomain" ]; then
76
+ # No deploy config - this is an existing project without team setup
77
+ # Show subtle hint in header (not blocking)
78
+ teamHint="│ 💡 Team sharing available: /tlc:deploy setup"
79
+ fi
80
+ ```
81
+
82
+ This adds a non-blocking hint. Users can also access it via Quick Actions [5].
83
+
67
84
  ### Step 1: Show Phase Checklist (ALWAYS SHOW THIS)
68
85
 
69
86
  **This is the core of `/tlc` - always show the current phase status:**
@@ -102,8 +119,9 @@ Phase 2: User Dashboard
102
119
  [2] Go back and fix skipped steps
103
120
  [3] Show all commands (/tlc:help)
104
121
  [4] Full project checklist (/tlc:checklist)
122
+ [5] Set up team dev server (/tlc:deploy setup)
105
123
 
106
- Choice [1/2/3/4]: _
124
+ Choice [1/2/3/4/5]: _
107
125
  ```
108
126
 
109
127
  ### Step 2: Detect Current Phase