Blyp Elysia
Install blyp-elysia after blyp-core when the application uses Elysia. This preset tells agents to integrate Blyp as an Elysia plugin and keep request-scoped logs on ctx.log.
When to install it
- the repo uses Elysia
- Blyp should be mounted through
.use(createLogger(...)) - handlers need request-scoped logging via
ctx.log
What it covers
createLogger()from@blyp/core/elysia- plugin mounting with
.use(...) - request-scoped logging through
ctx.log
Download raw skill file
Use the canonical source file directly if you want to copy it into an agent skill directory without copying from the rendered page.
/skills/blyp-elysia/SKILL.md| Agent | Project-local path | Global path |
|---|---|---|
| Codex | .agents/skills/blyp-elysia/SKILL.md | ~/.agents/skills/blyp-elysia/SKILL.md |
| OpenCode | .opencode/skills/blyp-elysia/SKILL.md | ~/.config/opencode/skills/blyp-elysia/SKILL.md |
| Claude Code | .claude/skills/blyp-elysia/SKILL.md | ~/.claude/skills/blyp-elysia/SKILL.md |
Related docs
Canonical skill source
Copy the exact markdown file contents and drop them into your agent skill directory.
---
name: blyp-elysia
description: Portable Blyp add-on skill for Elysia services using @blyp/core/elysia, createLogger() as a plugin, and ctx.log for request-scoped logging.
---
# Blyp Elysia
## What this skill is for
Use this add-on when Blyp is being wired into an Elysia application.
## When to use it
- Adding Blyp as an Elysia plugin
- Logging inside Elysia handlers
- Enabling client ingestion in an Elysia server
## Blyp-specific rules and constraints
- Install `blyp-core` first.
- Import from `@blyp/core/elysia`.
- Use `createLogger()` as an Elysia plugin via `.use(...)`.
- Access the request logger as `ctx.log` or `{ log }` in handlers.
- Keep ingestion behavior aligned with the configured path when client logging is enabled.
## Required implementation steps
1. Import `createLogger` from `@blyp/core/elysia`.
2. Add the plugin with `.use(createLogger(...))`.
3. Prefer `ctx.log` for request-scoped logging instead of a root logger inside handlers.
4. Keep any request metadata additions in `customProps`.
5. If browser ingestion is enabled, verify the configured path is the one Elysia accepts for client logs.
## Verification checklist
- The app imports from `@blyp/core/elysia`
- Blyp is mounted through `.use(createLogger(...))`
- Handlers log with `ctx.log`
- Client ingestion path is consistent with config
## References
- Import path: `@blyp/core/elysia`
- Main API: `createLogger()`
- Request logger: `ctx.log`