Repository navigation
Support platform-specific skills (e.g., iOS specific plugin migration) #198
Description
Problem
Loading specialized skills like the iOS specific plugin migration (#191) globally exposes them to all Flutter developers, regardless of whether they are working on iOS-specific tasks. That's why this PR was closed (PR feedback)
Proposed Solution
Explore scoping niche or platform-specific skills that users can select on demand.
• Reduces Noise: Prevents cluttering the core agent's context for general Flutter workflows.
• Better Targeting: Ensures specialized tools are only loaded when explicitly needed for platform-specific tasks.
Alternatives
Host this skill under a personal repo, or as a GitHub comment.
We plan to reach out to popular plugin authors with this skill included for AI assisted migration. Putting it under a personal account feels a bit sussy. GitHub comment can be hard to manage compared to a centralized repo.
Activity
[-]Create a sub-agent to less general / more specific skills[/-][+]Scope platform-specific skills (e.g., iOS UIScene migration) under dedicated sub-agents[/+][-]Scope platform-specific skills (e.g., iOS UIScene migration) under dedicated sub-agents[/-][+]Scope platform-specific skills (e.g., iOS specifiuc migration) under dedicated sub-agents[/+][-]Scope platform-specific skills (e.g., iOS specifiuc migration) under dedicated sub-agents[/-][+]Scope platform-specific skills (e.g., iOS specific plugin migration) under dedicated sub-agents[/+]reidbaker commentedon Jul 28, 2026
Part of what we are going to need to make progress on this style of organization is some documentation + evaluation for how different popular harnesses handle the concept of sub agents. I am not aware of a sub agent spec that we can follow.
So to be concrete. Can you point to the organizational style you want in the docs of antigravity, claude and codex?
[-]Scope platform-specific skills (e.g., iOS specific plugin migration) under dedicated sub-agents[/-][+]Support platform-specific skills (e.g., iOS specific plugin migration)[/+]hellohuanlin commentedon Jul 28, 2026
I updated the issue to remove the sub-agent bits. My ask is mainly about how we can publish a skill that's ios specific, to address our concern that we don't want to install it for all users. I suggested sub-agent because it seems to describe our concern here. For example, this quote from Claude's sub-agent page: https://code.claude.com/docs/en/sub-agents
I could be terribly wrong, though.