@jahanxu/trellis 0.5.0 → 0.5.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.
|
@@ -47,6 +47,7 @@ For triggered tasks, include all sections below:
|
|
|
47
47
|
| **Hit a gotcha** | Learned that X must be done before Y | Relevant code-spec + "Common Mistakes" section |
|
|
48
48
|
| **Established a convention** | Team agreed on naming pattern | `quality-guidelines.md` |
|
|
49
49
|
| **New thinking trigger** | "Don't forget to check X before doing Y" | `guides/*.md` (as a checklist item, not detailed rules) |
|
|
50
|
+
| **Role workflow improvement** | Better PRD template, mock data pattern | `roles/{detected-role}/*.md` (auto-detected) |
|
|
50
51
|
|
|
51
52
|
**Key Insight**: Code-spec updates are NOT just for problems. Every feature implementation contains design decisions and contracts that future AI/developers need to execute safely.
|
|
52
53
|
|
|
@@ -62,11 +63,26 @@ For triggered tasks, include all sections below:
|
|
|
62
63
|
├── frontend/ # Frontend coding standards
|
|
63
64
|
│ ├── index.md # Overview and links
|
|
64
65
|
│ └── *.md # Topic-specific guidelines
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
66
|
+
├── guides/ # Thinking checklists (NOT coding specs!)
|
|
67
|
+
│ ├── index.md # Guide index
|
|
68
|
+
│ └── *.md # Topic-specific guides
|
|
69
|
+
└── roles/ # Role-specific workflow specs (three-role pipeline)
|
|
70
|
+
├── pm/ # PM role conventions
|
|
71
|
+
├── designer/ # Designer role conventions
|
|
72
|
+
└── frontend-impl/ # Frontend implementation conventions
|
|
68
73
|
```
|
|
69
74
|
|
|
75
|
+
### Role-Aware Auto-Detection
|
|
76
|
+
|
|
77
|
+
When the developer name follows the `{role}-{name}` convention (e.g., `designer-bob`), this command automatically includes `spec/roles/{role}/` as an update target. No extra flags needed.
|
|
78
|
+
|
|
79
|
+
| Developer Name | Auto-detected Role Spec |
|
|
80
|
+
|---------------|------------------------|
|
|
81
|
+
| `pm-alice` | `spec/roles/pm/` |
|
|
82
|
+
| `designer-bob` | `spec/roles/designer/` |
|
|
83
|
+
| `frontend-carol` | `spec/roles/frontend-impl/` |
|
|
84
|
+
| `john` (no role prefix) | Role specs not included |
|
|
85
|
+
|
|
70
86
|
### CRITICAL: Code-Spec vs Guide - Know the Difference
|
|
71
87
|
|
|
72
88
|
| Type | Location | Purpose | Content Style |
|
|
@@ -47,6 +47,7 @@ For triggered tasks, include all sections below:
|
|
|
47
47
|
| **Hit a gotcha** | Learned that X must be done before Y | Relevant code-spec + "Common Mistakes" section |
|
|
48
48
|
| **Established a convention** | Team agreed on naming pattern | `quality-guidelines.md` |
|
|
49
49
|
| **New thinking trigger** | "Don't forget to check X before doing Y" | `guides/*.md` (as a checklist item, not detailed rules) |
|
|
50
|
+
| **Role workflow improvement** | Better PRD template, mock data pattern | `roles/{detected-role}/*.md` (auto-detected) |
|
|
50
51
|
|
|
51
52
|
**Key Insight**: Code-spec updates are NOT just for problems. Every feature implementation contains design decisions and contracts that future AI/developers need to execute safely.
|
|
52
53
|
|
|
@@ -62,11 +63,26 @@ For triggered tasks, include all sections below:
|
|
|
62
63
|
├── frontend/ # Frontend coding standards
|
|
63
64
|
│ ├── index.md # Overview and links
|
|
64
65
|
│ └── *.md # Topic-specific guidelines
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
66
|
+
├── guides/ # Thinking checklists (NOT coding specs!)
|
|
67
|
+
│ ├── index.md # Guide index
|
|
68
|
+
│ └── *.md # Topic-specific guides
|
|
69
|
+
└── roles/ # Role-specific workflow specs (three-role pipeline)
|
|
70
|
+
├── pm/ # PM role conventions
|
|
71
|
+
├── designer/ # Designer role conventions
|
|
72
|
+
└── frontend-impl/ # Frontend implementation conventions
|
|
68
73
|
```
|
|
69
74
|
|
|
75
|
+
### Role-Aware Auto-Detection
|
|
76
|
+
|
|
77
|
+
When the developer name follows the `{role}-{name}` convention (e.g., `designer-bob`), this command automatically includes `spec/roles/{role}/` as an update target. No extra flags needed.
|
|
78
|
+
|
|
79
|
+
| Developer Name | Auto-detected Role Spec |
|
|
80
|
+
|---------------|------------------------|
|
|
81
|
+
| `pm-alice` | `spec/roles/pm/` |
|
|
82
|
+
| `designer-bob` | `spec/roles/designer/` |
|
|
83
|
+
| `frontend-carol` | `spec/roles/frontend-impl/` |
|
|
84
|
+
| `john` (no role prefix) | Role specs not included |
|
|
85
|
+
|
|
70
86
|
### CRITICAL: Code-Spec vs Guide - Know the Difference
|
|
71
87
|
|
|
72
88
|
| Type | Location | Purpose | Content Style |
|
package/package.json
CHANGED