@fprad0/skill-master-mcp 0.0.9 → 0.0.10

package/docs/skill-candidates/v0.0.10/cli-creator/references/agent-cli-patterns.md

@@ -0,0 +1,154 @@
+# Codex CLI Patterns
+
+Use this reference when designing the command surface for a new CLI Codex should run.
+
+## Mental model
+
+The CLI is Codex's command layer. It should turn a service, app, API, log source, or database into shell commands Codex can run repeatedly from any repo.
+
+Good CLIs for Codex expose composable primitives. Avoid a single command that tries to "do the whole investigation" when smaller discover, read, resolve, download, inspect, draft, and upload commands would compose better.
+
+## Help is interface
+
+Write `--help` for a future Codex thread that only has the binary and a vague task. Each command should have a short description and flags with literal names from the product or API.
+
+Good top-level help should answer:
+
+- What containers can I discover?
+- What exact objects can I read?
+- What stable IDs can I resolve?
+- What files can I download or upload?
+- Which write actions exist?
+- What is the raw escape hatch?
+
+## Prefer this command shape
+
+Use product nouns, then verbs:
+
+```bash
+tool-name --json doctor
+tool-name --json accounts list
+tool-name --json projects list
+tool-name --json channels resolve --name codex
+tool-name --json messages search "exact phrase"
+tool-name --json messages context <message-id> --before 3 --after 3
+tool-name --json logs download <build-url> --failed --out ./logs
+tool-name --json media upload --file ./image.png
+tool-name --json drafts create --body-file draft.json
+```
+
+For APIs whose native noun is already strong, direct verbs can be fine:
+
+```bash
+tool-name --json social-sets
+tool-name --json drafts list --social-set <id>
+tool-name --json request get /v2/me
+```
+
+The important rule is consistency. Do not mix many styles unless the product vocabulary demands it.
+
+## Useful shapes from mature CLIs
+
+Prefer these patterns over clever agent-only abstractions:
+
+```bash
+# Field-selected structured output: make common reads scriptable.
+tool-name issues list --json number,title,url,state
+tool-name issues list --json number,title --jq '.[] | select(.state == "open")'
+
+# Human text by default, full API object when requested.
+tool-name pods get <name>
+tool-name pods get <name> -o json
+
+# Product workflow commands, not just REST nouns.
+tool-name logs tail
+tool-name webhooks listen --forward-to localhost:4242/webhooks
+tool-name webhooks trigger checkout.completed
+```
+
+Only implement filtering or templating if the user will actually need it. Stable JSON plus narrow read commands are the baseline.
+
+## Discovery, resolve, read, context
+
+Design first-pass commands in this order:
+
+1. **Discover** broad containers: workspaces, accounts, social sets, repos, projects, channels, queues.
+2. **Resolve** human input into IDs: user names, channel names, permalinks, PR URLs, build URLs, customer slugs.
+3. **Read** an exact object: issue, event, thread, draft, customer, job, run, media item.
+4. **Context** around an anchor when useful: nearby messages, parent thread, surrounding logs, audit history.
+
+Do not force Codex to repeatedly search when it already has a stable ID.
+
+## Text, JSON, files, exit codes
+
+Support human text by default if it helps. Support `--json` everywhere Codex will parse or pipe results.
+
+For `--json`:
+
+- Emit JSON to stdout only.
+- Send progress and diagnostics to stderr.
+- Keep success and error shapes documented.
+- Redact tokens, cookies, customer secrets, private headers, and unrelated payloads.
+
+For downloads and exports:
+
+- Write files under a user-provided `--out` path when possible.
+- In JSON output, return the file path, byte count if cheap, source URL or ID, and follow-up command.
+
+For exit codes:
+
+- Exit zero when the command succeeded, including an empty result.
+- Exit nonzero for auth failure, invalid input, network failure, parse failure, API error, or incomplete upload/download.
+- Make `doctor --json` usable even when auth is missing. It should report missing auth rather than crashing.
+
+## Pagination and breadth
+
+Start shallow by default. Add explicit knobs for breadth:
+
+```bash
+tool-name --json messages search "topic" --limit 10
+tool-name --json messages search "topic" --limit 50 --all-pages --max-pages 3
+tool-name --json drafts list --limit 20 --offset 40
+```
+
+Return `next_cursor`, `next_url`, `offset`, `page_count`, or whatever is real for the provider.
+
+## Raw escape hatch
+
+The raw command is a repair hatch, not the main interface.
+
+Good raw commands still use configured auth, base URL, JSON parsing, redaction, status/error handling, and `--json`.
+
+Make reads easy:
+
+```bash
+tool-name --json request get /v2/me
+```
+
+Treat raw writes as live writes. Do not hide POST/PUT/PATCH/DELETE behind a "debug" command.
+
+## Companion skill pattern
+
+The companion skill should be smaller than the CLI README. It should teach the path through the tool:
+
+```md
+Start with:
+
+tool-name --json doctor
+tool-name --json accounts list
+
+For [common job]:
+
+tool-name --json ... 
+tool-name --json ...
+
+Rules:
+
+- Prefer installed `tool-name` on PATH.
+- Use --json when analyzing output.
+- Create drafts by default.
+- Do not publish/delete/retry/submit unless the user asked.
+- Use `request get ...` only when high-level commands are missing.
+```
+
+Include JSON shape notes only when Codex needs them to choose the next command.

package/docs/skill-candidates/v0.0.10/developer-workstation-ops/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: developer-workstation-ops
+description: "Operate developer tooling across CLI, terminal, Git, GitHub, Windows, Linux, Codex, Claude, Gemini and Antigravity with path checks, config validation, cross-platform notes and safe diagnostics. Use when a task involves local environment readiness, shell automation or AI client integration."
+---
+
+# Developer Workstation Ops
+
+Use this skill when a task is about getting local developer tooling working reliably across machines and AI clients.
+
+## Workflow
+
+- Verify executable paths before editing config files.
+- Separate read-only diagnostics from mutating fixes.
+- Treat shell, terminal and editor/client integration as separate layers.
+- Prefer idempotent config merges over whole-file replacement.
+- Keep Windows and Linux differences explicit.
+- Check Git and GitHub auth before assuming network operations will work.
+- For Codex, Claude, Gemini and Antigravity, validate both config and executable command.
+- End with a smoke command the operator can rerun.
+
+## Coverage
+
+- CLI, terminal, shell scripts, PATH, Git, GitHub.
+- Windows, Linux, cross-platform environment behavior.
+- Codex, Claude, Gemini and Antigravity MCP/client readiness.
+
+## Guardrails
+
+- Do not delete unrelated config content.
+- Do not hide restart requirements.
+- Do not run destructive shell commands from convenience wrappers.
+- Do not claim readiness without a real smoke command.

package/docs/skill-candidates/v0.0.10/figma/LICENSE.txt

@@ -0,0 +1,2 @@
+Use of these Figma skills and related files ("Materials") is governed by the Figma Developer Terms (available at https://www.figma.com/legal/developer-terms/). By accessing, downloading, or using these Materials — including through automated systems or AI agents — you agree to the Figma Developer Terms.
+These Materials are currently offered as a Beta feature. Figma may modify, suspend, or discontinue them at any time without notice.

package/docs/skill-candidates/v0.0.10/figma/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: figma
+description: Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
+---
+
+# Figma MCP
+
+Use the Figma MCP server for Figma-driven implementation. For setup and debugging details (env vars, config, verification), see `references/figma-mcp-config.md`.
+
+## Figma MCP Integration Rules
+These rules define how to translate Figma inputs into code for this project and must be followed for every Figma-driven change.
+
+### Required flow (do not skip)
+1. Run get_design_context first to fetch the structured representation for the exact node(s).
+2. If the response is too large or truncated, run get_metadata to get the high-level node map and then re-fetch only the required node(s) with get_design_context.
+3. Run get_screenshot for a visual reference of the node variant being implemented.
+4. Only after you have both get_design_context and get_screenshot, download any assets needed and start implementation.
+5. Translate the output (usually React + Tailwind) into this project's conventions, styles and framework. Reuse the project's color tokens, components, and typography wherever possible.
+6. Validate against Figma for 1:1 look and behavior before marking complete.
+
+### Implementation rules
+- Treat the Figma MCP output (React + Tailwind) as a representation of design and behavior, not as final code style.
+- Replace Tailwind utility classes with the project's preferred utilities/design-system tokens when applicable.
+- Reuse existing components (e.g., buttons, inputs, typography, icon wrappers) instead of duplicating functionality.
+- Use the project's color system, typography scale, and spacing tokens consistently.
+- Respect existing routing, state management, and data-fetch patterns already adopted in the repo.
+- Strive for 1:1 visual parity with the Figma design. When conflicts arise, prefer design-system tokens and adjust spacing or sizes minimally to match visuals.
+- Validate the final UI against the Figma screenshot for both look and behavior.
+
+### Asset handling
+- The Figma MCP Server provides an assets endpoint which can serve image and SVG assets.
+- IMPORTANT: If the Figma MCP Server returns a localhost source for an image or an SVG, use that image or SVG source directly.
+- IMPORTANT: DO NOT import/add new icon packages, all the assets should be in the Figma payload.
+- IMPORTANT: do NOT use or create placeholders if a localhost source is provided.
+
+### Link-based prompting
+- The server is link-based: copy the Figma frame/layer link and give that URL to the MCP client when asking for implementation help.
+- The client cannot browse the URL but extracts the node ID from the link; always ensure the link points to the exact node/variant you want.
+
+## References
+- `references/figma-mcp-config.md` — setup, verification, troubleshooting, and link-based usage reminders.
+- `references/figma-tools-and-prompts.md` — tool catalog and prompt patterns for selecting frameworks/components and fetching metadata.

package/docs/skill-candidates/v0.0.10/figma/agents/openai.yaml

@@ -0,0 +1,14 @@
+interface:
+  display_name: "Figma"
+  short_description: "Use Figma MCP for design-to-code work"
+  icon_small: "./assets/figma-small.svg"
+  icon_large: "./assets/figma.png"
+  default_prompt: "Use $figma to inspect the target design and translate it into implementable UI decisions."
+
+dependencies:
+  tools:
+    - type: "mcp"
+      value: "figma"
+      description: "Figma MCP server"
+      transport: "streamable_http"
+      url: "https://mcp.figma.com/mcp"

package/docs/skill-candidates/v0.0.10/figma/assets/figma-small.svg

@@ -0,0 +1,3 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" viewBox="0 0 16 16">
+  <path fill="#000" fill-rule="evenodd" d="M4.994 5.986a2.014 2.014 0 1 0 0 4.028h2.069V5.986H4.994Zm5.063-.98h.055a2.014 2.014 0 1 0 0-4.026h-2.07v4.027h2.015Zm1.697.49A2.994 2.994 0 0 0 10.112 0H4.994a2.994 2.994 0 0 0-1.642 5.498A2.99 2.99 0 0 0 2 8a2.99 2.99 0 0 0 1.352 2.503A2.99 2.99 0 0 0 2 13.007C2 14.663 3.358 16 5.008 16c1.665 0 3.035-1.349 3.035-3.02v-2.765a2.984 2.984 0 0 0 2.014.778h.055a2.994 2.994 0 0 0 1.642-5.496Zm-1.642.49h-.055a2.014 2.014 0 1 0 0 4.028h.055a2.014 2.014 0 1 0 0-4.028Zm-7.132 7.02c0-1.111.902-2.013 2.014-2.013h2.069v1.987c0 1.123-.924 2.04-2.055 2.04a2.026 2.026 0 0 1-2.028-2.013Zm4.083-8H4.994a2.014 2.014 0 1 1 0-4.026h2.069v4.027Z" clip-rule="evenodd"/>
+</svg>

package/docs/skill-candidates/v0.0.10/figma/assets/icon.svg

@@ -0,0 +1,28 @@
+<svg
+  width="400"
+  height="400"
+  viewBox="0 0 400 400"
+  fill="none"
+  xmlns="http://www.w3.org/2000/svg"
+>
+  <path
+    d="M97.5 302.5C97.5 274.195 120.445 251.25 148.75 251.25H200V302.5C200 330.805 177.055 353.75 148.75 353.75C120.445 353.75 97.5 330.805 97.5 302.5Z"
+    fill="#0ACF83"
+  />
+  <path
+    d="M200 200C200 171.696 222.945 148.75 251.25 148.75C279.554 148.75 302.5 171.695 302.5 200C302.5 228.305 279.554 251.25 251.25 251.25C222.945 251.25 200 228.304 200 200Z"
+    fill="#1ABCFE"
+  />
+  <path
+    d="M97.5 200C97.5 228.305 120.445 251.25 148.75 251.25H200V148.75H148.75C120.445 148.75 97.5 171.695 97.5 200Z"
+    fill="#A259FF"
+  />
+  <path
+    d="M200 46.25V148.75H251.25C279.555 148.75 302.5 125.805 302.5 97.5C302.5 69.1954 279.555 46.25 251.25 46.25H200Z"
+    fill="#FF7262"
+  />
+  <path
+    d="M97.5 97.5C97.5 125.805 120.445 148.75 148.75 148.75H200V46.25L148.75 46.25C120.445 46.25 97.5 69.1954 97.5 97.5Z"
+    fill="#F24E1E"
+  />
+</svg>

package/docs/skill-candidates/v0.0.10/figma/references/figma-mcp-config.md

@@ -0,0 +1,35 @@
+# Figma MCP config reference
+
+Use this snippet to register the Figma MCP server in `~/.codex/config.toml` as a streamable HTTP server with bearer auth pulled from your env.
+
+```toml
+[mcp_servers.figma]
+url = "https://mcp.figma.com/mcp"
+bearer_token_env_var = "FIGMA_OAUTH_TOKEN"
+http_headers = { "X-Figma-Region" = "us-east-1" }
+```
+
+## Notes and options
+- The bearer token must be available as `FIGMA_OAUTH_TOKEN` in the environment that launches Codex.
+- Keep the region header aligned with your Figma region. If your org uses another region, update `X-Figma-Region` consistently.
+- OAuth on streamable HTTP requires the RMCP client: set `[features].rmcp_client = true` (or `experimental_use_rmcp_client = true` on older builds) at the top level of `config.toml`.
+- Optional per-server timeouts: `startup_timeout_sec` (default 10) and `tool_timeout_sec` (default 60) can be set inside `[mcp_servers.figma]` if needed.
+
+## Env var setup (if missing)
+- One-time set for current shell: `export FIGMA_OAUTH_TOKEN="<token>"`
+- Persist for future sessions: add the export line to your shell profile (e.g., `~/.zshrc` or `~/.bashrc`), then restart the shell or your IDE.
+- Verify before launching Codex: `echo $FIGMA_OAUTH_TOKEN` should print a non-empty token.
+
+## Setup + verification checklist
+- Add the snippet above to `~/.codex/config.toml` under `[mcp_servers.figma]`, and enable `[features].rmcp_client = true` (or `experimental_use_rmcp_client = true` on older releases).
+- Restart Codex (CLI/IDE) after updating config and env vars.
+- Ask Codex to list Figma tools or run a simple call to confirm the server is reachable.
+
+## Troubleshooting
+- Token not picked up: Export `FIGMA_OAUTH_TOKEN` in the same shell that launches Codex, or add it to your shell profile and restart.
+- OAuth errors: Verify `rmcp_client` is enabled and the bearer token is valid. Tokens copied from Figma should not include surrounding quotes.
+- Network/headers: Keep the `X-Figma-Region` header; if your org uses another region, update the header consistently across config and requests.
+
+## Usage reminders
+- The server is link-based: copy the Figma frame or layer link, then ask the MCP client to implement that URL. The client will extract the node ID from the link (it does not browse the page).
+- If output feels generic, restate the project-specific rules from the main skill and ensure you follow the required flow (get_design_context → get_metadata if needed → get_screenshot).

package/docs/skill-candidates/v0.0.10/figma/references/figma-tools-and-prompts.md

@@ -0,0 +1,34 @@
+# Figma MCP tools and prompt patterns
+
+Quick reference for the Figma MCP toolset, when to use each tool, and prompt examples to steer output toward your stack.
+
+## Core tools
+- `get_design_context` (Figma Design, Figma Make): Primary tool. Returns structured design data and default React + Tailwind code. Selection-based prompting works on desktop; the remote server uses a frame/layer link to extract the node ID.
+- `get_variable_defs` (Figma Design): Lists variables/styles (colors, spacing, typography) used in the selection. Useful to align with tokens.
+- `get_metadata` (Figma Design): Sparse XML outline of layer IDs/names/types/positions/sizes. Use before re-calling `get_design_context` on large nodes to avoid truncation.
+- `get_screenshot` (Figma Design, FigJam): Screenshot of the selection for visual fidelity checks.
+- `get_figjam` (FigJam): XML + screenshots for FigJam diagrams (architecture, flows).
+- `create_design_system_rules` (no file context): Generates a rule file with design-to-code guidance for your stack. Save it where the agent can read it.
+- `get_code_connect_map` (Figma Design): Returns mapping of Figma node IDs to code components (`codeConnectSrc`, `codeConnectName`). Use to reuse existing components.
+- `add_code_connect_map` (Figma Design): Adds/updates a mapping between a Figma node and a code component to improve reuse.
+- `get_strategy_for_mapping` (alpha, local only): Figma-prompted tool to decide mapping strategy for connecting a node to a code component.
+- `send_get_strategy_response` (alpha, local only): Sends the response after `get_strategy_for_mapping`.
+- `whoami` (remote only): Returns the authenticated Figma user identity (email, plans, seat types).
+
+## Prompt patterns (design context)
+- Change framework: “generate my Figma selection in Vue” or “in plain HTML + CSS” or “for iOS”.
+- Use my components: “generate my Figma selection using components from `src/components/ui`”.
+- Combine: “generate my Figma selection using components from `src/ui` and style with Tailwind”.
+- Note: On the remote server, selection-based prompting requires a frame/layer link; the server extracts the node ID from the URL.
+
+## Prompt patterns (variables/styles)
+- “get the variables used in my Figma selection”
+- “what color and spacing variables are used in my Figma selection?”
+- “list the variable names and their values used in my Figma selection”
+
+## Prompt patterns (code connect)
+- “show the code connect map for this selection”
+- “map this node to `src/components/ui/Button.tsx` with name `Button`”
+
+## Best-practice flow reminder
+Use `get_design_context` → (optionally `get_metadata` for large nodes) → `get_screenshot`, and keep project rules from `SKILL.md` in mind when applying the generated output.

package/docs/skill-candidates/v0.0.10/figma-code-connect-components/LICENSE.TXT

@@ -0,0 +1,2 @@
+Use of these Figma skills and related files ("Materials") is governed by the Figma Developer Terms (available at https://www.figma.com/legal/developer-terms/). By accessing, downloading, or using these Materials — including through automated systems or AI agents — you agree to the Figma Developer Terms.
+These Materials are currently offered as a Beta feature. Figma may modify, suspend, or discontinue them at any time without notice.