@whykusanagi/corrupted-theme 0.1.2 → 0.1.4
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/CHANGELOG.md +157 -0
- package/README.md +6 -0
- package/docs/CHARACTER_LEVEL_CORRUPTION.md +264 -0
- package/docs/CORRUPTION_PHRASES.md +529 -0
- package/docs/ROADMAP.md +266 -0
- package/docs/STYLE_GUIDE.md +605 -0
- package/docs/brand/BRAND_OVERVIEW.md +413 -0
- package/docs/brand/COLOR_SYSTEM.md +583 -0
- package/docs/brand/DESIGN_TOKENS.md +1009 -0
- package/docs/brand/TRANSLATION_FAILURE_AESTHETIC.md +525 -0
- package/docs/brand/TYPOGRAPHY.md +624 -0
- package/docs/components/ANIMATION_GUIDELINES.md +901 -0
- package/docs/components/COMPONENT_LIBRARY.md +1061 -0
- package/docs/components/GLASSMORPHISM.md +602 -0
- package/docs/components/INTERACTIVE_STATES.md +766 -0
- package/docs/governance/CONTRIBUTION_GUIDELINES.md +593 -0
- package/docs/governance/DESIGN_SYSTEM_GOVERNANCE.md +451 -0
- package/docs/governance/VERSION_MANAGEMENT.md +447 -0
- package/docs/governance/VERSION_REFERENCES.md +229 -0
- package/docs/platforms/COMPONENT_MAPPING.md +579 -0
- package/docs/platforms/NPM_PACKAGE.md +854 -0
- package/docs/platforms/WEB_IMPLEMENTATION.md +1221 -0
- package/docs/standards/ACCESSIBILITY.md +715 -0
- package/docs/standards/ANTI_PATTERNS.md +554 -0
- package/docs/standards/SPACING_SYSTEM.md +549 -0
- package/examples/button.html +1 -1
- package/examples/card.html +1 -1
- package/examples/form.html +1 -1
- package/examples/index.html +2 -2
- package/examples/layout.html +1 -1
- package/examples/nikke-team-builder.html +1 -1
- package/examples/showcase-complete.html +840 -15
- package/examples/showcase.html +1 -1
- package/package.json +16 -3
- package/src/css/components.css +676 -0
- package/src/lib/character-corruption.js +563 -0
- package/src/lib/components.js +283 -0
package/docs/ROADMAP.md
ADDED
|
@@ -0,0 +1,266 @@
|
|
|
1
|
+
# CelesteCLI Roadmap
|
|
2
|
+
|
|
3
|
+
This document tracks planned features, enhancements, and potential migrations for CelesteCLI.
|
|
4
|
+
|
|
5
|
+
## Current Status (December 2025)
|
|
6
|
+
|
|
7
|
+
### ✅ Completed
|
|
8
|
+
- Enterprise-grade RPG menu system with contextual help
|
|
9
|
+
- 18 AI-powered skills via function calling
|
|
10
|
+
- Multi-provider support (OpenAI, Grok, Venice, Anthropic, OpenRouter, DigitalOcean)
|
|
11
|
+
- Vertex AI support via OpenAI-compatible endpoint
|
|
12
|
+
- Session persistence and auto-save
|
|
13
|
+
- NSFW mode with Venice.ai image generation
|
|
14
|
+
- Context-aware /safe command
|
|
15
|
+
- Tool result filtering (hide raw JSON from UI)
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## Short-Term (Q1 2025)
|
|
20
|
+
|
|
21
|
+
### High Priority
|
|
22
|
+
|
|
23
|
+
#### 1. Vertex AI (Google Cloud) Setup Guide
|
|
24
|
+
- **Status**: Requires complex Google Cloud configuration
|
|
25
|
+
- **Goal**: Document complete Vertex AI setup for enterprise users
|
|
26
|
+
- **Provider Clarification**:
|
|
27
|
+
- **Gemini AI (AI Studio)**: Simple API keys ✅ READY
|
|
28
|
+
- **Vertex AI (Google Cloud)**: OAuth2 tokens, requires setup ⚠️ ENTERPRISE ONLY
|
|
29
|
+
|
|
30
|
+
**Vertex AI Requirements:**
|
|
31
|
+
1. **Google Cloud Project**: Active GCP project with billing enabled
|
|
32
|
+
2. **Vertex AI API**: Enable Vertex AI API in GCP console
|
|
33
|
+
3. **Service Account**: Create service account with `Vertex AI User` role
|
|
34
|
+
4. **Authentication**: Use OAuth2 tokens (NOT simple API keys)
|
|
35
|
+
5. **Token Management**: Tokens expire after 1 hour, need refresh mechanism
|
|
36
|
+
|
|
37
|
+
**Endpoint URL Format:**
|
|
38
|
+
```
|
|
39
|
+
https://aiplatform.googleapis.com/v1/projects/{PROJECT_ID}/locations/{LOCATION}/endpoints/openapi
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
**Configuration Example:**
|
|
43
|
+
```json
|
|
44
|
+
{
|
|
45
|
+
"api_key": "ya29.c.c0ASRK0Ga...", // OAuth2 access token
|
|
46
|
+
"base_url": "https://aiplatform.googleapis.com/v1/projects/my-project/locations/us-central1/endpoints/openapi",
|
|
47
|
+
"model": "gemini-2.0-flash",
|
|
48
|
+
"timeout": 60
|
|
49
|
+
}
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
**Token Generation (Go example):**
|
|
53
|
+
```go
|
|
54
|
+
import "golang.org/x/oauth2/google"
|
|
55
|
+
|
|
56
|
+
creds, _ := google.FindDefaultCredentials(ctx, "https://www.googleapis.com/auth/cloud-platform")
|
|
57
|
+
token, _ := creds.TokenSource.Token()
|
|
58
|
+
config.APIKey = token.AccessToken
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
**Why Most Users Should Use Gemini Instead:**
|
|
62
|
+
- Gemini AI: Simple API key from https://aistudio.google.com/apikey
|
|
63
|
+
- Vertex AI: Requires GCP project, billing, OAuth2 setup
|
|
64
|
+
- Both use same Gemini models, same function calling capabilities
|
|
65
|
+
- Vertex AI is for enterprise users with existing GCP infrastructure
|
|
66
|
+
|
|
67
|
+
- **Decision**: Gemini AI is the recommended provider for most users
|
|
68
|
+
|
|
69
|
+
#### 2. Improve Error Messaging
|
|
70
|
+
- **Goal**: Better error messages for common issues
|
|
71
|
+
- **Tasks**:
|
|
72
|
+
- [ ] API key validation on startup
|
|
73
|
+
- [ ] Clear messages for unsupported model features
|
|
74
|
+
- [ ] Network timeout handling with retry suggestions
|
|
75
|
+
- [ ] Configuration validation with fix suggestions
|
|
76
|
+
|
|
77
|
+
#### 3. Performance Optimization
|
|
78
|
+
- **Goal**: Reduce latency and improve responsiveness
|
|
79
|
+
- **Tasks**:
|
|
80
|
+
- [ ] Stream parsing optimization
|
|
81
|
+
- [ ] Reduce re-renders in TUI
|
|
82
|
+
- [ ] Cache provider model lists
|
|
83
|
+
- [ ] Lazy-load skill definitions
|
|
84
|
+
|
|
85
|
+
### Medium Priority
|
|
86
|
+
|
|
87
|
+
#### 4. Enhanced Skill Management
|
|
88
|
+
- **Goal**: Better skill discovery and usage
|
|
89
|
+
- **Tasks**:
|
|
90
|
+
- [ ] /skills menu shows skill descriptions on hover/selection
|
|
91
|
+
- [ ] Skill usage examples in help text
|
|
92
|
+
- [ ] Skill execution history (recent skills used)
|
|
93
|
+
- [ ] Skill favorites/pinning
|
|
94
|
+
|
|
95
|
+
#### 5. Configuration Management
|
|
96
|
+
- **Goal**: Easier config switching and management
|
|
97
|
+
- **Tasks**:
|
|
98
|
+
- [ ] /config list shows model details and capabilities
|
|
99
|
+
- [ ] /config test <profile> - test API connectivity
|
|
100
|
+
- [ ] Config templates for common providers
|
|
101
|
+
- [ ] Import/export config profiles
|
|
102
|
+
|
|
103
|
+
---
|
|
104
|
+
|
|
105
|
+
## Medium-Term (Q2-Q3 2025)
|
|
106
|
+
|
|
107
|
+
### Research & Evaluation
|
|
108
|
+
|
|
109
|
+
#### 6. Native Vertex AI SDK Migration (Option B)
|
|
110
|
+
- **Status**: Documented as potential enhancement
|
|
111
|
+
- **Trigger**: If Google deprecates OpenAI-compatible endpoint OR performance benefits are significant
|
|
112
|
+
- **Complexity**: MEDIUM (8-12 hours estimated)
|
|
113
|
+
- **Impact**: Better long-term stability, native Gemini features
|
|
114
|
+
|
|
115
|
+
**Migration Plan**:
|
|
116
|
+
|
|
117
|
+
##### Phase 1: Research & Prototyping (2-3 hours)
|
|
118
|
+
- [ ] Set up native genai SDK in test branch
|
|
119
|
+
- [ ] Prototype skill definition conversion (JSON → genai.FunctionDeclaration)
|
|
120
|
+
- [ ] Test response parsing (functionCall vs tool_calls)
|
|
121
|
+
- [ ] Benchmark performance vs OpenAI-compatible endpoint
|
|
122
|
+
|
|
123
|
+
##### Phase 2: Abstraction Layer (3-4 hours)
|
|
124
|
+
- [ ] Create provider abstraction interface
|
|
125
|
+
- [ ] Implement OpenAI provider adapter
|
|
126
|
+
- [ ] Implement native Gemini provider adapter
|
|
127
|
+
- [ ] Unified response format converter
|
|
128
|
+
|
|
129
|
+
##### Phase 3: Testing & Validation (2-3 hours)
|
|
130
|
+
- [ ] Test all 18 skills with native SDK
|
|
131
|
+
- [ ] Validate function calling accuracy
|
|
132
|
+
- [ ] Test multi-turn conversations
|
|
133
|
+
- [ ] Compare performance metrics
|
|
134
|
+
|
|
135
|
+
##### Phase 4: Migration (1-2 hours)
|
|
136
|
+
- [ ] Switch default Vertex AI provider to native SDK
|
|
137
|
+
- [ ] Update documentation
|
|
138
|
+
- [ ] Deprecation notice for OpenAI-compatible endpoint
|
|
139
|
+
|
|
140
|
+
**Code Structure Example**:
|
|
141
|
+
```go
|
|
142
|
+
// Future architecture with provider abstraction
|
|
143
|
+
|
|
144
|
+
type Provider interface {
|
|
145
|
+
SendMessage(ctx context.Context, messages []Message, tools []Tool) (*Response, error)
|
|
146
|
+
SupportsFunctionCalling() bool
|
|
147
|
+
ConvertSkillDefinition(skill SkillDefinition) interface{}
|
|
148
|
+
}
|
|
149
|
+
|
|
150
|
+
type OpenAIProvider struct {
|
|
151
|
+
client *openai.Client
|
|
152
|
+
}
|
|
153
|
+
|
|
154
|
+
type GeminiProvider struct {
|
|
155
|
+
client *genai.Client
|
|
156
|
+
}
|
|
157
|
+
|
|
158
|
+
// Skills remain unchanged - adapters handle conversion
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
**Decision Criteria**:
|
|
162
|
+
- Google announces deprecation of OpenAI endpoint → Migrate immediately
|
|
163
|
+
- Native SDK shows >20% performance improvement → Evaluate migration
|
|
164
|
+
- Native SDK enables exclusive features → Evaluate value vs effort
|
|
165
|
+
- Community reports OpenAI endpoint issues → Migrate proactively
|
|
166
|
+
|
|
167
|
+
**Resources**:
|
|
168
|
+
- [Google GenAI SDK Docs](https://pkg.go.dev/google.golang.org/genai)
|
|
169
|
+
- [Function Calling Guide](https://ai.google.dev/gemini-api/docs/function-calling)
|
|
170
|
+
- [Migration Guide](https://ai.google.dev/gemini-api/docs/migrate)
|
|
171
|
+
|
|
172
|
+
---
|
|
173
|
+
|
|
174
|
+
### Feature Enhancements
|
|
175
|
+
|
|
176
|
+
#### 7. Advanced Skill Features
|
|
177
|
+
- **Goal**: More powerful AI capabilities
|
|
178
|
+
- **Tasks**:
|
|
179
|
+
- [ ] Parallel skill execution (when LLM calls multiple)
|
|
180
|
+
- [ ] Skill chaining (output of one feeds another)
|
|
181
|
+
- [ ] Custom user-defined skills (plugin system)
|
|
182
|
+
- [ ] Skill templates and generators
|
|
183
|
+
|
|
184
|
+
#### 8. Conversation Management
|
|
185
|
+
- **Goal**: Better session handling
|
|
186
|
+
- **Tasks**:
|
|
187
|
+
- [ ] Named sessions (save/load by name)
|
|
188
|
+
- [ ] Session search (find past conversations)
|
|
189
|
+
- [ ] Session export (markdown, JSON)
|
|
190
|
+
- [ ] Session branching (fork conversation)
|
|
191
|
+
|
|
192
|
+
#### 9. Multi-Modal Support
|
|
193
|
+
- **Goal**: Beyond text interactions
|
|
194
|
+
- **Tasks**:
|
|
195
|
+
- [ ] Image input support (upload images for analysis)
|
|
196
|
+
- [ ] File attachment support
|
|
197
|
+
- [ ] Voice input/output (ElevenLabs integration)
|
|
198
|
+
- [ ] PDF parsing and analysis
|
|
199
|
+
|
|
200
|
+
---
|
|
201
|
+
|
|
202
|
+
## Long-Term (Q4 2025+)
|
|
203
|
+
|
|
204
|
+
### Major Features
|
|
205
|
+
|
|
206
|
+
#### 10. Team/Collaboration Features
|
|
207
|
+
- **Goal**: Multi-user support
|
|
208
|
+
- **Tasks**:
|
|
209
|
+
- [ ] Shared sessions
|
|
210
|
+
- [ ] Team workspaces
|
|
211
|
+
- [ ] Permission management
|
|
212
|
+
- [ ] Audit logs
|
|
213
|
+
|
|
214
|
+
#### 11. Cloud Sync
|
|
215
|
+
- **Goal**: Cross-device session sync
|
|
216
|
+
- **Tasks**:
|
|
217
|
+
- [ ] Optional cloud backup
|
|
218
|
+
- [ ] Encrypted session storage
|
|
219
|
+
- [ ] Device sync
|
|
220
|
+
- [ ] Web UI companion
|
|
221
|
+
|
|
222
|
+
#### 12. Advanced Analytics
|
|
223
|
+
- **Goal**: Usage insights
|
|
224
|
+
- **Tasks**:
|
|
225
|
+
- [ ] Token usage tracking
|
|
226
|
+
- [ ] Cost estimation per provider
|
|
227
|
+
- [ ] Skill usage analytics
|
|
228
|
+
- [ ] Performance metrics dashboard
|
|
229
|
+
|
|
230
|
+
---
|
|
231
|
+
|
|
232
|
+
## Deprecated/Archived
|
|
233
|
+
|
|
234
|
+
### Considered but Deferred
|
|
235
|
+
- **Local LLM support**: Complexity vs benefit ratio too high for v1
|
|
236
|
+
- **Browser extension**: Scope too large, focus on CLI first
|
|
237
|
+
- **Mobile app**: Desktop/terminal focus more valuable
|
|
238
|
+
|
|
239
|
+
---
|
|
240
|
+
|
|
241
|
+
## Contributing to Roadmap
|
|
242
|
+
|
|
243
|
+
This roadmap is living document. To propose additions:
|
|
244
|
+
|
|
245
|
+
1. Check existing items to avoid duplicates
|
|
246
|
+
2. Open GitHub issue with `[Roadmap]` prefix
|
|
247
|
+
3. Describe:
|
|
248
|
+
- Use case and problem being solved
|
|
249
|
+
- Estimated complexity (LOW/MEDIUM/HIGH)
|
|
250
|
+
- Impact on existing features
|
|
251
|
+
- User benefit
|
|
252
|
+
|
|
253
|
+
Priority is determined by:
|
|
254
|
+
- User requests and feedback
|
|
255
|
+
- Technical dependencies
|
|
256
|
+
- Maintenance burden
|
|
257
|
+
- Strategic value
|
|
258
|
+
|
|
259
|
+
---
|
|
260
|
+
|
|
261
|
+
## Version History
|
|
262
|
+
|
|
263
|
+
- **v0.1** (Dec 2025): Initial roadmap creation
|
|
264
|
+
- Enterprise menu system complete
|
|
265
|
+
- Vertex AI OpenAI-compatible endpoint implemented
|
|
266
|
+
- Native SDK migration documented as Option B
|