strata-202607

Estrelas10

Forks3

Atualizado16 de julho de 2026 às 03:43

Use Strata, the Legacy Code Labs macOS visual-spec app, through its local Streamable HTTP MCP server. Trigger when Codex needs to create, read, validate, update, version, diff, or restore Strata diagrams; build visual specs from user flows, discovery trees, architecture sketches, or D2; diagnose Strata MCP setup; or verify a feature against a shared Strata canvas.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

that-in-rust

that-in-rust/agent-room-of-requirements

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

7 arquivos

SKILL.md

readonly

name	strata-202607
description	Use Strata, the Legacy Code Labs macOS visual-spec app, through its local Streamable HTTP MCP server. Trigger when Codex needs to create, read, validate, update, version, diff, or restore Strata diagrams; build visual specs from user flows, discovery trees, architecture sketches, or D2; diagnose Strata MCP setup; or verify a feature against a shared Strata canvas.

Strata 202607

Strata is a native macOS visual-spec tool. The app runs a loopback-only MCP server at http://127.0.0.1:7337/mcp; use it to work against versioned D2 diagrams instead of keeping a visual spec only in chat.

Startup Check

Confirm Strata is installed and launch it:

test -x /Applications/Strata.app/Contents/MacOS/Strata
open -a Strata
lsof -nP -iTCP:7337 -sTCP:LISTEN

If Codex has not been configured yet, install the MCP server:

codex mcp add strata --url http://127.0.0.1:7337/mcp
codex mcp list

Probe the local server:

/Users/amulbadjatya/.codex/skills/strata-202607/scripts/strata_mcp_probe.py --kits

If this session does not expose Strata MCP tools after installation, restart Codex or use scripts/strata_mcp_tool.py as a temporary raw JSON-RPC fallback. Do not hand-edit Strata's SQLite database.

Core Workflow

List projects, then create or choose a project.
Pick the right kit:
- user_flow: UI navigation, user journeys, branching logic, E2E proof paths.
- discovery_tree: outcomes, nested tasks, planning trees.
- freeform: raw D2 for architecture, state machines, data flows.
Before authoring constrained diagrams, call describe_kit for the selected kit or read references/strata-kits.md.
Draft source and call validate_diagram until it compiles.
Call create_diagram for a new visual spec or get_diagram then update_diagram for an existing one.
Always preserve concurrency:
- Read version from get_diagram.
- Pass that as base_version to update_diagram.
- If Strata reports a conflict, re-read, merge, validate, and retry.
Use list_versions, diff_versions, get_version, and restore_version for review, rollback, and audit.

Safety Rules

Treat diagram_id, project_id, and group_id as opaque API handles.
In user-facing summaries, use diagram_name, not internal IDs.
Never claim an edit landed unless Strata returned render_ok: true or the create/update result succeeded.
Prefer validate_diagram before mutating diagrams.
Keep source replacement intentional: update_diagram replaces the full D2 source and creates a snapshot.
Use message on updates for meaningful snapshot notes.
Use delete_diagram and delete_group only after explicit confirmation; there is no MCP undo for deletion.
Do not use Strata for repo dependency analysis; use Clarity or codebase-memory for code structure, then represent the result in Strata if a visual spec is useful.

Raw MCP Fallback

Use the bundled helpers when the Codex tool list has not picked up Strata yet:

scripts/strata_mcp_probe.py --kits
scripts/strata_mcp_tool.py list_projects
scripts/strata_mcp_tool.py validate_diagram --args-json '{"kit":"user_flow","source":"@direction down\n\nstart s: Start\nscreen page: Page\nend e success: Done\ns -> page\npage -> e"}'

References

Read references/strata-mcp-tools.md when you need exact tool names, arguments, or installation evidence.
Read references/strata-kits.md when authoring user_flow, discovery_tree, or freeform diagrams.
Read references/strata-failure-modes.md when setup, validation, concurrency, or visibility is confusing.

Mais deste repositório

mesmo repositório

clarity202606

that-in-rust/agent-room-of-requirements

Use Clarity, the LegacyCodeHQ structural design CLI, for dependency impact graphs, architecture/refactoring verification, before-commit design checks, code review context, cycle/module/workspace exploration, AGENTS.md Clarity setup, or rebuilding/probing Clarity command availability. Use when Codex needs to run or interpret clarity show, watch, languages, extensions, modules, cycles, workspace, setup, or version-specific Clarity commands.

2026-07-0810

kotlin-backend-delivery-01

that-in-rust/agent-room-of-requirements

Plan, build, harden, and review Kotlin backend services with Spring Boot, Ktor, coroutines, typed configuration, persistence, migrations, testing, security, resilience, and operations. Use for Kotlin HTTP APIs, workers, service refactors, production-readiness reviews, or JVM backend architecture decisions.

2026-07-0510

kotlin-coder-01

that-in-rust/agent-room-of-requirements

Reliability-first Kotlin skill for implementing, refactoring, or reviewing Kotlin libraries, CLIs, JVM modules, shared domain code, coroutine code, and Java interop boundaries. Use when work needs null-safety discipline, value and sealed types, idiomatic scope-function use, typed errors, structured concurrency, testing, or JVM quality gates.

2026-07-0510

python-coder-01

that-in-rust/agent-room-of-requirements

Reliability-first Python skill for implementing, refactoring, or reviewing Python packages, CLIs, services, scripts, async code, tests, and typed modules. Use when work needs type hints, dataclasses, boundary parsing, exception design, context managers, asyncio cancellation, packaging, pytest or unittest strategy, ruff, mypy, pyright, or runtime safety.

2026-07-0510

local-vision-ollama

that-in-rust/agent-room-of-requirements

Analyze images using local Ollama vision model (qwen3.5:4b) with automatic pre-resizing and filename sanitization for reliable processing.

2026-05-1010

save-recent-chat-context

that-in-rust/agent-room-of-requirements

Save the most recent visible conversation text from the active Codex thread into a timestamped Markdown checkpoint file in the current repo root. Use when the user asks to back up the last few chat messages, dump recent thread context to disk, preserve a resume point before context loss, or create a lightweight conversation recovery file.

2026-04-2210

name	strata-202607
description	Use Strata, the Legacy Code Labs macOS visual-spec app, through its local Streamable HTTP MCP server. Trigger when Codex needs to create, read, validate, update, version, diff, or restore Strata diagrams; build visual specs from user flows, discovery trees, architecture sketches, or D2; diagnose Strata MCP setup; or verify a feature against a shared Strata canvas.

Strata 202607

Startup Check

Confirm Strata is installed and launch it:

test -x /Applications/Strata.app/Contents/MacOS/Strata
open -a Strata
lsof -nP -iTCP:7337 -sTCP:LISTEN

If Codex has not been configured yet, install the MCP server:

codex mcp add strata --url http://127.0.0.1:7337/mcp
codex mcp list

Probe the local server:

/Users/amulbadjatya/.codex/skills/strata-202607/scripts/strata_mcp_probe.py --kits

If this session does not expose Strata MCP tools after installation, restart Codex or use scripts/strata_mcp_tool.py as a temporary raw JSON-RPC fallback. Do not hand-edit Strata's SQLite database.

Core Workflow

List projects, then create or choose a project.
Pick the right kit:
- user_flow: UI navigation, user journeys, branching logic, E2E proof paths.
- discovery_tree: outcomes, nested tasks, planning trees.
- freeform: raw D2 for architecture, state machines, data flows.
Before authoring constrained diagrams, call describe_kit for the selected kit or read references/strata-kits.md.
Draft source and call validate_diagram until it compiles.
Call create_diagram for a new visual spec or get_diagram then update_diagram for an existing one.
Always preserve concurrency:
- Read version from get_diagram.
- Pass that as base_version to update_diagram.
- If Strata reports a conflict, re-read, merge, validate, and retry.
Use list_versions, diff_versions, get_version, and restore_version for review, rollback, and audit.

Safety Rules

Treat diagram_id, project_id, and group_id as opaque API handles.
In user-facing summaries, use diagram_name, not internal IDs.
Never claim an edit landed unless Strata returned render_ok: true or the create/update result succeeded.
Prefer validate_diagram before mutating diagrams.
Keep source replacement intentional: update_diagram replaces the full D2 source and creates a snapshot.
Use message on updates for meaningful snapshot notes.
Use delete_diagram and delete_group only after explicit confirmation; there is no MCP undo for deletion.
Do not use Strata for repo dependency analysis; use Clarity or codebase-memory for code structure, then represent the result in Strata if a visual spec is useful.

Raw MCP Fallback

Use the bundled helpers when the Codex tool list has not picked up Strata yet:

scripts/strata_mcp_probe.py --kits
scripts/strata_mcp_tool.py list_projects
scripts/strata_mcp_tool.py validate_diagram --args-json '{"kit":"user_flow","source":"@direction down\n\nstart s: Start\nscreen page: Page\nend e success: Done\ns -> page\npage -> e"}'

References

Read references/strata-mcp-tools.md when you need exact tool names, arguments, or installation evidence.
Read references/strata-kits.md when authoring user_flow, discovery_tree, or freeform diagrams.
Read references/strata-failure-modes.md when setup, validation, concurrency, or visibility is confusing.