Fentaris App Development

Use this skill when working inside an external application that already uses Fentaris.

Core Workflow

1. Inspect before editing:
   • Locate fentaris.json, src/index.ts, package scripts, package manager lockfile, env examples, tests, and docs.
   • Identify whether the app was generated by fentaris init or embeds @fentaris/core inside a larger app.
   • Check the installed Fentaris version and CLI help when changing auth or custom capability behavior; Fentaris CLI 1.1.0 added supported local user API-key commands.
   • Preserve existing style, module boundaries, and runtime assumptions.
2. Read references/api-guidance.md before choosing APIs or imports.
3. Read references/common-changes.md for upstreams, local/custom MCP capabilities, policies, users/groups, middleware, hooks, secrets, API keys, and endpoint changes.
4. Prefer high-level @fentaris/core application builders and declaration helpers, including app.mcp(...) for upstreams and app.local(...) for custom/local MCP capabilities. Use advanced low-level proxy/transport APIs only when the user explicitly requests direct wiring or the existing app already uses them.
5. If behavior is uncertain or version-sensitive, consult https://fentaris.mintlify.app or local Fentaris docs when available before implementing.
6. Implement the smallest coherent change. Update related config, env examples, tests, and local docs when the change affects them.
7. Read references/validation.md and run focused validation. Prefer fentaris check --offline, fentaris doctor, package scripts, and runtime checks when relevant.
8. Do not recommend deploy as available. Fentaris deploy is not implemented yet; keep changes deploy-ready and mention that the CLI is expected to provide a smoother deploy path later when that matters.