Skip to content

Harmonise AI agent skills with cross-platform standard#64

Draft
amccall-mindera wants to merge 1 commit intomainfrom
task/harmonise-ai-agent-skills
Draft

Harmonise AI agent skills with cross-platform standard#64
amccall-mindera wants to merge 1 commit intomainfrom
task/harmonise-ai-agent-skills

Conversation

@amccall-mindera
Copy link
Copy Markdown
Contributor

Summary

Standardises AI agent names and structure to be consistent across iOS, Android, and Flutter.

Changes

  • Renamed ios-feature-developerfeature-developer
  • Renamed mobile-security-specialistsecurity-specialist
  • Updated all cross-references in orchestrator and other agents to use new names
  • Enhanced graphql-specialist with example query/fragment/converter pattern
  • Enhanced spec-writer with acceptance criteria example and collaboration section
  • Added collaboration section to localization-specialist
  • Updated AGENTS.md agent table to reflect new standardised names

Agent names (now identical across all 3 platforms)

feature-orchestrator, feature-developer, graphql-specialist, localization-specialist, security-specialist, spec-writer, testing-specialist

All agents in .ai/agents/ for tool-agnostic compatibility (GitHub Copilot, Claude, Cursor, etc.)

- Rename ios-feature-developer -> feature-developer (standardised name)
- Rename mobile-security-specialist -> security-specialist (standardised name)
- Update all agent cross-references to use new standardised names
- Add example query/fragment/converter pattern to graphql-specialist
- Add acceptance criteria example + collaboration section to spec-writer
- Add collaboration section to localization-specialist
- Update AGENTS.md agent table to reflect new names and paths

Agents are now named consistently across iOS, Android, and Flutter:
feature-orchestrator, feature-developer, graphql-specialist,
localization-specialist, security-specialist, spec-writer, testing-specialist

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant