Agent skill

Tsz Architecture

by tsz-org in tsz-org/tsz

Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code.

Apache-2.0Auto-check passed

Install Tsz Architecture

skills CLI
$ npx skills add tsz-org/tsz --skill tsz-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tsz-org/tsz tsz-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tsz-org/tsz.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tsz-architecture .claude/skills/tsz-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tsz-architecture
GitHub stars
577
Token cost
~547 tokens
SKILL.md length
186 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code.

  • Works in 5 steps: Classify as WHAT (solver/query boundary)… → Search existing boundaries → Put checker-facing semantic adapters under → …
  • Planning semantic fixes
  • SKILL.md covers Rules, Owners, Boundary Workflow and Guards
  • Calls python3, rg and cargo

What it does

Tsz Architecture is an agent skill from tsz-org/tsz. Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code. Use when planning semantic fixes, moving logic across query boundaries, handling architecture guard failures, ratcheting boundary debt, or reviewing changes for solver-first and no hardcoding rules.

Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with WebAssembly. The repository describes itself as: An experiment in fully hand-off software engineering: A performance-first TypeScript checker. The licence is Apache-2.0.

When your agent uses it

  • Planning semantic fixes
  • Moving logic across query boundaries
  • Handling architecture guard failures
  • Ratcheting boundary debt

Example prompts

  • “/tsz-architecture”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Classify as WHAT (solver/query boundary) or WHERE (checker location/
  2. Search existing boundaries
  3. Put checker-facing semantic adapters under
  4. Avoid new checker TypeKey matching, direct CompatChecker, raw interning,
  5. Add owning-crate tests and adjacent cases varying names/wrappers.

What it can do on your machine

Read from SKILL.md and the folder at commit 153b25a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3
    • rg
    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tsz Architecture loads about 547 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 186 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~547

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tsz-org/tsz at commit 153b25a, republished under its Apache-2.0 licence (© tsz-org). 186 words, ~547 tokens.

Download SKILL.mdSave it as .claude/skills/tsz-architecture/SKILL.md (or your agent's skills folder).
name
tsz-architecture
description
Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code. Use when planning semantic fixes, moving logic across query boundaries, handling architecture guard failures, ratcheting boundary debt, or reviewing changes for solver-first and no hardcoding rules.

TSZ Architecture

Use for ownership-boundary work. Default direction: solver-first semantics, thin checker, syntax parser, symbol/flow binder, output-only emitter.

Rules

  • Read AGENTS.md and docs/plan/ROADMAP.md for conformance, emit, performance, architecture, LSP/WASM, Sound Mode, or DRY cleanup work.
  • Inspect overlapping PRs/issues.
  • State: When <structural condition>, tsc does X; tsz does X through <owner>.
  • No fixture paths, user names, source snippets, rendered strings, or single test names as decision inputs.
  • Prefer one query/boundary helper over local checker branches.

Owners

  • Scanner: tokens and interning.
  • Parser: syntax-only AST.
  • Binder: symbols, scopes, hoisting, flow graph.
  • Solver: relations, evaluation, inference, instantiation, operations, narrowing, semantic caches.
  • Checker: orchestration, diagnostics, source spans.
  • Emitter: JS/DTS output and transform scheduling.
  • LSP/WASM/CLI: API consumers.

Boundary Workflow

  1. Classify as WHAT (solver/query boundary) or WHERE (checker location/ diagnostic orchestration).
  2. Search existing boundaries: rg "struct .*Request|RelationRequest|query_boundaries|TypeData" crates/tsz-checker/src crates/tsz-solver/src
  3. Put checker-facing semantic adapters under crates/tsz-checker/src/query_boundaries/.
  4. Avoid new checker TypeKey matching, direct CompatChecker, raw interning, or type-shape recursion.
  5. Add owning-crate tests and adjacent cases varying names/wrappers.

Guards

bash
python3 scripts/arch/arch_guard.py
scripts/arch/check-checker-boundaries.sh
python3 scripts/arch/test_arch_guard.py

Use targeted cargo nextest run; wrap heavy runs with scripts/safe-run.sh.

PR notes: structural rule, owner layer, adjacent matrix, guard/tests, temporary debt/removal condition.

© tsz-org, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/tsz-architecture of tsz-org/tsz.

Open the folder on GitHubat commit 153b25a

Compare with similar skills

Tsz Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tsz Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tsz Architecture this skilltsz-org/tsz577—~547Automated safety check: PassApache-2.0
RuView CLI, API and WASMruvnet/RuView97k—~1.2kAutomated safety check: NotesMIT
Nginx To Higress Migrationhigress-group/higress9.5k—~3.9kAutomated safety check: PassApache-2.0
Update V86felixrieseberg/windows9524k—~1.7kAutomated safety check: PassCustom licence
Dotlottie WebLottieFiles/dotlottie-web892—~3.5kAutomated safety check: PassMIT
Adding Internal API RouteTriliumNext/Trilium38k—~3.3kAutomated safety check: PassAGPL-3.0

Similar skills

  • Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.

    97k GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check: notes
  • Nginx To Higress Migration

    higress-group/higress

    Migrate from ingress-nginx to Higress in Kubernetes environments.

    9.5k GitHub stars~3.9k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Update V86

    felixrieseberg/windows95

    Build and install v86 (wasm + libv86.js + BIOS) into windows95.

    24k GitHub stars~1.7k tokensUpdated 29 days ago
    Testing & QAAuto-check passed
  • Dotlottie Web

    LottieFiles/dotlottie-web

    Implement Lottie animations using dotLottie runtimes (@lottiefiles/dotlottie-web and @lottiefiles/dotlottie-react).

    892 GitHub stars~3.5k tokensUpdated 3 days ago
    Media & CreativeAuto-check passed
  • Adding Internal API Route

    TriliumNext/Trilium

    A skill your agent uses when adding, moving, or wiring an internal REST endpoint in Trilium (a new /api/ route) — choosing between a core-shared handler (packages/trilium-core/src/routes/index.ts…

    38k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed
  • Client Request Signature Reversal

    awarexone/Agentic-Bug-Hunter

    Recovers a client-side request signature or anti-bot token just far enough to replay blocked requests in bug bounty testing, starting from a captured packet.

    5.3k GitHub stars~4.7k tokensUpdated yesterday
    SecurityAuto-check passed

More from tsz-org/tsz

All 12 skills in this repo
  • Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.

    577 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Audit TSZ repo iteration speed and quality. An agent skill from tsz-org/tsz.

    577 GitHub stars~557 tokensUpdated 1 mo ago
    Auto-check passed
  • A skill your agent uses when planning, implementing, reviewing, or interpreting TSZ performance work, including benchmark regressions, cache/residency changes, timing claims, perf counters, hotspot…

    577 GitHub stars~746 tokensUpdated 1 mo ago
    Auto-check passed
  • Create, refresh, and publish TSZ pull requests with correct body and state.

    577 GitHub stars~555 tokensUpdated 1 mo ago
    Auto-check passed
  • Start TSZ work safely in a crowded multi-agent checkout. An agent skill from tsz-org/tsz.

    577 GitHub stars~518 tokensUpdated 1 mo ago
    Auto-check passed
  • Tsz CI PR

    tsz-org/tsz

    Drive TSZ GitHub PRs through review, CI, and the merge queue.

    577 GitHub stars~633 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Tsz Architecture

What does Tsz Architecture do?

Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code. Tsz Architecture is an agent skill from tsz-org/tsz. Preserve TSZ architecture boundaries while changing checker, solver, binder, emitter, LSP, WASM, or CLI code.

When should I use Tsz Architecture?

Tsz Architecture fits situations like: planning semantic fixes; moving logic across query boundaries; handling architecture guard failures; ratcheting boundary debt.

How do I install Tsz Architecture in Claude Code?

Run `npx skills add tsz-org/tsz --skill tsz-architecture -a claude-code`. Or copy the skill folder (.agents/skills/tsz-architecture in tsz-org/tsz) into .claude/skills/tsz-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Tsz Architecture in Codex?

Run `npx skills add tsz-org/tsz --skill tsz-architecture -a codex`. Or copy the skill folder (.agents/skills/tsz-architecture in tsz-org/tsz) into .agents/skills/tsz-architecture in your project. Codex loads it when a task matches its description.

Can I use Tsz Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tsz-org/tsz --skill tsz-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tsz-architecture, .gemini/skills/tsz-architecture, .github/skills/tsz-architecture and .opencode/skills/tsz-architecture in your project.

What does Tsz Architecture need to run?

Going by SKILL.md and its folder, Tsz Architecture needs the command-line tools its instructions call (python3, rg and cargo). Our summary lists: Python 3.

Does Tsz Architecture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tsz Architecture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tsz Architecture use?

Tsz Architecture is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tsz Architecture use?

About 547 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tsz Architecture?

Skills that share tags, products or a category with Tsz Architecture: RuView CLI, API and WASM (ruvnet/RuView, 97k stars), Nginx To Higress Migration (higress-group/higress, 9.5k stars), Update V86 (felixrieseberg/windows95, 24k stars) and Dotlottie Web (LottieFiles/dotlottie-web, 892 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tsz Architecture?

tsz-org (a GitHub organization) maintains it in tsz-org/tsz, which has 577 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 9, 2026.

Source: tsz-org/tsz on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.