mastergo
Retrieve and analyze MasterGo design DSL data. Use when users provide MasterGo links (https://mastergo.com/file/xxx or /goto/xxx) to fetch design structure, component documentation, and DSL metadata.
What this skill does
# MasterGo Skill
Retrieve and analyze design data from MasterGo files using self-contained Python scripts.
## Prerequisites
**Environment variable required:**
```bash
export MASTERGO_TOKEN="mg_your_token_here"
```
Get token: MasterGo Settings > Security > Personal Access Token
**Requirements**: Team Edition account, files in Team Projects (not Drafts).
### CRITICAL: Secure Token Handling
**NEVER do this:**
- `echo $MASTERGO_TOKEN` - exposes secret in output
- `echo "Token: $MASTERGO_TOKEN"` - exposes secret
- `printenv MASTERGO_TOKEN` - exposes secret
- Any command that prints the token value
**Secure verification method:**
```bash
test -n "$MASTERGO_TOKEN" && echo "Token is set" || echo "Token is NOT set"
```
This only prints whether the token exists, never its value.
## Script Location
Scripts are in `scripts/` relative to this SKILL.md file. Use absolute path when executing:
```
{this_skill_directory}/scripts/mastergo_*.py
```
## Workflow
### Step 1: Analyze DSL Structure
**Always analyze first** to understand the page structure:
```bash
python scripts/mastergo_analyze.py "https://mastergo.com/goto/xxx"
```
Output shows:
- Node tree (type, name, size)
- Text contents
- Component doc links
- Navigation targets
### Step 2: Get Full DSL (if needed)
For detailed DSL data:
```bash
python scripts/mastergo_get_dsl.py "https://mastergo.com/goto/xxx"
```
Output: JSON with `{ dsl, componentDocumentLinks, rules }`
### Step 3: Fetch Component Docs
If `componentDocumentLinks` is non-empty, fetch relevant docs:
```bash
python scripts/mastergo_get_dsl.py URL | python scripts/mastergo_fetch_docs.py --from-dsl
```
Or fetch individually:
```bash
python scripts/mastergo_fetch_docs.py "https://example.com/button.mdx"
```
## Scripts Reference
| Script | Purpose | Output |
|--------|---------|--------|
| `mastergo_analyze.py` | Structure summary | Human-readable tree to stdout |
| `mastergo_get_dsl.py` | Full DSL data | JSON to stdout |
| `mastergo_fetch_docs.py` | Component docs | Doc content to stdout |
| `mastergo_utils.py` | Utility functions | Import as module |
## DSL Key Concepts
- **`token` fields**: Design tokens for colors, shadows, fonts (convert to CSS variables when generating code)
- **`componentInfo`**: Component metadata including documentation links
- **`interactive` fields**: User interactions including page navigation targets
- **`rules` array**: Guidelines returned with DSL response
## CRITICAL: Do NOT Pollute User Projects
**FORBIDDEN actions:**
- Creating `.temp_dsl.json` or any DSL cache file in user project
- Creating `analyze_dsl.py` or any analysis script in user project
- Creating any temporary files in user project directory
- Writing any skill-related files outside of skill directory
**ALLOWED:**
- Running scripts and capturing stdout output
- Using output directly in memory
- Reading user's existing project files for context
All script output goes to **stdout only**. Use the output directly; do not save intermediate files to user's project.
## References
- [references/dsl-types.md](references/dsl-types.md) - Complete DSL type definitions
- [references/dsl-structure.md](references/dsl-structure.md) - Key fields and patterns
- [references/multi-page-workflow.md](references/multi-page-workflow.md) - Multi-page workflow
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.