frontmcp-development

name	frontmcp-development
description	Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents (Anthropic, OpenAI) and swarms; @Job background jobs (retry, progress, permissions) and @Workflow DAG pipelines; framework adapters and the OpenAPI adapter (turn OpenAPI 3.x specs into MCP tools with auth, polling, transforms); plugins, plugin lifecycle hooks (before / after / around / stage), and the official plugins; instruction-only skills and skills that reference tools; and the hierarchical decorator system from @FrontMcp down to @App. Triggers: create a resource, build a prompt, write a provider, add an agent, job, workflow, plugin, adapter, or OpenAPI integration.
when_to_use	Trigger when creating or editing a non-tool FrontMCP component: a *.resource.ts, *.prompt.ts, *.provider.ts, *.agent.ts, *.job.ts, *.workflow.ts, *.plugin.ts, or *.skill.ts file, or adding @Resource, @Prompt, @Provider, @Agent, @Job, @Workflow, a plugin, an adapter, or an OpenAPI integration. For tools (*.tool.ts) use create-tool instead.
paths	**/*.resource.ts, **/*.prompt.ts, **/*.provider.ts, **/*.agent.ts, **/*.job.ts, **/*.workflow.ts, **/*.plugin.ts, **/*.skill.ts
tags	["router","development","tools","resources","prompts","agents","skills","guide"]
category	development
targets	["all"]
bundle	["recommended","minimal","full"]
priority	10
visibility	both
license	Apache-2.0
metadata	{"docs":"https://docs.agentfront.dev/frontmcp/fundamentals/overview"}

FrontMCP Development Router

Entry point for building MCP server components. This skill helps you find the right development reference based on what you want to build. It does not teach implementation details itself — it routes you to the specific reference (under references/) that does.

When to Use This Skill

Must Use

• Starting a FrontMCP development task and unsure which component type to build (tool vs resource vs prompt vs agent)
• Onboarding to the FrontMCP development model and need an overview of all building blocks
• Planning a feature that may require multiple component types working together

Recommended

• Looking up the canonical name of a development reference to install or search
• Comparing component types to decide which fits your use case
• Understanding how tools, resources, prompts, agents, and skills relate to each other

Skip When

• You already know which component to build (go directly to create-tool, create-resource, etc.)
• You need to configure server settings, not build components (see frontmcp-config)
• You need to deploy or build, not develop (see frontmcp-deployment)

Decision: Use this skill when you need to figure out WHAT to build. Open the matching reference under references/ directly when you already know.

Prerequisites

• A scaffolded FrontMCP project (see frontmcp-setup if you don't have one).
• Familiarity with TypeScript decorators and Zod schemas — every component is decorator-driven and validates I/O via Zod.
• Decide whether you're adding to an existing @App or composing a new one (multi-app projects: see multi-app-composition).

Steps

This is a router skill. The "steps" here are how to choose the right reference (a markdown file under references/), not how to implement a component.

1. Identify the component type using the Scenario Routing Table below.
2. Open the matching reference (e.g. references/create-tool.md, references/create-resource.md) and follow its Steps section.
3. Compose, if needed: most non-trivial features need two or more components (e.g. tool + provider, resource + adapter). Read each reference independently before wiring them together.