Run any Skill in Manus with one click

add-tslc-backend

Stars3

Forks0

UpdatedJuly 14, 2026 at 15:23

Add a backend or backend capability to tslc. Use when asked to introduce a new generated language/backend, register backend IDs or capabilities, add backend-specific type/value/intrinsic translation, add backend render assets, or make backend support additive and validated.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

JPietrzykTUD

JPietrzykTUD/tslgen-v2

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	add-tslc-backend
description	Add a backend or backend capability to tslc. Use when asked to introduce a new generated language/backend, register backend IDs or capabilities, add backend-specific type/value/intrinsic translation, add backend render assets, or make backend support additive and validated.

Add TSLC Backend

Workflow

Read AGENTS.md, CHARTER.md, PLANS.md, tslc/AGENTS.md, tslc/CHARTER.md, and the existing tslc/src/tslc/backend/, tslc/src/tslc/render/, tslc/src/tslc/output/, relevant tsldata/detail/, and supplementary/ patterns.
Define the backend ID, supported profiles/extensions, type spellings, intrinsic/value translations, generated project layout, and verification story.
Add backend capabilities through the existing backend registry/support-policy boundary. Do not scatter hardcoded backend ID lists.
Add typed translation/render values before templates. Templates may format decided values only.
Place packaged backend static files, templates, and helpers under tslc/src/tslc/backend/assets/. Keep generated-documentation inputs under supplementary/docs/ and machine-profile configuration under supplementary/buildsystem/.
Diagnose unsupported capability combinations before rendering or artifact writing.
Add focused tests for registration, capability validation, rendering, deterministic artifacts, and verifier configuration.

Checks

Adding a future backend should mostly add a backend module/assets/tests, not edit unrelated schema, lowering, or renderer dispatch code.
Missing backend support should produce structured diagnostics, not late template errors.
Backend-specific syntax must not be inferred from raw TSIL text unless the accepted source form is already typed and tested.
Keep build/test verification injectable and skip-safe for unavailable toolchains.

Useful Commands

PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_support_policy.py tslc/tests/test_backend_target_capability.py
PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_render_model.py tslc/tests/test_output_format.py
PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_build_verify_config.py
./dev.sh generate --primitives add --profiles scalar --backends BACKEND

More from this repository

same repository

extend-tslc-verification

JPietrzykTUD/tslgen-v2

Add or change generated build and value-test verification in tslc. Use when asked to support a compiler or toolchain command, target triple or linker, runner or emulator, compiler or target preflight, cross-compilation path, verifier backend driver, missing-tool skip, command report, or generated verification capability independent of adding a backend.

2026-07-143

add-tsl-extension

JPietrzykTUD/tslgen-v2

Add a target extension or machine-profile family through TSL source data, typed compiler capabilities, generated artifacts, verification, and tests. Use when asked to add a SIMD ISA or extension, fixed or scalable profile, compiler-vector overlay, target family, machine profile, feature or compile mode, or the first primitive slice for a new target.

2026-07-143

add-value-test-shape

JPietrzykTUD/tslgen-v2

Extend typed generated value-test planning and rendering in tslc. Use when asked to support a new authored tests shape or signature, add a case kind or pattern, handle memory, mask, conversion, scalable, or differential cases, resolve authored_unplanned or backend_unsupported coverage, or add backend rendering for a planned case.

2026-07-143

add-tsil-region

JPietrzykTUD/tslgen-v2

Add a TSIL keyword region to tslc. Use when asked to recognize a new TSIL keyword, validate region shell syntax, lower a new body island, support nested TSIL regions, or replace raw implementation text with typed TSIL semantics.

2026-07-143

add-tsl-primitive-implementation

JPietrzykTUD/tslgen-v2

Add, complete, or refactor a specialization of an existing TSL primitive. Use when asked to add an implementation body for a specific extension, profile, type group, or backend; replace scattered intrinsic recipes with semantic TSL-primitive composition; close a missing coverage slot; or fix generated build/value-test gaps in existing primitive source data.

2026-07-143

add-tsl-primitive

JPietrzykTUD/tslgen-v2

Add or update a TSL primitive in tsldata and the tslc compiler. Use when asked to add a new primitive, change primitive signatures/tests/bodies, support a new primitive shape, or make primitive source data compile through parsing, validation, selection, lowering, rendering, and generated value tests.

2026-07-143

name	add-tslc-backend
description	Add a backend or backend capability to tslc. Use when asked to introduce a new generated language/backend, register backend IDs or capabilities, add backend-specific type/value/intrinsic translation, add backend render assets, or make backend support additive and validated.

Add TSLC Backend

Workflow

Read AGENTS.md, CHARTER.md, PLANS.md, tslc/AGENTS.md, tslc/CHARTER.md, and the existing tslc/src/tslc/backend/, tslc/src/tslc/render/, tslc/src/tslc/output/, relevant tsldata/detail/, and supplementary/ patterns.
Define the backend ID, supported profiles/extensions, type spellings, intrinsic/value translations, generated project layout, and verification story.
Add backend capabilities through the existing backend registry/support-policy boundary. Do not scatter hardcoded backend ID lists.
Add typed translation/render values before templates. Templates may format decided values only.
Place packaged backend static files, templates, and helpers under tslc/src/tslc/backend/assets/. Keep generated-documentation inputs under supplementary/docs/ and machine-profile configuration under supplementary/buildsystem/.
Diagnose unsupported capability combinations before rendering or artifact writing.
Add focused tests for registration, capability validation, rendering, deterministic artifacts, and verifier configuration.

Checks

Adding a future backend should mostly add a backend module/assets/tests, not edit unrelated schema, lowering, or renderer dispatch code.
Missing backend support should produce structured diagnostics, not late template errors.
Backend-specific syntax must not be inferred from raw TSIL text unless the accepted source form is already typed and tested.
Keep build/test verification injectable and skip-safe for unavailable toolchains.

Useful Commands

PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_support_policy.py tslc/tests/test_backend_target_capability.py
PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_render_model.py tslc/tests/test_output_format.py
PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_build_verify_config.py
./dev.sh generate --primitives add --profiles scalar --backends BACKEND