← all publishers

cmu-sei

@cmu-sei source repo

Report this profile Claim this profile

• 10 skills
• 0 followers
• 8 hours ago last updated

1. ▌
   Aspire · cmu-sei

   Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost. DO NOT USE FOR: non-Aspire .NET apps (use dotnet CLI), container-only deployments (use docker/podman), Azure deployment after local testing (use azure-deploy skill). INVOKES: Aspire CLI commands (aspire start, aspire describe, aspire otel logs, aspire docs search, aspire add), bash. FOR SINGLE OPERATIONS: Use Aspire CLI commands directly for quick resource status or doc lookups.
   2
   installs
2. ▌
   Playwright CLI · cmu-sei bundle

   Automate browser interactions, test web pages and work with Playwright tests.
   0
   installs
3. ▌
   Update Docs · cmu-sei

   Use when the user invokes `/update-docs <app-name>` to update Crucible application documentation to reflect the current state of a running app. Triggers a plan-driven documentation update workflow that browses the live app via Playwright, cross-references existing Playwright tests, produces or refreshes a plan file, waits for user approval, implements the approved plan, and validates linting.
   0
   installs
4. ▌
   Dotnet Inspect · cmu-sei

   Find evidence instead of guessing for .NET packages, platform libraries, local assemblies, APIs, dependencies, and version-to-version API changes.
   0
   installs
5. ▌
   Heal Crucible Tests · cmu-sei bundle

   Diagnose and repair failing Crucible end-to-end Playwright tests by dispatching the local playwright-test-healer agent. Use when a Crucible test fails, flakes, has stale selectors, or needs browser-based root-cause investigation and a focused fix.
   0
   installs
6. ▌
   Plan Crucible Tests · cmu-sei bundle

   Create or expand a Crucible end-to-end Playwright test plan by dispatching the local playwright-test-planner agent. Use when asked to explore a running Crucible app, document browser test scenarios, or update an app's test-plan markdown.
   0
   installs
7. ▌
   Generate Crucible Tests · cmu-sei bundle

   Generate Crucible end-to-end Playwright specs by dispatching the local playwright-test-generator agent. Use when asked to implement one or more scenarios from a Crucible app's test plan and verify them against the running stack.
   0
   installs
8. ▌
   Storybook Guidelines · cmu-sei

   **PRIMARY SKILL FOR CREATING AND UPDATING STORYBOOK STORIES** — Guidelines and best practices for writing Storybook story files for Vue 3 components. USE FOR: - Creating new .stories.js files for components - Modifying existing story files - Understanding story structure, argTypes, and templates - Adding variants, actions, and controls to stories DO NOT USE FOR: - Writing or modifying component .vue files (use components-guidelines) - Writing or improving unit tests (use unit-testing-guidelines) WHEN TO COMBINE: Load components-guidelines if you need to understand a component's props, emits, and slots to write its stories.
   0
   installs
9. ▌
   Components Guidelines · cmu-sei

   **PRIMARY SKILL FOR CREATING AND UPDATING COMPONENTS** — Guidelines and best practices for writing and modifying Vue 3 components. USE FOR: - Creating new .vue component files - Modifying existing component implementation - Understanding component structure, props, emits, defineModel - Questions about how components should be architected DO NOT USE FOR: - Writing or improving unit tests (use unit-testing-guidelines) - Understanding testing patterns or assertions WHEN TO COMBINE: Load unit-testing-guidelines if you're adding a new component and need to write tests for it.
   0
   installs
10. ▌
    Unit Testing Guidelines · cmu-sei

    **PRIMARY SKILL FOR TESTING** — Guidelines and best practices for writing unit tests for Vue 3 components, composables, and utilities. USE FOR: - Writing new test files or updating existing tests - Understanding testing patterns (AAA, mocking, async testing) - Testing defineModel(), props, emits, and slots - Debugging test failures or improving test coverage DO NOT USE FOR: - Understanding how components should be implemented (use components-guidelines) - Writing or modifying component .vue files (use components-guidelines) WHEN TO COMBINE: Only load components-guidelines if you have read the component file and need additional context with specific Vue patterns that aren't covered in the test examples or derrived from the component.
    0
    installs