← all publishers

AndyElessar

@andyelessar source repo

Report this profile Claim this profile

• 7 skills
• 0 followers
• 1 day ago last updated

1. ▌
   Aspire Dev · andyelessar bundle

   Orchestrates Aspire distributed applications using the Aspire CLI and MCP tools. USE FOR: aspire start/stop, aspire describe, aspire doctor, view logs/traces, add integrations, debug resources, AppHost management. Also trigger for DistributedApplication.CreateBuilder, AddProject, AddContainer, or Aspire resource references. DO NOT USE FOR: non-Aspire .NET apps (dotnet CLI), container-only deployments (docker/podman), Azure deployment (azure-deploy skill). INVOKES: Aspire CLI (aspire start, aspire describe, aspire otel), Aspire MCP tools (mcp_aspire_doctor, mcp_aspire_list_resources, mcp_aspire_list_traces).
   0
   installs
2. ▌
   Prose Guide · andyelessar bundle

   Guide AI-native development using the PROSE methodology — Progressive Disclosure, Reduced Scope, Orchestrated Composition, Safety Boundaries, Explicit Hierarchy. Use when: setting up AI-native projects, creating agent primitives (.instructions.md, .prompt.md, .agent.md, SKILL.md, .spec.md, AGENTS.md), designing context engineering strategies, implementing spec-driven workflows, choosing agent delegation strategies (local vs async vs hybrid), scaling AI development to teams, assessing PROSE maturity level, or optimizing context window utilization. Also use when user mentions 'AI-native', 'agent primitives', 'context engineering', 'spec-driven development', 'AGENTS.md', 'agentic workflows', 'SKILL.md', 'agent skills', or asks how to make AI coding more reliable and repeatable.
   0
   installs
3. ▌
   Skill Guide · andyelessar bundle

   Design, write, and review SKILL.md files using proven patterns. Use when creating, improving, or reviewing agent skills, choosing a design pattern (Tool Wrapper, Generator, Reviewer, Inversion, Pipeline), structuring progressive disclosure, writing skill descriptions, or composing patterns. Also trigger for 'skill design', 'skill architecture', 'skill anti-patterns', 'skill checklist', or questions about writing better skills. Do NOT use for plugin.json or marketplace.json (use plugin-creator instead).
   0
   installs
4. ▌
   Agents Creator · andyelessar bundle

   Use when creating, reviewing, rewriting, or debugging `agents.md`, `.github/agents/*.md`, and `*.agent.md` files for any repository. Trigger whenever users mention custom agents, Copilot agents, agent personas, agent boundaries, or project-specific AI behavior in agent files. Also use this skill when users ask about Copilot custom instructions, agent configuration, agent prompt engineering, setting up AI behavior rules for a repository, writing operating manuals for coding agents, or defining what an AI assistant should or shouldn't do in a project — even if they don't explicitly mention 'agents.md'. Do NOT use this skill for implementing application features, writing runtime code, configuring CI/CD pipelines, or general code review unrelated to agent files.
   0
   installs
5. ▌
   Plugin Creator · andyelessar bundle

   Guide AI agents through creating GitHub Copilot CLI and Claude Code plugins and plugin marketplaces — from scaffolding plugin directories and writing plugin.json manifests to building marketplace.json registries and testing installations. Use this skill whenever the user wants to create, scaffold, configure, package, or publish a Copilot CLI or Claude Code plugin, write or edit a plugin.json or marketplace.json file, set up a plugin marketplace repository, or troubleshoot plugin installation and loading issues. Also trigger when the user mentions 'copilot plugin', 'claude plugin', plugin manifests, plugin registries, plugin distribution, or asks how to package agents/skills/hooks/MCP servers into an installable plugin — even if they don't explicitly say 'plugin.json'. Do NOT use this skill for authoring the contents of plugin components (agents, skills, hooks, MCP configs) — delegate those to the appropriate specialized skills.
   0
   installs
6. ▌
   Microsoft Webui · andyelessar bundle

   Microsoft WebUI Framework expertise — a language-agnostic server-side rendering framework where templates compile to a binary protocol and interactive Web Components hydrate as islands. Use when authoring, reviewing, or debugging WebUI components (`.html` + `.css` + `.ts` triplets), wiring up routes, hydrating with `WebUIElement`, configuring `webui build` / `webui serve`, or integrating SSR into a backend. Also trigger when the user mentions `@microsoft/webui`, `@microsoft/webui-framework`, `@microsoft/webui-router`, `WebUIElement`, `@attr` / `@observable` decorators, `protocol.bin`, `Router.start`, `Router.navigate`, `Router.ensureLoaded`, `<route>` / `<outlet>` tags, `keep-alive`, `pending`, `cache-tags`, or shadow-DOM scoped components from Microsoft. Do NOT use for unrelated UI libraries (React, Vue, FAST standalone, Lit, Blazor, or generic Web Components projects).
   0
   installs
7. ▌
   Csharp Source Generator · andyelessar bundle

   Use when writing, reviewing, debugging, or testing C# source generators and Roslyn incremental generators. Covers IIncrementalGenerator architecture, SyntaxProvider pipelines, generated-code snapshots with Verify, analyzer packaging, marker attributes, AnalyzerConfigOptionsProvider, SDK compatibility, diagnostics, and performance. Also trigger when the user mentions source generator output, generated C# files, Roslyn analyzers with generators, ForAttributeWithMetadataName, RegisterSourceOutput, RegisterImplementationSourceOutput, RegisterPostInitializationOutput, CompilerVisibleProperty, InterceptsLocation, PolySharp, PolyType.Roslyn, or generator snapshot tests. Do NOT use for ordinary C# application code, runtime reflection serializers, T4 templates, or non-Roslyn code generation tools.
   0
   installs