envoydev
- 129 skills
- 0 followers
- 1 repo stars
- 3 days ago last updated
- ▌ Loop Test Coverage Quality · envoydev bundleUse when asked to raise the test coverage or run the coverage loop. Manual, /-only. Not for measuring only (capture-quality), code polish or architecture.
- ▌ Capture Preferences · envoydev bundleUse when asked to capture or change the user's personal, code, architecture, git or tool preferences ('answer briefly', 'rank my tools'). Manual, /-only.
- ▌ Habits Plan Writing · envoydevUse when writing, stamping or resuming a plan file - 'write a plan', 'write it up as a plan'. Not for the design, which task-design owns.
- ▌ Issue Signatures CI · envoydev bundleUse when CI or a PR check goes red - red CI, passes locally but fails in CI, NU1301, ERESOLVE, exit 137. Not for a local crash or authoring CI/CD.
- ▌ Repo Audit Plugins · envoydev bundleUse when auditing the third-party plugins Alfred Code installs and their dependencies - use, cost, supply chain, fit. Not for Alfred Code itself.
- ▌ Capture Usage Report · envoydev bundleUse when asked to analyze the stack usage or audit this project's sessions for token and tool cost. Manual, /-only. Not for live cost or fixing findings.
- ▌ Habits Code Comments · envoydevUse when writing a doc comment or an inline comment - XML docs, TSDoc, JSDoc, docstring. Not for READMEs or docs pages, which the docs skills own.
- ▌ Habits Create Ticket · envoydev bundleUse when the user wants a ticket written or reworked - 'create a bug/story/epic/task ticket', 'create jira ticket', 'file a bug'. Not for code fixes.
- ▌ Habits Explain Topic · envoydev bundleUse when asked to explain a topic or code in depth - 'teach me X', 'ELI5', 'step by step', 'walk me through this'. Not for quick lookups or fixes.
- ▌ Task Version Upgrade · envoydev bundleUse when planning a breaking upgrade - 'upgrade to .NET 10', 'ng update to v20', 'this package's new major breaks us'. Not for routine bumps.
- ▌ Repo Audit Claude Md · envoydev bundleUse when auditing and fixing the shipped CLAUDE.md template (stack/AGENTS.template.md) toward grade A - facts, hub, rule links, tokens. Not for rule files.
- ▌ Habits Adjust Agents Md · envoydevUse when asked to fill in or update AGENTS.md or CLAUDE.md, or one is written - an unfilled seed, a stale one, a part needing its own. Not for skills or rules.
- ▌ Task Build From Scratch · envoydev bundleUse when asked to build from scratch, start a new app or go greenfield - before any code exists. Manual, /-only. Not for changing an existing codebase.
- ▌ Habits Commit Checkpoint · envoydev bundleUse before a non-trivial git commit, a push or merging a change request - 'commit this', 'push it', 'merge it'. Not for the done gate, which proves it works.
- ▌ Issue Signatures Runtime · envoydev bundleUse when a runtime failure needs a cause - a local or production stack trace, exception, hang, broken screen, NullReferenceException, NG0201. Not for red CI.
- ▌ Habits Execution Strategy · envoydev bundleUse before deciding how to run a multi-step build or fix - route, mode, seats, 'split this up', 'run in parallel'. Not for a small task, which settles inline.
- ▌ Loop Architecture Quality · envoydev bundleUse when asked to run the architecture quality loop or to analyze and improve the architecture. Manual, /-only. Not for code polish or a capture-only run.
- ▌ Habits Root Cause · envoydevUse when a failure's cause is unproven, before any fix - red test, build or auth error, stack trace, flaky run. Not for a known error code, which catalogs hold.
- ▌ Habits Test First · envoydevUse before writing production code for a feature, bug fix or behavior change - before the first source edit. Not for config or docs edits, which skip tests.
- ▌ Loop Code Quality · envoydev bundleUse when asked to run the quality loop or the code-quality loop - analyze, triage, fix. Manual, /-only. Has a staged mode. Not for architecture.
- ▌ Plugin Authoring · envoydev bundleUse when creating or changing a Claude Code plugin - a `.claude-plugin/plugin.json` manifest, a `marketplace.json`, plugin commands / skills / agents / hooks / MCP or LSP config, `${CLAUDE_PLUGIN_ROOT}` paths - or when publishing, versioning or testing one (`claude plugin validate`, `--plugin-dir`, `claude plugin eval`). Covers manifest schema, layout and precedence, distribution, versioning, per-component rules, verification and the security review. Not for a project's own `.claude/` folder, and not for authoring one skill's body.
- ▌ Repo Audit Hooks · envoydev bundleUse when auditing this repo's hooks (stack/hooks) and hooks its plugins bring - placement, exit contract, cost, safety, ledger evidence, fit. Not for rules.
- ▌ Repo Audit Rules · envoydev bundleUse when auditing and fixing this repo's rule files (stack/rules) toward grade A - mechanism, always-on cost, conflicts, duplication. Not for CLAUDE.md.
- ▌ Repo Audit Usage · envoydev bundleUse when collecting consuming projects' Claude Code sessions and auditing how the stack did - tokens, gates, skills, docs. Not for one project's own report.
- ▌ Alfred Code · envoydevRoute to the right Alfred Code action when unsure which fits - inspects the install state and answers with the exact command to run: /alfred-code:init (nothing installed: the selection and the install, ending on a restart; typed again after it: the one-time bootstrap - language-server tools, the status line, captures, AGENTS.md), /alfred-code:update (no-questions refresh + prune of upstream removals), /alfred-code:configure (adjust an existing install - add or drop), /alfred-code:validate (reconcile an install against THIS project - prune what its frameworks do not use and add the detected stacks' missing artifacts), /alfred-code:status (read-only per-area tables of what is installed), /alfred-code:uninstall (remove the stack from this project, keeping the user's own config). Trigger by invoking /alfred-code.
- ▌ Desktop Automation · envoydev bundleUse when driving a native desktop app through a desktop server (Windows-MCP, MacOS-MCP) - click, type, read a Snapshot. Not for web pages or the app code.
- ▌ Mode Output Scorer · envoydev bundleUse when a 'scorer: on' or 'scorer: stacked' line is in context and a plan, verdict or answer is drafted - grade it with a fresh seat before releasing it.
- ▌ Repo Audit Agents · envoydev bundleUse when auditing and fixing this repo's shipped subagents (stack/agents) toward grade A - routing, expertise, tool scope, reuse. Not for skills or rules.
- ▌ Repo Audit Skills · envoydev bundleUse when auditing and fixing this repo's shipped skills (stack/skills) toward grade A - triggers, structure, token cost, reuse. Not for agents or rules.
- ▌ Repo Audit System · envoydev bundleUse when auditing Alfred Code as one system - conflicts across its parts, token budget, hook value, safety, fresh-session context, its own packaging.
- ▌ Javascript 2 · envoydev bundleLoad before writing or editing any .js, .jsx, .mjs or .cjs file in any runtime - the base layer for JS-family code. Not for C#/.NET or other languages.
- ▌ Solve Task · envoydevUse when solving a task in this repo end to end - '/solve-task', 'solve this', 'spec, plan and build it'. This repo's own flow, not the stack's task-solve.
- ▌ Mode Auto Run · envoydevUse when the user types /mode-auto-run <request> - auto-run turns on for the session and the request runs to its end, each ask taking its Recommended option.
- ▌ Habits Clarify · envoydev bundleUse before designing a change that can be read more than one way - 'make it better', 'add support for X'. Not for build choices, which a plan records.
- ▌ Task Implement · envoydev bundleUse to build a task plan in this chat, task by task - 'execute the plan', 'build the plan', 'implement task 2'. Not for ad-hoc edits or the full gated cycle.
- ▌ Capture Quality · envoydev bundleUse when asked about test coverage, or to assess how good the code or architecture is - deliberate only. Not for fixes or writing tests (the quality loops).
- ▌ Issue Diagnoser · envoydev bundleUse when a failure needs investigating - an error event, logs, red CI, a stack trace, 'what is causing this'. Not for the fix, which /task-solve owns.
- ▌ Review Security · envoydev bundleUse when a change touches auth, crypto, secrets, payment or data access - 'security review', 'is this safe'. Not for a full audit (security-auditor).
- ▌ Markdown Style 2 · envoydev bundleLoad when authoring or restructuring any .md, or on 'lint / style-check / fix this markdown', 'ATX vs setext', 'use a TOC?'. Not for prose clarity or spelling.
- ▌ Refining Plans · envoydev bundleUse when a spec or plan is drafted for the user's approval, or on 'grade this plan' / 'scoring for plans' - a fresh reviewer grades it to 90+.
- ▌ Habits Done Gate · envoydevUse before saying your own change is done, fixed, passing, working, ready or 'should work now'. Not for someone else's change, which a code review owns.
- ▌ Task Solve Cross · envoydev bundleUse when work spans backend and frontend, a cross-stack bug, or to route agent seats - 'plan the agents for this'. Not for greenfield builds.
- ▌ Task Verify Code · envoydev bundleUse to review an assembled build against its plan - 'review the build', 'review before done'. Not for an unplanned change (review-code) or the done gate.
- ▌ Task Verify Plan · envoydev bundleUse to audit an existing plan or design before code - 'review this plan', 'is this design sound', 'does it miss anything'. Not plan writing or code review.
- ▌ Skill Authoring · envoydevUse when writing, changing or reviewing a skill or its description - or when one does not fire. Not for a plugin manifest, which plugin-authoring owns.
- ▌ Capture Awareness · envoydev bundleUse when asked to capture or note project awareness - run book, Jira/Sentry, architecture map, module boundaries, code style, siblings. Not for judging quality.
- ▌ Auto Run · envoydevLoad before the first step when the user is away or says 'auto mode', 'without stopping', 'run without asking' or 'take the recommended options'.
- ▌ Task Solve · envoydev bundleUse to run a task through the gated single-chat vertical - 'run the task cycle', 'build this with approvals', 'with my sign-off'. Not a one-line edit.
- ▌ Review Code · envoydev bundleUse when reviewing a diff, branch, PR or path for bugs - 'review this', 'review my changes', 'code review'. Not for a planned build (task-verify-code).
- ▌ Task Design · envoydev bundleUse to settle how a feature fits the existing code before writing any - 'design this feature', 'plan this change'. Not for one-line edits or a plan audit.
- ▌ Nx · envoydevUse when working in an Nx monorepo - an `nx.json` / `project.json` workspace, or `nx` commands - for the token-efficient way to navigate the project graph and scope work. Orient through the CLI's derived graph (`nx show projects`, `nx graph`, `nx show project`) rather than reading config, scope every build/test/lint to `nx affected` instead of the whole tree, scaffold with `nx generate`, and enforce module boundaries with tags. Draws the line against serena - Nx answers project-graph and affected questions, serena answers symbol-level code questions. For the Angular code conventions themselves see `angular-conventions`; this is the workspace/monorepo layer above them.
- ▌ NPM · envoydev bundleProfessional npm usage for consuming and publishing packages: lockfile + npm ci discipline, the supply-chain baseline (ignore-scripts, the min-release-age cooldown, allow-git=none, OIDC publishing, scoped internal packages), honest npm-audit gating, overrides vs --legacy-peer-deps, exports maps and ESM-first publishing, update-bot cooldowns. Fires on package.json / package-lock.json / .npmrc work, npm install/ci/publish questions, dependency updates or vulnerability reports, supply-chain concerns, 'set up npm for this repo'. NOT for TS language style (typescript skill), Angular framework conventions (angular-conventions), or authoring CI pipelines beyond npm's own steps (the devops family).
- ▌ Ionic · envoydev bundleIonic / Capacitor mobile + hybrid app conventions - house rules for Ionic Angular UI (standalone + signals, IonRouterOutlet, page-caching view lifecycle, CSS-variable theming), Capacitor lifecycle + platform guards, runtime permissions, and Capacitor plugin sourcing (official -> Capawesome -> capacitor-community) + typed-service wrapping. Targets Ionic 8+ (9 current) / Angular 17+ / Capacitor 6+ (8 current). Load before building or editing an Ionic/Capacitor app - anywhere ionic.config.json or capacitor.config.* lives. Companions: angular-conventions, typescript. Do NOT load for plain web Angular with no native shell.
- ▌ Csharp · envoydev bundleC# conventions (.NET 8 / C# 12 floor) - style/structure (file layout, naming, member/ctor ordering, methods, types, visibility, design-pattern (GoF) awareness, modern C# 12/13/14 syntax, forbidden patterns, XML doc) and runtime behavior (DateTime/TimeProvider, async, dispose, exceptions + Result, structured logging, secrets/config, LINQ, System.Text.Json, decoupling + DI lifetimes). Load before creating or editing any `.cs` file - writing, reviewing, or refactoring C#; do not lean on recalled conventions. The always-load baseline; specialist areas (performance, EF, web, messaging, hosted workers) route out through the .NET companion router when your skill list has one, not here.
- ▌ Devops · envoydev bundleDevOps reference for the .NET/Angular house, by the delivery surface a change touches: container builds (multi-stage, cache-ordered layers, non-root, digest-pinned base images), Compose local topology, GitHub Actions CI/CD (SHA-pinned actions, masked secrets, least-privilege permissions, OIDC, real service containers), and safe deploys (immutable artifact promotion, gated expand-contract migrations, health-gated cutover with rollback). Load when authoring or reviewing a Dockerfile, a compose file, a workflow, a deploy pipeline, an env/secret template, or the Aspire AppHost - or when the devops vertical or security-auditor sweeps the delivery stack. Points at dotnet-aspire, dotnet-migrate, and dotnet-security / database-security. Do NOT load for application or schema code.
- ▌ Dotnet · envoydevRouter and complete index for .NET / C# specialist skills - maps a concrete work area (a construct, command, file, or task) to the one focused skill to load, across language & types, architecture & structure, ASP.NET Core & web, cross-cutting hardening, data & EF, messaging & orchestration, hosting & background work, testing & quality, diagnostics & performance, and desktop (WPF / WinForms). Routes per area, does not restate the skills. Load when starting or navigating any .NET / C# backend or desktop work - typed asks like 'add an endpoint to the orders API', 'my BackgroundService stopped overnight', or 'which skill covers EF Core queries' all start here. Companion: csharp (always, for any C#). For web front-end see frontend; for Ionic/Capacitor see mobile.
- ▌ Mobile · envoydevRouter and index for Ionic / Capacitor mobile + hybrid app work - maps a mobile area (Ionic Angular UI, the Capacitor native layer, native plugins, the store/release/signing pipeline, mobile security hardening) to the focused leaf skill via the body's routing table. Load when starting mobile work and unsure which area applies - 'add a camera feature', 'why does the back button close the app', 'get this build into TestFlight' - or when orienting in a codebase with ionic.config.json or capacitor.config.*; go straight to the leaf skill when the area is known. Companions: angular-conventions, typescript. For plain web frontend see frontend; for .NET backend see dotnet.
- ▌ Sqlite · envoydevSQLite engine specialist - the SQLite-specific delta on top of the cross-engine database-conventions hub: when SQLite fits, the single-writer / WAL concurrency model and busy-timeout, PRAGMAs (foreign_keys, journal_mode, synchronous), type affinity vs STRICT tables and date/bool storage, limited ALTER TABLE and the table-rebuild, connection-per-thread and in-memory test DBs, B-tree-only indexing, FTS5, and backup. Load for a SQLite .db, a PRAGMA, an embedded/desktop/mobile/test store, or an EF Core SQLite provider quirk. Not the cross-engine schema/transaction rules (-> database-conventions) or a server-class concurrent-writer workload (-> postgres). Companions: database-conventions (cross-engine hub - load first), dotnet-data-access (the EF Core / ORM side), postgres (the other engine).
- ▌ Webpack · envoydev bundleWebpack 5 build engineering, library-in-monorepo focus (TS + JS): the transpile/type-check split (swc-loader + fork-ts-checker + tsc --emitDeclarationOnly), externals from package.json, the tree-shaking preconditions, ESM output state and the fullySpecified/extensionAlias resolution traps, filesystem-cache pitfalls, the shared config-factory pattern. Fires on webpack.config work, loader/plugin choices, 'bundle this library', tree-shaking or 'failed to resolve as fully specified' errors, slow webpack builds. NOT for Vite/Rollup projects, Angular CLI builds (angular-conventions), or package publishing mechanics (npm skill).
- ▌ Frontend · envoydevRouter and index for web frontend work - maps a frontend area (Angular framework code, TypeScript/JavaScript language, Material/CDK components, CSS/SCSS styling, client-side security, library docs) to the focused skill to load, plus the in-skill Design quality bar. Load when starting web UI work where the right skill is not yet obvious - a feature spanning components, styles, and security, or orienting in an unfamiliar frontend codebase; asks like 'add a profile page with a form and avatar upload' or 'make this dashboard look less generic' start here. Do NOT load when the leaf skill is already known - go straight to it (typescript is always the companion for TS/JS). For Ionic/Capacitor mobile see mobile; for .NET backend see dotnet.
- ▌ Postgres · envoydev bundlePostgreSQL engine specialist - the Postgres-specific delta on top of the cross-engine database-conventions hub: identifier folding and idempotent DDL, index-type selection (B-tree/GIN/GiST/BRIN/hash), JSONB and full-text indexing, SARGable predicate rewrites, the planner (EXPLAIN ANALYZE, pg_stat_statements, autovacuum/ANALYZE, work_mem), connection pooling modes, and array-batching/ON CONFLICT/COPY. Load for any hand-written Postgres SQL, an .sql file on a Postgres project, an EXPLAIN plan, a slow query, or an index/pooling decision. Not the cross-engine schema/transaction rules (-> database-conventions), the ORM side (-> dotnet-data-access), or another engine's SQL. Companions: database-conventions (cross-engine hub - load first), database-security (RLS/privileges), dotnet-data-access (the EF Core / ORM side).
- ▌ Dotnet Wpf · envoydev bundleWPF conventions - strict MVVM with a one-way View-knows-ViewModel dependency, CommunityToolkit.Mvvm source generators over hand-rolled INotifyPropertyChanged, async commands carrying a CancellationToken, explicit binding modes, generic-host composition, off-UI-thread work via IProgress, list virtualization, styling/theming with the .NET 9 Fluent ThemeMode, and resx localization. Floors at .NET 8 / C# 12. Load before editing any XAML, code-behind, or ViewModel. Do NOT load for WinForms, UWP, WinUI 3, MAUI, Avalonia, or Uno - different frameworks; orchestration routes to csharp-design-patterns, tests to dotnet-testing, a paired Windows-Service worker to dotnet-hosted-services.
- ▌ Javascript · envoydev bundleJavaScript language conventions, framework-agnostic - the base layer for all JS-family code: ES modules only, named exports and boundary barrels, async/await discipline with cancellation, the two failure channels (returned result vs thrown Error), modern-feature adoption (structuredClone, iterator helpers, Temporal), untrusted-input rules, naming and shape. Load before writing or editing any .js, .jsx, .mjs, or .cjs file in any runtime - browser, Node, build script, service worker, extension. The type layer (TypeScript, and checked JS via JSDoc) is the `typescript` skill, which stacks on this baseline; frameworks add their own layer above that. Not for C#/.NET or other languages.
- ▌ Typescript · envoydev bundleThe TypeScript type layer over the `javascript` baseline - lean on the compiler (full strict plus the extra safety flags), model data with types, narrow unknown instead of any, brand look-alike primitives, and treat plain JS as checked JS via JSDoc and checkJs. Baseline is TypeScript 5+. Load before writing or editing any .ts or .tsx file - and load `javascript` with it, the base-language layer this stacks on. In an Angular project also load the Angular framework-conventions skill, when your skill list has one. Also fires for tsconfig work and for typing questions in checked .js files. Not for base-language rules alone (javascript) or C#/.NET.
- ▌ Dotnet Grpc · envoydev bundle.NET gRPC conventions - the .proto is the contract and Grpc.Tools generates from it at build, host with Grpc.AspNetCore (AddGrpc + MapGrpcService), consume through typed clients (AddGrpcClient over IHttpClientFactory) with a reused multiplexing channel, the four call shapes with a deadline and CancellationToken on every one, JWT-bearer or mTLS auth, interceptors for cross-cutting work, the gRPC health protocol, and gRPC-Web for browsers. Floors at .NET 8 / C# 12. Load when defining, implementing, or calling a gRPC service, or weighing gRPC against REST. Companions: dotnet-web-backend, dotnet-authentication, csharp. Do NOT load for plain REST or minimal APIs - that is dotnet-minimal-api.
- ▌ Docs As Code · envoydev bundleAuthoring conventions for documentation as versioned text artifacts - the docs-as-code practice: Mermaid diagrams (sequenceDiagram for interaction flows, erDiagram for schema sketches), decision records (ADR - Nygard + MADR 4), and C4 model views (context/container). Load before writing or reviewing ANY documentation artifact of these types, whatever the subject - a sequence/ER/C4 diagram in Markdown, an ADR or decision-log entry, or a diagram-tooling choice (Mermaid vs DBML vs Structurizr). Routes per doc type to references/. Triggers on sequence diagram, ER diagram, entity relationship, ADR, decision record, decision log, C4, container diagram, context diagram, docs-as-code - and on mermaid for those diagram types (other Mermaid forms get only the generic ground rules here). NOT the repo's committed architecture capture (project-architecture-analyzer owns <docs-path>/architecture/), not Markdown prose style (markdown-style), and not DB design itself (database-conventions).
- ▌ Create Ticket · envoydev bundleWrites a ticket in English from a raw description for any tracker (Jira, Azure DevOps, GitHub, GitLab, YouTrack): bug, user story, epic, or technical task - detects the type, routes to its template. Use whenever the user wants a ticket written or a not-yet-filed draft reworked (shorter, different focus), even casually or in Ukrainian - 'create a bug/story/epic/task ticket', 'create user story', 'create jira ticket', 'file a bug'. Do NOT fire to write code or fix the bug instead of filing it, to touch a ticket already in the tracker (query / update / comment / close), or for a commit / PR message.
- ▌ Dotnet Aspire · envoydev.NET Aspire conventions for local cloud-native orchestration - the AppHost that declares the topology, the shared ServiceDefaults extension every service calls once, name-based service discovery, AppHost-injected connection strings, and the developer dashboard. This is the local run, NOT production deployment or container publishing. Floors at .NET 8 / C# 12. Load when scaffolding or editing an AppHost or ServiceDefaults, declaring resources and references, wiring discovery, or when the user says Aspire, AppHost, AddProject, WithReference, service discovery, or Aspire dashboard. Companions: dotnet-web-backend, dotnet-testing. Do NOT load for non-Aspire projects, production deployment, or publishing images.
- ▌ TS JS Testing · envoydev bundlePlain TypeScript/JavaScript testing hub - practices and tooling only, no coverage numbers (the % bar is user-set via project-test-coverage-analyzer): runner routing (Vitest the house default, Jest where the workspace signals it, node:test the zero-dependency floor - detect, never install), a test strategy keyed off role (pure module / boundary seam / DOM-adjacent / Node-runtime / published types), fake timers vs real async, the mock-masking smoke spec, and the TS/JS exclusion catalog. Covers libraries, Node CLIs/tooling, framework-free web code, and the browser-extension unit layer (the chrome.* seam and extension E2E live in browser-extension). Load before writing, modifying, or reviewing TS/JS tests outside a framework harness, auditing suite quality, running mutation testing, or configuring coverage - do not rely on recall. Do NOT load for Angular/Ionic (angular-testing) or .NET (dotnet-testing).
- ▌ Dotnet Migrate · envoydev bundlesafe-migration playbook for .NET - the disciplined way to evolve a schema with EF Core, lift a solution onto a newer target framework, and refresh NuGet dependencies without breaking production. A process skill, version-neutral with a .NET 8 floor. Load when you run a database migration, raise the target framework or SDK, or bump packages - trigger words migrate, upgrade, update packages. Companions: `dotnet-data-access` for query and migration mechanics, `dotnet-project-setup` for central package management, `dotnet-web-backend` for the surrounding service. Skip it for ordinary feature work that touches no schema, no version, and no package.
- ▌ Dotnet Openapi · envoydevASP.NET Core OpenAPI conventions - how a service emits a correct, generated OpenAPI document and serves a browsable docs UI from it. Picks the generator by framework floor (Swashbuckle or NSwag on .NET 8; the built-in Microsoft.AspNetCore.OpenApi with AddOpenApi / MapOpenApi on .NET 9 and up), shapes the spec with transformers, declares security schemes, splits versioned documents, and renders with Scalar. Floors at .NET 8 / C# 12. Load before adding API docs, editing the generated spec, declaring a security scheme, or standing up the docs UI. Companions: dotnet-minimal-api (the endpoint metadata feeding the document), dotnet-web-backend, dotnet-authentication. Skip it for non-HTTP code and internal APIs with no published contract.
- ▌ Dotnet Testing · envoydev bundle.NET testing hub - the architecture-neutral approach for unit / integration / E2E tests, not a single library: AAA structure, a test strategy keyed off responsibility, coverage mechanics (the exclusion catalog + after-exclusions semantics; the % bar itself is user-set via project-test-coverage-analyzer), and runner / substitute / assertion library routing (xUnit, NSubstitute, FluentAssertions 7.x as defaults). Floors at .NET 8 / C# 12. Load before writing, modifying, or reviewing .NET tests, auditing test quality / smells, running mutation testing, or configuring coverage - do not rely on recall. Companions: csharp, dotnet-web-error-handling; Testcontainers, Aspire-orchestrated integration, and Verify/snapshot testing are folded in here as references/. Do NOT load for Angular/Jasmine/Karma/Jest (angular-testing) or plain TS/JS suites (ts-js-testing).
- ▌ Ionic Security · envoydevIonic / Capacitor mobile security-hardening reference for the native attack surface a WebView app adds beyond its web risks: secret storage in the Keychain / Keystore (never localStorage or Preferences - plaintext on-device), deep links as untrusted input, least-privilege native permissions, cleartext traffic and WebView debugging off in release, an allowNavigation allowlist and no live-reload server.url in production, FLAG_SECURE and backgrounding snapshots, plugin trust, pinning and biometric gating. Targets Capacitor 6+. Load when hardening or reviewing an Ionic/Capacitor feature - 'is it safe to store the token like this', 'lock the app behind Face ID', 'review our deep links' - or when the security-auditor sweeps the mobile stack. Points at angular-security, dotnet-security, capacitor-release. Do NOT load for non-security work.
- ▌ Markdown Style · envoydev bundleMarkdown authoring and review skill - the two-layer rule set (syntax canon = valid, portable Markdown from the Markdown Guide; style overlay = opinionated house form from Google's style guide) plus the review procedure. Load when authoring or restructuring any .md (README, ADR, runbook, how-to, design doc) or on an explicit 'lint / style-check / fix this markdown', 'ATX vs setext', 'should I use a TOC?', or 'fix the headings / list indentation' ask. Markdown form only - not prose clarity (that is Vale) or spelling (codespell / hunspell).
- ▌ Angular Styling · envoydev bundleAngular CSS and styling conventions for any Angular app, Material or not - component-scoped styles and the ViewEncapsulation choice, :host and :host-context, ::ng-deep discouraged and the sanctioned ways out, design tokens as CSS custom properties, mobile-first responsive with container queries and fluid type, where global vs component styles belong, utility-first vs scoped SCSS, and accessibility-affecting styling (focus-visible, prefers-reduced-motion, contrast). Targets Angular 17+. Load when writing or editing CSS or SCSS in an Angular workspace - in an Ionic app load it WITH ionic and see the shadow-DOM section here, because ion-* components ignore the usual escape hatches. Companions: angular-conventions, angular-material, ionic. Do NOT load for React, Vue, Svelte, plain non-Angular CSS, or Material theme token work which belongs to angular-material.
- ▌ Angular Testing · envoydev bundleAngular testing hub - practices and tooling only, no coverage numbers (the % bar is user-set via project-test-coverage-analyzer): TestBed + component-harness patterns for standalone components, a test strategy keyed off role (component / service / store / pipe), runner routing (whichever the workspace already runs - Karma/Jasmine, Jest, or Vitest - detect, never install), HttpTestingController, fakeAsync vs real-async timing, and the Angular exclusion catalog. Ionic/Capacitor apps share it. Load before writing, modifying, or reviewing Angular tests, auditing suite quality, running mutation testing, or configuring Angular coverage - do not rely on recall. Do NOT load for .NET (dotnet-testing) or plain TS/JS outside a framework harness (ts-js-testing).
- ▌ Dev Log Convert · envoydev bundleConverts a day's raw work notes (Ukrainian, English, or mixed) into a structured, past-tense English work log - ticket IDs normalized, time totalled, tasks grouped by project or prefix across one or more days. Fires only on the exact keyword 'dev-log' - do not use it for general note-taking, meeting minutes, commit messages, or status updates, which are not this format.
- ▌ Dotnet Realtime · envoydev bundle.NET real-time conventions for ASP.NET Core SignalR - server-to-client push over a persistent connection, connection-scoped, not durable. Covers strongly-typed Hub<TClient>, sending via IHubContext, group/user targeting, reconnection, JWT-over-query-string auth, additive client contracts, MessagePack, and scale-out (Redis backplane / Azure SignalR Service). Floors at .NET 8 / C# 12. Load for chat, notifications, live dashboards, or any real-time server push - or when the user names SignalR, hub, server-side WebSocket push, or live updates. Companions: dotnet-messaging, dotnet-authentication, dotnet-hosted-services, dotnet-web-backend. Do NOT load for broker-backed durable messaging (dotnet-messaging), request/response HTTP (dotnet-minimal-api), in-process reactive streams (Rx / System.Reactive), or an outbound ClientWebSocket (dotnet-hosted-services).
- ▌ Dotnet Security · envoydev bundle.NET application-security hardening reference, organized by the OWASP Top 10 (2021) mapped to concrete ASP.NET Core / .NET 8 mitigations: broken access control (fallback authz policy, resource-based ownership checks against IDOR, CORS lockdown), injection and XSS, cryptographic and integrity failures, insecure deserialization, misconfiguration, vulnerable dependencies, SSRF, and security logging. Owns the do-not-use list for dead-but-tempting APIs (BinaryFormatter, Code Access Security, .NET Remoting). Floors at .NET 8 / C# 12. Load when hardening a feature, threat-modeling an endpoint, or reviewing a change for vulnerabilities. Companions: dotnet-authentication, dotnet-cryptography, database-security. Do NOT load for building the sign-in flow itself (dotnet-authentication) or choosing crypto primitives (dotnet-cryptography) - this skill reviews and hardens; those build.
- ▌ Dotnet Winforms · envoydev bundleWinForms conventions for maintenance and modernization - logic out of code-behind (MVP passive view for legacy, the .NET 8 MVVM binding engine for new), DI-resolvable forms, async/await with no UI-thread blocking, BindingSource + INotifyPropertyChanged binding, control/component/GDI disposal, PerMonitorV2 high-DPI, virtual-mode grids, presenter unit tests. Floors new work at .NET 8 / C# 12 and covers 4.8 as the supported-but-frozen maintenance surface. Load before editing any Form, UserControl, code-behind, presenter, or .Designer.cs. Do NOT load for WPF (-> dotnet-wpf), WinUI 3, MAUI, Avalonia, or Uno; async baseline -> csharp, MVP/command orchestration -> csharp-design-patterns, tests -> dotnet-testing, upgrade playbook -> dotnet-migrate, a paired Windows-Service worker -> dotnet-hosted-services + dotnet-windows-service.
- ▌ Ilspy Decompile · envoydevDecompile a compiled .NET assembly to read its real implementation - see how a framework or NuGet API actually works, view source you do not ship, or confirm behavior before a framework upgrade. Uses ilspycmd (via dnx or a pinned global tool). Load when you need ground truth from a .dll instead of guessing at an API, not for source you already have (that is serena / the LSP). Companions: `dotnet-migrate` (upgrade investigation), `csharp`.
- ▌ Angular Material · envoydev bundleAngular Material and CDK conventions - import only the component modules a standalone component uses (no shared barrel), theme through the M3 mat.theme API and its CSS custom properties rather than hand-edited .mat-* rules, reach for CDK primitives before rolling your own, and test through the official harnesses, not DOM queries on internals. Targets @angular/material 17+. Load when building UI with @angular/material or @angular/cdk. Companions: angular-conventions, typescript, angular-styling. This is the @angular/material library specifically, not generic Material Design 3 or @material/web. Skip for PrimeNG, Spartan UI, Ionic, or apps not using Angular Material.
- ▌ Angular Security · envoydevAngular / web frontend security-hardening reference mapped to concrete Angular 17+ mitigations: XSS and the DomSanitizer bypassSecurityTrust* escape hatches, innerHTML injection, nonce-based CSP, CSRF via HttpClient's XSRF support, secrets that must never ship in the bundle (environment.ts, source maps), auth-token storage (httpOnly cookie over localStorage), SSR/TransferState leaks, open redirects, target=_blank window.opener, unsafe URL bindings, and vulnerable npm dependencies. Load when hardening or reviewing an Angular web feature, or when the security-auditor sweeps the web stack. Points at dotnet-security for the API side, ionic-security for the Capacitor native shell. Do NOT load for non-security work or the mobile native surface.
- ▌ Dotnet Messaging · envoydev.NET asynchronous messaging conventions - broker-backed, event-driven communication between modules and services using Wolverine (recommended) over MassTransit, the transactional outbox for exactly-publish-on-commit, idempotent consumers under at-least-once delivery, choreography versus sagas, immutable versioned message contracts, and RabbitMQ or Azure Service Bus transports configured (never hardcoded). Floors at .NET 8 / C# 12. Load when wiring a message bus, an outbox, a saga or process manager, integration events, or background message processing, or when the user names Wolverine, MassTransit, RabbitMQ, Azure Service Bus, queue, or pub/sub. Companions: dotnet-hosted-services (the consumer's host), dotnet-realtime, dotnet-aspire, csharp. Do NOT load for in-process reactive streams or synchronous request/response over HTTP (dotnet-web-backend).
- ▌ Browser Extension · envoydev bundleBrowser-extension engineering (TypeScript/JavaScript, Manifest V3): the ephemeral service-worker model, content-script isolation and MAIN-world boundaries, typed cross-context messaging, storage tiers and quotas, least-privilege permissions, CSP-safe UI frameworks, WXT-first tooling, store review and monetization reality. Fires on manifest.json / MV3 work, content scripts, extension service workers, chrome.* or browser.* APIs, popup/options/side-panel UI, Web Store or AMO publishing, 'build a chrome extension'. NOT for regular browser web apps (angular-conventions / frontend), Electron or VS Code extensions (Node-runtime work), or npm mechanics (npm skill).
- ▌ Capacitor Release · envoydev bundlerelease-pipeline conventions for an Ionic / Capacitor app - the gap from a feature-complete build to a signed store submission: cap sync and native build artifacts (.ipa, .aab), iOS and Android code signing, store submission (TestFlight, Play tracks), OTA / live updates and the native-binary boundary, marketing-version vs build-number sync, and the Fastlane / GitHub Actions CI shape with secrets handling and dSYM / sourcemap upload. Targets Capacitor 6+ (8 current). Load when cutting a release, wiring signing, or building the release CI. Companions: ionic, mobile. Do NOT load for in-app feature work with no release or signing concern.
- ▌ Database Security · envoydevSQL / data-layer security-hardening reference, organized by the persistence threat surface: SQL injection closed at every sink, least-privilege database accounts, row-level security and tenant isolation (the data-layer IDOR), secrets kept out of connection strings, encryption at rest and in transit, sensitive-data exposure and masking, and audit logging that never records the secret. Load when hardening or reviewing a SQL / data-persistence feature, when the security-auditor sweeps the data stack, or on asks like 'is this query injectable' or 'can one tenant read another's rows'. Points at dotnet-security for the app-layer EF and injection surface, dotnet-cryptography for crypto primitives, and dotnet-migrate for safe migration mechanics. Do NOT load for non-security work.
- ▌ Dotnet Data Access · envoydev bundleThe .NET ORM / data-access layer (.NET 8 floor) - ORM-agnostic access principles here, per-ORM mechanics in references/: session or context lifetime and thread-safety, change tracking, loading strategy and N+1, projection to read models, bounded results and no-generic-repository, and the full-ORM-for-writes + micro-ORM-for-reads split. Load when you configure a DbContext or ISession, write or review an ORM query, pick a loading strategy, or design a read/write store; then use references/efcore.md for EF Core or references/nhibernate.md for NHibernate. Not the engine side (raw SQL, index, planner -> postgres / sqlite) nor the migration playbook (-> dotnet-migrate). Companions: csharp (async, mapping), dotnet-testing (integration tests).
- ▌ Dotnet Diagnostics · envoydev bundleMeasure and diagnose a live .NET process - the layer that decides whether to benchmark a hot path or capture a dump. Microbenchmarking: BenchmarkDotNet in a separate Release console project, [MemoryDiagnoser], reading mean/alloc/ratio. Dumps: capture a crash/hang/OOM dump with dotnet-dump or DOTNET_DbgEnableMiniDump, managed-heap-only with dotnet-gcdump, then first-look SOS analysis (clrstack, dumpheap, gcroot). Load when timing a hot path, comparing two implementations, or when a process crashed, hung, or is leaking - CoreCLR only, not .NET Framework or NativeAOT dumps. Do NOT load for CPU/memory profiling, APM, or distributed tracing - this owns benchmarks and dumps. Companions: `csharp`, `dotnet`, `dotnet-performance`, `dotnet-testing`.
- ▌ Dotnet Minimal API · envoydev bundleASP.NET Core minimal API mechanics - how an endpoint is shaped and wired, not what surrounds it: feature-grouped registration via extension methods and MapGroup, TypedResults and Results<> outcome unions, IEndpointFilter for per-endpoint cross-cutting, parameter binding (AsParameters, explicit From-attributes, custom BindAsync/TryParse), endpoint metadata, and hardened IFormFile uploads. Floors at .NET 8 / C# 12; later additions are flagged optional. Load before writing or editing minimal API endpoints - MapGet, MapPost, MapGroup, endpoint filters. Companions: dotnet-web-backend (pipeline-wide concerns), dotnet-web-error-handling, dotnet-openapi, dotnet-authentication. Do NOT load for MVC or API controllers, gRPC, SignalR, or non-HTTP code.
- ▌ Dotnet Performance · envoydev bundlePerformance-aware .NET design decisions and where they matter - the layer that decides whether an allocation/memory-layout or serialization-format choice is worth spending on here. Type design: struct vs class, readonly struct, seal by default, fewer allocations, `Span`, `ValueTask`, frozen/immutable returns. Serialization: pick the format - `System.Text.Json` source-gen for JSON, Protobuf for wire, MessagePack for cache/messaging. Load when a type sits on a hot path or high-throughput loop, or when choosing how bytes cross a process boundary. Do NOT start here for 'my app is slow' - that is usually a bad query or an N+1: route to `dotnet-diagnostics` and measure first. Companions: `csharp`, `dotnet`, `dotnet-diagnostics`.
- ▌ Dotnet Web Backend · envoydev bundle.NET web / HTTP service conventions - the architecture-neutral cross-cutting baseline every ASP.NET Core service shares: IHttpClientFactory, FluentValidation, resilience via Microsoft.Extensions.Http.Resilience, API versioning, OpenAPI, typed options with startup validation (IOptions / ValidateOnStart), observability (structured logging, OpenTelemetry to OTLP, correlation IDs, health checks), and caching (IMemoryCache, HybridCache, Redis). This is the web hub - load it first for any ASP.NET Core / Web API / minimal API / microservice work, then the focused companion for the how. It owns the 'pick exactly one architecture' rule but mandates no specific one. Floors at .NET 8 / C# 12. Do NOT load for console binaries, CLI tools, desktop apps, WPF/MAUI, daemons, or message-only consumers.
- ▌ Explain Code Tutor · envoydev bundleExplains code, a bug, a concept, or an architecture/approach trade-off like a patient senior engineer for someone new to the stack: walks the real project files with one fitting analogy, numbered steps over short quoted snippets, a marked break-point/key-insight/verdict, the real fix, and a one-line takeaway. Depth adjustable (ELI5, intermediate, expert). Use when the user wants something explained, even casually: 'explain this code', 'walk me through this', 'how does this work', 'which is better X or Y'. Do NOT fire on quick lookups answerable in a sentence (glossary asks, yes/no questions) or for writing new feature code or formal code review.
- ▌ Project Solve Task · envoydevUse to run a task, feature, or bug through the whole single-chat vertical with a hard user gate between every step: design -> plan audit -> user approval + build-mode choice -> build -> build review (skippable): project-verify-code inline or the verifier seat -> done-gate. Every stop is a real pause - switch model or effort, add context, or edit the plan before saying go - and the plan file plus a serena cycle note make every step resumable after compaction or in a fresh session. Trigger on run the task cycle, build this with approvals, gated implementation, step-by-step with my sign-off. Not the dispatched multi-agent flow (project-solve-cross-task), not greenfield (project-build-from-scratch), not a one-line edit.
- ▌ Claude Stack · envoydevRoute to the right claude-stack action when unsure which fits - inspects the install state and answers with the exact command to run: /claude-stack:setup (fresh install from scratch), /claude-stack:update (no-questions refresh + prune of upstream removals), /claude-stack:configure (adjust an existing install - add or drop), /claude-stack:validate (reconcile an install against THIS project - prune what its frameworks do not use and add the detected stacks' missing artifacts), /claude-stack:status (read-only per-area tables of what is installed). Trigger by invoking /claude-stack.
- ▌ Angular Conventions · envoydev bundleAngular conventions from v17 up - standalone everything, signals as the default state primitive, OnPush and zoneless, block control flow, signal inputs and outputs, deferred loading, RxJS only where streams earn it, forms, routing, SSR and hydration, accessibility, harness testing, banned patterns, reward-hacking shortcuts to reject. Load when creating or editing a component, service, directive, or template; refactoring to signals; or reviewing Angular code. Companions: typescript, angular-material, angular-styling, angular-security, frontend, mobile. Not for React, Vue, Svelte, Solid, plain DOM, or non-Angular TypeScript.
- ▌ Dotnet Architecture · envoydev bundleChoose and hold a .NET application architecture - the decision layer here, each style's depth in references/. Two axes plus one additive: topology (single deployable -> modular-monolith -> microservices), internal organization (clean-architecture vs vertical-slice), and DDD tactical patterns layered on when the domain has real invariants. Load when deciding where code belongs, structuring a new app or module, picking a layering/slicing style, drawing a service or module boundary, reviewing architecture drift, or when the user says clean architecture, vertical slice, DDD, modular monolith, microservices, or bounded context. Companions: dotnet-architecture-tests, dotnet-web-backend, dotnet-messaging, csharp. Do NOT load for encoding the boundaries as build-failing tests (dotnet-architecture-tests) or raw SQL / query tuning (postgres).
- ▌ Dotnet Code Quality · envoydev bundle.NET conventions for mechanically enforcing code quality - making the house style a build gate, not a review opinion. Floors at .NET 8 / C# 12. Load when setting up or fixing formatting, analyzers, .editorconfig, warnings-as-errors, or a CI quality gate, or when the user names CSharpier, dotnet format, Roslynator, editorconfig, analyzer, AnalysisLevel, or NoWarn. Companions: csharp (the conventions this enforces), dotnet-project-setup (Directory.Build.props), dotnet-security (CA3xxx/CA5xxx rules), dotnet-migrate (analyzer churn on upgrades). Do NOT load for authoring Roslyn analyzers/source generators (dotnet-source-generators) or test-suite quality (dotnet-testing).
- ▌ Dotnet Console Apps · envoydev bundleConventions for the console app's interface surface - what a .NET console binary IS to the outside world, on top of the generic host that runs it. Two shapes: a one-shot CLI tool (System.CommandLine 2.0 / Spectre.Console.Cli / Cocona, subcommands, exit codes) and a long-running gateway bot or consumer (Telegram.Bot, Discord.Net, SlackNet, CryptoExchange.Net, broker queue-workers) run inside a BackgroundService. Floors at .NET 8 / C# 12. Load when building a CLI tool, a chat or trading bot, or a bot's command surface, or when the user names System.CommandLine, Spectre.Console, Telegram.Bot, Discord.Net, or a bot. Companions: dotnet-hosted-services (host lifecycle + 24/7 hardening), dotnet-messaging, csharp, dotnet-testing. Do NOT load for the host lifecycle itself (dotnet-hosted-services), a web API or webhook endpoint (dotnet-web-backend), or a desktop GUI (dotnet-wpf).
- ▌ Dotnet Cryptography · envoydev bundle.NET cryptography conventions for System.Security.Cryptography - pick the right primitive and use it the one correct way: SHA-2 for integrity, AES-GCM for authenticated encryption, RSA-OAEP/PSS and ECDsa for asymmetric work, PBKDF2 or Argon2id for password hashing, RandomNumberGenerator for entropy, and FixedTimeEquals for any secret comparison. Carries the dead-algorithm list and notes post-quantum ML-KEM/ML-DSA as a .NET 10+ opt-in. Floors at .NET 8 / C# 12. Load when encrypting, decrypting, hashing, signing, verifying, or deriving a key. Secret STORAGE belongs to your secrets/config layer (never source); sign-in to dotnet-authentication; OWASP categories to dotnet-security. Do NOT load for TLS/HTTPS pipeline config.