Run any Skill in Manus with one click

toolchain-fidelity

Stars3

Forks0

UpdatedJuly 6, 2026 at 23:29

Load before hand-writing or hand-editing files a toolchain normally generates or owns — Xcode project files, lockfiles, generated schemas or migrations, IDE workspace files. Do not load for ordinary source code.

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

AmbitiousRealism2025

AmbitiousRealism2025/Albion

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

SKILL.md

readonly

name	toolchain-fidelity
description	Load before hand-writing or hand-editing files a toolchain normally generates or owns — Xcode project files, lockfiles, generated schemas or migrations, IDE workspace files. Do not load for ordinary source code.

Toolchain Fidelity

Extend charter §4: a generated-format file is correct only if its owning tool accepts it — linting is a floor, not the standard.

Rules

Prefer the generating tool over hand-writing. If the environment has the generator (project scaffolds, package managers, schema generators), use it and modify its output minimally.
A hand-written or hand-edited generated-format file must round-trip through its owning tool before verification: open it, build with it, or validate with it, and record that check in verification.md.
Do not invent keys or structure by analogy. Copy from a tool-generated reference or the format's documentation, and cite which on the board.
A setting that fights the platform default (manual signing, disabled automatic schemes, pinned generated versions) needs its reason recorded in task.md — otherwise the default stands.

More from this repository

same repository

hot-path

AmbitiousRealism2025/Albion

Load before implementing anything that runs continuously or per-item at scale — animation and render loops, timers, pollers, per-request middleware, large-collection iteration. Do not load for one-shot scripts, setup code, or paths that run a bounded handful of times.

2026-07-063

maturity-assessment

AmbitiousRealism2025/Albion

Load when entering an unfamiliar codebase, or before proposing an architecture-level change. Do not load for tiny edits, known local fixes, post-implementation summaries, or tasks already scoped by a current state-map.md.

2026-07-053

recovery

AmbitiousRealism2025/Albion

Load on strike 3, a tangled run, or a contradiction that cannot be localized. Do not load for first failures, ordinary test red/green loops, or known environment outages.

2026-07-053

conductor

AmbitiousRealism2025/Albion

Load for cross-session orchestration — dispatching work to an Albion/GLM worker over tmux, polling a worker completion manifest, or reviewing worker output. Do not load for in-session subagent delegation; use delegation instead.

2026-07-043

completion-gate

AmbitiousRealism2025/Albion

Load when the stop gate blocks twice on the same task. Do not load for ordinary unfinished work, first gate blocks, or reports where no completion claim is being made.

2026-07-043

delegation

AmbitiousRealism2025/Albion

Load when writing a subagent brief for non-trivial dispatched work. Do not load for direct edits, trivial lookups, user-facing summaries, or delegation already covered by an existing brief.

2026-07-043

name	toolchain-fidelity
description	Load before hand-writing or hand-editing files a toolchain normally generates or owns — Xcode project files, lockfiles, generated schemas or migrations, IDE workspace files. Do not load for ordinary source code.

Toolchain Fidelity

Extend charter §4: a generated-format file is correct only if its owning tool accepts it — linting is a floor, not the standard.

Rules

Prefer the generating tool over hand-writing. If the environment has the generator (project scaffolds, package managers, schema generators), use it and modify its output minimally.
A hand-written or hand-edited generated-format file must round-trip through its owning tool before verification: open it, build with it, or validate with it, and record that check in verification.md.
Do not invent keys or structure by analogy. Copy from a tool-generated reference or the format's documentation, and cite which on the board.
A setting that fights the platform default (manual signing, disabled automatic schemes, pinned generated versions) needs its reason recorded in task.md — otherwise the default stands.