arm64 # Build for macOS (Apple Silicon only)
pnpm build:linux # Build for Linux
```
### Testing
```bash
pnpm test # Run Playwright tests
pnpm test:ui # Run tests with Playwright UI
pnpm test
Development Rules
### Commit Messages
Follow [Conventional Commits](https://www.conventionalcommits.org/): `feat:` / `fix:` / `docs:` / `refactor:` / `test:` / `chore:`
### Version Management
Keep all version surfaces in sync via `./scripts/sync-version.sh` (the script
Streamable HTTP.
## Setup and validation
Use the locked uv environment:
```bash
uv sync --extra test --extra dev
uv run black --check .
uv run pytest
```
Apply formatting with:
```bash
evaluation format (used by generate) |
| `uv run agent-eval create-dataset` | Convert ADK test files to golden dataset format |
| `uv run agent-eval dashboard` | Launch interactive Gradio dashboard for comparing
skills add jakubkrehel/make-interfaces-feel-better`. It is documentation-only; there is no build, lint, or test tooling.
## Structure
The skill lives in `skills/make-interfaces-feel-better/`:
- `SKILL.md` is the entry point. Its YAML frontmatter contains
official IDE extensions. Built with pure Lua and zero dependencies.
## Common Development Commands
### Testing
- `mise run test` - Run all tests using busted with coverage
- `busted tests/unit/specific_spec.lua` - Run specific test file
NETWORK_CLIENT_BRIDGES`. Third-party Jev
plugins are still never called.
## Build & Test
```sh
PYTHONPATH=tests uv run python -m unittest discover -s tests -v # full suite
PYTHONPATH=tests
commands from the root.
## Model Selection
When you name a model anywhere (examples, defaults, tests), use a **current** generation —
newer beats biggest. The provider enums are the source of truth
docs/`: `safety.md`, `backends.md`, `deployment.md`. `scripts/`: install, demo, smoke, screenshots, check, deploy, verify.
- `tests/`: the suites that span packages (both roles on all three paths); each package keeps its own `tests
custom APIs
- **instructions-writer**: Write optimized instructions using prompt engineering best practices
- **qa-tester**: Test agents with actual interactions and tool validation
## Orchestration Responsibilities
1. **User Clarification**: Ask questions
only when explicitly needed.
- Never touch the user's real `~/.ccs/` or `~/.claude/` in tests. Use
`getCcsDir()` from `src/utils/config-manager.ts`; it respects `CCS_HOME`.
- Do not commit directly
files are stored in `skill-packages/` and should be regenerated after any skill modifications.
### Testing Skills
Skills are tested by invoking them in Claude Code conversations:
1. Copy skill folder
only
make run # Run the bot
make run-debug # Run with debug logging
make test # Run tests with coverage
make lint # Black + isort + flake8 + mypy
make format # Auto-format with
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.