sanstudio Design Chain

    1

    A design pipeline for your agent that researches before it designs, offers three real directions, reviews its own mockup with fresh eyes, and waits for your approval at every gate.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    sanstudio Design Chain

    Example session with this skill installed

    lane: standard
    Our budgeting app's transaction list feels cluttered. Users say they can't find last week's coffee. Screenshot attached. Keep the tab bar. iOS first.

    • Read your context and instructions
    • Compiled the sanstudio design chain

    Illustrative session, abridged. The chain stops after every gate; each block below is one stop, and the user's reply is shown in italics.

    DESIGN CHAIN READY
      contract: none   product: none   taste: user taste file
      lane: standard (redesign of one screen, approach open)
    

    G0 Research

    IdFindingConfidence
    C1Users report trouble finding one past paymentproblem: supported (2 quotes); cause: plausible
    C2The list is flat reverse-chronological with no groupingobserved in screenshot
    GapAre people searching for one payment or scanning a week?decides the direction

    G0 done. Reply APPROVE, ITERATE, BACK or STOP. APPROVE

    G1 Context lock

    • Visitor mode: Operate. Invention scope: surface (existing app look kept).
    • Category default to refuse: a flat dated list with category color chips.
    • Tokens extracted from the screenshot into the design contract: real hex values, SF Pro, 16px gutters.
    • One question: is search already in the app? "No, add it if it helps." APPROVE

    G2 Three directions

    DirectionAnswersDiffers on
    ADay headers with a fact row per day (count, total)C1information architecture
    BGrouped by merchant, last visit on topC1, gapinformation architecture
    CSearch-first, list as resultsgapinteraction

    Recommended: A. The familiar version is offered as a quiet option. "B, with A's day headers." The direction contract (idea, look, journey, first screen, signature move, done when) is written to the brief.

    G3 Hi-fi and review

    • A hi-fi HTML mockup in a phone frame, real merchants and amounts, no dots in chips, no bordered cards.
    • Anti-slop pass: clean. Captures taken at 390 x 844.
    • Independent review: heuristics 29/40; persona walk as a one-thumb commuter and a screen-reader user;

    one P1: no empty state for a merchant with no visits this month. Fixed before the user saw the screen. Disposition: ship.

    • Figma export JSON written to the session folder.

    ITERATE quieter tones down the merchant category colors without touching layout, then the review re-runs on the changed area.

    Next steps: APPROVE to finish, or take it to G4 for a production package (all states, components, handoff).

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A design pipeline for your agent that researches before it designs, offers three real directions, reviews its own mockup with fresh eyes, and waits for your approval at every gate.

    What it does. Six skills that turn a design request into artifacts you can keep: a research report, a session DESIGN.md with tokens and rules, three directions that differ in structure (not color), a hi-fi HTML mockup with real content, a review with heuristic scores and P0 to P3 issues, Figma JSON, and on the major lane a production package with states, components and a readiness scorecard.

    How it works. design-chain picks a lane (fast, standard, major), a visitor mode (Persuade, Operate, Read, Experience) and an invention scope, then runs the gates in order. Research always comes first. Directions refuse the category's default page. Gate 3 is checked against 50+ craft rules (no dots in chips, no gradient text, generous spacing, chosen fonts) and then reviewed from rendered captures by a context that did not build it. After every gate you reply APPROVE, ITERATE, BACK or STOP; refine verbs such as bolder, quieter and distill give scoped passes.

    GateSkillOutput
    entrydesign-chainlane, mode, gate control
    G0research-synthesisresearch report with findings and gaps
    G1context-locksession DESIGN.md (tokens and rules)
    G2direction-lockthree directions and a direction contract
    G3design-lockhi-fi HTML, captures, review, Figma JSON
    G4production-lockstates, components, handoff, readiness scorecard

    Where it stops. It designs; it does not write your product code or merge anything. Mockups are proposals, not shipped UI. It uses the tools your agent already has (search, browser, Figma MCP) and records any missing tool as an evidence gap instead of faking it. Your brand stays yours: a TASTE.md, PRODUCT.md or .sanstudio/ contract in your project overrides its defaults.

    Credits. Original pipeline and rules, with a few ideas adapted in new wording from impeccable (Apache 2.0), design.md (Apache 2.0), hallmark (MIT) and taste-skill (MIT). Full credits and licence texts ship in NOTICE.md and licenses/.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Branding & Design.

    Designs, does not code: mockups are HTML proposals, never your product code, and it never edits your repository. It stops at every gate and waits for your reply, so it is not a one-shot generator. Output quality depends on the tools your agent has; a missing tool (image search, browser, subagents) is recorded as an evidence gap rather than faked. Gate 4 produces a buildable design spec with an honest readiness scorecard, not shippable code.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    • Free with an Agensi account

    Nothing to install. It runs in your AI agent.

    Optional
    Web searchImage searchBrowser toolSubagentsFigma MCP

    The browser tool renders captures for the review, subagents give an independent review and Figma MCP exports directly.

    Permissions

    Network Access
    Read Files
    Write Files
    Browser

    Read and write files: the chain reads your TASTE.md, PRODUCT.md and .sanstudio/ folder, and writes its artifacts (research report, DESIGN.md, HTML mockups, review, Figma JSON) to ./sanstudio-output/ in your project. Network: only through your agent's own web and image search during research and image sourcing; the pack ships no scripts and makes no network calls itself. Browser: renders the mockup to capture screenshots for the review. It never writes your product code.

    Listed19 days ago

    What's inside

    Frequently Asked Questions

    Agents jump straight to a pretty screen that looks like every other AI screen and ignores why the change was asked for. The chain researches the reason first, locks your visual contract, offers three directions that differ in structure, and has a separate context review the result before you see it. You decide at every step.

    Any agent that loads SKILL.md folders; it is built for Claude Code. It needs no MCP server. It works best when the agent has web search, image search, a browser tool and subagents. A Figma MCP is optional and only used to push the mockup into Figma.

    Yes. Put a TASTE.md in your project for colors, type and rules, a PRODUCT.md for durable product facts, or a whole design system in a .sanstudio/ folder (DESIGN.md, QA gates, accepted decisions). Contract values are used exactly; the chain only adds overrides for the current request, and raises any clash with its craft rules for you to decide.

    Six skills (design-chain, research-synthesis, context-lock, direction-lock, design-lock, production-lock) with their reference files: the DESIGN.md format, 50+ numbered craft rules, the review protocol, refine verbs, mobile app patterns, a Figma export schema, and TASTE and PRODUCT templates. Text only; no scripts.

    If your agent has a Figma MCP connected, Gate 3 pushes the mockup into Figma directly. Without one, it writes figma/design-export.json in the session folder. Gate 1 can also read a Figma link you give it as a reference. No Figma credentials are stored in the pack.

    New in Branding & Design

    Free