elysia-admin: Instructions file for Kiro

.kiro/steering/structure.md

elysia-admin structure.md is an instructions file for Kiro from meishanlaoyao/elysia-admin. It costs 467 tokens per session, scanned A, original, MIT.

A repository guide for the elysia-admin codebase, describing its frontend and backend folders, their responsibilities, and where to look when adding features.

In plain words
What is it for?
Use it when navigating this Vue, TypeScript, Elysia, and Bun project or planning a new frontend page or backend module.
Why use it?
It reduces guesswork about where code belongs and which existing examples to follow. It also limits unnecessary reading of unrelated files.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is meishanlaoyao/elysia-admin's own configuration. It tells Kiro how to work on elysia-admin itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything elysia-admin configures →

Reuse

Borrowing it

Nothing to install: this file belongs to meishanlaoyao/elysia-admin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/meishanlaoyao/elysia-admin/master/.kiro/steering/structure.md
Clone the repo
git clone --depth 1 https://github.com/meishanlaoyao/elysia-admin

Made for: Kiro.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for elysia-admin structure.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/meishanlaoyao/elysia-admin/structure/github.svg)](https://agentmods.dev/instructions/meishanlaoyao/elysia-admin/structure)
Your own site
<a href="https://agentmods.dev/instructions/meishanlaoyao/elysia-admin/structure"><img src="https://agentmods.dev/badge/instructions/meishanlaoyao/elysia-admin/structure/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for elysia-admin structure.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/meishanlaoyao/elysia-admin/structure"><img src="https://agentmods.dev/badge/instructions/meishanlaoyao/elysia-admin/structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 467 This file is loaded in full into every session.
When invoked 467 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00467 $0.00467
Opus 5 $0.00234 $0.00234
Sonnet 5 $0.00093 $0.00093
Haiku 4.5 $0.00047 $0.00047

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

Security

Grade A, and why

elysia-admin structure.md 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.

.kiro/steering/structure.md · 34 lines

What it actually says

仓库与目录结构

elysia-admin/
├── admin/src/          # 前端(Vue 3 + TypeScript,Art Design Pro)
└── server/src/         # 后端(Elysia + Bun)
    ├── modules/        # 业务模块,每模块独立目录
    ├── worker-sandbox/ # 沙箱 Worker 任务注册(可 import modules;queue processor 只 import 此处)
    ├── types/          # 可 import 的手写类型(*.ts);`types/ambient/` 仅放 *.d.ts
    ├── core/           # 基础设施(默认不要修改)
    ├── shared/         # 无状态纯工具
    └── infrastructure/ # 外部客户端封装

Server 类型文件约定server/src/types/*.ts 为业务/公共类型;server/src/types/ambient/*.d.ts 仅放 ambient 声明,不要把大段业务 interface 写进 ambient/

职责边界

  • 前端 admin/src/:仅通过 HTTP 调用后端;不直连数据库。
  • 后端 server/src/modules/:业务与数据访问;依赖可指向 coresharedinfrastructure不可反向依赖其他模块目录来「抄捷径」。

新功能时的唯一参考样例(各读一个)

  • 新后端模块:只打开 server/src/modules/system-api/ 作为结构参考。
  • 新前端页面:只打开 admin/src/views/system/user/ 作为结构参考。

读文件纪律(摘要)

  • 改哪个文件就只读哪个文件;需要类型时再读对应 types/apidatabase/schema 中的单表文件。
  • 禁止为「摸清项目」而扫描整个 views/modules/ 或通读 admin/src/components/core/server/src/core/(除非任务明确要求或修复 core 缺陷)。
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 · 34 lines · 467 tokens per session scan A b7adc5bdb3eb

Subscribe to this mod's changes

elysia-admin structure.md is an instructions file published in the GitHub repository meishanlaoyao/elysia-admin (49 stars, last pushed today), licensed MIT. It adds 467 tokens to every session, about $0.0023 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-09-06.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens