jframe-module-design

A guide for designing and scaffolding modules in jframe, a Go framework that organizes application features as separate components with defined startup and shutdown stages.

In plain words
What is it for?
Use it when creating a jframe module, adding a feature or external service, defining configuration, planning dependencies, or mapping the module's lifecycle.
Why use it?
It helps you structure new features and services without making modules depend directly on one another. It also clarifies how configuration, dependency injection, startup, and stopping fit together.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/juanjitech/jframe/jframe-module-design
Any agent
npx skills add juanjiTech/jframe --skill jframe-module-design
Clone the repo
git clone --depth 1 https://github.com/juanjiTech/jframe

Made for: Claude Code, Codex.

Per session 185 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,908 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00185 $0.02908
Opus 5 $0.00093 $0.01454
Sonnet 5 $0.00037 $0.00582
Haiku 4.5 $0.00018 $0.00291

Measured 2d ago against content hash f6c8efd35bd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

jframe-module-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/jframe-module-design/SKILL.md · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

jframe Module Design

This skill guides you through designing and creating a new module for the jframe Go scaffolding framework. jframe uses a kernel-based modular architecture where every feature is a kernel.Module with a structured lifecycle managed by a dependency injection container.

When to use this skill

  • User wants to add a new feature/service to the jframe application
  • User asks to create/scaffold/design a new module
  • User wants to integrate an external service (database, cache, API, etc.) as a module

Overview of the module system

Every module implements kernel.Module (defined in core/kernel/module.go). The kernel runs modules through 6 sequential lifecycle phases, each receiving a *kernel.Hub that wraps the DI container (inject.Injector) plus a namespaced logger:

Config loading → PreInit → Init → PostInit → Load → Start (goroutine)
                                                         ↓
                                                     Stop (concurrent via WaitGroup)

Modules interact exclusively through the Hub's DI container — they never import each other directly. This is the core decoupling mechanism.

Step 1: Gather requirements

Before writing any code, clarify these with the user:

  1. What does the module do? — Is it a service client (DB, cache, API), a protocol server (HTTP routes, gRPC), a background worker, or business logic?
  2. What name should it have? — The Name() return value determines the YAML config key and log namespace. Convention: camelCase for infrastructure (myDB, rds), descriptive for business modules (users, orders).
  3. Does it need configuration? — External services almost always do. Business modules may or may not.
  4. What does it produce for other modules? — What will it Map into the DI container? (e.g., *gorm.DB, *redis.Client, a custom service interface)
  5. What does it consume from other modules? — What will it Load from the DI container? (e.g., *jin.Engine for HTTP routes, *gorm.DB for data access)
  6. Does it need a long-running goroutine? — Only if it runs a server or background loop.

Read the full file on GitHub · 301 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 301 lines · 185 tokens per session scan A f6c8efd35bd1

Subscribe to this mod's changes

jframe-module-design is a skill published in the GitHub repository juanjiTech/jframe (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 185 tokens to every session and 2,908 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens