samchon

Acquires and verifies speech, music, effects, and ambience for this production. Use when sourcing or generating audio, arranging dialogue, or checking the finished soundtrack.

Maps the development checklists, common, design, implementation, assets, motion, shots and testing, onto the source declarations and tests that answer them in their doc comments. Use before writing or citing a development contract item.

Holds the checklists Evidence asks, in two families: development for source and tests, and story for research through the screenplay. Use before selecting, answering or citing a contract item.

Maps the story checklists, from performance research and settings through treatments, scripts and the final screenplay to naturalness, discovery and review, onto their unit and population respondents. Use before selecting, answering or citing a story contract…

Implements and tests production source, integrations, dependencies and commands. Use for code or host changes and behavioral tests; documentation owns technical writing and story owns creative bodies.

Owns production requirements, evidence answers and graph configuration. Use to adopt a requirement, configure what the graph selects, or write and audit source evidence; story owns creative answers.

Programs deterministic scene performance, staging, timing, and physical responses. Use when authoring or changing animated behavior, assembling a motion hint, or upgrading a moving instance's representation.

Keeps the project's scope and setup and carries the work after motion, conditioning, video generation, editing, encoding and handoff, to the delivered artifact. Use for project context, sustained runs, media, instruction sync and finishing; story,…

Defines the form each subject of a production takes, namely the polygon man for a person, a coarse form of a few primitives for anything else, and on the user's request a generated, crafted or recovered form with its rig. Use before building or changing a…

Decides what each shot sounds like for the video model to generate, makes a voice preview when the user wants to hear voices before video generation, and builds a soundtrack only when the commission asks for one, always for the user to accept by ear. Use when…

Maps the development checklists, common, design, implementation, testing, entities, behaviors and composition, onto the source declarations and tests that answer them in their doc comments. Use before writing or citing a development contract item.

Holds the checklists Evidence asks, in two families: development for source and tests, and story for research through the screenplay, each broad item with its detailed statements. Use before selecting, answering or citing a contract item.

Maps the story checklists, from research and settings or a short's brief through treatments, scripts and the final screenplay to naturalness, discovery and review, onto their unit and population respondents. Use before selecting, answering or citing a story…

Implements and tests production source, integrations, dependencies and commands, reusing installed packages before writing a capability. Use for code or host changes and behavioral tests; documentation owns technical writing and story owns creative bodies.

Owns how any document is written, with its sentences, terms, paragraphs and lists, and what a README holds. Use before writing or changing a technical document, README or doc comment; instructions for an agent add the prompting skill's rules.

Owns production requirements, evidence answers and graph configuration. Use to adopt a requirement, configure what the graph selects, or write and audit source evidence; story owns creative answers.

Repairs, implements, tests, and validates ttsc source, tests, fixtures, workflows, and package wiring. Use before editing any of them; acknowledgments belong to contracts and the typescript-go shim to typescript-go-sync.

Keeps ttsc's compiler-target shims synchronized with TypeScript-Go and complete for plugin authors. Use before adding a shim re-export, bumping a target's compiler, changing the shim audit or generators, or chasing a missing compiler API.

Defines the @evidence checklists every maintained ttsc declaration and test answers, and their evidence.config.json wiring. Use when writing or reviewing maintained source or tests, or changing Evidence selection.

Owns ttsc's writing rules and writes its READMEs, website guides, and doc comments. Use before writing or changing a README, anything under website/src/content, or a doc comment.

Runs ttsc's issue campaign, repeating full discovery rounds until one finds nothing new, publishing the issues, and landing them in one pull request per cycle. Use for a broad audit or repeated issue-to-pull-request work, not for one defined issue.

Runs, supervises, changes, and publishes ttsc's performance, graph, and evidence benchmarks under benchmarks/. Use before running, changing, or publishing any benchmark or its fixtures.

Writes and trims ttsc's prompts for agents, namely AGENTS.md, CLAUDE.md, and the skills under .agents/skills. Use before changing any of them, together with the documentation skill's writing rules.

Branches, commits, pushes, opens, updates, and merges ttsc pull requests. Use only when the user asks for one of those actions or a mandate names delivery.

Defines the review of @evidence and @evidenceExclude for fake citations, for cited requirements the code contradicts, and for exclusions created solely to evade compiler errors, of configuration edited beyond the one permitted activation, and of the compiler…

Defines how an @samchon/lint-plugin-evidence benchmark campaign is set up, launched under frozen inputs, run, supervised, recovered, and reported, from issue creation through pull-request completion. Use whenever operating, supervising, or reporting a…

Defines the Evidence Graph tag grammar, truthfulness rules, claim activation, frozen configuration, behavioral proof, citations, exclusions, and the stub marker. Read before Evidence implementation or handling a graph diagnostic; backend.md and frontend.md…

Defines backend layer ownership, implementation order, compiler checking, generation boundaries, and the backend gate. Read before backend work, then read every sibling topic.

Defines frontend implementation order, contract use, resident development checking, live integration, and the frontend gate. Read before frontend work, then read every sibling topic.

Defines the full-scope review loop until dry for backend, frontend, and overall review objectives. Read for a review objective or when a final objective must complete an omitted review.

Defines the workspace, package boundaries, generated artifacts, phase order, compiler gates, development processes, and canonical commands. Read before choosing where to work or which command to run.

Defines the authored and generated parts of packages/api, its public entry, shared diagnosers, SDK connections, and simulation boundary. Read before editing or importing the API package.

Defines typia implementation rules, testing standards, validation, consequence analysis, and change integrity. Use before writing or modifying source, tests, workflows, package wiring, fixtures, generated baselines, or algorithms.

Defines the default solo repository-wide issue campaign for typia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo Self-Review, and repeated rediscovery until a full clean round. Use…

Defines the typia product contract, workspace layout, package boundaries, and canonical commands. Use when orienting in the repository, working inside any package, or choosing a build, test, or format command.

Defines the explicitly parallel variants of typia review and issue campaigns. Use only when the user explicitly requests a team, parallel, or multi-agent review or campaign. Route review work to review.md and issue campaigns to issue-campaign.md. Self-Review…

Defines typia benchmark fixture integrity, result reporting, and publication safeguards. Use before running or modifying @typia/benchmark, changing a fixture, or publishing benchmark results.

Defines self-acknowledgments for production declarations and tests. Use when implementing or reviewing maintained source, unit tests or E2E tests, or selecting Evidence checklists.

Defines typia branch, commit, pull-request, check, and merge workflows. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push, update, or…

Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for typia. Use for every self-review or unqualified review request and as the default review mode inside issue campaigns. This skill never spawns review agents; use…

Defines nestia implementation rules, testing standards, validation, consequence analysis, and change integrity. Use before writing or modifying source, tests, workflows, package wiring, fixtures, generated baselines, or algorithms.

Defines the default solo repository-wide issue campaign for nestia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo Self-Review, and repeated rediscovery until a full clean round. Use…

Defines the nestia product contract, workspace layout, package boundaries, the Go plugin composition model, and canonical commands. Use when orienting in the repository, working inside any package, or choosing a build, test, or format command.

Defines nestia branch, commit, pull-request, check, and merge workflows. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push, update, or…

Defines self-acknowledgments for production declarations and tests. Use when implementing or reviewing maintained source, unit tests or E2E tests, or selecting Evidence checklists.

Defines the explicitly parallel variants of nestia review and issue campaigns. Use only when the user explicitly requests a team, parallel, or multi-agent review or campaign. Route review work to review.md and issue campaigns to issue-campaign.md. Self-Review…

Defines README, website-guide, and agent-instruction structure, audience, prose formatting, and voice for nestia. Use before writing, modifying, renaming, or moving repository documentation.

Defines exhaustive solo review, Self-Review, and solo repository-wide issue-discovery rounds for nestia. Use for every self-review or unqualified review request and as the default review mode inside issue campaigns. This skill never spawns review agents; use…

Defines how @samchon/graph keeps its supported-language registry, LSP configuration, static fallback, CLI and MCP names, deterministic fixtures, real-server experiments, workflows, and documentation synchronized. Use before adding or changing a language,…

Defines @samchon/graph implementation rules, consequence analysis, testing standards, validation, and change integrity. Use before writing or modifying source, tests, workflows, package wiring, fixtures, generated publications, index algorithms, MCP…

Defines the explicitly parallel @samchon/graph variants of review and issue campaigns. Use only when the user explicitly requests a team, parallel, or multi-agent review or issue campaign. Route review work to review.md and issue campaigns to…

Defines exhaustive solo @samchon/graph Self-Review, unqualified review, and repository-wide issue-discovery rounds. Use for every self-review or unqualified review request and as the default review mode inside an issue campaign. This skill never spawns review…

Defines the default solo @samchon/graph repository-wide issue campaign: exhaustive discovery, lead-vetted issue publication, one integrated implementation pull request per cycle, CI repair, solo Self-Review, cleanup, and renewed discovery. Use for broad…

Defines @samchon/graph branch, commit, pull-request, check, and merge workflows. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push,…

Defines @samchon/graph benchmark selection, external fixture isolation, comparator fairness, trace and result integrity, and publication safeguards. Use before running or modifying deterministic benchmark checks, corpus manifests, paid agent A/B runs,…

Defines public README, maintainer-document, and agent-instruction structure, source-of-truth boundaries, concise prose, formatting, and voice for @samchon/graph. Use before writing, modifying, renaming, or moving repository Markdown documentation, CLI or MCP…

Defines the authored and generated parts of packages/api, its public entry, shared diagnosers, SDK connections, and simulation boundary. Read before editing or importing the API package.

Defines the authored and generated parts of packages/api, its public entry, shared diagnosers, SDK connections, and simulation boundary. Read before editing or importing the API package.

Defines the Evidence Graph tag grammar, per-citation reviews, truthfulness rules, claim activation, frozen configuration, behavioral proof, citations, exclusions, and the stub marker. Read before Evidence implementation or handling a graph diagnostic;…

Defines frontend implementation order, contract use, resident development checking, live integration, and the frontend gate. Read before frontend work, then read every sibling topic.

Defines the authored and generated parts of packages/api, its public entry, shared diagnosers, SDK connections, and simulation boundary. Read before editing or importing the API package.

Defines the Evidence Graph tag grammar, per-citation reviews, truthfulness rules, claim activation, frozen configuration, behavioral proof, citations, exclusions, and the stub marker. Read before Evidence implementation or handling a graph diagnostic;…

Defines frontend implementation order, contract use, resident development checking, live integration, and the frontend gate. Read before frontend work, then read every sibling topic.

Defines the authored and generated parts of packages/api, its public entry, shared diagnosers, SDK connections, and simulation boundary. Read before editing or importing the API package.

Defines the CodeHUD product contract, what the product deliberately does not do, the two adapter axes, workspace layout, and canonical commands. Use when orienting in the repository, working inside any package, choosing a build, test, format, or evidence…

Defines CodeHUD implementation rules, package boundaries, testing standards, the coverage obligation on changed positions, validation, and change integrity. Use before writing or modifying source, tests, workflows, package wiring, or fixtures.

Defines CodeHUD branch, commit, pull-request, check-reading, and merge workflows. Use when shipping a topic-unit PR under the standing instruction, when the user asks to open, update, or merge a pull request, or when the standing autonomous mandate authorizes…

Defines the .wiki/ working knowledge base, package READMEs, source JSDoc, agent-instruction conventions, and the repository writing voice for CodeHUD. Use before writing or modifying any document, AGENTS.md, or a SKILL.md, and revise the wiki as the work…

Defines the committed trace from product requirements through system specifications to public source exports for CodeHUD, its @wrtnlabs/evidence populations, citations, exclusions, stable anchors, and the review of the required triangle. Use before adding,…

Defines the solo issue campaign for CodeHUD: exhaustive discovery, wiki-backed adjudication, issue publication, then one issue at a time through implementation, Self-Review, CI, and merge, followed by renewed discovery. Use for broad audits, many issue…

Defines exhaustive review, Self-Review, and solo repository-wide issue-discovery rounds for CodeHUD. Use for every self-review or unqualified review request and as the review mode inside an issue campaign. One reviewer always covers one whole declared…

Defines how to settle a claim that only a physical pair of glasses can settle, what a measurement must record, and how the result reaches the contract documents. Use when an issue is labelled hardware, when a design decision rests on an unmeasured device…

Defines @samchon/evidence-graph implementation rules, testing standards, validation, consequence analysis, and change integrity. Use before writing or modifying source, tests, workflows, package wiring, fixtures, or algorithms.

Defines README, guide, and agent-instruction structure, audience, concise prose, and voice for @samchon/evidence-graph. Use before writing, modifying, renaming, or moving user-facing repository documentation, AGENTS.md, or any SKILL.md; do not use for the…

Defines the evidence graph domain model for @samchon/evidence-graph — the tag grammar, node kinds, reference resolution, the three questions the rules ask (integrity, obligation, coverage), activation gates, and exemptions. Use before changing rule semantics,…

Defines the @ttsc/lint contributor contract for @samchon/evidence-graph — the hybrid TypeScript-descriptor plus Go-source package shape, the Go rule API, project-scoped rules, options typing, and the expensive defaults the API sets for you. Use before adding…

Defines the @samchon/evidence-graph product contract, workspace layout, package boundaries, and canonical commands. Use when orienting in the repository, working inside any package, or choosing a build, test, or format command.

Defines @samchon/evidence-graph branch, commit, pull-request, check, and merge workflow. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open,…

Defines the .wiki/ knowledge base for @samchon/evidence-graph — what belongs in it, its Korean and no-wrap writing rules, and the obligation to correct it the moment a claim proves false. Use when researching prior art, recording an architectural decision, or…

Owns Blendia declaration and test Evidence checklists and their package selectors. Use when writing or reviewing selected declarations, test scenarios, or Evidence configuration.

Implements and validates Blendia source, tests, package wiring, tooling, and workflows. Use before editing those files; declaration evidence belongs to contracts.

Writes Blendia maintained documentation, README examples, and doc comments. Use before authoring or changing those surfaces, including skill prose.

Defines Blendia scope, package and language boundaries, and workspace commands. Use when deciding ownership, product scope, or how to build and run checks.

Maintains Blendia user instructions, agent routers, skills, and supporting guides with single ownership and precise triggers. Use before changing AGENTS.md, CLAUDE.md, .agents/user-instructions.md, or .agents/skills.

Maintains Blendia issue records and delivers scoped pull requests under the user's standing merge mandate. Use for issue updates and branch, commit, push, PR, or merge work.

Reviews a complete Blendia change and its real consumers, evidence, tests, and CI. Use for every review and self-review before delivery.

Defines the @ttsc/lint contributor contract for @samchon/evidence — the hybrid TypeScript-descriptor plus Go-source package shape, the Go rule API, project-scoped rules, options typing, and the expensive defaults the API sets for you. Use before adding or…

Defines the evidence graph domain model for @samchon/evidence — the tag grammar, node kinds, reference resolution, the three questions the rules ask (integrity, obligation, coverage), activation gates, and exemptions. Use before changing rule semantics, the…

Defines @samchon/evidence implementation rules, testing standards, validation, consequence analysis, and change integrity. Use before writing or modifying source, tests, workflows, package wiring, fixtures, or algorithms.

Defines README and guide structure, audience, prose formatting, and voice for @samchon/evidence. Use before writing, modifying, renaming, or moving user-facing repository documentation; do not use for the .wiki knowledge base, which the wiki skill owns.

Defines the @samchon/evidence product contract, workspace layout, package boundaries, and canonical commands. Use when orienting in the repository, working inside any package, or choosing a build, test, or format command.

Defines @samchon/evidence branch, commit, pull-request, check, and merge workflow. Use when the user explicitly asks to open, submit, update, or merge a pull request, or when a standing autonomous mandate authorizes end-to-end delivery; never open, push,…

Defines the .wiki/ knowledge base for @samchon/evidence — what belongs in it, its Korean and no-wrap writing rules, and the obligation to correct it the moment a claim proves false. Use when researching prior art, recording an architectural decision, or…