Reinspro Skill + MCP
Real interfaces. A more considered process. Help your agent turn visual research into professional, distinctive work that fits your brand.
Free Skill download. Reinspro MCP is required for design work; live access requires a paid plan.
Download SKILL.md only01 / Two parts. One better starting point.
A Skill tells your agent how to approach the work. An MCP connection gives it references to work with. Both are required for the design workflow; neither replaces your brief.
A portable SKILL.md with mandatory MCP preflight, reference-led synthesis, focused improvement modes and implementation QA.
A remote connection to search the design catalog and retrieve accessible screens, pages and sections.
MCP is mandatory for the design workflow. You can read or install the public Skill without it, but design work starts only after tool discovery, a successful authenticated read and actual reference-image inspection. If access or images are unavailable, the agent stops and helps with setup.
02 / Less guessing. More intention.
A useful reference does more than set a mood. It gives your agent specific design decisions to examine, explain and adapt.
Study type scale, spacing, grids and CTA placement. Turn a vague brief into clear rules that hold together across the page.
Compare approaches from two or three brands. Borrow the principles that fit your audience, then create your own layout, content and visual language.
Use one token system across sections and responsive states. Keep the reference set and decision notes so the next change has a reason, not just a new look.
A better process, not a guarantee. Quality depends on the model, the references it actually inspects and the implementation. The Skill does not guarantee uniqueness or accessibility.
Mandatory MCP preflight. Discover the tools, make an authenticated read and inspect actual images. No working connection or useful visual evidence means no claimed Reinspro design result.
Version 2 adds focused, Impeccable-informed playbooks without replacing your accepted brand or exact brief. These are agent instructions, not newly installed tools or a bundled automatic detector.
Separate hierarchy, clarity and design judgment from measurable accessibility, responsive and performance findings. An audit-only request reports evidence rather than silently changing code.
Refine typography roles, reading order, alignment, spacing and action labels. Review generic gradients, redundant cards and decoration; your approved design still wins.
Check real empty, loading, error and translated states. Recompose mobile layouts rather than simply shrinking desktop. Measure bottlenecks before and after a performance fix.
Use motion for feedback or continuity, preserve reduced-motion and static fallbacks, then batch the final corrections. Do not turn focused work into endless cosmetic rebuilds.
Also included: shape, distill, bolder/quieter, color, delight, onboarding, reusable tokens and controlled variants. See all quality playbooks and source attribution. The ZIP includes the companion guides and license files.
03 / Reference first. Build second.
Define the audience, goal, content, stack and essential behavior. For a redesign, inspect the existing brand and page first.
Start with one focused query and four results. Shortlist three useful references across at least two brands, rather than collecting a huge gallery.
Inspect accessible previews or full captures. Compare hierarchy, typography, whitespace, density and CTA placement. Metadata alone is not visual analysis; a static image does not prove an interaction works.
Write a short comparison and choose one cohesive direction. Derive original tokens and layout decisions for your brand. Avoid a collage of unrelated components.
Use the existing stack and content. Include semantic markup, keyboard access, responsive states and reduced-motion support.
Check desktop, mobile and 320px layouts, functional states, overflow and contrast. Inspect rendered screenshots. Report the references and the decisions you adapted.
Reference links → pattern comparison → design direction → tokens → build → QA evidence
04 / Your workspace, your agent
Choose a client below. The Skill is a file, not an executable installer. The MCP is a Streamable HTTP service; no local Reinspro server is needed.
REINSPRO_MCP_KEY. Never put the actual key in a Skill, committed configuration, prompt or screenshot.https://reinspro.com/api/mcpCommands below use a POSIX shell. On Windows, download the ZIP and copy its reinspro folder into the client’s Skill directory instead. Review an existing Skill before replacing it, and merge server entries rather than overwriting your configuration.
From your project root, save the instructions to .claude/skills/reinspro/SKILL.md. Review the downloaded instructions before using them. For the companion setup and prompt guides, extract the ZIP’s reinspro folder into .claude/skills/; keep its references/ folder alongside the Skill.
mkdir -p .claude/skills/reinspro
curl -fL https://reinspro.com/skills/reinspro/SKILL.md \
-o .claude/skills/reinspro/SKILL.mdMake REINSPRO_MCP_KEY available in the environment that launches Claude Code. Merge this entry into the project’s .mcp.json; the variable below is a placeholder, not a key.
{
"mcpServers": {
"reinspro": {
"type": "http",
"url": "https://reinspro.com/api/mcp",
"headers": {
"Authorization": "Bearer ${REINSPRO_MCP_KEY}"
}
}
}
}Start a fresh Claude Code session from the project. Review any project MCP approval prompt. Run /mcp to inspect Reinspro, then invoke /reinspro with your task. Ask it to list the available Reinspro tools and run the discovery prompt below.
Use the Hermes skills installer. Review its security-scan results and the instructions. This installs into the active Hermes profile, not your project’s Claude or Codex folders.
hermes skills install https://reinspro.com/skills/reinspro/SKILL.md
hermes skills listStore REINSPRO_MCP_KEY privately in your active profile’s environment file; the default is ~/.hermes/.env. Merge the server into ~/.hermes/config.yaml, or the corresponding profile configuration.
mcp_servers:
reinspro:
url: "https://reinspro.com/api/mcp"
headers:
Authorization: "Bearer ${REINSPRO_MCP_KEY}"Start a fresh session so the environment and installed Skill are loaded. For an existing CLI session after an environment edit, use /reload, then /reload-mcp. Run the connection test, load the instructions with /skill reinspro, then try the discovery prompt below.
hermes mcp test reinsproFrom your project root, place the instructions at .agents/skills/reinspro/SKILL.md. This is the repository Skill directory, not .claude/skills. For the companion guides, extract the ZIP’s reinspro folder into .agents/skills/ with its references/ folder intact.
mkdir -p .agents/skills/reinspro
curl -fL https://reinspro.com/skills/reinspro/SKILL.md \
-o .agents/skills/reinspro/SKILL.mdMerge this block into ~/.codex/config.toml. Set REINSPRO_MCP_KEY in the environment that launches Codex. The bearer setting takes the variable’s name, not the secret itself.
[mcp_servers.reinspro]
url = "https://reinspro.com/api/mcp"
bearer_token_env_var = "REINSPRO_MCP_KEY"Restart the CLI or desktop app after changing its launch environment. Confirm the server is configured, then invoke $reinspro or select the Skill with /skills. Ask it to list its Reinspro tools and run the discovery prompt. A configured server alone is not proof of a successful search.
codex mcp listUse the Reinspro Skill. MCP is mandatory: stop design work if connection, authorization or useful image inspection fails. List the available Reinspro MCP tools, then use search_pages to find SaaS landing-page references with limit 4. Show the real results and their detail links. Inspect accessible images; if image inspection is unavailable or there is no exact match, say so instead of inventing a reference.Expect seven read-only tools. Names may be prefixed by your client. An empty result is honest connection evidence, not an inspected visual reference. If useful images remain unavailable after a broader relevant query, stop the design workflow and report the blocker.
Using Claude web, Claude Desktop or OpenClaw? Keep the existing MCP connection guide for those clients. Setup screens and discovery behavior can vary by client version and workspace policy.
05 / Give the agent a useful brief
Replace the bracketed context with your own. Each prompt asks for evidence, an original direction and a tested result.
Use the Reinspro Skill and MCP for a landing page for [product], aimed at [audience], with [primary conversion goal]. Inspect my existing brand and stack. Compare three accessible references from two or three brands, including actual images. Explain their hierarchy, typography and section rhythm. Propose one original direction for my content, then build it in my project. Do not copy logos, assets or an exact composition. Verify desktop, mobile, 320px, keyboard access and reduced motion; show the QA evidence.Use Reinspro to research [component] for [product and audience]. Search relevant sections, inspect accessible images and compare two or three brands. Separate visible patterns from unverified interaction assumptions. Adapt the best principles to our current tokens and stack, not a different brand's styling. Build default, focus, loading and error states where relevant. Test the behavior with keyboard and narrow mobile layouts.Use the Reinspro Skill to audit [existing page]. First inspect its actual desktop and mobile render, brand, content and important flows. Find a small reference set with MCP and inspect the images. Identify the specific hierarchy and spacing problems, then propose a cohesive improvement without replacing our identity. Preserve working functionality and content. Implement only the approved scope and compare before/after screenshots and behavior.Verify the mandatory Reinspro MCP gate and reuse our existing relevant reference set and design direction. Improve only [specific section or issue] to achieve [observable goal]. Explain the pattern behind the change; fetch a new reference only if the current set is insufficient. Preserve the rest of the page, content and tokens. Verify the affected interaction and desktop, 390px and 320px layouts. Report exactly what changed and what stayed intact.06 / What the connection actually does
Seven read-only tools. Search matches indexed titles, brands, tags and curated related terms—not semantic or vector similarity. Start with four results; the maximum is six per page.
search_capturessearch_screenssearch_pagessearch_sectionsget_captureget_itemget_capture_imageoffset_y to inspect farther down a tall capture; the first segment is not the whole page.Image content blocks provide visual evidence when the client and model support inspection. If they do not, the agent should disclose that limit.
Keep the durable detail_url in your brief. The link is stable; viewing the capture still depends on account access.
Open structuredContent.gallery_url in a browser. In-conversation gallery rendering depends on the host; a native panel is not guaranteed.
Search only returns catalog items that exist and are indexed. If the request is too specific, try a relevant brand, tag or broader page kind, and label nearby matches honestly. See the full MCP reference.
07 / Access, expectations and fixes
The instructions are free to download and read. Using the Reinspro design workflow requires its live MCP, a verified, enabled account and active paid access. The agent must discover tools, make a successful authenticated read and inspect relevant images before designing. If the gate fails, it stops and helps with setup. Installing the Skill does not grant catalog access.
Check the exact client-specific Skill path and launch the agent in the right project or Hermes profile. Ensure the key is available to the process that actually runs the client—not just an unrelated terminal. Restart after environment changes, check server approvals and tool settings, then run the client’s discovery check and one real search.
A desktop app launched from the system UI may not inherit a terminal export. For Hermes CLI environment edits, use /reload followed by /reload-mcp, or start fresh. A missing Skill and a failed MCP connection are separate problems.
Confirm that the private key is valid, your account is enabled, email is verified and the paid subscription is active. Keep the endpoint exact and use the Bearer header shown in the guide. Check that REINSPRO_MCP_KEY resolves in the client’s environment. Never debug by posting the actual key.
If a key is lost or exposed, revoke it and create a new one in MCP settings. Update your private environment, then reload or restart the client.
Gallery links and thumbnails last 15 minutes and are token-bound. Full-media links are signed for five minutes and check user entitlement. An already-issued full-media URL can remain usable until its expiry even after key revocation. Revocation is not an instant recall of an issued signed URL.
Repeat the search or image request for fresh links if you still have access. Do not publish temporary gallery or media URLs; keep the durable capture detail link instead.
It helps make research and design decisions explicit. It cannot guarantee originality, quality or accessibility. Ask the agent to compare multiple brands, inspect real images, explain its adaptations and test the implementation. References are evidence—not permission to reuse trademarks, third-party assets or private content.
No. Reinspro’s MCP tools read design references; they do not change billing, account details or grant entitlement. Your coding agent uses its own project tools to implement a design, subject to your approvals. This guide never asks for or stores a private key in the browser.
Gallery support varies by host and version. Open the returned gallery link in a browser when a native view is unavailable; use the image blocks and detail links as the fallback. If images cannot be inspected, the agent should say so, not claim a visual analysis.
Keep searches narrow, start with four results and request full images only for the shortlist. Save a compact comparison and direction note before implementation. Do not keep adding galleries to the same conversation.
Manage and revoke keys in your account. Keep keys, tokens and temporary signed links out of repositories, shared logs and screenshots. Never paste one into this public page.
Manage MCP accessA clearer reference. A better starting point.