How do I install the Shadmin Feature Dev skill?

Run npx skillmds@latest add tomevault-io/shadmin-feature-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Shadmin Feature Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Shadmin Feature Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Shadmin Feature Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Shadmin Feature Dev?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Shadmin Feature Dev by tomevault-io

Name: Shadmin Feature Dev
Author: tomevault-io

Shadmin Feature Dev

Apply Shadmin feature-development standards (backend Go/Gin/Ent + frontend React/TS). Use when adding/modifying features, CRUD modules, API routes/controllers/usecases/repositories, Ent schemas, or web pages/routes. Use when this capability is needed.

tomevault-io 8e00ab4 2 files · 3.0 KB Updated Sep 17, 2026

File contents

Shadmin Feature Development

Purpose

When the user asks to add/modify a feature in this repo, follow Shadmin’s established architecture and conventions, and land code in the correct layers with minimal, verifiable changes.

Mandatory rules

Always follow: AI_RULES.md
Use the existing layering:
- Backend: api (controller/route) → usecase → repository → ent/schema
- Frontend: web/src/services → web/src/features/<feature> → web/src/routes
Permissions must be consistent:
- Protected APIs must use JWT + Casbin CheckAPIPermission() for /api/v1/system/* routes.
Response format must be consistent:
- Use domain.RespSuccess(...) / domain.RespError(...).
Finish with verification:
- Backend: go test ./...
- If frontend changed: cd web && (npm|pnpm) run lint && (npm|pnpm) run format:check

Workflow (apply every time)

Clarify scope (what to do / not do) + list APIs, data model, permissions, and UI impact.
List touched files first (grouped by backend/frontend layers) before editing.
Implement changes layer-by-layer:
- domain/ (DTOs + interfaces + errors)
- ent/schema/ (if data model changes)
- repository/
- usecase/ (timeouts, validation, orchestration)
- api/controller/ (HTTP only + swagger comments)
- api/route/ + api/route/factory.go (wiring)
- web/src/types + web/src/services + web/src/features + web/src/routes
Output at the end:
- Change summary
- File list
- How to verify

References (optional)

Prompt template: AI提示词模板.md
Repo guidelines: AGENTS.md

Examples (triggers)

“新增项目管理模块（Project CRUD）”
“给字典增加一个字段并在前端表格显示”
“新增 /api/v1/system/xxx 接口并接入菜单权限”

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: shadmin-feature-devdescription: Apply Shadmin feature-development standards (backend Go/Gin/Ent + frontend React/TS). Use when adding/modifying features, CRUD modules, API routes/controllers/usecases/repositories, Ent schemas, or web pages/routes. Use when this capability is needed.---# Shadmin Feature Development## PurposeWhen the user asks to add/modify a feature in this repo, follow Shadmin’s established architecture and conventions, and land code in the correct layers with minimal, verifiable changes.## Mandatory rules1. **Always follow**: [AI_RULES.md](../../../AI_RULES.md)2. **Use the existing layering**: - Backend: `api (controller/route) → usecase → repository → ent/schema` - Frontend: `web/src/services → web/src/features/<feature> → web/src/routes`3. **Permissions must be consistent**: - Protected APIs must use JWT + Casbin `CheckAPIPermission()` for `/api/v1/system/*` routes.4. **Response format must be consistent**: - Use `domain.RespSuccess(...)` / `domain.RespError(...)`.5. **Finish with verification**: - Backend: `go test ./...` - If frontend changed: `cd web && (npm|pnpm) run lint && (npm|pnpm) run format:check`## Workflow (apply every time)1. **Clarify scope** (what to do / not do) + list APIs, data model, permissions, and UI impact.2. **List touched files first** (grouped by backend/frontend layers) before editing.3. Implement changes **layer-by-layer**: - `domain/` (DTOs + interfaces + errors) - `ent/schema/` (if data model changes) - `repository/` - `usecase/` (timeouts, validation, orchestration) - `api/controller/` (HTTP only + swagger comments) - `api/route/` + `api/route/factory.go` (wiring) - `web/src/types` + `web/src/services` + `web/src/features` + `web/src/routes`4. **Output at the end**: - Change summary - File list - How to verify## References (optional)- Prompt template: [AI提示词模板.md](../../../AI提示词模板.md)- Repo guidelines: [AGENTS.md](../../../AGENTS.md)## Examples (triggers)- “新增项目管理模块（Project CRUD）”- “给字典增加一个字段并在前端表格显示”- “新增 /api/v1/system/xxx 接口并接入菜单权限”---> Converted and distributed by [TomeVault](https://tomevault.io/claim/ahaodev) — claim your Tome and manage your conversions.

Frequently asked questions