irsdl
- 12 skills
- 0 followers
- 20 hours ago last updated
- ▌
- ▌ Ysonet Dev Create Plan · irsdl bundleCreates an evidence-backed development plan or design document for a non-trivial ysonet change and saves the draft under dev-kitchen/ideas/ for review before implementation. Use when the user asks to plan, propose, design, research a proposed change, or draft an approach for a refactor, architecture or UI change, new gadget, plugin, serializer, build change, dependency change, or other work that should be settled before code is written. Not for immediate implementation, diagnosis-only requests, or tiny mechanical edits.
- ▌ Ysonet Categorize Gadget · irsdl bundleCategorize or review a ysonet gadget and its variants by broad payload kind, formatter, accepted input, target requirements, and the runtime versions the effect is recorded on. Use when adding or changing a gadget, filling uncategorized or unspecified metadata, or checking category search and gadget-help output. Do not use for plugins, which intentionally have no category filter.
- ▌ Ysonet Dev Clr2 Coverage · irsdlTest which ysonet gadgets and plugins fire on the legacy .NET Framework CLR-v2 generation (.NET 2.0 / 3.0 / 3.5) and add only evidence-backed runtime-version claims. Use when asked to check, prove, sweep, or add CLR-v2 / .NET 2-3.5 / legacy-framework coverage, to add NetFx20/30/35 claims, to extend the LEGACY test tier, or to make an inner gadget target an old framework by downgrading its assembly identities. Not for modern .NET (net5+).
- ▌ Ysonet Dev Create Gadget · irsdl bundleCreates or scaffolds a new ysonet IGenerator gadget from verified technique code. It checks uniqueness, gathers missing requirements and credits, classifies facets, systematically attempts the maximum plausible formatter and serializer set, implements real formatter and bridge behavior, registers the source, adds focused and runtime-effect tests, updates the public catalogs, and runs Debug and FULL verification. Use when the user asks to add, create, or scaffold a gadget and expects implementation. Use ysonet-dev-create-plan when the requested deliverable is only a plan. Not for plugins or small edits to an existing gadget.
- ▌
- ▌ Ysonet Dev Implement Plan · irsdl bundleImplements, tests, and verifies an approved ysonet development plan from dev-kitchen/to-be-implemented/ while re-checking it against current code and any configured code-graph database, preserving unrelated work, recording material deviations, updating tests and docs, and surfacing follow-ups. Use when the user asks to implement, build, execute, or finish an existing settled plan. Not for drafting a plan, choosing among unsettled designs, or tiny ad-hoc edits with no plan.
- ▌ Ysonet Audit Gadget Metadata · irsdl bundleAudit or repair ysonet gadget metadata for one gadget or the whole catalog, checking broad categories, accepted input, requirements, formatters, variants, help, documentation, and tests. Use for consistency checks, suspected misinformation, incomplete metadata, or category drift. Do not use for plugins.
- ▌ Ysonet Curate Research Links · irsdl bundleRehydrates docs/dotnet-deserialization-research.md with new .NET deserialization articles, tools, talks, CVE write-ups and advisories, and repairs its links by adjudicating every redirect against the destination page, adopting the new URL when it holds the same material and falling back to a Wayback Machine snapshot when it does not. Use when the user asks to refresh, expand, top up or update the research reading list, add a paper, blog post, tool or CVE to the docs, check the links on a reference page, or fix 404s, moved pages and dead links in the documentation.
- ▌ Ysonet Dev Consistency Check · irsdl bundleRuns a whole-repo consistency audit of ysonet before a release or after a change. Checks that docs match the code, docs/ARCHITECTURE.md is current, both CLIs expose every gadget and plugin, each gadget and plugin has all required parts, tests exist for everything following the existing test patterns, no test opens a real application and every fired command goes through the test sink, all skills and agent files match the Anthropic skill standard, the git-tracked memory under .claude/memory/ is still true and indexed, no ignored, private, or machine-specific content leaked into tracked files, and the full test suite passes with zero errors. Use when the user asks to check consistency, audit the repo, verify docs and tests are in sync, check for private or local data leaking into the public repo, or confirm the tool is release-ready. Read-only until the user approves fixes.
- ▌ Ysonet Dev Validate And Refine · irsdl bundleValidates and refines an existing ysonet development plan, design document, review note, or other Markdown file by treating every factual statement as untrusted, verifying claims against current source, tests, repository rules, and authoritative external evidence, resolving contradictions and vagueness through repeated user questions, and editing or rewriting the document until it is accurate, complete, consistent, actionable, and has no unresolved uncertainty. Use when the user asks to review, validate, verify, fact-check, critique, refine, correct, improve, or rewrite a plan or .md file, including a draft under dev-kitchen/ideas/ or an approved plan that may have drifted.
- ▌ Ysonet Edit Binaryformatter Payload · irsdlInspect, decode, dump, hand-edit, and re-emit a BinaryFormatter / MS-NRBF byte stream as readable JSON without deserializing it, using ysonet's record-level parser. Use when reading an unknown BF blob, changing type or assembly names in an existing payload, hand-building or splicing BF records, spoofing a type, debugging a minified binary payload, or embedding a BF stream inside another gadget. Not for designing a new gadget chain and not for porting a chain to modern .NET.