Explore skills
Showing 47641–47670 of 77104 skills
Design, implement, migrate, debug, review, and test ReactiveUI 24+ applications. USE FOR: ReactiveObject; WhenAnyValue; ObservableAsPropertyHelper/ToProperty; ReactiveCommand; WhenActivated; Bind/OneWayBind/BindCommand; Interaction; routing and view location; RxAppBuilder; source generators; ReactiveUI.Primitives vs *.Reactive distributions; schedulers; DynamicData; validation; WPF, Avalonia, MAUI, WinUI, WinForms, Blazor. DO NOT USE FOR: generic Rx.NET pipelines without MVVM (use dotnet-rx); unrelated MVVM frameworks; visual UI design.
NetFabric/intelligentium
Stars: 2Claude CodeCodexModern .NET and C# best practices for code quality, performance, and correctness. USE FOR: choosing struct/class/record/readonly-record-struct; nullable reference types; pattern matching; primary constructors; collection expressions; required members; init-only properties; file-scoped namespaces; global usings; async/await patterns; ConfigureAwait; ValueTask vs Task; CancellationToken propagation; IAsyncEnumerable; Span<T>/Memory<T> usage; avoiding boxing; readonly struct; ArrayPool<T>; FrozenDictionary/FrozenSet; LINQ vs loops in hot paths; ArgumentNullException.ThrowIfNull; ThrowIfNegative; ThrowIfZero; IReadOnlyList return types; error handling patterns; GeneratedRegex; LoggerMessage; source generators for regex and logging; avoiding Math/MathF in favor of static methods on the numeric type. DO NOT USE FOR: generic math interfaces (use dotnet-generic-math); ASP.NET Core middleware; EF Core modeling.
NetFabric/intelligentium
Stars: 2Claude CodeCodexBuild, run, and publish .NET applications from a single C# file without a .csproj, using .NET 10 SDK file-based apps. USE FOR: dotnet run file.cs; dotnet run --file; shebang/shell-executable C# scripts; colon-prefixed directives (sdk, package, project, property, include); converting a file-based app to a project with dotnet project convert; publishing file-based apps with native AOT; packaging a file-based app as a .NET tool (PackAsTool); user secrets for file-based apps; flat *.run.json launch profiles; dotnet build/clean/publish/pack/restore on a .cs file; build caching behavior and dotnet clean file-based-apps; folder layout to avoid project-file cone conflicts. DO NOT USE FOR: traditional .csproj solution scaffolding (use dotnet-solution-setup); C# language idioms unrelated to the SDK/CLI (use csharp-best-practices); benchmarking (use dotnet-benchmarking).
NetFabric/intelligentium
Stars: 2Claude CodeCodexDesign, implement, debug, test, and review in-process producer-consumer pipelines with System.Threading.Channels. USE FOR: Channel<T>, ChannelReader<T>, ChannelWriter<T>, bounded/unbounded queues, BoundedChannelFullMode, backpressure, TryWrite, WriteAsync, ReadAsync, ReadAllAsync, completion, cancellation, concurrent producers/consumers, BackgroundService workers, in-memory event queues, overload protection, and channel performance. DO NOT USE FOR: durable or cross-process messaging, distributed pub/sub, broker delivery guarantees, Rx.NET stream composition, task-parallel dataflow blocks, or simple thread-safe collections with no asynchronous producer-consumer requirement.
NetFabric/intelligentium
Stars: 2Claude CodeCodexAbstract math for trigonometric functions: definitions, domains, ranges, key identities, and inverse functions. USE FOR: implementing sin/cos/tan/cot/sec/csc; implementing arcsin/arccos/arctan/atan2/acot/asec/acsc; validating input domains for inverse trig; applying Pythagorean and angle-sum identities; choosing atan vs atan2; precision near domain boundaries. DO NOT USE FOR: angle unit conversions (use angles-and-circular-arithmetic); coordinate system conversions (use coordinate-system-conversions); rotation representations (use 3d-rotation-theory).
NetFabric/intelligentium
Stars: 2Claude CodeCodexBuild, maintain, debug, and review Visual Studio Code extensions. Use when: extension manifest, activation, commands, views, tree views, webviews, notifications, settings, language providers, tasks, debuggers, custom editors, authentication, Accounts, sign-in, account management, session lifecycle, Workspace Trust, desktop or web compatibility, testing, CI, packaging, Marketplace publishing. DO NOT USE FOR: general web applications or Copilot agent customization; use the relevant web-development or agent-authoring guidance.
NetFabric/intelligentium
Stars: 2Claude CodeCodexImplement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexCreate a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexIndependent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexStandalone testing skill — owns writing and running tests, verifying behavior, and two-pass TDD orchestration. Default mode analyzes changed scope and runs the relevant tests; `--unit`/`--integration`/`--e2e`/`--all` scope by test type; `--verify` reruns exactly the prior failures; `--all-phases <plan>` sweeps every completed phase for regression. `--tdd --prepare`/`--tdd --verify` bracket `ck:cook` for red-green TDD. Never edits production code, and blocks until a phase's `ck:quality` gate is APPROVED (except `--tdd --prepare`, which runs before any implementation exists).
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexDispatch to the right problem-solving technique based on how you're stuck
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 1 of the SRS workflow. User gives a project topic → AI runs a deep, categorized brainstorm (5 mandatory rounds) to fully understand actors, features, scope boundary, tech constraints, and business rules before writing anything.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 6 of the SRS workflow. Reads approved plan files and generates a complete IEEE 830-compliant SRS — one file per section, no word limit. A full SRS may span 300+ pages across all files.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 8 of the SRS workflow. Generates an improvement report covering deferred features, technical risks, validation warnings, and next-version candidates. No word limit.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 4 of the SRS workflow. Reads spec.md and writes one detailed plan file per SRS section (§1–§3 + Appendices). Each file is a complete blueprint for the corresponding SRS section. No word limit.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 9 of the SRS workflow. Saves all project context to _context/ files so future Claude sessions can resume without re-reading the full SRS.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 2 of the SRS workflow. Reads projects/{slug}/brainstorm.md and writes a comprehensive spec.md. No word limit.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 7 of the SRS workflow. Runs srs_validator.py --dir on the generated SRS files, reports errors and warnings, auto-fixes ERRORs, and outputs a COMPLIANT / PARTIALLY COMPLIANT / NON-COMPLIANT verdict.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexGenerate IEEE 830 SRS from raw requirements. Use when the user says "write SRS", "generate requirements doc", "analyze requirements", "I have raw requirements from a client", or pastes a client email/chat/PRD.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexFull SRS workflow: Brainstorm → Spec → Plan (per-section files) → User Review → SRS Generation → Validation → Improvement Report → Context Save. Use when user provides a project topic and wants a complete requirements pipeline.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexImplement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexCreate a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexIndependent senior-engineering quality auditor — architecture, ownership, domain integrity, abstraction, and maintainability. Use as `--gate` inside the ck:cook pipeline (blocks a phase on BLOCKER/HIGH/current-change MEDIUM findings) or call directly with `--audit`, `--diff`, `--changed` on any repository, directory, or file. Never writes tests and never edits production code — it returns structured findings only; ck:cook or ck:fix apply the fix.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexStandalone testing skill — owns writing and running tests, verifying behavior, and two-pass TDD orchestration. Default mode analyzes changed scope and runs the relevant tests; `--unit`/`--integration`/`--e2e`/`--all` scope by test type; `--verify` reruns exactly the prior failures; `--all-phases <plan>` sweeps every completed phase for regression. `--tdd --prepare`/`--tdd --verify` bracket `ck:cook` for red-green TDD. Never edits production code, and blocks until a phase's `ck:quality` gate is APPROVED (except `--tdd --prepare`, which runs before any implementation exists).
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexDispatch to the right problem-solving technique based on how you're stuck
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 1 of the SRS workflow. User gives a project topic → AI runs a deep, categorized brainstorm (5 mandatory rounds) to fully understand actors, features, scope boundary, tech constraints, and business rules before writing anything.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 6 of the SRS workflow. Reads approved plan files and generates a complete IEEE 830-compliant SRS — one file per section, no word limit. A full SRS may span 300+ pages across all files.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 8 of the SRS workflow. Generates an improvement report covering deferred features, technical risks, validation warnings, and next-version candidates. No word limit.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 4 of the SRS workflow. Reads spec.md and writes one detailed plan file per SRS section (§1–§3 + Appendices). Each file is a complete blueprint for the corresponding SRS section. No word limit.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexPhase 9 of the SRS workflow. Saves all project context to _context/ files so future Claude sessions can resume without re-reading the full SRS.
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodex