dills122
- 46 skills
- 0 followers
- 3 hours ago last updated
- ▌
- ▌ Filter Syntax · dills122 bundleReference data for test filter syntax across all platform and framework combinations: VSTest --filter expressions, MTP filters for MSTest/NUnit/xUnit v3/TUnit, and VSTest-to-MTP filter translation. DO NOT USE directly — loaded by run-tests, mtp-hot-reload, and migrate-vstest-to-mtp when they need filter syntax.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Directory Build Organization · dills122 bundleGuide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props, and Directory.Build.rsp. USE FOR: structuring multi-project repos, centralizing build settings, implementing NuGet Central Package Management (CPM) with ManagePackageVersionsCentrally, consolidating duplicated properties across .csproj files, setting up multi-level Directory.Build hierarchy with GetPathOfFileAbove, understanding evaluation order (Directory.Build.props → SDK .props → .csproj → SDK .targets → Directory.Build.targets). Critical pitfall: $(TargetFramework) conditions in .props silently fail for single-targeting projects — must use .targets. DO NOT USE FOR: non-MSBuild build systems, migrating legacy projects to SDK-style (use msbuild-modernization), single-project solutions with no shared settings.
- ▌ Product Strategy · dills122Create a comprehensive product strategy using the 9-section Product Strategy Canvas — vision, segments, costs, value propositions, trade-offs, metrics, growth, capabilities, and defensibility. Use when building a product strategy, creating a strategic plan, or defining product direction.
- ▌ Positioning Ideas · dills122Brainstorm product positioning ideas differentiated from competitors. Identifies top competitors and generates positioning statements with rationale. Use when developing product positioning, differentiating from competitors, or crafting brand positioning strategy.
- ▌ Competitor Analysis · dills122Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
- ▌ Customer Journey Map · dills122Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
- ▌ Brainstorm Ideas New · dills122Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
- ▌ Opportunity Solution Tree · dills122Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to opportunities, solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when structuring discovery work, mapping opportunities to solutions, or deciding what to build next.
- ▌ Idea Refine · dills122 bundleRefines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or "stress-test my plan".
- ▌ Browser Testing With Devtools · dills122Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
- ▌ Dependency Auditor · dills122 bundleAudit and manage dependencies across multi-language projects. Identifies vulnerabilities, license conflicts, transitive dependency risks, and safe-upgrade paths. Use when auditing third-party packages before release, investigating a CVE, planning a major version bump, or running a license-compliance review.
- ▌ API Design Reviewer · dills122 bundleComprehensive REST API design review with automated linting, breaking-change detection, and design scorecards. Catches inconsistent conventions, missing versioning, and design smells before APIs ship. Use when reviewing a PR that adds or changes API endpoints, auditing an existing API for v2 migration, or establishing API standards for a team.
- ▌ Performance Profiler · dills122 bundleSystematic performance profiling for Node.js, Python, and Go applications. Identifies CPU, memory, and I/O bottlenecks, generates flamegraphs, analyzes bundle sizes, optimizes database queries, runs load tests with k6 and Artillery. Always measures before and after. Use when investigating a slow endpoint, planning a performance budget, or hunting a memory leak in production.
- ▌ CI CD Pipeline Builder · dills122 bundleGenerate pragmatic CI/CD pipelines from detected project stack signals — fast baseline generation, repeatable checks, environment-aware deployment stages. Use when setting up CI for a new project, refactoring existing pipelines, or standardizing deployment workflows across multiple repos.
- ▌ Observability Designer · dills122 bundleDesign production-ready observability strategies combining metrics, logs, and traces. Includes SLI/SLO design, golden-signals monitoring, alert optimization. Use when adding observability to a new service, refactoring alerting that is too noisy, or designing an SLO program before scaling production load.
- ▌ Review · dills122 bundleReview Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".
- ▌ Slo Architect · dills122 bundleUse when defining, reviewing, or operating SLOs/SLIs/error budgets. Triggers on "define an SLO", "what should our SLO be", "error budget", "burn rate", "SLI", "service level objective", "Google SRE workbook", "multi-window burn-rate alert", or any reliability-target question. Ships SLO designer, error-budget calculator with multi-window burn-rate thresholds, and SLO reviewer that catches the common bugs (target too aggressive, window too short, conflicting SLOs, no SLI definition). 4 references on SLO principles + SLI design + error budget math + composition with feature-flags-architect/chaos-engineering/kubernetes-operator. NOT a generic observability skill — specifically the SLO discipline.
- ▌ Humanizer · dills122 bundleAudit and revise existing prose so it reads naturally, specifically, and consistently with the author's voice while preserving every supported fact, number, citation, code block, link target, and intentional technical term. Use for a final editorial pass on blog posts, documentation, essays, announcements, or other prose that feels generic, repetitive, inflated, or recognizably machine-shaped; do not use as the primary research or drafting workflow or to evade disclosure requirements.
- ▌ Hallmark Design · dills122Design, audit, redesign, or study distinctive user-facing pages without generic AI aesthetics. Use for intentional landing pages, portfolios, product marketing pages, visual redesigns, or design-DNA analysis of a screenshot or public URL.
- ▌ Dotnet Architecture · dills122 bundleAssess, design, implement, or review architectural boundaries in a .NET application using Clean Architecture, ports and adapters, onion architecture, modular monolith, or vertical slices. Use when a task changes project dependencies, domain/application/infrastructure ownership, use-case flow, repositories or query models, domain events, composition roots, or architecture tests. Do not use for a local C# edit whose boundary ownership is already clear.
- ▌ Planning Files Lite · dills122Uses persistent markdown files to keep complex multi-step work organized across long sessions. Use when work requires research, many tool calls, multiple phases, or context recovery.
- ▌ Session Handoff · dills122 bundleCreate, validate, consume, or refresh a durable repository handoff for continuing work in another Codex chat or after context reset. Use when pausing substantial work, moving an outcome to a separate task, resuming from a handoff, or preserving state that would otherwise exist only in conversation history. Do not create handoffs for trivial completed work.
- ▌ Spec Traceability · dills122 bundleMaintain end-to-end traceability from repository requirements and decisions through implementation tasks, tests, evidence, and completion status. Use when writing or updating specs and plans, splitting work across sessions or agents, validating a feature against acceptance criteria, reconciling plan drift, or deciding whether work is actually complete.
- ▌ Frontend Design Review · dills122Reviews and improves frontend interfaces for visual craft, UX clarity, accessibility, responsive behavior, interaction states, content hierarchy, and implementation quality. Use when building, redesigning, auditing, or polishing user-facing UI.
- ▌ Kotlin Jvm Engineering · dills122 bundleImplement, refactor, review, or debug Kotlin/JVM services, libraries, CLI tools, and applications built with Gradle. Use for Kotlin source, Gradle Kotlin DSL, JVM toolchain compatibility, dependency and module changes, coroutine behavior, public APIs, Java interoperability, generated code, tests, or CI.
- ▌ Independent Review · dills122 bundlePrepare and conduct a fresh-context engineering review of completed or substantially complete work, covering both the code changes and the implementation plan. Use when an implementation chat must explain its approach for a senior-maintainer review, when that explanation and repository scope will be handed to a brand-new chat for independent assessment, or when reviewing whether completed work is correct, well-designed, idiomatic, sufficiently tested, and faithful to its plan. Do not use as a substitute for ordinary in-session self-checks or for a review that intentionally shares the author's full conversation history.
- ▌ Project Story Miner · dills122 bundleReconstruct a software project's journey from repository history, source code, issues, pull requests, ADRs, benchmarks, incident notes, and author recollections, then produce a story-ready evidence brief. Use before writing an engineering retrospective, architecture journey, performance story, migration post, launch narrative, or multi-post series when the important turning points and proof boundaries are scattered across project artifacts.
- ▌ Github Keychain Auth · dills122 bundleUse the macOS Keychain-backed GitHub credential safely outside the sandbox for GitHub CLI, Git, and API operations. Use when GitHub authentication fails, an inherited GH_TOKEN or GITHUB_TOKEN may be stale, a task needs the routinely configured Keychain credential, or an agent must verify GitHub access without exposing credential bytes.
- ▌ Repository Doc Drift · dills122 bundleAudit canonical repository documentation against current code, configuration, tests, generated contracts, and recent Git history, then make minimal evidence-backed corrections. Use after feature merges or releases, when plans and status may be stale, when README or architecture claims are questioned, or when multiple docs disagree about the current source of truth.
- ▌ Research To Decision · dills122 bundleRun bounded technical or product research and turn it into a decision-ready repository artifact. Use when a spec, architecture choice, dependency, standard, feasibility gate, or implementation plan depends on external evidence or a controlled experiment, especially when research is delegated to another agent or chat.
- ▌ Run Tests · dills122 bundleRun or recommend the exact .NET test command. ALWAYS USE when asked to run, filter, or troubleshoot .NET tests or provide precise flags/argument order. Supports SDK-style dotnet test and classic non-SDK projects using MSBuild plus vstest.console/MSTest or repository scripts. USE FOR: all tests or subsets by class/category/trait; multi-TFM --framework; TRX reports; crash/hang dumps; VSTest vs Microsoft.Testing.Platform; bridged vs native MTP argument syntax; --filter, --filter-class, --filter-trait, --filter-query, and --treenode-filter. Detects MSTest/xUnit/NUnit/TUnit and packages.config/classic project constraints. DO NOT USE FOR: writing tests (use code-testing-agent), MTP hot-reload iteration, CI/CD configuration, or debugging test logic.
- ▌ Orchestrated Delivery · dills122 bundlePlan, dispatch, monitor, reconcile, and close multi-agent or multi-chat repository work. Use when a brain or lead chat owns a larger outcome, when work must be split across subagents or separate Codex tasks, when a task graph has parallel lanes, or when child handoffs must be integrated into one verified repository result. Do not use for a small self-contained change that one agent can finish directly.
- ▌ Technical Blog Writer · dills122 bundleDraft, rewrite, review, or structure technical blog posts, engineering retrospectives, architecture explainers, benchmark analyses, project stories, tutorials, how-to guides, and related series from a brief, evidence packet, notes, or source files. Use when prose must remain technically accurate, preserve facts and proof boundaries, explain why engineering details matter, and sound conversational and recognizably authored rather than generic or promotional.
- ▌ Inspect Node Package API · dills122 bundleResolve and inspect the public API of an installed Node.js package without executing it. Use when Codex needs to understand a dependency in node_modules, verify an import or subpath, find exported functions, classes, types, or signatures, trace TypeScript declaration re-exports, compare ESM/CommonJS/type entry points, or determine the installed package version and interface before writing integration code.
- ▌ Using Agent Skills · dills122Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
- ▌ Platform Detection · dills122 bundleDetect a .NET project's test platform/framework and SDK-style vs classic project system. ALWAYS USE for "which test platform/framework?", "VSTest or MTP?", a wrong dotnet test runner, or hidden runner settings in global.json, .csproj, packages.config, Directory.Build.props, or Directory.Packages.props. Handles SDK-version precedence and MSTest/xUnit/NUnit/TUnit. DO NOT USE for running/filtering tests (run-tests), hot reload, or migration.
- ▌ Migration Architect · dills122 bundleZero-downtime migration planning, compatibility validation, and rollback strategy generation. Tools for system, database, and infrastructure migrations with minimal business impact. Use when planning a database migration, infrastructure cutover, system replacement, or any high-risk transition that needs explicit rollback paths.
- ▌ Terraform Patterns · dills122 bundleTerraform infrastructure-as-code agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Covers module design patterns, state management strategies, provider configuration, security hardening, policy-as-code with Sentinel/OPA, and CI/CD plan/apply workflows. Use when: user wants to design Terraform modules, manage state backends, review Terraform security, implement multi-region deployments, or follow IaC best practices.