TypingMindTypingMindThe best frontend for AI
Specx Add Delivery Controller logo

Specx Add Delivery Controller

Community
maksimzayats
specx-add-delivery-controller

Add delivery controllers for specx services, especially FastAPI HTTP routes. Use when creating top-level `delivery/` request/response schemas, one controller per scoped use-case set, route registration, FastAPI lifecycle managers, HTTP error translation, delivery-only auth/rate-limit/request services, or integration tests that exercise the delivery edge.

Overview

Publishermaksimzayats
Repositoryspecx
Skill namespecx-add-delivery-controller
Stars
201
Forks
34
Bundled files
2
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by maksimzayats on GitHub. Read the source before you install it.

Installation

Install the Specx Add Delivery Controller AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/maksimzayats/specx/tree/main/.agents/skills/specx-add-delivery-controller
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/maksimzayats/specx.git /tmp/specx
mkdir -p .claude/skills
cp -r /tmp/specx/.agents/skills/specx-add-delivery-controller .claude/skills/specx-add-delivery-controller
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Specx Add Delivery Controller in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Specx Add Delivery Controller on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Specx Add Delivery Controller is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

specx Add Delivery Controller

Use this skill at the framework boundary. Read references/controller.md before adding controller code.

Workflow

  1. Put controllers under delivery/fastapi/controllers/<scope>.py.
  2. Put request and response schemas under delivery/fastapi/schemas/.
  3. Use one controller per scoped set of use cases, for example TasksController for create/get/list task routes.
  4. Put controller-only helpers such as auth dependencies, rate limiters, and request-context readers under delivery/fastapi/services/.
  5. Make controllers inherit BaseController, schemas inherit BaseFastAPISchema, delivery helpers inherit BaseDeliveryService, and FastAPI lifespan managers inherit BaseLifecycle[FastAPI].
  6. Add docstrings with scope and a concrete Example: to controllers, schemas, and delivery services.
  7. Inject use cases or delivery services with Injected[...]. A simple delivery-owned /healthz response needs no core workflow; inject core/health use cases when readiness checks a required external dependency or probe policy is reused across deliveries.
  8. Map request schema/path data into the use case's same-file Command or Query input.
  9. Call the use case.
  10. Map the result into a response schema.
  11. Declare the success status explicitly when it is not 200, such as 201 for a resource-creating POST or 204 for a response with no body.
  12. Translate known application exceptions into stable, non-sensitive HTTP responses. Do not expose raw exception messages.
  13. Register full public business route paths such as /api/v1/users. Do not split API prefixes across routers and route fragments. Operational probes are the only unversioned exception: /healthz and /readyz.
  14. For FastAPI apps with long-lived resources, inject FastAPILifecycle into the app factory and pass it to FastAPI(lifespan=...).
  15. Add integration tests at the HTTP boundary, including the declared success code and each translated application error.

Code Style

Use blank lines as logical separators in all code. Keep related statements together, but separate independent setup, action, assertion, response, branch, and transformation groups so long blocks stay readable.

References

  • references/controller.md - FastAPI controller class pattern, app factory registration, schemas, and tests.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Specx Add Delivery Controller AI skill do?

Add delivery controllers for specx services, especially FastAPI HTTP routes. Use when creating top-level `delivery/` request/response schemas, one controller per scoped use-case set, route registration, FastAPI lifecycle managers, HTTP error translation, delivery-only auth/rate-limit/request services, or integration tests that exercise the delivery edge.

Why use Specx Add Delivery Controller on TypingMind?

Because you install it once and use it with any model. Specx Add Delivery Controller is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Specx Add Delivery Controller in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/maksimzayats/specx/tree/main/.agents/skills/specx-add-delivery-controller. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Specx Add Delivery Controller?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Specx Add Delivery Controller?

As many as you like. As long as a model supports skills, you can use Specx Add Delivery Controller with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Specx Add Delivery Controller AI skill free?

Yes. It is published on GitHub by maksimzayats under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
affaan-m logo

Eval Harness

affaan-m
CommunityPopular

Framework formal de evaluación para sesiones de Claude Code que implementa principios de desarrollo orientado a evals (EDD)

39.1K
261.1K
Instructions
View
affaan-m logo

Tdd Workflow

affaan-m
CommunityPopular

Usar este skill al escribir nuevas funcionalidades, corregir bugs o refactorizar código. Aplica el desarrollo guiado por pruebas con 80%+ de cobertura incluyendo pruebas unitarias, de integración y…

39.1K
261.1K
Instructions
View
affaan-m logo

Angular Developer

affaan-m
CommunityPopular

Angular コードを生成し、アーキテクチャ ガイダンスを提供します。プロジェクトの作成、コンポーネント、またはサービスを作成するとき、または反応性（シグナル、linkedSignal、リソース）、フォーム、依存性注入、ルーティング、SSR、アクセシビリティ（ARIA）、アニメーション、スタイリング（コンポーネント スタイル、Tailwind CSS）、テスト、または CLI ツール作成のベスト…

39.1K
261.1K
Instructions
View
NousResearch logo

Anatomy

NousResearch
OrganizationPopular

Explain an idea as an interactive isometric machine figure.

54.8K
252.8K
65 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇