feat(skills): integrate the visual explainer skill

[andrewDoing]

🔧 - Generated by Copilot

Pull Request

Description

Add a lightly modified version of the visual-explainer skill.

Related Issue(s)

Closes #157

Type of Change

Select all that apply:

Code & Documentation:

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to change)
• Documentation update

Infrastructure & Configuration:

• GitHub Actions workflow
• Linting configuration (markdown, PowerShell, etc.)
• Security configuration
• DevContainer configuration
• Dependency update

AI Artifacts:

• Reviewed contribution with prompt-builder agent and addressed all feedback
• Copilot instructions (.github/instructions/*.instructions.md)
• Copilot prompt (.github/prompts/*.prompt.md)
• Copilot agent (.github/agents/*.agent.md)
• Copilot skill (.github/skills/*/SKILL.md)

Note for AI Artifact Contributors:

• Agents: Research, indexing/referencing other project (using standard VS Code GitHub Copilot/MCP tools), planning, and general implementation agents likely already exist. Review .github/agents/ before creating new ones.
• Skills: Must include both bash and PowerShell scripts. See Skills.
• Model Versions: Only contributions targeting the latest Anthropic and OpenAI models will be accepted. Older model versions (e.g., GPT-3.5, Claude 3) will be rejected.
• See Agents Not Accepted and Model Version Requirements.

Other:

• Script/automation (.ps1, .sh, .py)
• Other (please describe):

Sample Prompts (for AI Artifact Contributions)

> using the visual-explainer skill, draw a diagram of our authentication flow
> /viz-diff-review
> /viz-plan-review ~/docs/refactor-plan.md

User Request:

Create a single page html visualization of the research done in .copilot-tracking/research/*

Execution Flow:

Output Artifacts:

Success Indicators:

For detailed contribution requirements, see:

• Common Standards: docs/contributing/ai-artifacts-common.md - Shared standards for XML blocks, markdown quality, RFC 2119, validation, and testing
• Agents: docs/contributing/custom-agents.md - Agent configurations with tools and behavior patterns
• Prompts: docs/contributing/prompts.md - Workflow-specific guidance with template variables
• Instructions: docs/contributing/instructions.md - Technology-specific standards with glob patterns
• Skills: docs/contributing/skills.md - Task execution utilities with cross-platform scripts

Testing

Checklist

Required Checks

• Documentation is updated (if applicable)
• Files follow existing naming conventions
• Changes are backwards compatible (if applicable)
• Tests added for new functionality (if applicable)

AI Artifact Contributions

• Used /prompt-analyze to review contribution
• Addressed all feedback from prompt-builder review
• Verified contribution follows common standards and type-specific requirements

Required Automated Checks

The following validation commands must pass before merging:

• Markdown linting: npm run lint:md
• Spell checking: npm run spell-check
• Frontmatter validation: npm run lint:frontmatter
• Skill structure validation: npm run validate:skills
• Link validation: npm run lint:md-links
• PowerShell analysis: npm run lint:ps
• Plugin freshness: npm run plugin:generate

Security Considerations

• This PR does not contain any sensitive or NDA information
• Any new dependencies have been reviewed for security issues
• Security-related scripts follow the principle of least privilege

Additional Notes

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.45%. Comparing base (67585f5) to head (05b1f6b).
⚠️ Report is 155 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #864      +/-   ##
==========================================
+ Coverage   83.41%   85.45%   +2.03%     
==========================================
  Files          20       27       +7     
  Lines        3510     5123    +1613     
==========================================
+ Hits         2928     4378    +1450     
- Misses        582      745     +163     

Flag	Coverage Δ
pester	85.45% <ø> (+2.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 22 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[WilliamBerryiii]

What I'd like to see out of this tool (and the PR) is effectively what roles (using our role based documentation), this tool supports, and I'd like to see where it could be integrated into the any of the extension workflows so there's natural inclusion in the toolchains. My recommendation would be to select one of the following scenarios to show its toolchain integration:

• when I exit the researcher I get a handoff/conversation fork to this that can provide me "would you like a learning path for this project so you can upskill while we plan and implement it"
• when I am in planner mode I get a handoff/conversation fork that offers me a flowchart embedded in an html page that shows how planner anticipates executing the work
• when I'm in design thinking I get a handoff/conversation fork that offers me a stakeholder map

Demonstrating how we can weave the tool into just one of these workflows (or one fo your choosing) will show how it fits in the project.

Thanks and looking forward to seeing the outcome!

[andrewDoing]

I think I'm going to close this one in favor of determining a better pattern for how we want to host collections of public skills that we can more easily keep synced with their remotes.