xcodebuildmcp-rendering-streaming-review
This skill provides specialized code review capabilities for XcodeBuildMCP's rendering and streaming components, helping developers identify architectural violations and design inconsistencies in iOS and macOS build automation. It integrates with the Model Context Protocol to analyze changes against established patterns and best practices for the XcodeBuild MCP server.
XcodeBuildMCP rendering boundaries review examines architectural violations in rendering and streaming components for iOS and macOS build automation. The skill validates fragment emission, output mode boundaries in tool handlers, runtime streaming architecture compliance, and type safety across tool invokers and domain fragments to ensure consistency with established patterns.
AI-generated summary based on this skill's SKILL.md
Install
getsentry/XcodeBuildMCP/xcodebuildmcp-rendering-streaming-review · repository language: TypeScript
git clone https://github.com/getsentry/XcodeBuildMCP
cp -r XcodeBuildMCP/.agents/skills/xcodebuildmcp-rendering-streaming-review ~/.claude/skills/xcodebuildmcp-rendering-streaming-reviewFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does xcodebuildmcp rendering boundaries review cover?
XcodeBuildMCP rendering boundaries review examines architectural violations in rendering and streaming components for iOS and macOS build automation. The skill validates fragment emission, output mode boundaries in tool handlers, runtime streaming architecture compliance, and type safety across tool invokers and domain fragments to ensure consistency with established patterns.
How does xcodebuildmcp validate streaming fragments?
XcodeBuildMCP validates streaming fragments by inspecting tool handler boundaries, checking runtime streaming architecture guardrails, and ensuring proper separation between CLI and MCP output modes. The review confirms that fragment emission follows design rules and that final contract integrity is maintained across the pipeline.
What are the output mode guardrails in xcodebuildmcp?
XcodeBuildMCP enforces strict separation between CLI and MCP output modes through guardrails that validate tool handler boundaries and fragment emission rules. The skill checks that ctx.emit calls respect architectural boundaries and that rendering strategies maintain proper output format separation for both streaming and non-streaming tools.
Does xcodebuildmcp check domain fragments runtime status?
Yes, XcodeBuildMCP inspects domain fragments runtime status by validating type safety in tool invokers and domain fragment handlers. The review ensures that streaming architecture compliance is maintained at runtime and that fragment lifecycle rendering follows established architectural patterns without violations.
How can xcodebuildmcp help with tool handler review?
XcodeBuildMCP provides specialized code review for tool handlers by analyzing rendering strategies, validating fragment emission boundaries, and checking output mode separation. The skill identifies architectural inconsistencies in tool lifecycle rendering and ensures structured output validation across both streaming and non-streaming tool implementations.
What license does xcodebuildmcp rendering-streaming-review use?
XcodeBuildMCP rendering-streaming-review is released under the MIT license, enabling open-source use and integration with other development tools and workflows for iOS and macOS build automation analysis.
SKILL.md
rendered from the published skill — quoted content, verbatim
XcodeBuildMCP Rendering and Streaming Review
Review guardrails for rendering boundaries, streaming fragments, and output modes.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
src/rendering/**src/types/domain-fragments.tssrc/types/runtime-status.tssrc/runtime/tool-invoker.tssrc/runtime/__tests__/tool-invoker.test.tsxcodebuildmcp.com/app/docs/_content/architecture-rendering-output.mdxxcodebuildmcp.com/app/docs/_content/architecture-tool-lifecycle.mdxxcodebuildmcp.com/app/docs/_content/output-formats.mdx
Guardrails
- Tool handlers do not branch on CLI vs MCP output mode.
- Fragments represent progress, not final contract data.
- Final structured output remains canonical.
- Do not invent
json/jsonlrender strategies. - Streaming tools emit typed fragments and one final structured result.
- Non-streaming tools do not emit unnecessary
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agents/skills/xcodebuildmcp-rendering-streaming-review/SKILL.md