richlander
- 58 skills
- 0 followers
- 161 repo stars
- last month last updated
- ▌ System Commandline Adopter Probe · richlanderUse when building or modifying a .NET command-line app with System.CommandLine (RootCommand, Command, Option<T>, Argument<T>) on the current GA / 2.x–3.x API. This library had a large breaking redesign at 2.0 GA, so training data and web snippets are FULL of the removed beta stack (SetHandler, AddOption, BinderBase, IConsole). The #1 silent trap: the Option/Argument constructor's 2nd positional argument is an ALIAS, not a description. Covers the core shapes: declaring inputs, building the command tree, SetAction, and reading values by identity. beta-to-GA migration, options/arguments in depth, actions/invocation, subcommands/help, and 3.x additions are covered separately. Don't web-search this API — the current idioms are in the System.CommandLine skills.
- ▌ Dotnet Inspect 2 · richlanderFind evidence for .NET packages, platform libraries, assemblies, APIs, dependencies, SourceLink/source, and API version diffs.
- ▌ Markout · richlanderUse when generating Markdown or other structured output (plain text, ANSI, pretty tables, TSV/JSONL) from C# objects instead of hand-built strings — CLIs, tools, reports, agent output. Markout is a source-generated .NET serializer: it looks like System.Text.Json source-gen but the rules differ (NO reflection fallback), so it needs a generated MarkoutSerializerContext and Markout-specific attributes. Start here for the required pattern; branch to the domain skills for conditional reports, multi-view/verbosity, output formats, built-in shapes, and composite cells/cards. Don't decompile the Markout assembly or web-search its API — every idiom you need is in these skills.
- ▌ Nugetfetch · richlanderLightweight, AOT-friendly NuGet client library for .NET: query versions, download and extract .nupkg packages, and search nuget.org. It is NOT the official NuGet.Protocol / NuGet.Client API — the surface is much smaller and the shapes differ. Key rules: you bring your own HttpClient (NuGetClient has no parameterless ctor), extraction lives on a separate static PackageExtractor class, and NormalizeVersion is static. See the body.
- ▌ Output Formats · richlanderUse when you need output other than default Markdown — plain text / Unicode, ANSI terminal (Spectre), pretty aligned tables, or TSV/JSONL exports — or when one model must serve several formats from a single render path (a CLI `--format` switch). Pick the format with a formatter + MarkoutWriterOptions; never hand-build TSV/JSONL. Requires the base `markout` pattern. Don't decompile the assembly or web-search the API — the TSV/JSONL/formatter idioms are all here.
- ▌ Markout 2 · richlanderSource-generated .NET serializer that renders annotated objects as Markdown. Reach for it when a CLI or tool needs structured, readable output instead of hand-built strings. It looks like System.Text.Json source generation but the rules differ — there is NO reflection fallback, so it needs a generated MarkoutSerializerContext and Markout-specific attributes. Pinned to Markout 0.13.7.
- ▌ Built In Shapes · richlanderUse when a report needs rich visual elements — bar charts, stacked/proportional bars, alert boxes, tree hierarchies, term/definition glossaries, or code blocks — instead of hand-drawn ASCII or manual Markdown. Markout ships these as data types (Metric, Breakdown/Slice, Callout, TreeNode, Description, CodeSection) you attach as model properties. Requires the base `markout` pattern. Don't decompile the assembly or web-search the API — the shape types are here.
- ▌ Nuget MCP · richlander bundleExperiment harness shell that attaches the real upstream NuGet MCP server (NuGet.Mcp.Server). Carries no inline grounding; package context is delivered only via the server's get_package_context tool when the agent chooses to call it.
- ▌ Composite Cells Cards · richlanderUse when a single value must render dense in Markdown but decompose into typed columns in TSV/JSONL — before/after changes, fractions, shares, percentages, segment breakdowns, deltas and goal polarity — or when building metric / role-matrix / verdict cards from one model (Change<V>, Fraction, Share, Percent, Segments, Delta/Goal, MetricChange<T>, MultiSourceRow, Verdict). This is Markout's most advanced tier. Requires the base `markout` pattern. Don't decompile the assembly or web-search the API — these composite types are here.
- ▌ Conditional Composition · richlanderUse when a Markout report must adapt to its data — show or hide whole sections, drop table columns that are empty/uniform, filter output to a chosen set of sections, or render one model into several shapes ("one model, many views"). This is Markout's highest-value idiom: declare the conditions with attributes instead of hand-writing if/else + StringBuilder. Requires the base `markout` pattern (model + context + Serialize). Don't decompile the assembly or web-search the API — the conditional idioms are here.
- ▌ System Text JSON · richlanderUse when a .NET program (de)serializes JSON with System.Text.Json — reading/writing DTOs, configuring JsonSerializerOptions, migrating from Newtonsoft.Json, or hitting a compile-clean behavioral difference. The #1 trap: STJ matches property names CASE-SENSITIVELY by default, so camelCase JSON into PascalCase members silently yields null/default with no exception. Covers the core shapes: options, the naming/casing defaults, and the compile-clean behavioral traps. Newtonsoft migration, source generation / Native AOT, custom converters and polymorphism, DOM / streaming, and .NET 10+ strictness are covered separately. Don't web-search STJ usage — the idioms are in the System.Text.Json skills.
- ▌ System Commandline · richlanderUse when building or modifying a .NET command-line app with System.CommandLine (RootCommand, Command, Option<T>, Argument<T>) on the current GA / 2.x–3.x API. This library had a large breaking redesign at 2.0 GA, so training data and web snippets are FULL of the removed beta stack (SetHandler, AddOption, BinderBase, IConsole). The #1 silent trap: the Option/Argument constructor's 2nd positional argument is an ALIAS, not a description. Covers the small core shape. Pull actions/invocation for dedicated Command.Action classes or cancellation; options/arguments for HelpName, completion, stable case-insensitivity, custom parsing, or cross-option validators; beta migration, subcommands/help, and 3.x additions are separate. Don't web-search this API.
- ▌ Markout Realmcp · richlander bundleExperiment harness shell: attaches the real NuGet.Mcp.Server to the Markout task. Carries no inline grounding; package context is delivered only via the real server's get_package_context tool (README or the package's shipped agent doc, depending on what ships in the package).
- ▌ Markout Custommcp · richlander bundleExperiment harness shell for the custom MCP delivery environment on the Markout task. Carries no inline grounding; curated package context is delivered only via the get_package_context MCP tool when the agent chooses to call it (gate under test = GROUNDING_GATE).
- ▌ Multi Package MCP · richlander bundleExperiment harness shell for the MCP delivery environment (multi-package triage). Carries no inline grounding; package context for any referenced package is delivered only via the get_package_context MCP tool when the agent chooses to call it.
- ▌ Markout Broadskill · richlander bundleThe complete Markout coding-agent integration guide: installation, the required 3-part source-generation pattern (annotate, register on a partial MarkoutSerializerContext, serialize through it), the full attribute reference (including MarkoutLink, MarkoutValueMap, MarkoutSection.GroupBy, MarkoutMaxItems, MarkoutBoolFormat), every built-in shape type (Metric, Breakdown, Callout, TreeNode, Description, CodeSection), and formatter selection (Markdown, TSV, plain text, Spectre). Markout has NO reflection fallback, so a MarkoutSerializerContext is always required.
- ▌ Prefer Dotnet Inspect · richlanderHow to fetch a NuGet package's own authoritative docs with the dotnet-inspect CLI before writing or editing code against it. Use whenever a task requires calling or implementing against a NuGet package's API — especially a package you are not fully confident about. The key rule: run `dotnet-inspect package <id>@<version> --readme`, which returns the package's best shipped doc, and prefer it over guessing or relying on training memory. This is a discovery directive only; it contains no package-specific API content.
- ▌ Microsoft Extensions AI · richlanderMicrosoft.Extensions.AI (IChatClient) usage and migration gotchas. Use when building or fixing chat clients, tool/function calling, or middleware pipelines with Microsoft.Extensions.AI — above all that automatic tool calling requires building the client with ChatClientBuilder(...).UseFunctionInvocation(); without it, tools placed in ChatOptions.Tools are silently never invoked, response.Text is empty, and no error is thrown. Also covers the preview→GA API renames (which have no [Obsolete] shims).
- ▌ System Text JSON MCP · richlander bundleExperiment harness shell for the MCP delivery environment (resident-API probe). Carries no inline grounding; System.Text.Json context is delivered only via the get_package_context MCP tool when the agent chooses to call it.
- ▌ System Text JSON Dom And Streaming · richlanderUse when System.Text.Json work is not a plain POCO round-trip — inspecting/mutating JSON without a model (including answering a few questions about an unknown payload), editing JSON whose shape is not controlled by the app, reading or writing at high throughput (Utf8JsonReader / Utf8JsonWriter, byte and Stream overloads), or processing a JSON array/feed too large to fit in memory (DeserializeAsyncEnumerable).
- ▌ System Commandline MCP · richlander bundleExperiment harness shell for the MCP delivery environment. Carries no inline grounding; package context is delivered only via the get_package_context MCP tool when the agent chooses to call it.
- ▌ System Commandline Net 3x Additions · richlanderUse when targeting System.CommandLine 3.x specifically — the members added over 2.x GA (Argument<T>.CaptureRemainingTokens, the AcceptOnlyFromAmong(StringComparer,...) overload, RootCommand.HelpName) and the current TFM targeting (net10.0 + netstandard2.0, no in-box net8.0). 3.x is additive over 2.x: existing 2.x code compiles unchanged.
- ▌ System Text JSON Newtonsoft Migration · richlanderUse when migrating serialization code from Newtonsoft.Json (Json.NET) to System.Text.Json — replacing JsonConvert / JsonSerializerSettings / [JsonProperty] and reconciling the behavioral differences that compile clean but silently change output (case-sensitivity, fields, nulls, comments, dates).
- ▌ System Text JSON Source Generation Aot · richlanderUse when System.Text.Json runs under Native AOT or trimming (PublishAot / PublishTrimmed), or when you want the faster, reflection-free serialization path — i.e. a JsonSerializerContext with [JsonSerializable]. Reflection-based JsonSerializer compiles but THROWS at run time under AOT; the source generator is the only supported path. Also covers configuring a context with [JsonSourceGenerationOptions] and why naming policy is per-context, not per-model, so one type serialized by two contexts can emit two different spellings, plus word-valued enums that must remain trim/AOT-safe.
- ▌ System Text JSON Dotnet 10 11 Strictness · richlanderUse when targeting recent .NET runtimes (8/9/10+) and you need the newer, stricter System.Text.Json behavior or APIs a model trained on older docs may not know — the JsonSerializerOptions.Strict preset, AllowDuplicateProperties, RespectNullableAnnotations / RespectRequiredConstructorParameters, rejecting unknown/unmapped configuration properties, PipeReader overloads, and JsonMarshal. Also covers why duplicate-key rejection matters at untrusted parse boundaries, the .NET 11 [JsonNamingPolicy] attribute and its non-transitivity, and getting newer STJ APIs on an older runtime via the out-of-band package.
- ▌ System Commandline Readme · richlander bundleOfficial System.CommandLine package README and getting-started documentation. System.CommandLine provides robust support for command-line parsing, invocation, and shell completions in .NET applications. Use when building or working with System.CommandLine command-line apps.
- ▌ System Commandline Beta To Ga Migration · richlanderUse when migrating a .NET CLI from System.CommandLine 2.0.0-beta (beta1–beta4) to the GA / 3.x API, or when you see removed beta symbols (SetHandler, AddOption, AddCommand, AddGlobalOption, BinderBase<T>, IConsole, HelpBuilder, getDefaultValue:, IsRequired, ExistingOnly). beta4 → GA was a breaking redesign of the invocation and binding stack: beta code does NOT compile against GA.
- ▌ System Commandline Subcommands And Help · richlanderUse when building a multi-command System.CommandLine app (nested Command hierarchy), sharing options across subcommands with Recursive (global) options, or customizing help output. HelpBuilder and IConsole are gone — custom help is a SynchronousCommandLineAction on the help option.
- ▌ System Commandline Options And Arguments · richlanderUse when declaring or configuring System.CommandLine inputs — Option<T> and Argument<T>: names vs aliases, Description, HelpName, completion, Required, DefaultValueFactory, Arity, stable-2.x case-insensitive known values, collection parsing, existing file/directory requirements, rejecting bad input, and checking explicit option presence across a command. This is where CompletionSources, CustomParser, Validators.Add, GetResult, and result.AddError belong.
- ▌ System Commandline Actions And Invocation · richlanderUse when the action itself is the hard part — especially a dedicated synchronous/asynchronous action class, Command.Action assignment, shared action bases, dependency-carrying actions, cancellation, Task<int>, exit codes, or splitting Parse(args) from Invoke/InvokeAsync. SetHandler and positional binding are gone. Declaring inputs and rejecting bad ones are separate topics.
- ▌ System Commandline Stable 2x · richlanderUse when building or modifying a .NET command-line app with System.CommandLine (RootCommand, Command, Option<T>, Argument<T>) on the current GA / 2.x–3.x API. This library had a large breaking redesign at 2.0 GA, so training data and web snippets are FULL of the removed beta stack (SetHandler, AddOption, BinderBase, IConsole). The #1 silent trap: the Option/Argument constructor's 2nd positional argument is an ALIAS, not a description. Covers the core shapes: declaring inputs, building the command tree, SetAction, and reading values by identity. beta-to-GA migration, options/arguments in depth, actions/invocation, subcommands/help, and 3.x additions are covered separately. Don't web-search this API — the current idioms are in the System.CommandLine skills.
- ▌ System Text JSON Converters And Polymorphism · richlanderUse when System.Text.Json needs custom value handling — a JsonConverter<T> for a type STJ can't round-trip out of the box (custom dates, value objects, unions), string enums, or polymorphic (base/derived) serialization with a type discriminator.
- ▌ Multi Package Ambiguous MCP · richlander bundleExperiment harness shell for the MCP delivery environment (ambiguous multi-package triage). Carries no inline grounding; package context for any referenced package is delivered only via the get_package_context / summarize_package_context MCP tools when the agent chooses to call them.
- ▌ System Commandline Options And Arguments 2 · richlanderUse when declaring or configuring System.CommandLine inputs — Option<T> and Argument<T>: names vs aliases, Description, Required, DefaultValueFactory, Arity, restricting a value to a fixed set with AcceptOnlyFromAmong, requiring that a file or directory path already exists, rejecting bad or out-of-range input, and checking one option against another. This is where CustomParser, Validators.Add and result.AddError belong. Covers the constructor-alias gotcha in depth.
- ▌ System Commandline Actions And Invocation 2 · richlanderUse when the action itself is the hard part — returning Task<int> from an async action, choosing the process exit code from what the action returns, and splitting Parse(args) from Invoke/InvokeAsync so the ParseResult can be inspected in between. SetHandler and positional binding are gone. Wiring a plain action and reading values are core shapes; declaring inputs and rejecting bad ones are separate topics.
- ▌ Dotnet Allocation Triage · richlanderCross-tool workflow to reduce .NET heap allocations — static triage with dotnet-inspect, then confirm the win with BenchmarkDotNet or dotnet-trace/dotnet-counters before changing code. Use when chasing allocation hot spots on a hot path.
- ▌ Dotnet Releases · richlanderAnswer .NET release lifecycle, timeline, patch, and CVE questions by driving the public `dotnet-release` CLI over the release-index graph.
- ▌
- ▌ Update Os Packages · richlanderAudit and update os-packages.json files in dotnet/core to ensure Linux distribution package names are correct. Verifies package names against upstream package repositories and fixes mismatches.
- ▌ Update Supported Os · richlander bundleAudit and update supported-os.json files in dotnet/core to reflect current OS version support. Uses release-notes verify for automated checking against upstream lifecycle data.
- ▌ Update Distro Packages · richlanderUpdate per-distro package files in release-notes/<version>/distros/ documenting dependencies and .NET package availability for each Linux distribution.
- ▌ Dotnet Inspect Query · richlanderOutput formats, -D/-S discovery and selection, -Q query-capability discovery, value projection, @ categories, and output limits shared across commands.
- ▌ Dotnet Inspect Signals · richlanderSurface a dependency's observable signals — provenance, compatibility, dependency risk, unsafe/PInvoke surface, artifact-text containment, and identifier confusion — to judge how much caution it warrants. Observations, not verdicts.
- ▌ Dotnet Inspect Metadata · richlanderQuery raw ECMA-335 assembly metadata — discover table and heap sections, inspect decoded rows and handles, address table or heap coordinates, and project bounded machine-readable results.
- ▌ Dotnet Inspect Decompiler · richlanderReconstruct a method or type as C# and IL — decompiled source, annotated source with hidden facts, raw IL, fidelity levels, and IL-offset lookup. Use --offline to prohibit package and PDB network acquisition.
- ▌ Dotnet Inspect Sourcelink · richlanderInspect source mapped by Portable PDB and SourceLink data — map files and member locations, fetch source, or resolve checksum-matched content locally.
- ▌ Dotnet Inspect Correctness · richlanderJudge whether code is sound and safe to call — its exception surface (throws, catches, exception types) and the unsafe operations in a method body.
- ▌ Dotnet Inspect Performance · richlanderWhole-assembly call-graph leverage ranking and performance triage for libraries (experimental).
- ▌ Dotnet Inspect Compatibility · richlanderDecide whether a change or upgrade is safe — API-surface diffs, behavioral diffs (allocations, exceptions), feature switches, and version resolution.
- ▌ Dotnet Inspect Private Feeds · richlanderInspect packages from private and custom NuGet feeds safely — select and map sources, use credential providers or explicit configuration, diagnose authentication failures, and reason about source-bound caches and offline operation.
- ▌ Dotnet Inspect Relationships · richlanderMap how code connects — implementors and subclasses, extension methods, dependency graphs, reverse callers, and ecosystem integrations. Many outputs are graph-shaped (add --mermaid).
- ▌ Dotnet Inspect · richlanderFind evidence instead of guessing for .NET packages, platform libraries, local assemblies, APIs, dependencies, and version-to-version API changes.
- ▌ Dotnet Inspect Package Skills · richlanderDiscover and use version-matched agent skills from NuGet packages, and persist selected skills in a repository only when the user explicitly requests it.
- ▌ Release · richlanderUse when shipping a new dotnet-inspect version; coordinate certification, NuGet and GitHub publication, and matching production and CoreCLR site deployments.
- ▌ Deep Inspect · richlanderUse when a dotnet-inspect change needs expensive evidence outside normal PR CI, or when preparing release certification; coordinate Deep Inspect lanes (full slow tests, cross-platform certification, IL round-trip sweep, corpus sensors, package discovery, validity scans, and analysis census).
- ▌ Update Agents Md · richlanderUse before adding, growing, or restructuring content in AGENTS.md — keeps it under its 600-line cap, free of a large table of contents, and limited to cross-cutting binding rules.
- ▌
- ▌