ABC-Layering para Deno + Hono
publicdomainrelay/agent-skill-deno-hono-abc-patterns
Padrão arquitetural rigoroso para monorepos TypeScript com Deno e Hono
Ver no GitHubSkill que força Claude a estruturar todo trabalho TypeScript usando um padrão monorepo opinionado: Deno + Hono + JSR com camadas ABC (interfaces, implementação, factory, CLI). Garante dependências unidirecionais, zero I/O em lógica pura e exportações declarativas.
Instalação
npx convez-ai publicdomainrelay/agent-skill-deno-hono-abc-patterns1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Scaffolding de projetos TypeScript/Deno com estrutura consistente
- Refatoração de código para respeitar camadas ABC e fluxo de dependências
- Adição de novos conceitos mantendo separação entre interfaces, implementação e integração
- Garantir conformidade estrutural em projetos multi-camada com Hono
Veredito

Skill altamente especializado para times que adotam padrão ABC-layering em Deno/Hono. Resolve o problema real de inconsistência estrutural (taxa de conformidade sobe de 43% para 100%), mas exige comprometimento com convenções rigorosas e não é flexível para variações arquiteturais.
README
A tradução para o português deste README ainda está na fila.
deno-hono-abc-patterns
A Claude Code / Agent skill that makes Claude structure all TypeScript work using one opinionated Deno + Hono + JSR "ABC-layering" monorepo style. It triggers on creating, scaffolding, re-implementing, refactoring, or extending any TypeScript / Deno / Hono project, and governs the project/file structure that code lands in - folding the tactical advice of other TS/Deno/Hono skills into this layout rather than abandoning it.
The pattern in one screen
Every capability ("concept") is split into four layers, and the layer a file belongs to is visible from its path:
lib/common/${shared} leaf utilities, types, constants (no concept logic)
lib/abc/${concept} interfaces + pure state, zero I/O
lib/${concept}-${transport} concrete implementation: timers, crypto, fetch, sockets
lib/hono-factory-${concept}-${transport} final Hono integration, composed not subclassed
hono-${concept} thin CLI entrypoint: read config, build factory, serve
Dependencies flow strictly one way: common <- abc <- impl <- factory <- CLI.
No cycles, no abc importing an implementation, no cross-concept imports.
Hard rules the skill always enforces:
- One
mod.tsexport per package (no sub-module exports). - Declarative config (
cli-args-env.json+config.json) instead of hardcoded ports/hosts/flags orDeno.env.get()in CLI code. - No I/O in
lib/abc(interfaces and pure state only). - No code comments. ASCII only. Predictable package names.
Layout of this skill
SKILL.md triggering description + workflow + hard rules
references/abc-layering.md the four layers in full, worked code, add-a-concept recipe
references/cli-config.md cli-args-env.json + config.json + priority chain + CONFIG_PATH
references/package-and-workspace.md deno.json shapes, JSR imports, naming, dependency direction
evals/evals.json test prompts + structural assertions used to validate the skill
evals/files/ input fixtures for the refactor / add-concept evals
The conventions are derived from a reference implementation's docs/patterns.md.
The skill is self-contained: the patterns are baked in, so it applies even when
that file is not present in the working repo.
Install
Copy the skill into your skills directory:
git clone https://github.com/publicdomainrelay/agent-skill-deno-hono-abc-patterns \
~/.claude/skills/agent-skill-deno-hono-abc-patterns
Or install the packaged deno-hono-abc-patterns.skill artifact through your
skill manager.
How it was validated
The skill was benchmarked with-skill vs. a no-skill baseline across three tasks (greenfield scaffold, cross-stack refactor, add-a-concept). Structural pass rate: 1.00 with the skill vs. 0.43 baseline. The gap is largest where there is no existing example to copy (greenfield, porting another stack) and smallest when the repo already demonstrates the pattern.
License
Unlicense (public domain). See LICENSE.