rudironsoni

AI-powered wiki generation for code repositories with commands, agents, and skills

Routes .NET/C# work to domain skills. Loads coding-standards for code paths.

Skill manifest management for dotnet-agent-harness. Tracks skill dependencies, conflicts, version compatibility, and provides validation and resolution tools. Triggers on: skill manifest, dependency resolution, skill compatibility, version conflicts, build manifest, validate dependencies.

Design patterns and architectural guidance for .NET applications. Navigation skill covering vertical slices, domain modeling, messaging patterns, resilience, caching, and system design. For building scalable, maintainable applications. Keywords: architecture, patterns, vertical slices, domain modeling, messaging, resilience, caching, design patterns

Configures artifacts output layout. UseArtifactsOutput, ArtifactsPath, impact on CI and Docker.

Containerizes .NET apps. Multi-stage Dockerfiles, SDK container publish (.NET 8+), rootless.

Reads and modifies SDK-style .csproj files. PropertyGroup, ItemGroup, CPM, props.

Core C# and .NET language fundamentals. Navigation skill covering coding standards, language patterns, async/await, dependency injection, configuration, and foundational runtime concepts. Entry point for developers building .NET applications. Keywords: csharp, dotnet, fundamentals, coding standards, async, patterns, dependency injection, configuration, basics

Rulesync CLI tool documentation - unified AI rule file management for various AI coding tools

Publishes .NET artifacts from Azure DevOps. NuGet push, containers to ACR, pipeline artifacts.

Reads and modifies SDK-style .csproj files. PropertyGroup, ItemGroup, CPM, props.

Publishes .NET artifacts from GitHub Actions. NuGet push, container images, signing, SBOM.

Builds event-driven systems. Pub/sub, competing consumers, DLQ, sagas, delivery guarantees.

Adds fault tolerance. Polly v8 + MS.Extensions.Http.Resilience, retry/circuit breaker/timeout.

Microsoft Learn MCP Server integration for accessing official Microsoft documentation

Rulesync CLI tool documentation - unified AI rule file management for various AI coding tools

Review code for quality, correctness, and maintainability. Use this skill when reviewing pull requests, auditing existing code, refactoring for clarity, or enforcing coding standards. Covers DRY principles, SOLID design, error handling, performance, security, testing, and TypeScript/JavaScript best practices. For Obsidian plugin-specific API guidance, refer to the obsidian-plugin-development skill.

Use the Obsidian CLI to inspect a running advanced-code-block Obsidian plugin session during development. Covers plugin reloads, console/errors, runtime evaluation, settings tab checks, reading-mode and live-preview syntax highlighting, screenshots, and mobile emulation with app.emulateMobile(true). Use WebdriverIO for automated runtime acceptance.

Build, modify, and debug Obsidian plugins using the TypeScript API. Use this skill when working with Obsidian plugin source code, the obsidian npm package, plugin UI (views, modals, settings, commands, ribbons), vault file operations, editor manipulation, workspace management, metadata cache, events, markdown rendering, or the Obsidian CLI. Covers plugin lifecycle, best practices, common patterns, and the full TypeScript API surface.

Acceptance test workflow for the obsidian-advanced-code-editor Obsidian plugin. Use when the user asks to test the plugin, smoke test a release, verify before release, test BRAT/mobile installs, validate syntax highlighting, or judge whether startup and rendering still work. Uses local checks first, then WebdriverIO runtime checks, then release-asset or BRAT-style verification. Does not spend API tokens and does not commit source changes.

Acceptance test workflow for the obsidian-advanced-code-editor Obsidian plugin. Use when the user asks to test the plugin, smoke test a release, verify before release, test BRAT/mobile installs, validate syntax highlighting, or judge whether startup and rendering still work. Uses local checks first, then Obsidian CLI/runtime checks, then release-asset or BRAT-style verification. Does not spend API tokens and does not commit source changes.

Use the Obsidian CLI to inspect a running advanced-code-block Obsidian plugin session during development. Covers plugin reloads, console/errors, runtime evaluation, settings tab checks, reading-mode and live-preview syntax highlighting, screenshots, and mobile emulation with app.emulateMobile(true). Use WebdriverIO for automated runtime acceptance.

Acceptance test workflow for the obsidian-advanced-code-editor Obsidian plugin. Use when the user asks to test the plugin, smoke test a release, verify before release, test BRAT/mobile installs, validate syntax highlighting, or judge whether startup and rendering still work. Uses local checks first, then WebdriverIO runtime checks, then release-asset or BRAT-style verification. Does not spend API tokens and does not commit source changes.

Use the Obsidian CLI to inspect a running advanced-code-block Obsidian plugin session during development. Covers plugin reloads, console/errors, runtime evaluation, settings tab checks, reading-mode and live-preview syntax highlighting, screenshots, and mobile emulation with app.emulateMobile(true). Use WebdriverIO for automated runtime acceptance.

Draft outbound announcements from ontology-brain facts. Use when asked to announce, summarize for others, write an update, or turn brain facts into a reviewable message.

Update ontology-brain from one changed source, object, decision, or note. Use when a specific item should be filed, canonical facts should change, references should be propagated, or a page should be created or refreshed.

Health-check ontology-brain. Use before shipping any brain change, when asked to lint or audit the brain, or when pages may have broken links, stale index entries, duplicated facts, relationship drift, or ontology anti-patterns.

Answer questions from ontology-brain. Use for what, why, status, dependency, ownership, source, or relationship questions where the compiled brain should be checked before re-reading raw material.

Reconcile ontology-brain with a source set or maintenance window. Use when asked to refresh, sync, audit freshness, or bring the brain up to date across multiple pages.

Apply the Palantir Foundry Ontology model to ontology-brain. Use for schema decisions, object type choices, typed links, property placement, normalization, source modeling, or ontology health reviews.

Configures GitHub Actions .NET build/test -- setup-dotnet, NuGet cache, reporting.

Deploys .NET from GitHub Actions. Azure Web Apps, GitHub Pages, container registries.

Composes GitHub Actions workflows. Reusable workflows, composite actions, matrix, caching.

Publishes .NET artifacts from GitHub Actions. NuGet push, container images, signing, SBOM.

Publishes .NET artifacts from Azure DevOps. NuGet push, containers to ACR, pipeline artifacts.

Publishes .NET artifacts from GitHub Actions. NuGet push, container images, signing, SBOM.