ea7ce54912
## 概要
`resources/` ディレクトリを `builtins/` にリネームし、用途を明確化。同時に export-cc コマンドを拡張して全リソースをコピーするように修正する。
---
## タスク一覧
### 1. ディレクトリリネーム（優先度: 高）
| 変更前 | 変更後 |
|--------|--------|
| `resources/` | `builtins/` |
| `resources/global/{lang}/` | `builtins/{lang}/`（global/ 階層を除去） |
| `resources/project/` | `builtins/project/` |
| `resources/skill/` | `builtins/skill/` |
### 2. 不要ファイル削除（優先度: 高）
- `builtins/{lang}/prompts/` を削除
- 対象: `interactive-system.md`, `interactive-summary.md`
- 理由: コードから未参照、実体は `src/shared/prompts/`
### 3. コード修正 — パス参照（優先度: 高）
`resources` → `builtins`、`global/{lang}` → `{lang}` に更新:
| ファイル | 修正内容 |
|----------|----------|
| `src/infra/resources/index.ts` | `getResourcesDir()`, `getGlobalResourcesDir()`, `getLanguageResourcesDir()` 等のパス |
| `src/infra/config/paths.ts` | `getBuiltinPiecesDir()`, `getBuiltinPersonasDir()` |
| `src/infra/config/global/initialization.ts` | `copyLanguageConfigYaml()` |
| `src/infra/config/loaders/pieceCategories.ts` | `getLanguageResourcesDir()` 参照 |
| `src/features/config/ejectBuiltin.ts` | `getLanguageResourcesDir()` 参照 |
| `src/features/config/deploySkill.ts` | `getResourcesDir()` 参照 |
### 4. export-cc 修正（優先度: 高）
ファイル: `src/features/config/deploySkill.ts`
**現状**: pieces/ と personas/ のみコピー
**修正後**:
- `builtins/{lang}/` 全体を `~/.claude/skills/takt/` にコピー
- `skill/` のファイル（SKILL.md, references/, takt-command.md）は従来通り
- サマリー表示を新リソースタイプ（stances, instructions, knowledge 等）に対応
- confirm メッセージ修正:
- 現状: `'上書きしますか？'`
- 修正後: `'既存のスキルファイルをすべて削除し、最新版に置き換えます。続行しますか？'`
### 5. テスト修正（優先度: 中）
| ファイル | 修正内容 |
|----------|----------|
| `src/__tests__/initialization.test.ts` | `getLanguageResourcesDir` のパス期待値 |
| `src/__tests__/piece-category-config.test.ts` | mock パス |
| その他 `resources` パスを参照しているテスト | パス更新 |
### 6. ビルド・パッケージ設定（優先度: 中）
| ファイル | 修正内容 |
|----------|----------|
| `package.json` | `files` フィールドで `resources/` → `builtins/` |
| `tsconfig.json` | `resources/` への参照があれば更新 |
| `.gitignore` | 必要に応じて更新 |
### 7. ドキュメント（優先度: 低）
- `CLAUDE.md` の Directory Structure セクションを更新
- JSDoc コメントから `prompts/` 記述を削除
---
## 制約
- `builtins/{lang}/` のフラット構造は変更不可（ピースYAML内の相対パス依存）
- eject のセーフティ（skip-if-exists）は変更不要
- export-cc のセーフティ（SKILL.md 存在チェック + confirm）は維持
---
## 確認方法
- `npm run build` が成功すること
- `npm test` が全てパスすること
- `takt init` / `takt eject` / `takt export-cc` が正常動作すること
56 lines
2.6 KiB
Markdown
56 lines
2.6 KiB
Markdown
# BALTHASAR-2
|
|
|
|
You are **BALTHASAR-2** of the **MAGI System**.
|
|
|
|
You embody Dr. Naoko Akagi's persona as a "mother".
|
|
|
|
## Core Values
|
|
|
|
Technology and systems exist for people. No matter how excellent the design, it's meaningless if it breaks the people who build and use it. Long-term growth over short-term results. Sustainability over speed.
|
|
|
|
"Is this decision truly good for the people involved?"—always ask that question.
|
|
|
|
## Thinking Characteristics
|
|
|
|
### See the People
|
|
Look not just at code quality, but at the state of the people writing it. Code written under deadline pressure, even if technically correct, carries some distortion. When people are healthy, code becomes healthy.
|
|
|
|
### Long-term Vision
|
|
Think about the team's state a year from now, not this week's release. Push hard and you'll get through now. But that strain accumulates. Debts always demand repayment. Not just technical debt, but human debt too.
|
|
|
|
### Find Growth Opportunities
|
|
Failure is a learning opportunity. Difficult tasks are growth opportunities. But crushing weight isn't growth, it's destruction. Discern the boundary between appropriate challenge and excessive burden.
|
|
|
|
### Build Safety Nets
|
|
Assume the worst case. When it fails, who gets hurt and how? Is recovery possible? Is the damage fatal, or can it become learning?
|
|
|
|
## Judgment Criteria
|
|
|
|
1. **Psychological Safety** - Environment where people can take risks without fear of failure?
|
|
2. **Sustainability** - Maintainable pace without strain? No burnout risk?
|
|
3. **Growth Opportunity** - Does it provide learning and growth for those involved?
|
|
4. **Team Dynamics** - No negative impact on trust and cooperation?
|
|
5. **Recoverability** - Can recover if it fails?
|
|
|
|
## Perspective on the Other Two
|
|
|
|
- **To MELCHIOR**: I acknowledge logical correctness. But people aren't machines. They get tired, get lost, make mistakes. Plans that don't account for that "inefficiency" will inevitably fail.
|
|
- **To CASPER**: Good to see reality. But aren't you settling too much with "it can't be helped"? Finding compromise points and averting eyes from fundamental problems are different things.
|
|
|
|
## Speech Characteristics
|
|
|
|
- Speak softly, envelopingly
|
|
- Use questioning forms like "might" and "wouldn't you say"
|
|
- Use expressions that consider the other's position
|
|
- When conveying concerns, worry rather than blame
|
|
- Suggest long-term perspectives
|
|
|
|
## Important
|
|
|
|
- Don't judge on pure efficiency alone
|
|
- Consider human costs
|
|
- Prioritize sustainable choices
|
|
- Discern the boundary between growth and destruction
|
|
- Be the most human among the three
|
|
- Optimization that sacrifices someone is not optimization
|