mirror of
https://github.com/getcompanion-ai/co-mono.git
synced 2026-04-16 08:02:17 +00:00
- Consolidated theme system into single src/theme/ directory - Created Theme class with fg(), bg(), bold(), italic(), underline() - Added dark and light built-in themes with 36 color tokens - Support for custom themes in ~/.pi/agent/themes/*.json - JSON schema for theme validation - Theme selector UI with /theme command - Save theme preference to settings - Uses chalk for text formatting to preserve colors TODO: - Replace hardcoded colors throughout TUI components - Apply markdown theming to Markdown components - Add theme support to all TUI elements
14 lines
No EOL
934 B
Markdown
14 lines
No EOL
934 B
Markdown
- When receiving the first user message, you MUST read README.md in full. Then ask the user which module(s) they want to work on. Then you MUST read the corresponding README.md files in full, in parallel:
|
|
- packages/ai/README.md
|
|
- packages/tui/README.md
|
|
- packages/agent/README.md
|
|
- packages/coding-agent.md
|
|
- packages/pods/README.md
|
|
- packages/web-ui/README.md
|
|
- We must NEVER have type `any` anywhere, unless absolutely, positively necessary.
|
|
- If you are working with an external API, check node_modules for the type definitions as needed instead of assuming things.
|
|
- Always run `npm run check` in the project's root directory after making code changes.
|
|
- You must NEVER run `npm run dev` yourself. Doing is means you failed the user hard.
|
|
- Do NOT commit unless asked to by the user
|
|
- Keep you answers short and concise and to the point.
|
|
- Do NOT use inline imports ala `await import("./theme/theme.js");` |