* Modified tools to make the agent more efficient
* Added skill for importing Azure Infrastructure as Code
* Updated readme
* Some wording improvements
* Added / to skills path endings
* ran npm start
Add two new agents for the Vue.js ecosystem:
- nuxt-expert.agent.md: Expert Nuxt Developer agent covering Nuxt 3,
Nitro, rendering modes, data fetching, and legacy Nuxt 2 compatibility.
- vuejs-expert.agent.md: Expert Vue.js Frontend Engineer agent covering
Vue 3 Composition API, Pinia, Vue Router, TypeScript integration, and
legacy Vue 2/Options API compatibility.
Both agents use Claude Sonnet 4.5 and follow existing agent conventions.
README.agents.md regenerated via npm run build.
Updated agent guidelines to specify the use of accessibility_snapshot over visual screenshots for element identification. Accessibility snapshots provide structured DOM/ARIA data, which is more reliable for browser automation than pixel-based visual analysis.
Remove redundant `<operating_rules>`, agent-specific parameters, and
`<delegation_validation>` sections. This removes duplicate content
to ensure a single source of truth for the agent's behavior protocols
and configuration.
- Refined `gem-browser-tester` workflow to separate initialization from
execution and enforce an Observation-First loop.
- Added retry logic for transient failures (e.g., timeouts, network issues)
in browser automation tasks.
- Standardized artifact generation paths to `docs/plan/{plan_id}/`
across multiple agents.
- Updated failure actions to specify evidence capture locations
(logs, network) for improved debugging and traceability.
Introduce explicit sections for input, output, and verification criteria.
Define structured JSON output including detailed evidence paths and error counts.
Update workflow to reference new guides and move Observation-First loop to operating rules.
Clarify verification steps with specific pass/fail conditions for console, network, and accessibility checks.
- Remove redundant `<mission>` section from gem-browser-tester
- Add "Reflect" step to gem-documentation-writer for self-review on high-priority or failed tasks
- Refactor gem-orchestrator completion phase to generate a walkthrough markdown file instead of a review
- Update orchestrator rules to allow direct execution for creating walkthrough files
Remove "detailed thinking on" directive and consolidate operating_rules sections for consistency. Both gem-browser-tester.agent.md and gem-devops.agent.md now share standardized rules: unified tool activation phrasing ("Always activate tools before use"), merged context-efficient reading instructions, and removed agent-specific variations. This simplifies maintenance and ensures consistent behavior across different agent types while preserving core functionality like evidence storage, error handling, and output constraints.
Rename the Chrome-specific testing agent to a browser-agnostic version
to support multiple automation tools (Playwright, Chrome DevTools, etc.).
Updates all references in orchestrator and planner configurations, and
broadens the description and execution workflow to be tool-flexible.
Evidence storage rule clarified to apply primarily on failures.
- Introduced new agents: gem-chrome-tester, gem-devops, gem-documentation-writer, gem-implementer, gem-orchestrator, gem-planner, gem-researcher, and gem-reviewer.
- Updated README.collections.md to include the new Gem Team Multi-Agent Orchestration collection.
- Created gem-team.collection.yml and gem-team.md for structured documentation of the multi-agent orchestration framework.
- Each agent includes detailed descriptions, workflows, operating rules, and final anchors for clarity on their functionalities and usage.
Add an agent for AI-powered LinkedIn content creation, scheduling, and
analytics through Reepl (https://reepl.io). Enables creating posts,
carousels, and managing LinkedIn presence directly from GitHub Copilot.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add tools for maximizing GitHub Copilot effectiveness through better
context management:
- Instructions: Guidelines for structuring code so Copilot understands it
- Agent: Context Architect - plans multi-file changes by mapping dependencies
- Prompts:
- context-map: Map all affected files before changes
- what-context-needed: Ask Copilot what files it needs
- refactor-plan: Create phased refactor plans with rollback steps
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Anders Eide
dwizzle204
Geoffrey Casaubon
Aaron Powell
Muhammad Ubaid Raza
Roberto Perez
Imran Siddique
Jan Krivanek
Ivan Charapanau
abhibavishi
vfaraji89
Roberto Perez