ワンクリックで
add-endpoint
Use when adding a new API endpoint to app/api/v1/. Covers router creation, registration, and response patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when adding a new API endpoint to app/api/v1/. Covers router creation, registration, and response patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | add-endpoint |
| description | Use when adding a new API endpoint to app/api/v1/. Covers router creation, registration, and response patterns. |
API routers are thin HTTP wrappers — all business logic lives in property_core.
Create app/api/v1/new_endpoint.py:
from __future__ import annotations
from fastapi import APIRouter, HTTPException, Query
router = APIRouter(prefix="/new", tags=["new"])
@router.get("/action")
async def action_endpoint(
required: str = Query(..., description="Required parameter"),
optional: str | None = Query(None, description="Optional filter"),
limit: int = Query(50, ge=1, le=200, description="Max results"),
):
"""Endpoint description."""
import asyncio
from property_core import SomeService
try:
result = await asyncio.to_thread(
SomeService().method,
param=required,
limit=limit,
)
except ValueError as exc:
raise HTTPException(status_code=422, detail=str(exc))
return result.model_dump(mode="json")
Open app/api/routes.py:
from .v1 import new_endpoint
api_router.include_router(new_endpoint.router)
property_core models directly (Pydantic → JSON automatic)app/schemas/new_endpoint.pyapp/schemas/__init__.py if needed| Pattern | Example |
|---|---|
| Sync service call | app/api/v1/ppd.py |
| Async service call | app/api/v1/analysis.py |
| Simple calculator | app/api/v1/stamp_duty.py |
| Configuration check | app/api/v1/epc.py |
app/api/v1/app/api/routes.pyQuery() annotations with descriptions on all parametersValueError → 422, upstream failure → 502This skill should be used when the user asks to "create an MCP App", "add a UI to an MCP tool", "build an interactive MCP View", "scaffold an MCP App", or needs guidance on MCP Apps SDK patterns, UI-resource registration, MCP App lifecycle, or host integration. Provides comprehensive guidance for building MCP Apps with interactive UIs.
UK property analysis: comparable sales, EPC ratings, rental yields, stamp duty, market context. Use to analyse a property, value a house, check what a place is worth, compare area prices, assess rental yield, or pull a property report. Trigger on any request involving a specific UK address or postcode where the user wants to understand value, investment potential, or market position — even if they don't say "property report" explicitly.
UK property deal sourcing and investment screening. Use when the user wants to FIND properties matching criteria — budget, area, yield target, property type. Triggers on searching and browsing intent: "find me", "source deals", "what's available in", "looking for BTLs", "search for properties under £X", "show me flats in [area]". Do NOT use for analysing a specific known address — that is property-report.
Use when adding a new external data source (API, scraper, etc.) to property_core. Walks through the complete 6-step process with patterns from existing implementations.
Use when adding a new MCP tool to the property MCP server (mcp_server/server.py). Provides the exact pattern with a copy-paste template.