agentleFS
Sign inStart free
cameroncookecameroncooke/XcodeBuildMCP/.agents/skills/mobilebuildmcp-rendering-streaming-review/SKILL.md

mobilebuildmcp-rendering-streaming-review

Skill6.5k starsChanged 50 days agoMITView on GitHub

Use when reviewing MobileBuildMCP rendering, streaming fragment, next-step, and CLI output mode changes for boundary violations.

2 other projects use a version of this.

Trending

Quiet since May.about the whole repository

Dec 2025: 1 mentionJan 2026: 4 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the cameroncooke/XcodeBuildMCP repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about cameroncooke/XcodeBuildMCP

The biggest 5 of 21 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 21

Talked about on GitHub and Bluesky (21 times).

On GitHub · 17

12 more on GitHub

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not edit product code unless the user explicitly requests implementation changes.

    line 13
  2. Very specific:

    Do not invent json/jsonl render strategies.

    line 31
  3. Very specific:

    Keep ctx.emit and xcodebuild pipeline emitFragment contexts separate.

    line 34
  4. Distinctive:

    Keep next-step rendering in runtime/rendering boundary.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MobileBuildMCP 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.ts
  • src/types/runtime-status.ts
  • src/runtime/tool-invoker.ts
  • src/runtime/__tests__/tool-invoker.test.ts
  • xcodebuildmcp.com/app/docs/_content/architecture-rendering-output.mdx
  • xcodebuildmcp.com/app/docs/_content/architecture-tool-lifecycle.mdx
  • xcodebuildmcp.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/jsonl render strategies.
  • Streaming tools emit typed fragments and one final structured result.
  • Non-streaming tools do not emit unnecessary fragments.
  • Keep ctx.emit and xcodebuild pipeline emitFragment contexts separate.
  • Keep next-step rendering in runtime/rendering boundary.

Validation

  • npm test -- src/runtime/__tests__/tool-invoker.test.ts
  • npm run test:snapshots
  • npm run typecheck
  • npx skill-check .agents/skills/mobilebuildmcp-rendering-streaming-review

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free