also run via Docker: `docker buildx bake lint` (uses version pinned in `Dockerfile`)
## Code Style
- Formatting is enforced by golangci-lint (gofumpt + gci)
- Import order: stdlib, third-party, local module
Follow di existing code style and patterns
- Add explanatory comments for complex logic
- Update relevant documentation
- Test changes across different lesson modules if e apply
- Review di CONTRIBUTING.md file
## Additional
they are defects authors agree
with on sight. Authors apply them **before writing code**, and reviewers check
against them; each cites the PRs where reviewers litigated it.
1. **Every caught
post to GitHub directly** — no comments, reviews, or replies. Draft when asked and hand the text to the user.
## Code formatting
- `make style` and `make fix-copies` should
intended behavior
differs from the existing spec, do not silently implement the code first:
discuss the change with maintainers and update the affected specs as part of
the design
path aliases: `@/*`, `@process/*`, `@renderer/*`
- Prefer `type` over `interface` (per Oxlint config)
- English for code comments; JSDoc for public functions
### Internationalization (i18n)
New or changed user-facing text must use i18n
party GitHub Actions to reviewed full commit SHAs. Minimize
job-level token permissions and never expose secrets or write-capable tokens
to untrusted pull-request code.
- Preserve separate build
must push
- If push fails, resolve and retry until it succeeds
## MCP Tools: code-review-graph
**This project has a knowledge graph. Start with the code-review-graph
MCP tools
projects that are not deployed on Vercel, greenfield projects with no traffic, or general codereview.
## Requirements
- Node.js 20+
- Vercel CLI with `vercel metrics`, `vercel usage`, `vercel contract`, and `vercel
other AI coding agents.
## Scope
This is the Composio SDK v3 monorepo. Most product code lives in `ts/` and `python/`; docs live in `docs/`. Branch new work from `next
docs-decisions` skill for docs content, changelogs, decisions, docs automation, or docs review.
- Context references live under `docs/agent-guidance/context/`; use `docs/agent-guidance/context/twoslash.md` before editing typed MDX examples.
- Agent workflow prompts live under
time context, not required startup reading.
- Treat source code and tests as authoritative. A brief's unknowns and review items are verification gaps, not automatic requirements.
- Prefer the narrowest quiet
before proceeding
### Phase 2: Implement
- Follow your plan step by step
- Write clean, idiomatic code that matches existing patterns
- Run tests after each significant change
- If tests fail, debug