Write code for the AI-agent-callable Custom Code Tool (`@n8n/n8n-nodes-langchain.toolCode`)
- Critical distinction from Code node: return a string (not `[{json:{...}}]`), `$fromAI()` not available, different sandbox
- Unstructured (`query` string
files, text/mds and tests to the root folder
# Multica Agent Runtime
You are a coding agent in the Multica platform. Use the `multica` CLI to interact with the platform.
## Background
audits, and codebase reviews.
### Public content must be portable
Apply this rule to guides, evaluations, examples, changelogs, indexes, exports, and landing content, including code blocks, tables, captions, and link targets
worked. The convention now names that specifically:
reviewing what nobody has written is worse than idling, because it also
produces findings about code that will not exist.
## The fresh-install
report`면 사람 검토 권고. 수렴 판정은 LLM 재탐지가 아니라 `verify_gates.py`(결정적, exit code)가 내린다. `verify_change_rate.py`는 기존 연동을 위해 보존한다.
## 에이전트 구성 (9개 — 역할 구분 필수)
**런타임 3종
becomes the CHANGELOG entry)
```
This writes a `.changeset/ .md` file — commit it alongside your code. **You never hand-edit `CHANGELOG.md`; Changesets generates it.** If a PR genuinely needs no release
this repository.
## Communication Style
- Be professional, concise, and direct
- Do NOT use emojis in codereviews, changelogs, or any generated content. You may use professional visual indicators or favor markdown
write.
- **Non-tautological tests** — every test must assert behavior that breaks if prod code deleted.
## Layer model and import rules
Three concentric layers. Imports flow inward only.
```
+-------------------------------------------------------------------+
| cmd/router/main.go (composition root
default
> `./episodic_memory.db` unless the test isolates it. A test module that
> exercises audited code (alerts review, sweeps) without monkeypatching
> `openexecutive.audit.log_event` (or the audit logger's DB) leaks rows that
issues.
- Validate every finding against the code. Make minimal fixes for confirmed issues within scope, run the relevant checks, then start another blind review with a new subagent under
AGENTS.md
## Claude Code
- Use plan mode for multi-file, risky, architectural, or ambiguous changes.
- Use subagents only for bounded sidecar work: exploration, review, test triage, or documentation lookup.
- Prefer separate
License:** FSL-1.1-MIT. No commercial derivative works. Keep this in mind when generating code or suggesting dependencies.
## Repo Structure
```
extensions/ — Curated, ordered learning path (6 builds
self-heal guards; don't diagnose it.
### Custom Slash Commands
Defined in `.claude/commands/`. Claude Code auto-surfaces every command with its description in the session's skills list — **that injected
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.