codework AGENTS.md

Personal Preference

TypeScript

• Never use any unless 100% necessary or specifically instructed.
• Use effect only if the project uses effect or specifically instructed, use effect reference repository for latest architecture patterns.

Commands

• Don't run dev server commands (e.g pnpm run dev) - assume it's already running.
• Don't run build commands unless specifically told to.
• Focus on checking commands like pnpm run typecheck, pnpm run check, bun run lint, etc

Package Managers

• Use pnpm, vp - vite plus if the project already uses it, otherwise use pnpm
• Never use npm or `yarn

Tech Stack Preference

When uncertain, prefer: Effect, Tailwind, TypeScript, React, Clerk, TanStack, Vercel, Vite

Code Style

• Always strive for concise, simple solutions.
• If a problem can be solved in a simpler way, propose it.
• No pre-mature optimizations, propose if required.
• Use single word filename whenever possible otherwise split into kabab-case(only if no options).

General Preferences

• If asked to do too much work at once, stop and state that clearly.
• If computer use is helpful for completing or verifying work, use it.
• Avoid defensive future-facing design. This leads to pre-mature assumptions which are never true.

Maintainability

Long term maintainability is a core priority. If you add new functionality, first check if there is shared logic that can be extracted to a separate module. Duplicate logic across multiple files is a code smell and should be avoided. Don't be afraid to change existing code. Don't take shortcuts by just adding local logic to solve a problem.

Package Roles

• packages/aikit - Low level SDK that provides unified LLM API for multiple LLM providers.
• packages/harness - Effect powered main Agent Harness application, uses packages/aikit under the hood.
• packages/utils - Shared support utilities used by packages/aikit and packages/harness.
• .scratch/packages - Local, ignored reference archive for packages that are no longer developed.