feat: add platform-specific store profiles - #3
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d03853f0cf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
Addressed and resolved the previous review findings in @greptileai |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0a99f32d97
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Summary
Why
The two directories review tools and agent instructions differently. Platform-specific packaging lets Macaly keep the full universal MCP while presenting each store with scoped, accurate instructions and safety metadata.
What changed
.mcp.claude.jsonand wire the Claude plugin manifest to the Claude endpointskills-claude/build-app-on-macalyrun_project_commandImpact
Direct and marketplace installations retain the complete app-building workflow. Store-specific packages no longer rely on aggressive routing language or iframe rendering.
Related work
Verification
pnpm run buildclaude plugin validate plugins/macaly-codegit diff --checkNeed help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.