Help us improve
Share bugs, ideas, or general feedback.
Materal-specific enum adaptation workflow: fetch enum values from provider API, let LLM fill suggested_name, then apply patch with aptx-ft. Use ONLY when: (1) user mentions Materal framework, (2) Materal naming rules are required, or (3) adapting Materal enum semantics. Do NOT use for generic OpenAPI projects.
npx claudepluginhub haibaraaiaptx/frontend-openapi-skills --plugin frontend-openapi-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/frontend-openapi-skills:adapt-materal-enumsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Specialized workflow for Materal framework enum adaptation with semantic naming.
Applies production-ready Mistral AI SDK patterns for TypeScript and Python: singleton clients, retries, structured JSON outputs, streaming, function calling, and error handling.
Generates AI-powered suggestions via `speakeasy suggest` to improve SDK method names from operation IDs and error types in OpenAPI specs. Ideal for fixing auto-generated ugly names.
Guides REST, GraphQL, and gRPC API design. Produces OpenAPI specs, GraphQL schemas, or proto definitions with versioning strategies and consistency validation.
Share bugs, ideas, or general feedback.
Specialized workflow for Materal framework enum adaptation with semantic naming.
pnpm add -D @aptx/frontend-tk-cli
suggested_name based on comment field (no Value1/Value2 style allowed)suggested_name fields are filled# 1) Fetch Materal enum patch (disable auto-naming, delegate to LLM)
pnpm exec aptx-ft -i <spec-file> materal enum-patch \
--base-url <base-url> \
--output ./tmp/enum-patch.json \
--naming-strategy none
# 2) LLM fills suggested_name in patch
# Rule: Translate comment to semantic PascalCase name, preserve value/comment
# 3) Apply translated patch (requires non-empty suggested_name)
pnpm exec aptx-ft -i <spec-file> model enum-apply \
--patch ./tmp/enum-patch.translated.json \
--output ./generated/models \
--style module \
--conflict-policy patch-first
# 4) Cleanup intermediate files (required in production)
rm -f ./tmp/enum-patch.json ./tmp/enum-patch.translated.json
Alternative (without pnpm):
npx aptx-ft -i <spec-file> materal enum-patch --base-url <base-url> --output ./tmp/enum-patch.json --naming-strategy none
npx aptx-ft -i <spec-file> model enum-apply --patch ./tmp/enum-patch.translated.json --output ./generated/models --style module --conflict-policy patch-first
| Option | Default | Description |
|---|---|---|
--max-retries <n> | 3 | Max retry attempts on network failure |
--timeout-ms <ms> | 10000 | Request timeout in milliseconds |
pnpm exec aptx-ft -i <spec-file> materal enum-patch \
--base-url <base-url> \
--output ./tmp/enum-patch.json \
--naming-strategy none \
--max-retries 5 \
--timeout-ms 30000
| File | Description |
|---|---|
enum-patch.json | Raw patch from API (value/suggested_name/comment) |
enum-patch.translated.json | LLM-filled patch |
./generated/models/ | Final TypeScript models with adapted enums |
Cleanup required: Delete enum-patch.json and enum-patch.translated.json after successful apply.
This skill is ONLY for Materal framework adaptation:
generate-artifacts or generate-models