How do I install the Fmprod Fmdel Crosswalk skill?

Run npx skillmds@latest add hugocantor/fmprod-fmdel-crosswalk 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 Fmprod Fmdel Crosswalk safe to use?

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

Which AI agents work with Fmprod Fmdel Crosswalk?

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 Fmprod Fmdel Crosswalk free to use?

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

Who published Fmprod Fmdel Crosswalk?

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

Fmprod Fmdel Crosswalk by hugocantor

Name: Fmprod Fmdel Crosswalk
Rating: 4.2 (5 reviews)
Author: hugocantor

Fmprod Fmdel Crosswalk

Map FMPROD and FMDEL green-screen fields to Db2 for i SQL UDTFs, Kotlin API endpoints, Angular UI fields, and documentation. Use when comparing legacy screens with REST calls, TF_FMPROD* objects, product inquiry/status behavior, field mappings, maintenance screens, or docs/fmprod analysis under /home/hcantor/Projects.

hugocantor Updated Sep 22, 2026

File contents

FMPROD/FMDEL Crosswalk

Purpose

Use this skill when the user asks how legacy FMPROD/FMDEL screen fields, business behavior, SQL objects, API routes, and Angular UI fields correspond.

Workflow

Identify the screen, panel, field label, option, or workflow being mapped.
Gather evidence from the canonical locations in reference.md.
Build the chain in this order when possible:
- Legacy screen or RPG source.
- SourceAnalysis file/table/program evidence.
- sqlobjects UDTF, view, or procedure.
- Kotlin apis/apiv1 endpoint and DTO.
- Angular API/model/mapper/facade/component field.
- Docs or analysis markdown that explains business meaning.
Distinguish display labels from physical fields, SQL aliases, DTO names, and Angular property names.
If any link is missing, report it as unknown instead of filling it in from naming similarity alone.

Output Format

For crosswalk answers, prefer this compact table shape:

Legacy field | Meaning | Source evidence | SQL object | API endpoint/DTO | Angular field | Notes

For implementation planning, return:

Existing behavior and source evidence.
New or changed SQL/API/frontend contract.
Files likely affected.
Tests or parity checks to run.
Open questions where the legacy mapping is ambiguous.

Guardrails

Treat docs/fmprod_analysis_* and related markdown as narrative evidence, not a substitute for source when changing behavior.
Do not assume FMPROD and FMDEL names are interchangeable; verify the workflow and source path.
Preserve legacy-compatible field meanings unless the user explicitly asks to redesign the contract.

---name: fmprod-fmdel-crosswalkdescription: Map FMPROD and FMDEL green-screen fields to Db2 for i SQL UDTFs, Kotlin API endpoints, Angular UI fields, and documentation. Use when comparing legacy screens with REST calls, TF_FMPROD* objects, product inquiry/status behavior, field mappings, maintenance screens, or docs/fmprod analysis under /home/hcantor/Projects.---# FMPROD/FMDEL Crosswalk## PurposeUse this skill when the user asks how legacy FMPROD/FMDEL screen fields, business behavior, SQL objects, API routes, and Angular UI fields correspond.## Workflow1. Identify the screen, panel, field label, option, or workflow being mapped.2. Gather evidence from the canonical locations in [reference.md](reference.md).3. Build the chain in this order when possible: - Legacy screen or RPG source. - SourceAnalysis file/table/program evidence. - `sqlobjects` UDTF, view, or procedure. - Kotlin `apis/apiv1` endpoint and DTO. - Angular API/model/mapper/facade/component field. - Docs or analysis markdown that explains business meaning.4. Distinguish display labels from physical fields, SQL aliases, DTO names, and Angular property names.5. If any link is missing, report it as unknown instead of filling it in from naming similarity alone.## Output FormatFor crosswalk answers, prefer this compact table shape:```textLegacy field | Meaning | Source evidence | SQL object | API endpoint/DTO | Angular field | Notes```For implementation planning, return:- Existing behavior and source evidence.- New or changed SQL/API/frontend contract.- Files likely affected.- Tests or parity checks to run.- Open questions where the legacy mapping is ambiguous.## Guardrails- Treat `docs/fmprod_analysis_*` and related markdown as narrative evidence, not a substitute for source when changing behavior.- Do not assume FMPROD and FMDEL names are interchangeable; verify the workflow and source path.- Preserve legacy-compatible field meanings unless the user explicitly asks to redesign the contract.

Frequently asked questions