telos-framework 0.3.0 → 0.3.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/commands/telos/init.md +88 -14
- package/package.json +1 -1
|
@@ -59,20 +59,94 @@ Run: `git status` to check if this is an active repository
|
|
|
59
59
|
|
|
60
60
|
## Step 2: Propose Telos Hierarchy
|
|
61
61
|
|
|
62
|
-
Based on your analysis, propose a complete 9-level hierarchy. Present it
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
62
|
+
Based on your analysis, propose a complete 9-level hierarchy. Present it using
|
|
63
|
+
this block format:
|
|
64
|
+
|
|
65
|
+
```
|
|
66
|
+
═══════════════════════════════════════════════════════════════════════════
|
|
67
|
+
PROPOSED TELOS HIERARCHY
|
|
68
|
+
═══════════════════════════════════════════════════════════════════════════
|
|
69
|
+
|
|
70
|
+
───────────────────────────────────────────────────────────────────────────
|
|
71
|
+
L9 - Telos-Guardian (Ultimate Purpose)
|
|
72
|
+
───────────────────────────────────────────────────────────────────────────
|
|
73
|
+
Purpose: [Proposed ultimate purpose statement]
|
|
74
|
+
|
|
75
|
+
Reasoning: [Why this is the ultimate purpose - based on README, project
|
|
76
|
+
description, and inferred mission]
|
|
77
|
+
───────────────────────────────────────────────────────────────────────────
|
|
78
|
+
|
|
79
|
+
───────────────────────────────────────────────────────────────────────────
|
|
80
|
+
L8 - Market-Analyst (Business Value)
|
|
81
|
+
───────────────────────────────────────────────────────────────────────────
|
|
82
|
+
Purpose: [Proposed business value statement]
|
|
83
|
+
|
|
84
|
+
Reasoning: [Business outcomes this project serves - based on metrics, KPIs,
|
|
85
|
+
or market positioning mentioned in docs]
|
|
86
|
+
───────────────────────────────────────────────────────────────────────────
|
|
87
|
+
|
|
88
|
+
───────────────────────────────────────────────────────────────────────────
|
|
89
|
+
L7 - Insight-Synthesizer (Product Strategy)
|
|
90
|
+
───────────────────────────────────────────────────────────────────────────
|
|
91
|
+
Purpose: [Proposed product strategy statement]
|
|
92
|
+
|
|
93
|
+
Reasoning: [How it delivers user value - based on features, roadmap, or
|
|
94
|
+
user-facing goals]
|
|
95
|
+
───────────────────────────────────────────────────────────────────────────
|
|
96
|
+
|
|
97
|
+
───────────────────────────────────────────────────────────────────────────
|
|
98
|
+
L6 - UX-Simulator (Experience Philosophy)
|
|
99
|
+
───────────────────────────────────────────────────────────────────────────
|
|
100
|
+
Purpose: [Proposed UX philosophy statement]
|
|
101
|
+
|
|
102
|
+
Reasoning: [User experience principles - based on UI framework, design
|
|
103
|
+
system, or accessibility mentions]
|
|
104
|
+
───────────────────────────────────────────────────────────────────────────
|
|
105
|
+
|
|
106
|
+
───────────────────────────────────────────────────────────────────────────
|
|
107
|
+
L5 - Journey-Validator (Workflow Validation)
|
|
108
|
+
───────────────────────────────────────────────────────────────────────────
|
|
109
|
+
Purpose: [Proposed workflow validation statement]
|
|
110
|
+
|
|
111
|
+
Reasoning: [User journey requirements - based on E2E tests, integration
|
|
112
|
+
tests, or workflow documentation]
|
|
113
|
+
───────────────────────────────────────────────────────────────────────────
|
|
114
|
+
|
|
115
|
+
───────────────────────────────────────────────────────────────────────────
|
|
116
|
+
L4 - Integration-Contractor (API Contracts)
|
|
117
|
+
───────────────────────────────────────────────────────────────────────────
|
|
118
|
+
Purpose: [Proposed API contract statement]
|
|
119
|
+
|
|
120
|
+
Reasoning: [Based on detected API frameworks, protocols, and integration
|
|
121
|
+
patterns]
|
|
122
|
+
───────────────────────────────────────────────────────────────────────────
|
|
123
|
+
|
|
124
|
+
───────────────────────────────────────────────────────────────────────────
|
|
125
|
+
L3 - Component-Architect (Component Design)
|
|
126
|
+
───────────────────────────────────────────────────────────────────────────
|
|
127
|
+
Purpose: [Proposed component architecture statement]
|
|
128
|
+
|
|
129
|
+
Reasoning: [Based on detected UI framework, component patterns, and
|
|
130
|
+
architectural choices]
|
|
131
|
+
───────────────────────────────────────────────────────────────────────────
|
|
132
|
+
|
|
133
|
+
───────────────────────────────────────────────────────────────────────────
|
|
134
|
+
L2 - Function-Author (Function Implementation)
|
|
135
|
+
───────────────────────────────────────────────────────────────────────────
|
|
136
|
+
Purpose: [Proposed function implementation statement]
|
|
137
|
+
|
|
138
|
+
Reasoning: [Based on detected test framework, testing strategy, and code
|
|
139
|
+
coverage requirements]
|
|
140
|
+
───────────────────────────────────────────────────────────────────────────
|
|
141
|
+
|
|
142
|
+
───────────────────────────────────────────────────────────────────────────
|
|
143
|
+
L1 - Syntax-Linter (Code Quality)
|
|
144
|
+
───────────────────────────────────────────────────────────────────────────
|
|
145
|
+
Purpose: [Proposed code quality statement]
|
|
146
|
+
|
|
147
|
+
Reasoning: [Based on detected linters, formatters, and quality standards]
|
|
148
|
+
═══════════════════════════════════════════════════════════════════════════
|
|
149
|
+
```
|
|
76
150
|
|
|
77
151
|
### Auto-generation Guidelines for L1-L4:
|
|
78
152
|
|
package/package.json
CHANGED