Coding Agent
mastra-ai/mastra
Authoring playbook for building agents that write, edit, review, or refactor code.
Keeps truST's architecture simple and well separated, and runs the automated architecture checks.
Install St Lsp Solid
$ npx skills add johannesPettersson80/trust-platform --skill st-lsp-solid -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install johannesPettersson80/trust-platform st-lsp-solid --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/st-lsp-solid .claude/skills/st-lsp-solid && rm -rf skills-srcUse ~/.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/
Install the "st-lsp-solid" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/st-lsp-solid into .claude/skills/st-lsp-solid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "st-lsp-solid", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/st-lsp-solidType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add johannesPettersson80/trust-platform --skill st-lsp-solid -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install johannesPettersson80/trust-platform st-lsp-solid --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/st-lsp-solid .agents/skills/st-lsp-solid && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "st-lsp-solid" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/st-lsp-solid into .agents/skills/st-lsp-solid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "st-lsp-solid", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add johannesPettersson80/trust-platform --skill st-lsp-solid -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install johannesPettersson80/trust-platform st-lsp-solid --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/st-lsp-solid .cursor/skills/st-lsp-solid && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "st-lsp-solid" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/st-lsp-solid into .cursor/skills/st-lsp-solid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "st-lsp-solid", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/johannesPettersson80/trust-platform.git --path .codex/skills/st-lsp-solid--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add johannesPettersson80/trust-platform --skill st-lsp-solid -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install johannesPettersson80/trust-platform st-lsp-solid --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/st-lsp-solid .gemini/skills/st-lsp-solid && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "st-lsp-solid" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/st-lsp-solid into .gemini/skills/st-lsp-solid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "st-lsp-solid", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install johannesPettersson80/trust-platform st-lsp-solidInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add johannesPettersson80/trust-platform --skill st-lsp-solid -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/st-lsp-solid .github/skills/st-lsp-solid && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "st-lsp-solid" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/st-lsp-solid into .github/skills/st-lsp-solid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "st-lsp-solid", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add johannesPettersson80/trust-platform --skill st-lsp-solid -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install johannesPettersson80/trust-platform st-lsp-solid --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/johannesPettersson80/trust-platform.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/st-lsp-solid .opencode/skills/st-lsp-solid && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "st-lsp-solid" agent skill from https://github.com/johannesPettersson80/trust-platform/tree/main/.codex/skills/st-lsp-solid into .opencode/skills/st-lsp-solid/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "st-lsp-solid", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
st-lsp-solid- GitHub stars
- 222
- Token cost
- ~1.3k tokens
- SKILL.md length
- 583 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Keeps truST's architecture simple and well separated, and runs the automated architecture checks.
- Boundary changes in the runtime
- SKILL.md covers Before changing structure, Rules, Architecture automation and Validation
- Calls cargo and bash
- Language server
What it does
St Lsp Solid is an agent skill from johannesPettersson80/trust-platform. Keeps truST's architecture simple and well separated, and runs the automated architecture checks. Use for refactors, module splits, ownership or boundary changes in the runtime, language server, IDE, CLI or xtask gates; for files nearing 1,000 lines; for runtime launcher, control, I/O, retain, watchdog or debugger flow; and for architecture-doctor, software maps, diagram claims, and static-analysis, fuzz, Miri, mutation or performance tooling.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Refactoring and Static analysis and SAST. It works with Rust and TypeScript. The repository describes itself as: truST Platform — IEC 61131‑3 Structured Text tooling suite. The licence is Apache-2.0.
When your agent uses it
- Boundary changes in the runtime
- Language server
- For files nearing 1
- For runtime launcher
Example prompts
- “Use the st-lsp-solid skill to keep truST's architecture simple and well separated, and runs the automated architecture checks”
- “/st-lsp-solid”
What it can do on your machine
Read from SKILL.md and the folder at commit b7d8ffb. 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:
cargobash
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
St Lsp Solid loads about 1.3k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 583 words of instructions outside code blocks.
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 johannesPettersson80/trust-platform at commit b7d8ffb, republished under its Apache-2.0 licence (© johannesPettersson80). 583 words, ~1,257 tokens.
Download SKILL.mdSave it as
.claude/skills/st-lsp-solid/SKILL.md (or your agent's skills folder).- name
- st-lsp-solid
- description
- Keeps truST's architecture simple and well separated, and runs the automated architecture checks. Use for refactors, module splits, ownership or boundary changes in the runtime, language server, IDE, CLI or xtask gates; for files nearing 1,000 lines; for runtime launcher, control, I/O, retain, watchdog or debugger flow; and for architecture-doctor, software maps, diagram claims, and static-analysis, fuzz, Miri, mutation or performance tooling.
Architecture and structure
Hard rule (AGENTS.md): all logic is in Rust. Logic is anything whose result is stored, sent to a runtime or PLC, or decides an engineering or operator outcome. TypeScript only presents (drawing, layout, mouse interaction, view state) and forwards requests to Rust. Never add logic in TypeScript. Existing TypeScript logic is debt to move into Rust, not to extend.
A structural change never moves logic into TypeScript. Reshaping code that holds TypeScript logic
moves that logic into a Rust crate, reached through a trust-lsp command or the runtime protocol.
Before changing structure
- Name the change. State the module's single responsibility, and say whether the change is a behaviour-preserving refactor or a behaviour change.
- Refactors keep behavior-lock tests passing before and after (
trust-test-authoring). - Boundary crossings: when a change crosses runtime boundaries (launcher, control, I/O, retain, watchdog, debug), design the interface or subsystem split first.
- Known gaps: read the Runtime SOLID section of
docs/internal/testing/checklists/architecture-improvements.md, and add any new gaps you find there.
Rules
- Transport and logic: keep transport separate from business logic. The control server stays apart from its handlers, and CLI parsing apart from runtime assembly.
- External dependencies: put them behind traits. These include I/O drivers, retain stores and watchdog actions.
- No god objects or god files: this includes xtask gate and proof files.
- Add a small module for each responsibility, and compose them.
- Split a file that passes about 1,000 lines or mixes responsibilities.
- New validators and proof checks always go in a new module.
- Stable contracts: keep public APIs and contracts stable unless the task changes them.
- Unavoidable deviations: record them in
docs/notes/runtime-refactor-notes.mdwith a follow-up item. - Diagrams: changes to ownership, data flow or execution flow update the PlantUML diagrams (AGENTS.md, "Diagrams").
Show full SKILL.md (297 more words)Show less
Architecture automation
Facts first: code facts are the truth, and diagrams are views checked against them. Prefer repo-specific doctor checks for project semantics; generic tools supply raw facts.
The doctor: run
cargo xtask architecture-doctorbefore declaring architecture work complete.- Add
--full-mapfor module splits, for large-file waivers, or for changes toxtask/config/full_map_policy.json. bash scripts/architecture_safety_gate.shis the CI form.- A new doctor check is proven by a known-bad fixture that fails before the fix and passes after.
- Add
Diagram order: regenerate diagrams only after the factual checks pass.
Tool records: plan and record tool work in
docs/internal/testing/checklists/architecture-automation-tooling.md. If a tool cannot be installed or run, record the blocker and the fallback.Tools by purpose:
Purpose Tools Code map cargo metadata, guppy,cargo tree,cargo-modules, rustdoc JSON,ra_ap_syntax, ast-grep, tree-sitter,cargo-call-stackForbidden patterns Semgrep, Dylint Supply chain and API cargo deny,cargo audit,cargo machete,cargo udeps,cargo geiger,cargo about,cargo semver-checks,cargo public-apiTest adequacy cargo nextest,cargo llvm-cov,cargo mutants,cargo fuzz, property testsDeep checks Miri, sanitizers, loom, Valgrind, rr Performance and size Criterion, trust-runtime bench,cargo bloat,cargo llvm-lines,cargo build --timings, flamegraphVariable initializers (parser, HIR, runtime): the doctor keeps these properties:
parse_var_initializeris called only in initializer-aware contexts;- HIR owns the source initializer metadata and never stores a runtime
Value; - the runtime materializes lowered initializers through the initializer service;
- VM local and static initializers behave like normal startup;
- cross-project imports translate initializer IDs;
- no
_initializerdiscard ordefault_initializer: Noneregression comes back.
Validation
- Runtime changes: run the runtime vertical (AGENTS.md).
- Local checks:
cargo test -p xtaskand the doctor for the touched area are cheap enough to run on the Pi. - Performance: measure on the product CPU, an AM6442 Cortex-A53. Results from the Pi 5's Cortex-A76 or from the builder do not transfer.
© johannesPettersson80, 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 .codex/skills/st-lsp-solid of johannesPettersson80/trust-platform.
Open the folder on GitHubat commit b7d8ffb
Compare with similar skills
St Lsp Solid 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| St Lsp Solid this skilljohannesPettersson80/trust-platform | 222 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Coding Agentmastra-ai/mastra | 29k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| jscpd Duplicate Code Detectorkucherenko/jscpd | 6.4k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Rust Architectsergigp/yarrtube | 141 | — | ~6.1k | Automated safety check: Pass | MIT | |
| Maintainability Reviewpmndrs/glyph | 395 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Code RefinerMathews-Tom/armory | 329 | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
jscpd Duplicate Code Detector
kucherenko/jscpd
Finds duplicated code in 220+ languages with jscpd, reports exact, renamed and near-miss clones in a compact agent-friendly format and measures duplication.
Rust Architect
sergigp/yarrtube
Architecture, naming, and testing conventions guidelines for architecting Rust codebases.
Maintainability Review
pmndrs/glyph
Audit and improve repository code milestone by milestone for correctness, clarity, local reasoning, DRY design, explicit state modeling, panic resistance, and trustworthy TypeScript boundaries.
Code Refiner
Mathews-Tom/armory
Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust.
Docstring Generator
espennilsen/pi
Generate and update language-idiomatic doc comments for TypeScript (TSDoc/JSDoc) and Rust (Rustdoc).
More from johannesPettersson80/trust-platform
Trust CI Release Gates
johannesPettersson80/trust-platform
Prepares and ships truST changes - changelog and version updates, CI parity, pre-push checks, the exact-SHA release-candidate guard, merge, tag and release verification.
Trust Remote Builder
johannesPettersson80/trust-platform
Runs truST builds and tests on the shared trust-builder machine.
Trust Test Authoring
johannesPettersson80/trust-platform
Routes truST behaviour changes from the written specification to a native executable test.
Trust Hmi Contracts
johannesPettersson80/trust-platform
Guides work on truST's HMI - the HMI Builder editor, page files, the runtime display at /hmi, bindings, commands and writes, authorization, alarms and trends, the plant library and the HMI tests.
Trust Lsp Iec
johannesPettersson80/trust-platform
Guides IEC 61131-3 Structured Text language work in truST - lexer, parser, types, semantics, standard functions and function blocks, OOP, namespaces and editor features - checked against the standard.
Trust Vscode Quality
johannesPettersson80/trust-platform
Builds and verifies truST's VS Code extension - commands, webviews, snippets, debug flows, Control Studio, HMI Builder, Devices & Connections and the test harness.
Related
Works with
Categories
Questions about St Lsp Solid
What does St Lsp Solid do?
Keeps truST's architecture simple and well separated, and runs the automated architecture checks. St Lsp Solid is an agent skill from johannesPettersson80/trust-platform. Keeps truST's architecture simple and well separated, and runs the automated architecture checks.
When should I use St Lsp Solid?
St Lsp Solid fits situations like: boundary changes in the runtime; language server; for files nearing 1; for runtime launcher.
How do I install St Lsp Solid in Claude Code?
Run `npx skills add johannesPettersson80/trust-platform --skill st-lsp-solid -a claude-code`. Or copy the skill folder (.codex/skills/st-lsp-solid in johannesPettersson80/trust-platform) into .claude/skills/st-lsp-solid in your project. Claude Code loads it when a task matches its description.
How do I install St Lsp Solid in Codex?
Run `npx skills add johannesPettersson80/trust-platform --skill st-lsp-solid -a codex`. Or copy the skill folder (.codex/skills/st-lsp-solid in johannesPettersson80/trust-platform) into .agents/skills/st-lsp-solid in your project. Codex loads it when a task matches its description.
Can I use St Lsp Solid 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 johannesPettersson80/trust-platform --skill st-lsp-solid -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/st-lsp-solid, .gemini/skills/st-lsp-solid, .github/skills/st-lsp-solid and .opencode/skills/st-lsp-solid in your project.
What does St Lsp Solid need to run?
Going by SKILL.md and its folder, St Lsp Solid needs the command-line tools its instructions call (cargo and bash).
Does St Lsp Solid 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 St Lsp Solid 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 St Lsp Solid use?
St Lsp Solid 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 St Lsp Solid use?
About 1.3k tokens (SKILL.md is roughly 5k 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 St Lsp Solid?
Skills that share tags, products or a category with St Lsp Solid: Coding Agent (mastra-ai/mastra, 29k stars), jscpd Duplicate Code Detector (kucherenko/jscpd, 6.4k stars), Rust Architect (sergigp/yarrtube, 141 stars) and Maintainability Review (pmndrs/glyph, 395 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains St Lsp Solid?
johannesPettersson80 (a GitHub user) maintains it in johannesPettersson80/trust-platform, which has 222 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 11, 2026.
Source: johannesPettersson80/trust-platform on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.