菜单
Use when working on the AniTrend edge service, especially for repo research, debugging, feature work, dependency lookups, Deno practices, security or performance checks, CI/CD, or keeping this skill's reference map and evals current.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AniTrend/on-the-edge --skill on-the-edge-dev命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | on-the-edge-dev |
| description | Use when working on the AniTrend edge service, especially for repo research, debugging, feature work, dependency lookups, Deno practices, security or performance checks, CI/CD, or keeping this skill's reference map and evals current. |
| license | Apache-2.0 |
| compatibility | Requires Deno 2.7+ and the on-the-edge repo layout. |
| metadata | {"migrated-from":".github/instructions/context.instructions.md","source-format":"instructions"} |
| allowed-tools | ["mcp_context-mode_ctx_search","mcp_context-mode_ctx_batch_execute","mcp_context-mode_ctx_execute","mcp_context-mode_ctx_execute_file"] |
This skill keeps development work on the AniTrend edge service anchored to the repository's current structure, validation rules, and research workflow. Context-mode is the preferred path for repo discovery and output processing.
This skill is context-mode first. Use the context-mode MCP tools before raw file reads, grep, or web fetches whenever you are exploring, summarizing, or comparing repo state.
mcp_context-mode_ctx_search using sort: "timeline" when you
need prior session or repo context.mcp_context-mode_ctx_batch_execute for multi-file or large-output
tasks.mcp_context-mode_ctx_search for focused questions.mcp_context-mode_ctx_execute or
mcp_context-mode_ctx_execute_file.src/package/**)src/service/**)Load a reference when the task falls in that domain. Do not load all at once.
| Area | File | Load When |
|---|---|---|
| Context-Mode Map | ./references/context-mode.md | Any repo research, history lookup, or output processing task |
| Libraries & Frameworks | ./references/libraries.md | Looking up docs, adding packages, reviewing API usage |
| Deno Practices | ./references/deno-practices.md | Permissions, tasks, imports, unstable flags, module structure |
| Security & Performance | ./references/security-performance.md | Code review, new integrations, optimization |
| CI/CD | ./references/cicd.md | Workflow failures, adding jobs, dependency updates, releases |
The reference map is the source of truth for how to research this repository. Keep it current as the project evolves and use it before loading any other reference when you are unsure where to start.
| Need | Start Here |
|---|---|
| Repo discovery | ./references/context-mode.md |
| Package docs | ./references/libraries.md |
| Deno commands and imports | ./references/deno-practices.md |
| Safety and performance | ./references/security-performance.md |
| CI or release work | ./references/cicd.md |
.github/instructions/.src/; check the matching .github/instructions/*.instructions.md for domain-specific rules.@c4spar/mock-fetch only.deno task fmt
deno task lint
deno task check
deno task test -- --filter "<module>"
README.md or docs/ if public behavior changed.src/
package/<domain>/ Domain feature (controller, service, repository, transformer, spec/)
service/<provider>/ External API clients (trakt, tmdb, jikan, thexem, …)
common/ Shared utilities, env loading, date helpers
cache/ Redis-backed caching layer
client/ Fetch wrapper & retry logic
database/ MongoDB factory and Collection<T> interface
experiment/ GrowthBook feature flags
guard/ Request guards (auth, rate-limit)
logger/ Optic-based structured logging + OTEL stream
middleware/ HTTP middleware (logging, headers, tracing)
secret/ Environment variable sourcing
telemetry/ OTEL SDK setup; trace/metric/log exporters
// Cross-module — use @scope alias defined in the module's deno.json exports
import { something } from "@scope/common/core";
// Within the same module — use relative paths
import { helper } from "./utils.ts";
// Never cross module boundaries with deep relative paths
// BAD: import { x } from '../../other-module/internal/file.ts';
// Prefer nullish + default over optional
field: z.string().nullish().default(null),
// Use finite numbers for values that must survive JSON/OpenAPI/GraphQL serialization
publishedOn: z.number().finite(),
// Transform at the boundary
rawField: z.string().transform((v) => v.trim()),
// Compose reusable fragments
const base = z.object({ id: z.string() });
const extended = base.extend({ name: z.string().nullish() });