Create Object logo

Create Object

Community
babamba2
create-object

ABAP object creation workflow — confirm transport+package, auto-create and activate

Overview

Publisherbabamba2
Repositorysuperclaude-for-sap
Skill namecreate-object
Stars
69
Forks
26
Bundled files
5
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by babamba2 on GitHub. Read the source before you install it.

Installation

Install the Create Object AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/babamba2/superclaude-for-sap/tree/main/skills/create-object
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/babamba2/superclaude-for-sap.git /tmp/superclaude-for-sap
mkdir -p .claude/skills
cp -r /tmp/superclaude-for-sap/skills/create-object .claude/skills/create-object
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Create Object in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Create Object on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Create Object is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

SC4SAP Create Object

Guided ABAP object creation workflow. Hybrid mode: confirms transport and package interactively, then auto-creates, writes initial code, and activates the object.

<Response_Prefix> Every response triggered by this skill MUST begin with [Model: <main-model> · Dispatched: <sub-summary>] per ../../common/model-routing-rule.md § Response Prefix Convention. </Response_Prefix>

<Phase_Banner> Multi-phase skill. Before each Agent(...) dispatch, emit ▶ phase=<id> (<label>) · agent=<name> · model=<Opus|Sonnet|Haiku> per ../../common/model-routing-rule.md § Phase Banner Convention. Resolve the dispatch mode first per ../../common/model-dispatch-mode.md: auto (default) uses the model below/in the rule; user-defined asks the user Opus / Sonnet / Haiku (recommended one first) before each dispatch group. </Phase_Banner>

<Use_When>

  • User says "create", "new class", "new program", "create object", "add a function module", "new table", etc.
  • A new ABAP development artifact needs to be created from scratch
  • User knows what they want to build but needs the creation scaffolded correctly </Use_When>

<Do_Not_Use_When>

  • Modifying an existing object -- use direct MCP Update* tools (UpdateClass, UpdateProgram, UpdateInclude, etc.)
  • Creating multiple interdependent objects -- use /sc4sap:create-program for a full program with includes
  • User just wants to understand what type to use -- ask a module consultant agent directly </Do_Not_Use_When>

<Session_Trust_Bootstrap> MANDATORY — runs as Step 0 before any MCP call or user interaction.

Invoke /sc4sap:trust-session with parent_skill=sc4sap:create-object to pre-grant all MCP tool + file-op permissions for this session (eliminates per-tool "Allow this tool?" prompts during Create* + activation flow).

  • If .sc4sap/session-trust.log already has a line within the last 24h, skip silently.
  • Otherwise run it and surface the one-line confirmation.

Full spec: see ../trust-session/SKILL.md. </Session_Trust_Bootstrap>

<Supported_Object_Types>

TypeMCP Create ToolDescription
ClassCreateClassABAP OO class (local or global)
InterfaceCreateInterfaceABAP OO interface
ProgramCreateProgramExecutable program (report)
Function ModuleCreateFunctionModule + CreateFunctionGroupRFC-capable function module
TableCreateTableTransparent database table
StructureCreateStructureABAP structure (type definition)
Data ElementCreateDataElementDomain-based data element
DomainCreateDomainValue domain with fixed values or ranges
CDS ViewCreateViewCore Data Services view
Service DefinitionCreateServiceDefinitionOData service definition
Service BindingCreateServiceBindingOData service binding (UI5/API)
Behavior DefinitionCreateBehaviorDefinitionRAP behavior definition
ScreenCreateScreenDynpro screen (selection screen or dialog)
GUI StatusCreateGuiStatusPF-Status (menu bar, toolbar, function keys)
</Supported_Object_Types>

<ECC_DDIC_Fallback> MANDATORY: Read ../../common/ecc-ddic-fallback.md before creating any Table / Data Element / Domain. It defines when the ECC branch triggers, the helper-program naming rules, the strict template format (mirroring the files under ecc/), and the hard constraints ($TMP only, no activate, no CTS). </ECC_DDIC_Fallback>

<Field_Typing_Rule> MANDATORY for every Table / Structure / Table Type field-type decision (standard MCP flow and ECC helper-program fallback): read ../../common/field-typing-rule.md.

Priority: Standard DE (1) → existing CBO DE (2) → new CBO DE (3) → Data Type + Length (4, last resort). Raw primitives like LIFNR CHAR 10 / MATNR CHAR 40 / BUKRS CHAR 4 are forbidden when an authoritative SAP data element exists. Before each field, run SearchObject against DTEL and check .sc4sap/cbo/<MODULE>/<PACKAGE>/inventory.json. </Field_Typing_Rule>

<Function_Module_Rule> MANDATORY for every UpdateFunctionModule source emission: read ../../common/function-module-rule.md.

FM signature is stored inline in the FUNCTION statement source (SAP parses it on write and updates TFDIR/FUPARAREF automatically). There is no separate "parameters" endpoint. Every FM source MUST declare IMPORTING / EXPORTING / CHANGING / TABLES / EXCEPTIONS clauses directly between FUNCTION {name} and the first .. Never emit the placeholder " You can use the template 'functionModuleParameter' ... line, never use *"*"Local Interface: blocks as a substitute, never declare shadow locals like lv_iv_xxx TYPE ... to stand in for missing parameters.

Remote-Enabled (RFC) flag is a separate concern — stored in TFDIR.FMODE, not in source. Currently requires manual SE37 Properties update; flag this in the completion report. </Function_Module_Rule>

<Hybrid_Mode> Confirm (interactive):

  • Object name (enforce Z/Y prefix, max 30 chars, uppercase)
  • Package assignment (search with GetPackage if unsure)
  • Transport number (list open transports via ListTransports, or create new)
  • Short description

Auto-execute (after confirmation):

  • Create object via appropriate MCP Create* tool
  • Generate initial implementation (skeleton with proper structure)
  • Activate the object
  • Verify activation via GetInactiveObjects </Hybrid_Mode>

<Workflow_Steps> MANDATORY: Follow the step sequence defined in workflow-steps.md.

Per-step model allocation (the main thread follows the session model — model: inherit; creation delegates to sap-executor; the report is rendered on main):

StepOwnerModelRole
0 Trustskill-to-skillSonnetpermission bootstrap
1 ClassifymainSonnetkeyword → object type
2 MetadatamainSonnetname / package / transport / description (Q&A + SearchObject + ListTransports + naming validation)
3 Pre-Creation CheckmainSonnetSearchObject (name-exists guard)
3.5 Version BranchmainSonnetSAP_VERSION ECC vs S/4 routing
4 + 5 + 6 Create + Implement + Activate (standard flow)sap-executor with model: "opus" overrideOpusOne dispatch covers: CreateClass/CreateProgram/... → UpdateClass/UpdateProgram/... with initial implementation code → ActivateObjects → GetInactiveObjects verify. The Opus override is justified because Step 5 is novel code generation (common/model-routing-rule.md § Tier 1 (Opus)) — field typing priority 1–4, class constructor + method signatures, FM inline parameter declarations, etc.
4-ECC DDIC Helper Program (ECC fallback)sap-executor with model: "opus" overrideOpusECC-only branch for Table/DTEL/DOMA. Executor picks the matching template from skills/create-object/ecc/, substitutes names, fills the field list per common/field-typing-rule.md, and CreateProgram + UpdateProgram + ActivateObjects the helper into $TMP.
7 Completion ReportmainSonnetPure formatting from the executor's structured return — no agent dispatch. Localizes to the user's current conversation language. Render rules: dispatch-prompts.md § Step 7. For ECC fallback, use the mandatory report format there verbatim (do NOT rephrase the ⚠ header + 3-step SE38/SE11 checklist).

At Step 2 (metadata collection) — when the object belongs to a specific SAP module (MM table, SD structure, PS data element, …) — the main thread reads SAP_ACTIVE_MODULES from sap.env / config.json and consults ../../common/active-modules.md. If companion modules are active, proactively suggest integration fields (e.g., creating an MM CBO table in a landscape with PS active → suggest adding PS_POSID / AUFNR). Do NOT add silently — propose to user and let them accept/decline, then pass the confirmed field list through to the executor dispatch. </Workflow_Steps>

<Naming_Convention_Enforcement> MANDATORY: Always read configs/common/naming-conventions.md for the complete, authoritative ABAP naming conventions reference before creating any object.

The reference file covers:

  • General rules (prefix, case, character set, length limits)
  • Module codes (SD/MM/FI/CO/...) for the Z{MODULE}_... pattern
  • Object-specific patterns — Classes (ZCL_/ZIF_/ZCX_), Programs (ZR_), Function Groups/Modules, Data Dictionary (ZT_/ZDE_/ZDO_), UI (Dynpro/GUI Status), OData/RAP (Z_I_/Z_C_/Z_BP_/Z_SB_), Enhancements, IDoc/ALE
  • Code-level naming (variables: LV_/LS_/LT_/IV_/EV_/MV_; constants GC_/LC_; types TY_; methods)
  • Validation rules (uppercase, Z/Y prefix, character set, max length, non-generic)

Quick validation checklist (applied before every create):

  1. Starts with Z or Y (customer namespace)
  2. UPPERCASE only, characters in [A-Z0-9_]
  3. Within max length (30 chars for most objects)
  4. Not generic (ZTEST/ZTEMP/ZDUMMY forbidden)
  5. Object-type prefix follows the reference (e.g., ZCL_ for classes, ZIF_ for interfaces)
  6. Screen = 4-digit number (e.g., 0100); GUI Status = uppercase identifier (e.g., STATUS_0100) — both require a parent program

If the user-provided name violates any rule, suggest a compliant alternative based on configs/common/naming-conventions.md before proceeding. </Naming_Convention_Enforcement>

<MCP_Tools_Used>

  • SearchObject — check for existing objects
  • ListTransports — list available transports
  • GetPackage — verify package existence
  • CreateClass / CreateInterface / CreateProgram / CreateFunctionGroup / CreateFunctionModule / CreateTable / CreateStructure / CreateDataElement / CreateDomain / CreateView / CreateServiceDefinition / CreateServiceBinding / CreateBehaviorDefinition / CreateScreen / CreateGuiStatus
  • UpdateClass / UpdateProgram / UpdateScreen / UpdateGuiStatus / etc. — write initial implementation
  • GetInactiveObjects — verify activation
  • ECC DDIC fallback: only CreateProgram + UpdateProgram (target $TMP). CreateTable / CreateDataElement / CreateDomain must NOT be attempted when SAP_VERSION = ECC. </MCP_Tools_Used>

Task: $ARGUMENTS

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Create Object AI skill do?

ABAP object creation workflow — confirm transport+package, auto-create and activate

Why use Create Object on TypingMind?

Because you install it once and use it with any model. Create Object is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Create Object in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/babamba2/superclaude-for-sap/tree/main/skills/create-object. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Create Object?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Create Object?

As many as you like. As long as a model supports skills, you can use Create Object with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Create Object AI skill free?

Yes. It is published on GitHub by babamba2 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇