Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

thin-runtime-handler

Étoiles0

Forks0

Mis à jour30 juin 2026 à 04:58

Keep HTTP, queue, and cron handlers focused on protocol translation

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

feel-flow

feel-flow/harness-skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	thin-runtime-handler
description	Keep HTTP, queue, and cron handlers focused on protocol translation
metadata	{"type":"Reference","origin":"harness-engineering/ch8","helpful":0,"harmful":0,"status":"active"}

Thin Runtime Handler

Rules

Runtime handlers parse input, call a service, and map results to protocol output.
Do not put DB access in runtime handlers.
Do not put business decisions in runtime handlers.
Keep error-to-status mapping explicit and local to runtime.

Checklist

Handler body is short or split by protocol responsibilities
Handler imports services, not repositories or ORM clients
Invalid input and service failure are handled differently
HTTP status mapping is not leaked into services

Plus depuis ce dépôt

même dépôt

config-boundary

feel-flow/harness-skills

Keep environment variables and deploy-time settings inside a typed config boundary

2026-06-300

forward-only-layers

feel-flow/harness-skills

Enforce six-layer forward-only imports: types -> config -> repositories -> services -> runtime -> ui

2026-06-300

harness-adr-write

feel-flow/harness-skills

Write ADRs for harness boundaries, provider choices, dependency exceptions, and enforcement changes

2026-06-300

harness-bootstrap

feel-flow/harness-skills

Introduce the six-layer harness into an existing TypeScript project gradually

2026-06-300

harness-layer-fix

feel-flow/harness-skills

Fix six-layer harness violations reported by dependency-cruiser, ESLint, or review

2026-06-300

harness-pr-review

feel-flow/harness-skills

Review a PR for six-layer harness, provider, ADR, and enforcement consistency

2026-06-300

name	thin-runtime-handler
description	Keep HTTP, queue, and cron handlers focused on protocol translation
metadata	{"type":"Reference","origin":"harness-engineering/ch8","helpful":0,"harmful":0,"status":"active"}

Thin Runtime Handler

Rules

Runtime handlers parse input, call a service, and map results to protocol output.
Do not put DB access in runtime handlers.
Do not put business decisions in runtime handlers.
Keep error-to-status mapping explicit and local to runtime.

Checklist

Handler body is short or split by protocol responsibilities
Handler imports services, not repositories or ORM clients
Invalid input and service failure are handled differently
HTTP status mapping is not leaked into services