AI Assistant Configuration Guide
Every EasyAdminBlazor source license includes a set of AI assistant configurations tuned for this framework: let ChatGPT / Cursor / Claude follow the framework conventions and generate clean, compilable business code for you.
What's included
| Asset | Location | Purpose |
|---|---|---|
| easyadminblazor-dev skill | .github/skills/easyadminblazor-dev/SKILL.md |
Mandatory development conventions (architecture, naming, entity model, page patterns, DI, security, testing, anti-patterns) plus admin CRUD (AdminTable) and CMS-driven corporate front-end generation; includes the references/pitfalls.md self-check table |
| Corporate templates | .github/skills/easyadminblazor-dev/assets/templates/corporate/ |
Standard corporate site (CMS-driven): Home / Services / Products / News / Contact — copy and page content are editable in the admin; includes sample data and images |
Using it with Qoder Desktop
The canonical location of the skills is .github/skills/ in the repository; Qoder loads project skills from .qoder/skills/. So install them once after you get the source:
- Open the source folder in Qoder (or copy it into your own project root) and tell the Agent: “install the skills from
.github”. - The Agent copies
easyadminblazor-devfrom.github/skills/into.qoder/skills/(that folder is listed in.gitignore, so it never enters version control). It loads automatically in new sessions, and you can also invoke it explicitly with/easyadminblazor-dev. - After you update
.github/skills/, say the same thing again to refresh the local copy..qoder/skills/is just an install artifact — delete it and reinstall if anything looks stale.
Using it with ChatGPT
- Open a ChatGPT project / agent that supports skills, and add the skill directory
.github/skills/(or addeasyadminblazor-dev/SKILL.md). - Just describe what you need, for example:
- "Generate the front-end and back-end pages for the product module: admin CRUD (AdminTable) plus public list/detail pages"
- "Build a corporate site for the company website: Home, Services, Products, News, Contact"
- The AI follows the conventions in easyadminblazor-dev first, then produces framework-compliant code.
Using it with Cursor / Claude
- Add the contents of
easyadminblazor-dev/SKILL.mdto your project's Cursor Rules (.cursor/rules/or.cursorrules) orCLAUDE.md. - Ask the AI to generate or refactor modules against those rules, for example:
- "Create a read-only admin list page for feedback"
- "Check whether my new module complies with the easyadminblazor-dev conventions and fix it"
Example prompts
- Full module:
Generate the front-end and back-end pages for the product module: CMS-driven content management plus public list/detail pages(catalog content goes through the CMS by default — no entity needed; only real business data like orders gets an entity + AdminTable) - Front-end pages:
Create a public news list page and detail page with category filtering and comments - Corporate site:
Build a corporate site for the company website: Home, Services, Products, News, Contact (CMS-driven) - Admin page:
Create a read-only admin list page for feedback - Code review:
Check whether my new module complies with the easyadminblazor-dev conventions and fix it
Tip: just describe the business domain in plain words, e.g. "products", "news" or "feedback". Catalog content (services / products / news) goes through the CMS module by default and is editable in the admin; only real business data (orders, feedback) needs an entity — the AI locates or creates it first, then generates the pages following the skill workflow.
Anti-pattern checklist after generation
- Catalog content (services / products / news) goes through the CMS (
[CmsPage]+CmsData) by default — do not create duplicate entities + CRUD for it - Access CMS data through
ICmsContentService/ICmsCommentService— never queryCmsDatatables directly - Front-end pages must not inject
IFreeSql— business data always usesIBaseRepository<TEntity> - Navigation properties: no
= null!— use nullable for optional,= []for collections - Enum members must be English
- Only trusted back-office content may be rendered with
Html.Raw - Front-end pages must not reuse the admin
MainLayout— use a dedicated public layout - Entity string fields: no
= null!— use= string.Empty
Related docs
doc/代码生成.md: type → component mappingdoc/开始一个新模块.md: new module workflow