learnship 2.3.5 → 2.3.6

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "learnship",
3
3
  "description": "Agentic engineering done right — 57 structured workflows, 17 specialist agent personas, persistent memory across sessions, integrated learning partner, and impeccable UI design system. Works with Claude Code, Windsurf, Cursor, Gemini CLI, OpenCode, and Codex.",
4
- "version": "2.3.5",
4
+ "version": "2.3.6",
5
5
  "author": {
6
6
  "name": "Favio Vazquez",
7
7
  "email": "favio.vazquezp@gmail.com"
@@ -2,7 +2,7 @@
2
2
  "name": "learnship",
3
3
  "displayName": "learnship",
4
4
  "description": "Agentic engineering done right — 57 structured workflows, 17 specialist agent personas, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
5
- "version": "2.3.5",
5
+ "version": "2.3.6",
6
6
  "logo": "assets/logo.png",
7
7
  "author": {
8
8
  "name": "Favio Vazquez",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "learnship",
3
- "version": "2.3.5",
3
+ "version": "2.3.6",
4
4
  "description": "Agentic engineering done right — 57 structured workflows, 17 specialist agent personas, persistent memory across sessions, integrated learning partner, and impeccable UI design system.",
5
5
  "author": "Favio Vazquez",
6
6
  "homepage": "https://faviovazquez.github.io/learnship/",
@@ -226,14 +226,14 @@ Each plan produces 2-4 commits (tasks + metadata). Clear, granular, bisectable.
226
226
  ## Why Per-Task Commits?
227
227
 
228
228
  **Context engineering for AI:**
229
- - Git history becomes primary context source for future Claude sessions
229
+ - Git history becomes primary context source for future agent sessions
230
230
  - `git log --grep="{phase}-{plan}"` shows all work for a plan
231
231
  - `git diff <hash>^..<hash>` shows exact changes per task
232
232
  - Less reliance on parsing SUMMARY.md = more context for actual work
233
233
 
234
234
  **Failure recovery:**
235
235
  - Task 1 committed ✅, Task 2 failed ❌
236
- - Claude in next session: sees task 1 complete, can retry task 2
236
+ - Agent in next session: sees task 1 complete, can retry task 2
237
237
  - Can `git reset --hard` to last successful task
238
238
 
239
239
  **Debugging:**
@@ -242,8 +242,8 @@ Each plan produces 2-4 commits (tasks + metadata). Clear, granular, bisectable.
242
242
  - Each commit is independently revertable
243
243
 
244
244
  **Observability:**
245
- - Solo developer + Claude workflow benefits from granular attribution
245
+ - Solo developer + agent workflow benefits from granular attribution
246
246
  - Atomic commits are git best practice
247
- - "Commit noise" irrelevant when consumer is Claude, not humans
247
+ - "Commit noise" irrelevant when consumer is the agent, not humans
248
248
 
249
249
  </commit_strategy_rationale>
@@ -155,7 +155,7 @@ Loop until "Create PROJECT.md" selected.
155
155
  - **Rushing** — Minimizing questions to get to "the work"
156
156
  - **Shallow acceptance** — Taking vague answers without probing
157
157
  - **Premature constraints** — Asking about tech stack before understanding the idea
158
- - **User skills** — NEVER ask about user's technical experience. Claude builds.
158
+ - **User skills** — NEVER ask about user's technical experience. The agent builds.
159
159
 
160
160
  </anti_patterns>
161
161
 
@@ -599,7 +599,7 @@ Some things can't be verified programmatically. Flag these for human testing:
599
599
  ## Pre-Checkpoint Automation
600
600
 
601
601
  Key principles for automation-first verification:
602
- - Claude sets up verification environment BEFORE presenting checkpoints
602
+ - The agent sets up verification environment BEFORE presenting checkpoints
603
603
  - Users never run CLI commands (visit URLs only)
604
604
  - Server lifecycle: start before checkpoint, handle port conflicts, keep running for duration
605
605
  - CLI installation: auto-install where safe, checkpoint for user choice otherwise
@@ -28,7 +28,7 @@ Implementation decisions captured during `discuss-phase [N]`. This file is the p
28
28
  ### [Area 3 that was discussed]
29
29
  - **D-04:** [Specific decision made]
30
30
 
31
- ### Claude's Discretion
31
+ ### Agent's Discretion
32
32
  [Areas where user explicitly said "you decide" — the agent has flexibility here during planning/implementation]
33
33
 
34
34
  </decisions>
@@ -122,7 +122,7 @@ Display posts from followed users in a scrollable feed. Users can view posts and
122
122
  - Friendly illustration + "Follow people to see posts here"
123
123
  - Suggest 3-5 accounts to follow based on interests
124
124
 
125
- ### Claude's Discretion
125
+ ### Agent's Discretion
126
126
  - Loading skeleton design
127
127
  - Exact spacing and typography
128
128
  - Error state handling
@@ -185,7 +185,7 @@ CLI command to backup database to local file or S3. Supports full and incrementa
185
185
  - --no-retry flag to fail fast
186
186
  - Partial backups are deleted on failure (no corrupt files)
187
187
 
188
- ### Claude's Discretion
188
+ ### Agent's Discretion
189
189
  - Exact progress bar implementation
190
190
  - Compression algorithm choice
191
191
  - Temp file handling
@@ -35,9 +35,9 @@ created: [date]
35
35
 
36
36
  ---
37
37
 
38
- ## Claude's Discretion
38
+ ## Agent's Discretion
39
39
 
40
- [Areas delegated to Claude's judgment — list what was deferred and why]
40
+ [Areas delegated to agent's judgment — list what was deferred and why]
41
41
 
42
42
  ## Deferred Ideas
43
43
 
@@ -20,7 +20,7 @@ Extract implementation decisions that downstream planning needs. Analyze the pha
20
20
 
21
21
  2. **Planner** — Reads CONTEXT.md to know WHAT decisions are locked
22
22
  - "Pull-to-refresh on mobile" → planner includes that in task specs
23
- - "Claude's Discretion: loading skeleton" → planner can decide approach
23
+ - "Agent's Discretion: loading skeleton" → planner can decide approach
24
24
 
25
25
  **Your job:** Capture decisions clearly enough that downstream agents can act on them without asking the user again.
26
26
 
@@ -305,7 +305,7 @@ Write `.planning/phases/[padded_phase]-[phase_slug]/[padded_phase]-CONTEXT.md`:
305
305
  ### [Category discussed]
306
306
  - [Decision captured]
307
307
 
308
- ### Claude's Discretion
308
+ ### Agent's Discretion
309
309
  [Areas where user said "you decide"]
310
310
 
311
311
  </decisions>
@@ -365,7 +365,7 @@ Also write a discussion log for audit purposes using `@./templates/discussion-lo
365
365
  Write `.planning/phases/[padded_phase]-[phase_slug]/[padded_phase]-DISCUSSION-LOG.md` with:
366
366
  - All options considered for each area (not just the selected one)
367
367
  - The user's verbatim choice and rationale
368
- - Areas delegated to Claude's discretion
368
+ - Areas delegated to agent's discretion
369
369
  - Deferred ideas
370
370
 
371
371
  This file is for human audit trails only — it is NOT referenced by downstream agents.
@@ -118,7 +118,7 @@ Write `CONTEXT.md` to the task directory:
118
118
  ### [Area discussed]
119
119
  - [Decision captured]
120
120
 
121
- ### Claude's Discretion
121
+ ### Agent's Discretion
122
122
  [Areas not discussed or "you decide" answers]
123
123
 
124
124
  </decisions>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "learnship",
3
- "version": "2.3.5",
3
+ "version": "2.3.6",
4
4
  "description": "Learn as you build. Build with intent. — A multi-platform agentic engineering system for Windsurf, Claude Code, Cursor, OpenCode, Gemini CLI, and Codex: 57 spec-driven workflows, 17 specialist agent personas, integrated learning, and production-grade design.",
5
5
  "keywords": [
6
6
  "agentic",