{"owner":"BloopAI","repo":"vibe-kanban","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Repository Guidelines\n\n## Project Structure & Module Organization\n- `crates/`: Rust workspace crates — `server` (API + bins), `db` (SQLx models/migrations), `executors`, `services`, `utils`, `git` (Git operations), `api-types` (shared API types for local + remote), `review` (PR review tool), `deployment`, `local-deployment`, `remote`.\n- `packages/local-web/`: Local React + TypeScript app entrypoint (Vite, Tailwind). Shell source in `packages/local-web/src`.\n- `packages/remote-web/`: Remote deployment frontend entrypoint.\n- `packages/web-core/`: Shared React + TypeScript frontend library used by local + remote web (`packages/web-core/src`).\n- `shared/`: Generated TypeScript types (`shared/types.ts`, `shared/remote-types.ts`) and agent tool schemas (`shared/schemas/`). Do not edit generated files directly.\n- `assets/`, `dev_assets_seed/`, `dev_assets/`: Packaged and local dev assets.\n- `npx-cli/`: Files published to the npm CLI package.\n- `scripts/`: Dev helpers (ports, DB preparation).\n- `docs/`: Documentation files.\n\n### Crate-specific guides\n- [`crates/remote/AGENTS.md`](crates/remote/AGENTS.md) — Remote server architecture, ElectricSQL integration, mutation patterns, environment variables.\n- [`docs/AGENTS.md`](docs/AGENTS.md) — Mintlify documentation writing guidelines and component reference.\n- [`packages/local-web/AGENTS.md`](packages/local-web/AGENTS.md) — Web app design system styling guidelines.\n\n## Managing Shared Types Between Rust and TypeScript\n\nts-rs allows you to derive TypeScript types from Rust structs/enums. By annotating your Rust types with #[derive(TS)] and related macros, ts-rs will generate .ts declaration files for those types.\nWhen making changes to the types, you can regenerate them using `pnpm run generate-types`\nDo not manually edit shared/types.ts, instead edit crates/server/src/bin/generate_types.rs\n\nFor remote/cloud types, regenerate using `pnpm run remote:generate-types`\nDo not manually edit shared/remote-types.ts, instead edit crates/remote/src/bin/remote-generate-types.rs (see crates/remote/AGENTS.md for details).\n\n## Build, Test, and Development Commands\n- Install: `pnpm i`\n- Run dev (web app + backend with ports auto-assigned): `pnpm run dev`\n- Backend (watch): `pnpm run backend:dev:watch`\n- Web app (dev): `pnpm run local-web:dev`\n- Type checks: `pnpm run check` (frontend + all backend Rust workspaces) and `pnpm run backend:check` (all backend Rust workspaces, including `crates/remote`)\n- Rust tests: `cargo test --workspace`\n- Generate TS types from Rust: `pnpm run generate-types` (or `generate-types:check` in CI)\n- Prepare SQLx (offline): `pnpm run prepare-db`\n- Prepare SQLx (remote package, postgres): `pnpm run remote:prepare-db`\n- Local NPX build: `pnpm run build:npx` then `pnpm pack` in `npx-cli/`\n- Format code: `pnpm run format` (runs `cargo fmt` for all backend Rust workspaces + web-core/web Prettier)\n- Lint: `pnpm run lint` (runs web/ui ESLint + `cargo clippy` for all backend Rust workspaces)\n\n## Before Completing a Task\n- Run `pnpm run format` to format all Rust workspaces and web code.\n\n## Coding Style & Naming Conventions\n- Rust: `rustfmt` enforced (`rustfmt.toml`); group imports by crate; snake_case modules, PascalCase types.\n- TypeScript/React: ESLint + Prettier (2 spaces, single quotes, 80 cols). PascalCase components, camelCase vars/functions, kebab-case file names where practical.\n- Keep functions small, add `Debug`/`Serialize`/`Deserialize` where useful.\n\n## Testing Guidelines\n- Rust: prefer unit tests alongside code (`#[cfg(test)]`), run `cargo test --workspace`. Add tests for new logic and edge cases.\n- Web app: ensure `pnpm run check` and `pnpm run lint` pass. If adding runtime logic, include lightweight tests (e.g., Vitest) in the same directory.\n\n## Security & Config Tips\n- Use `.env` for local overrides; never commit secrets. Key envs: `FRONTEND_PORT`, `BACKEND_PORT`, `HOST` \n- Dev ports and assets are managed by `scripts/setup-dev-environment.js`.\n\n\n"},"files":{"AGENTS.md":"# Repository Guidelines\n\n## Project Structure & Module Organization\n- `crates/`: Rust workspace crates — `server` (API + bins), `db` (SQLx models/migrations), `executors`, `services`, `utils`, `git` (Git operations), `api-types` (shared API types for local + remote), `review` (PR review tool), `deployment`, `local-deployment`, `remote`.\n- `packages/local-web/`: Local React + TypeScript app entrypoint (Vite, Tailwind). Shell source in `packages/local-web/src`.\n- `packages/remote-web/`: Remote deployment frontend entrypoint.\n- `packages/web-core/`: Shared React + TypeScript frontend library used by local + remote web (`packages/web-core/src`).\n- `shared/`: Generated TypeScript types (`shared/types.ts`, `shared/remote-types.ts`) and agent tool schemas (`shared/schemas/`). Do not edit generated files directly.\n- `assets/`, `dev_assets_seed/`, `dev_assets/`: Packaged and local dev assets.\n- `npx-cli/`: Files published to the npm CLI package.\n- `scripts/`: Dev helpers (ports, DB preparation).\n- `docs/`: Documentation files.\n\n### Crate-specific guides\n- [`crates/remote/AGENTS.md`](crates/remote/AGENTS.md) — Remote server architecture, ElectricSQL integration, mutation patterns, environment variables.\n- [`docs/AGENTS.md`](docs/AGENTS.md) — Mintlify documentation writing guidelines and component reference.\n- [`packages/local-web/AGENTS.md`](packages/local-web/AGENTS.md) — Web app design system styling guidelines.\n\n## Managing Shared Types Between Rust and TypeScript\n\nts-rs allows you to derive TypeScript types from Rust structs/enums. By annotating your Rust types with #[derive(TS)] and related macros, ts-rs will generate .ts declaration files for those types.\nWhen making changes to the types, you can regenerate them using `pnpm run generate-types`\nDo not manually edit shared/types.ts, instead edit crates/server/src/bin/generate_types.rs\n\nFor remote/cloud types, regenerate using `pnpm run remote:generate-types`\nDo not manually edit shared/remote-types.ts, instead edit crates/remote/src/bin/remote-generate-types.rs (see crates/remote/AGENTS.md for details).\n\n## Build, Test, and Development Commands\n- Install: `pnpm i`\n- Run dev (web app + backend with ports auto-assigned): `pnpm run dev`\n- Backend (watch): `pnpm run backend:dev:watch`\n- Web app (dev): `pnpm run local-web:dev`\n- Type checks: `pnpm run check` (frontend + all backend Rust workspaces) and `pnpm run backend:check` (all backend Rust workspaces, including `crates/remote`)\n- Rust tests: `cargo test --workspace`\n- Generate TS types from Rust: `pnpm run generate-types` (or `generate-types:check` in CI)\n- Prepare SQLx (offline): `pnpm run prepare-db`\n- Prepare SQLx (remote package, postgres): `pnpm run remote:prepare-db`\n- Local NPX build: `pnpm run build:npx` then `pnpm pack` in `npx-cli/`\n- Format code: `pnpm run format` (runs `cargo fmt` for all backend Rust workspaces + web-core/web Prettier)\n- Lint: `pnpm run lint` (runs web/ui ESLint + `cargo clippy` for all backend Rust workspaces)\n\n## Before Completing a Task\n- Run `pnpm run format` to format all Rust workspaces and web code.\n\n## Coding Style & Naming Conventions\n- Rust: `rustfmt` enforced (`rustfmt.toml`); group imports by crate; snake_case modules, PascalCase types.\n- TypeScript/React: ESLint + Prettier (2 spaces, single quotes, 80 cols). PascalCase components, camelCase vars/functions, kebab-case file names where practical.\n- Keep functions small, add `Debug`/`Serialize`/`Deserialize` where useful.\n\n## Testing Guidelines\n- Rust: prefer unit tests alongside code (`#[cfg(test)]`), run `cargo test --workspace`. Add tests for new logic and edge cases.\n- Web app: ensure `pnpm run check` and `pnpm run lint` pass. If adding runtime logic, include lightweight tests (e.g., Vitest) in the same directory.\n\n## Security & Config Tips\n- Use `.env` for local overrides; never commit secrets. Key envs: `FRONTEND_PORT`, `BACKEND_PORT`, `HOST` \n- Dev ports and assets are managed by `scripts/setup-dev-environment.js`.\n\n\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Repository Guidelines\n\n## Project Structure & Module Organization\n- `crates/`: Rust workspace crates — `server` (API + bins), `db` (SQLx models/migrations), `executors`, `services`, `utils`, `git` (Git operations), `api-types` (shared API types for local + remote), `review` (PR review tool), `deployment`, `local-deployment`, `remote`.\n- `packages/local-web/`: Local React + TypeScript app entrypoint (Vite, Tailwind). Shell source in `packages/local-web/src`.\n- `packages/remote-web/`: Remote deployment frontend entrypoint.\n- `packages/web-core/`: Shared React + TypeScript frontend library used by local + remote web (`packages/web-core/src`).\n- `shared/`: Generated TypeScript types (`shared/types.ts`, `shared/remote-types.ts`) and agent tool schemas (`shared/schemas/`). Do not edit generated files directly.\n- `assets/`, `dev_assets_seed/`, `dev_assets/`: Packaged and local dev assets.\n- `npx-cli/`: Files published to the npm CLI package.\n- `scripts/`: Dev helpers (ports, DB preparation).\n- `docs/`: Documentation files.\n\n### Crate-specific guides\n- [`crates/remote/AGENTS.md`](crates/remote/AGENTS.md) — Remote server architecture, ElectricSQL integration, mutation patterns, environment variables.\n- [`docs/AGENTS.md`](docs/AGENTS.md) — Mintlify documentation writing guidelines and component reference.\n- [`packages/local-web/AGENTS.md`](packages/local-web/AGENTS.md) — Web app design system styling guidelines.\n\n## Managing Shared Types Between Rust and TypeScript\n\nts-rs allows you to derive TypeScript types from Rust structs/enums. By annotating your Rust types with #[derive(TS)] and related macros, ts-rs will generate .ts declaration files for those types.\nWhen making changes to the types, you can regenerate them using `pnpm run generate-types`\nDo not manually edit shared/types.ts, instead edit crates/server/src/bin/generate_types.rs\n\nFor remote/cloud types, regenerate using `pnpm run remote:generate-types`\nDo not manually edit shared/remote-types.ts, instead edit crates/remote/src/bin/remote-generate-types.rs (see crates/remote/AGENTS.md for details).\n\n## Build, Test, and Development Commands\n- Install: `pnpm i`\n- Run dev (web app + backend with ports auto-assigned): `pnpm run dev`\n- Backend (watch): `pnpm run backend:dev:watch`\n- Web app (dev): `pnpm run local-web:dev`\n- Type checks: `pnpm run check` (frontend + all backend Rust workspaces) and `pnpm run backend:check` (all backend Rust workspaces, including `crates/remote`)\n- Rust tests: `cargo test --workspace`\n- Generate TS types from Rust: `pnpm run generate-types` (or `generate-types:check` in CI)\n- Prepare SQLx (offline): `pnpm run prepare-db`\n- Prepare SQLx (remote package, postgres): `pnpm run remote:prepare-db`\n- Local NPX build: `pnpm run build:npx` then `pnpm pack` in `npx-cli/`\n- Format code: `pnpm run format` (runs `cargo fmt` for all backend Rust workspaces + web-core/web Prettier)\n- Lint: `pnpm run lint` (runs web/ui ESLint + `cargo clippy` for all backend Rust workspaces)\n\n## Before Completing a Task\n- Run `pnpm run format` to format all Rust workspaces and web code.\n\n## Coding Style & Naming Conventions\n- Rust: `rustfmt` enforced (`rustfmt.toml`); group imports by crate; snake_case modules, PascalCase types.\n- TypeScript/React: ESLint + Prettier (2 spaces, single quotes, 80 cols). PascalCase components, camelCase vars/functions, kebab-case file names where practical.\n- Keep functions small, add `Debug`/`Serialize`/`Deserialize` where useful.\n\n## Testing Guidelines\n- Rust: prefer unit tests alongside code (`#[cfg(test)]`), run `cargo test --workspace`. Add tests for new logic and edge cases.\n- Web app: ensure `pnpm run check` and `pnpm run lint` pass. If adding runtime logic, include lightweight tests (e.g., Vitest) in the same directory.\n\n## Security & Config Tips\n- Use `.env` for local overrides; never commit secrets. Key envs: `FRONTEND_PORT`, `BACKEND_PORT`, `HOST` \n- Dev ports and assets are managed by `scripts/setup-dev-environment.js`.\n\n\n","category":"root","tokens":996}]}