skills.rest
zhcndoc
zhcndocOFFICIAL
Explore all skills by this author →
WebsiteGitHub

create-evlog-framework-integration

Scaffold evlog framework integrations with middleware, tests, and build configs.

Updated Apr 15, 2026
Search Tags:#testing#logging#middleware#enrich#framework-integration#drain#evlog
One-click install
npx skills add https://github.com/zhcndoc/evlog --skill create-evlog-framework-integration-zhcndoc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-evlog-framework-integration
Source: https://github.com/zhcndoc/evlog/tree/main/.agents/skills/create-framework-integration
Command: npx skills add https://github.com/zhcndoc/evlog --skill create-evlog-framework-integration-zhcndoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a reproducible blueprint to scaffold a new evlog framework integration, enabling automatic wide-event logging across HTTP frameworks and ensuring consistent structure for source glue, tests, docs, and example apps.

Core Features & Use Cases

  • Unified integration blueprint for multiple frameworks (Hono, Elysia, Express, Fastify, NestJS, etc.) that standardizes the middleware/plugin pattern and logger lifecycle.
  • End-to-end scaffolding covering source glue, build config, package exports, tests, example apps, and documentation so teams can ship integrations rapidly.
  • Publish-ready configurations with peer dependencies, exports, and type versions that align with the evlog core utilities and shared SDK.

Quick Start

Follow the checklist to scaffold a new framework integration by implementing framework glue, add tests, docs, and examples, then wire up the build config and exports.

Frequently Asked Questions about create-evlog-framework-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a logging middleware integration for an HTTP framework?▼

Scaffolding a logging middleware integration involves generating source glue, build configurations, package exports, tests, and example apps. This process automates wide-event logging by applying a standardized middleware pattern and a strict 16-point touchpoint checklist.

Which HTTP frameworks are supported for automatic wide-event logging?▼

Supported HTTP frameworks include Hono, Elysia, Fastify, Express, and NestJS. The integration scaffolding applies a unified blueprint to standardize the middleware or plugin pattern and logger lifecycle across these specific environments.

What is included when scaffolding a framework integration package?▼

Scaffolding includes source glue, build configuration, package exports, tests, an example app, and documentation. It produces publish-ready package configurations with proper peer dependencies and type versions aligned with the core utilities.

Does Hono or Express integration require manual logger lifecycle management?▼

Hono and Express integrations do not require manual logger lifecycle management. The scaffolding process standardizes the logger lifecycle automatically by applying a unified blueprint to ensure consistent wide-event logging across supported HTTP frameworks.

Why do I need a 16-point touchpoint checklist for framework integration?▼

A 16-point touchpoint checklist ensures consistent structure for source glue, tests, documentation, and example apps. It provides a reproducible blueprint that aligns package exports and peer dependencies with shared SDK utilities for publish-ready configurations.

Related Skills

Explore More Software Engineering Skills→
PhantomKnight287PhantomKnight287
9

create-evlog-framework-integration

Generate framework-specific evlog integration scaffolds with source, tests, and docs.

Community
Advanced
popmechanicpopmechanic
134

exe

Deploy a Vibes app to an exe.dev VM with nginx and SSH.

Community
Advanced
zhcndoczhcndoc

create-evlog-adapter

Automate adding a built-in evlog adapter across source, build, exports, tests, and docs.

Official
Advanced
qazuorqazuor

hono-patterns

**error handling and validation in one place. It simplifies Http API development by providing reusable patternsbff for frequent tasks, ensuring consistency and reducing boilerplate code. Here is how it works in terms of code architecture: it separates View from Controller and delegates heavy lifting to handlers and services, making onboarding easier for developers who are familiar with MVC-ish pat

Community
Intermediate