Run any Skill in Manus with one click

add-value-test-shape

Stars3

Forks0

UpdatedJuly 14, 2026 at 15:42

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.

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 Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

name	add-value-test-shape
description	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.

Add Value-Test Shape

Workflow

Read AGENTS.md, CHARTER.md, PLANS.md, tslc/AGENTS.md, tslc/CHARTER.md, the differential-value-test section of tslc/DESCRIPTION.md, the source primitive/tests, and the closest patterns, case planners, capabilities, renderers, and tests under tslc/src/tslc/value_tests/.
Define the authored contract and oracle first: signature/result kinds, parameter layout, fixed or scalable lanes, masks, memory/alignment/aliasing, immediates, representation changes, safety, and supported backends.
Reuse an existing case kind when its typed components express the contract. Add vocabulary only when the new case has distinct invariants or render requirements; do not create one case kind per primitive or signature.
Keep source data semantic. Do not embed C++/Rust harness code or renderer policy in .tsl tests.
Plan before rendering: the focused pattern owns acceptance and actionable unplanned reasons; case planners construct typed components; case_capabilities.py declares invariants; patterns.py owns deterministic registration. Do not let renderers rediscover source semantics.
Declare backend case-kind support through renderer capabilities and add focused backend rendering. Missing support must remain backend_unsupported, not fail through a late dispatch or template error.
Keep fixed, scalable, differential, memory, and conversion behavior explicit. A missing harness primitive or ambiguous oracle must produce authored_unplanned coverage or a structured diagnostic, not fabricated expected behavior.
Test accepted and nearby rejected forms, unplanned reasons, component invariants, backend capability validation, deterministic planning, and rendering. Run executable generated tests for every affected backend/profile that the available toolchains can verify.

Checks

Every authored case is planned, explicitly unplanned, or backend-unsupported with a deterministic reason.
Planning remains backend-neutral until declared renderer capabilities and target-specific formatting are needed.
Generated tests exercise the real primitive contract rather than merely proving that a harness compiles.

Useful Commands

PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_value_test_planning.py
PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_backend_target_capability.py tslc/tests/test_value_tests.py
PYTHONPATH=tslc/src python -m pytest -q --run-generated-builds tslc/tests/test_value_tests.py
git diff --check

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-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

add-tslc-backend

JPietrzykTUD/tslgen-v2

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.

2026-07-143

name	add-value-test-shape
description	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.

Add Value-Test Shape

Workflow

Read AGENTS.md, CHARTER.md, PLANS.md, tslc/AGENTS.md, tslc/CHARTER.md, the differential-value-test section of tslc/DESCRIPTION.md, the source primitive/tests, and the closest patterns, case planners, capabilities, renderers, and tests under tslc/src/tslc/value_tests/.
Define the authored contract and oracle first: signature/result kinds, parameter layout, fixed or scalable lanes, masks, memory/alignment/aliasing, immediates, representation changes, safety, and supported backends.
Reuse an existing case kind when its typed components express the contract. Add vocabulary only when the new case has distinct invariants or render requirements; do not create one case kind per primitive or signature.
Keep source data semantic. Do not embed C++/Rust harness code or renderer policy in .tsl tests.
Plan before rendering: the focused pattern owns acceptance and actionable unplanned reasons; case planners construct typed components; case_capabilities.py declares invariants; patterns.py owns deterministic registration. Do not let renderers rediscover source semantics.
Declare backend case-kind support through renderer capabilities and add focused backend rendering. Missing support must remain backend_unsupported, not fail through a late dispatch or template error.
Keep fixed, scalable, differential, memory, and conversion behavior explicit. A missing harness primitive or ambiguous oracle must produce authored_unplanned coverage or a structured diagnostic, not fabricated expected behavior.
Test accepted and nearby rejected forms, unplanned reasons, component invariants, backend capability validation, deterministic planning, and rendering. Run executable generated tests for every affected backend/profile that the available toolchains can verify.

Checks

Every authored case is planned, explicitly unplanned, or backend-unsupported with a deterministic reason.
Planning remains backend-neutral until declared renderer capabilities and target-specific formatting are needed.
Generated tests exercise the real primitive contract rather than merely proving that a harness compiles.

Useful Commands

PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_value_test_planning.py
PYTHONPATH=tslc/src python -m pytest -q tslc/tests/test_backend_target_capability.py tslc/tests/test_value_tests.py
PYTHONPATH=tslc/src python -m pytest -q --run-generated-builds tslc/tests/test_value_tests.py
git diff --check