* docs(java): clarify Sonar, Java version, and code-style guidance
- Clarify SonarQube/SonarCloud setup, token handling, and CI scanner steps
- Add guidance for Records, pattern matching, and `var` usage heuristics
- Provide fallbacks when static analysis is unavailable and troubleshooting steps
- Original rules are no longer included in the standard Sonar Way ruleset
- Remove future dependency on Sonar by prompting to use when integrated or available
- If not, the agent will now read Sonar rules as part of its analysis
- Removed obsolete and redundant sections on Java version and code style
Generated-by: GitHub Copilot <github.copilot@github.com>
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
* docs(java): improve SonarQube setup instructions readability
- Break long bullet points into structured sub-bullets for clarity
- Organize SonarQube troubleshooting steps into numbered sequence
- Separate fallback tools configuration from main Sonar workflow
Fixes#296
Co-authored-by: GitHub Copilot <github.copilot@github.com>
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
---------
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
* Add Java MCP Server Development collection
- Add Java MCP server best practices instruction
- Add Java MCP server project generator prompt
- Add Java MCP expert chat mode
- Add Java MCP development collection manifest
- Update category READMEs
Features:
- Server setup with official MCP Java SDK
- Tool/resource/prompt handlers with reactive streams
- Project Reactor for async processing
- Spring Boot integration with starters
- Stdio and HTTP transport support
- JSON schema construction with fluent builders
- Synchronous facade for blocking use cases
- Maven and Gradle build configurations
* Fix Java MCP generator prompt
- Add missing import statements for handler classes
- Add handler registration in test server setup
---------
Co-authored-by: Aaron Powell <me@aaron-powell.com>
- Add Swift MCP server best practices instruction
- Add Swift MCP server project generator prompt
- Add Swift MCP expert chat mode
- Add Swift MCP development collection manifest
- Update category READMEs
Features:
- Server setup with official Swift SDK package
- Tool/resource/prompt handlers with withMethodHandler
- Async/await and actor-based concurrency patterns
- ServiceLifecycle integration for graceful shutdown
- Stdio, HTTP, and network transport support
- JSON schema construction with Value type
- Swift 6.0+ with modern concurrency features
- Platform support: macOS 13+, iOS 16+, Linux
* Add Go MCP Server Development collection
* Fix: Wrap description in single quotes per prompt guidelines
* Fix: Wrap chatmode description in single quotes per guidelines
* Fix: Wrap instruction description in single quotes per guidelines
- Add instructions for Python MCP server development best practices
- Add prompt for generating complete Python MCP server projects
- Add expert chat mode for Python MCP development assistance
- Add collection grouping all Python MCP resources together
- Update README files with new contributions
Co-authored-by: Aaron Powell <me@aaron-powell.com>
* Add TypeScript MCP Server Development collection
- Add instructions for TypeScript MCP server development best practices
- Add prompt for generating complete TypeScript MCP server projects
- Add expert chat mode for TypeScript MCP development assistance
- Add collection grouping all TypeScript MCP resources together
- Update README files with new contributions
* Revert unintended change to power-bi-development.md
* Add C# MCP Server Development collection
- Add instructions for C# MCP server development best practices
- Add prompt for generating complete MCP server projects
- Add expert chat mode for C# MCP development assistance
- Add collection grouping all C# MCP resources together
- Update README files with new contributions
* Add applyTo field to C# MCP instructions
* Add Power BI resources: 4 chat modes, 6 instructions, 4 prompts, and resources README
* Remove power-bi-resources-README.md - not needed for PR
* Add Power BI Development collection
* Fix PR review feedback: Add collection YAML file and remove double fenced code blocks
- Add power-bi-development.collection.yml with proper metadata
- Remove outer 4-backtick fences from all Power BI files (chatmodes, instructions, prompts)
- Files now have only the standard 3-backtick fences for proper GitHub Copilot compatibility
* Remove outer code fences from Power BI chatmode files
* Add comprehensive Svelte 5 and SvelteKit development guidelines
* Update Svelte instructions to include server-side rendering with client-side hydration
Update error handling examples to use $PSCmdlet.WriteError() and
$PSCmdlet.ThrowTerminatingError() instead of Write-Error and throw for better PowerShell cmdlet integration.
* feat(chatmodes): Add HLBPA (documentation architect) chat modes
- HLBPA is a high-level, big-picture architect for systems documentation
- It can be used either in VSC as usual or dropped in coding agent for auto-updates
- Depends on user's prompting skills to get the best results
- Will default to a more generalist mode if not enough context is given
- Minor updates to README and CONTRIBUTING to fix formatting errors
Assisted-by: GitHub Copilot & Verdent AI
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
* chore(chatmodes): Remove copy from md fence in HLBPA chat mode
- Copilot complains about the copy in the md fence
- Isn't likely to be used in this context anyway
Assisted-by: GitHub Copilot
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
---------
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
* Add comprehensive WordPress development instructions for Copilot
- Introduced a detailed guide covering core principles, coding standards, security practices, internationalization, performance optimization, admin UI, REST API, block development, asset loading, testing strategies, and documentation best practices.
- Emphasized the importance of following WordPress Coding Standards (WPCS) and provided examples for plugin headers, linting setup, and security measures.
- Included a checklist to ensure compliance with best practices for plugin development.
* Add WordPress development instructions for Copilot, detailing coding, security, and testing rules for plugins and themes
* Fix formatting inconsistencies in WordPress instructions file by changing double quotes to single quotes for 'applyTo' and 'description' fields.
