maker
Skill0 starsChanged 10 months agoMITView on GitHub
Generate .NET Core data API code from model definitions using the Maker XML specification and CLI. Use when users need to: (1) Create Maker XML models from JSON objects, SQL scripts, or database schemas, (2) Generate .NET Core CRUD API endpoints from Maker XML, (3) Understand or validate Maker XML model definitions, or (4) Work with the Maker CLI tool for code generation.
In this repository4 other files it gives its agents.
- aspose-slidesSkill
- dotnet-cqrs-apiSkill
- reindex-docsSkill
- repo-docsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
When converting JSON objects or data models to Maker XML:
- Distinctive: line 31
Add appropriate filters and auto-population attributes
- Distinctive: line 32
Follow Maker naming conventions (IsActive, not Active)
- Distinctive: line 40
When converting SQL CREATE TABLE scripts to Maker XML:
- Distinctive: line 49
Add XML comments for assumptions or complex mappings
- Distinctive: line 57
When working with existing Maker XML or needing to understand the specification:
- Distinctive: line 69
When generating code from Maker XML models:
- Very specific: line 105
When a field ends with Id, ID, or _id:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Maker - .NET Core Data API Code Generation
Overview
Maker transforms XML model definitions into complete .NET Core data API endpoints with full CRUD functionality. This skill helps generate Maker XML models from various sources and understand the Maker CLI workflow.
Workflow Decision Tree
Choose your workflow based on the starting point:
Starting from JSON or data model? → Use the From JSON Workflow
Starting from SQL CREATE TABLE script? → Use the From SQL Workflow
Starting from existing Maker XML? → Use the Understanding Maker XML
Need to generate code from Maker XML? → Use the CLI Generation Workflow
From JSON or Data Model
When converting JSON objects or data models to Maker XML:
- Read the conversion prompt: Load
references/Prompt_to_create_Maker_XML_from_json_model.mdto understand the conversion guidelines - Read the specification: Load
references/Maker_XML_specification.mdfor type mappings and patterns - Apply the conversion logic:
- Infer relationships from field names ending in
Id,ID, or_id - Map JSON types to Maker column types (string → text/name/label, boolean → flag, etc.)
- Suggest property tables for type/status/state fields
- Add appropriate filters and auto-population attributes
- Follow Maker naming conventions (IsActive, not Active)
- Infer relationships from field names ending in
- Generate three artifacts:
- Maker XML
<Table>definition - Corresponding
<View>definition - Property table initialization SQL (if applicable)
- Maker XML
From SQL CREATE TABLE Script
When converting SQL CREATE TABLE scripts to Maker XML:
- Read the conversion prompt: Load
references/Prompt_to_create_Maker_XML_from_sql_script.mdfor SQL-specific guidelines - Read the specification: Load
references/Maker_XML_specification.mdfor type mappings - Apply the conversion logic:
- Map SQL types to Maker column types
- Identify foreign key relationships from column names
- Improve naming where SQL uses poor conventions
- Suggest virtual columns for views
- Add XML comments for assumptions or complex mappings
- Generate three artifacts:
- Maker XML
<Table>definition - Corresponding
<View>definition - Property table initialization SQL (if applicable)
- Maker XML
Understanding Maker XML
When working with existing Maker XML or needing to understand the specification:
Read the specification: Load references/Maker_XML_specification.md to understand:
- Column types (identity, text, name, label, note, integer, decimal, flag, datetime, property, uniqueid)
- Table attributes (type, name, description, alias, view, schema, search)
- View definitions and virtual columns
- Property tables and relational patterns
- Auto-population and filtering rules
- Naming conventions and best practices
CLI Generation Workflow
When generating code from Maker XML models:
Read the CLI documentation: Load references/MakerCLI.md to understand:
- Command-line syntax and arguments
- Validation-only mode for model verification
- Publishing workflow for deployment
- File placement and integration requirements
Standard generation command:
MakerCLI --modelname=[Name] --publish=false --validate=trueValidation-only mode:
MakerCLI --modelname=[Name] --validate=onlyThis performs model validation without generating files, useful for verifying XML before generation.
Type Mapping Quick Reference
| Source Type | Maker Type | Notes |
id, guid, uuid | identity or uniqueid | identity for PKs, uniqueid for tokens |
string (short) | name, label, or text | Based on context/length |
string (medium) | note or text length="note" | Descriptions |
string (long) | desc or text length="desc" | Large text, JSON |
boolean | flag | Ensure Is/Has/Want/Can prefix |
number, integer | integer or decimal | Based on precision needs |
date, datetime | datetime | Add auto/update attributes as needed |
| Enum/lookup fields | property | Create property table |
Common Patterns
Foreign Key Relationships
When a field ends with Id, ID, or _id:
<Column type="integer" name="SiteID" filter="yes"/>Property Tables (Type/Status/State)
For enumeration fields:
<Column type="property" name="Type">
<Property name="TypeID" table="Type"/>
</Column>With initialization SQL:
INSERT INTO Type (Code, Name, Description) VALUES
('standard', 'Standard', 'Standard type'),
('premium', 'Premium', 'Premium type');Auto-Populated Timestamps
<Column type="datetime" name="Created" filter="no" auto="yes" update="no"/>
<Column type="datetime" name="Updated" filter="no" auto="yes" update="yes"/>Boolean Flags with Correct Naming
<Column type="flag" name="IsActive"/> <!-- Correct -->
<!-- Not: <Column type="flag" name="Active"/> -->References
This skill includes comprehensive reference documentation:
- Maker_XML_specification.md: Complete Maker XML specification with all column types, attributes, and patterns
- MakerCLI.md: CLI usage, commands, and workflow documentation
- Prompt_to_create_Maker_XML_from_json_model.md: JSON-to-XML conversion guidelines
- Prompt_to_create_Maker_XML_from_sql_script.md: SQL-to-XML conversion guidelines
Load these references as needed based on the specific conversion or generation task.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

