#Money Project

Use this skill when working in the @teakit/money repository.

#Core Rules

1. Start with AGENTS.md, README.md, docs/knowledge/index.md, and docs/memory/index.md.
2. Keep README.md short and route deeper material to focused docs.
3. Put background and rationale in docs/knowledge/.
4. Distill stable decisions into docs/memory/.
5. Put version direction in docs/proposals/ and executable SDD contracts in docs/specs/.
6. Keep skills/llms.md and SKILL.md thin; put detailed API or concept docs in focused reference files when needed.
7. Document only real public APIs and supported workflows.
8. Update tests and docs when behavior, commands, config, runtime targets, or agent-facing usage changes.
9. Keep proposed money APIs in proposals or specs until implementation and tests exist.

#Workflow

1. Identify whether the task changes source code, public API, docs, commands, config, or project memory.
2. Read the smallest relevant source, test, doc, or skill file.
3. Make scoped changes that follow the existing project style.
4. Run relevant verification: bun run check, bun run typecheck, bun run test, bun run build.
5. For documentation site changes, also run bun run docs:build.
6. Summarize what changed and any verification that could not run.