# saglitzdesign-mcp - Doramagic AI Context Pack > Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated. ## Sufficiency Principle - **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary. - **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work. ## How the Host AI Should Use This You are reading the AI Context Pack that Doramagic compiled for saglitzdesign-mcp. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project. ## Claim Consumption Rules - **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure. - **Minimum status for a fact**: `supported` - `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path. - `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying. - `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact. - `unverified`: Must not be used as fact; state clearly that evidence is insufficient. - `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf. ## Who It Fits Best - **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `skills/apple-platform-design/SKILL.md`, `skills/clean-interface-design/SKILL.md`, `skills/design-review/SKILL.md`, `skills/landing-page-conversion/SKILL.md` et al. Claim: `clm_0004` supported 0.86 ## What It Can Do - **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `skills/apple-platform-design/SKILL.md`, `skills/clean-interface-design/SKILL.md`, `skills/design-review/SKILL.md`, `skills/landing-page-conversion/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ## How to Start - `npx saglitzdesign-mcp` Evidence: `README.md` Claim: `clm_0005` supported 0.86 - `git clone https://github.com/HalidSaglam/saglitzdesign-mcp.git` Evidence: `README.md` Claim: `clm_0006` supported 0.86 - `claude mcp add --scope user saglitzdesign -- npx -y saglitzdesign-mcp` Evidence: `README.md` Claim: `clm_0007` supported 0.86 - `claude mcp add --scope user saglitzdesign node /absolute/path/to/saglitzdesign-mcp/dist/index.js` Evidence: `README.md` Claim: `clm_0008` supported 0.86 - `npx skills@latest add HalidSaglam/saglitzdesign-mcp` Evidence: `README.md` Claim: `clm_0009` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Trial the research framework first - **Why**: This project targets research workflows; the core risk is source credibility and output quality. Verify the research framework with Prompt Preview first, then trial it in an isolated environment. ### 30-Second Read - **What to do now**: Trial the research framework first - **Minimum safe next step**: Verify the research framework with Prompt Preview first; trial in isolation only once satisfied - **Do not trust yet**: Research conclusions, citations, and experiment results cannot be trusted before install. - **Continuing will touch**: Research judgment, Command execution, Host AI configuration ### What You Can Trust Now - **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `skills/apple-platform-design/SKILL.md`, `skills/clean-interface-design/SKILL.md`, `skills/design-review/SKILL.md`, `skills/landing-page-conversion/SKILL.md` et al. Claim: `clm_0004` supported 0.86 - **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `skills/apple-platform-design/SKILL.md`, `skills/clean-interface-design/SKILL.md`, `skills/design-review/SKILL.md`, `skills/landing-page-conversion/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0002` supported 0.86 - **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0005` supported 0.86 ### What You Cannot Trust Yet - **Research conclusions, citations, and experiment results cannot be trusted before install.** (unverified): A research Skill can organize questions and paths, but it cannot replace real literature search, paper verification, and experiment reproduction. - **Whether it fits your specific research field cannot be trusted directly.** (unverified): The Skill covering many research topics does not mean it is sufficient for your field, source requirements, and credibility standards. - **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project. - **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment. - **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `skills/apple-platform-design/SKILL.md`, `skills/clean-interface-design/SKILL.md`, `skills/design-review/SKILL.md`, `skills/landing-page-conversion/SKILL.md` et al. - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. ### What Continuing Will Touch - **Research judgment**: Problem decomposition, source paths, experiment paths, conclusion structure, and credibility judgment. Why: A research Skill can make output look more professional but cannot replace real evidence verification. - **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md` - **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `skills/apple-platform-design/SKILL.md`, `skills/clean-interface-design/SKILL.md`, `skills/design-review/SKILL.md`, `skills/landing-page-conversion/SKILL.md` et al. - **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md` - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Verify whether it can correctly frame the research question and evidence boundaries first; do not trust the research output up front. (applies when: Applies to any project, especially when output quality is unknown.) - **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.) - **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state. - **Keep a source and conclusion verification checklist**: If citations or experiment paths later prove unreliable, you can return to the evidence-boundary stage and re-check. - **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually. - **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck. ## What Can Only Be Previewed - Explain who the project fits and what it can do - Demonstrate a typical conversation flow based on project docs - Help the user decide whether it is worth installing or researching further ## What Must Be Verified After Install - Actually installing the Skill, plugin, or CLI - Running scripts, modifying local files, or accessing external services - Verifying real output quality, performance, and compatibility ## Boundary & Risk Decision Card - **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0010` inferred 0.45 - **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0011` supported 0.86 - **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment. - **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments. ## Pre-Work Working Context ### Loading Order - First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset. - Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative. - Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match. - When you need to carry out a concrete task, check role_skill_index first, then evidence_index. - For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required. ### Task Routes - **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `skills/apple-platform-design/SKILL.md`, `skills/clean-interface-design/SKILL.md`, `skills/design-review/SKILL.md`, `skills/landing-page-conversion/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0002` supported 0.86 ### Context Scale - Total files: 141 - Important-file coverage: 40/141 - Evidence index entries: 80 - Role / Skill entries: 5 ### Handling Insufficient Evidence - **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts. - **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install. - **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run. - **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version. ## Prompt Recipes ### Fit assessment - Goal: Judge whether this project fits the user's current task. - Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation. ```text Based on the AI Context Pack for saglitzdesign-mcp, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id. ``` ### Pre-install experience - Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise. - Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language. ```text Treat saglitzdesign-mcp as a pre-install experience asset, not an already-installed tool or a real runtime environment. Output exactly four parts: 1. Ask me 3 necessary questions first. 2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow. 3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run. 4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project. Hard boundaries: - Do not claim you have installed, run, executed tests, modified files, or produced real results. - Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing". - If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...". - The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating". - Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment. - Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions. ``` ### Role / Skill selection - Goal: Pick the best-matching asset from the project's roles or Skills. - Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed. ```text Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs. ``` ### Risk pre-check - Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting. - Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items. ```text Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have. ``` ### Host AI kickoff instruction - Goal: Turn the project context into a host AI instruction for the start of a conversation. - Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI. ```text Based on the AI Context Pack for saglitzdesign-mcp, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results. ``` ## Role / Skill Index - Indexed 5 role / Skill / project-doc entries. - **apple-platform-design** (skill): Design iOS, iPadOS, and macOS apps that feel native, in the Liquid Glass era. Use when building or reviewing Apple-platform UI — navigation, controls, sheets, materials, typography, haptics — or deciding what must change when porting from web/Android. Covers Apple's HIG, the Liquid Glass design language iOS 26 / macOS Tahoe , fluid-interface principles, and "Mac-assed" native conventions. Activation hint: When the user's task is highly relevant to the workflow described by “apple-platform-design”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/apple-platform-design/SKILL.md` - **clean-interface-design** (skill): Design clean, calm, uncluttered interfaces that don't read as templated AI output. Use when building or restyling any UI web, iOS, Android, macOS and it needs visual hierarchy, restraint, spacing discipline, one clear primary action, and a cohesive look. Covers accent color, whitespace, corner radius, type scale, fonts, icons, borders-vs-shadows, and the "remove until it breaks" pass. Activation hint: When the user's task is highly relevant to the workflow described by “clean-interface-design”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/clean-interface-design/SKILL.md` - **design-review** (skill): Critique a UI screenshot, live page, or code like a rigorous senior designer — grounded, reproducible, element-citing, and ranked by severity. Use when someone asks "review this design", "what's wrong with this screen", or wants feedback on a mockup/site/app. Avoids the failure modes of typical AI critique hallucinated issues, padded lists, critiquing the description instead of the pixels . Activation hint: When the user's task is highly relevant to the workflow described by “design-review”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/design-review/SKILL.md` - **landing-page-conversion** (skill): Build or improve landing pages and marketing sites that convert, not just look good. Use when writing a hero, structuring a page, choosing a CTA, adding social proof, or diagnosing why a page isn't converting. Covers positioning, copy-first workflow, the above-the-fold contract, page narrative, CTAs, trust, and pricing — grounded in StoryBrand, Cialdini, and conversion research. Activation hint: When the user's task is highly relevant to the workflow described by “landing-page-conversion”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/landing-page-conversion/SKILL.md` - **motion-and-animation** (skill): Add motion and animation that feels great, not like slop. Use when animating any UI — transitions, hovers, presses, sheets, drawers, modals, page transitions, gestures — or when an animation feels "off". Covers the easing rules agents get wrong ease-out for enter, ease-in for exit , springs, interruptibility, durations, component craft never scale 0 , origin-aware , and reduced motion. Grounded in Apple's fluid-inte… Activation hint: When the user's task is highly relevant to the workflow described by “motion-and-animation”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/motion-and-animation/SKILL.md` ## Evidence Index - Indexed 80 evidence entries. - **SaglitzDesign MCP** (documentation): An expert design & marketing brain for your AI coding agent. Evidence: `README.md` - **SaglitzDesign Skills** (documentation): Self-contained design skills you can install into any skills-compatible agent Claude Code, Cursor, and others with the skills https://skills.sh CLI: Evidence: `skills/README.md` - **Package** (package_manifest): { "name": "saglitzdesign-mcp", "version": "0.11.0", "mcpName": "io.github.HalidSaglam/saglitzdesign-mcp", "description": "SaglitzDesign — expert MCP server for mobile app & website design: UI, UX, buttons, design languages, SEO and GEO guidance backed by a curated knowledge base and real-world pattern research.", "type": "module", "bin": { "saglitzdesign-mcp": "dist/index.js" }, "main": "dist/index.js", "files": "dist", "knowledge", "recipes", "!knowledge/examples/images", "scripts/regenerate-examples.md", "LICENSE", "README.md", "NOTICE.md" , "engines": { "node": " =18" }, "scripts": { "build": "tsc && chmod +x dist/index.js", "dev": "tsx src/index.ts", "start": "node dist/index.js", "insp… Evidence: `package.json` - **Apple Platform Design** (skill_instruction): Apple apps feel native because they respect platform conventions, use system materials and motion, and get the small physical details right. Copying a web or Android design onto iOS/macOS reads as foreign instantly. Evidence: `skills/apple-platform-design/SKILL.md` - **Clean Interface Design** (skill_instruction): Most "AI-looking" UI fails the same way: too many colors, too many type sizes, inconsistent radii, no clear primary action, and no breathing room. Fix those and almost anything looks intentional. Evidence: `skills/clean-interface-design/SKILL.md` - **Design Review** (skill_instruction): Most AI design feedback guesses: it flags issues inconsistently, pads the list to look thorough, and critiques a text description instead of the actual pixels. Do the opposite — a fixed rubric applied to what you actually see. Evidence: `skills/design-review/SKILL.md` - **Landing Page Conversion** (skill_instruction): A beautiful page with unclear positioning converts worse than a plain page with sharp positioning. Fix upstream first: positioning → copy → structure → design → speed. Evidence: `skills/landing-page-conversion/SKILL.md` - **Motion & Animation** (skill_instruction): Motion exists to explain where did this come from? , confirm did that work? , and occasionally delight. If an animation does none of those, delete it. The details compound — wrong easing or a scale 0 pop is the difference between "premium" and "cheap." Evidence: `skills/motion-and-animation/SKILL.md` - **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE` - **Notice on bundled content** (documentation): The software is licensed under the MIT License LICENSE . Evidence: `NOTICE.md` - **Buttons — Complete Design Guide** (documentation): Buttons are the single highest-leverage component in any interface. Get hierarchy, sizing, states, and labels right and most flows fix themselves. Evidence: `knowledge/components/buttons.md` - **Design Critique & Scoring — How Experts Judge Quality** (documentation): Design Critique & Scoring — How Experts Judge Quality Evidence: `knowledge/craft/design-critique-scoring.md` - **Apple Human Interface Guidelines & Liquid Glass iOS 26** (documentation): Apple Human Interface Guidelines & Liquid Glass iOS 26 Evidence: `knowledge/design-languages/apple-hig-liquid-glass.md` - **Material 3 & Material 3 Expressive** (documentation): Material 3 M3 is Google's design system for Android, Wear OS, and the web. Material 3 Expressive announced May 2025, rolled out through 2025–2026 with Android 16 and Wear OS 6 is its current evolution: springier motion, bolder shapes and color, and a set of new components. Google backed it with 46 research studies and 18,000+ participants; expressive designs tested as both preferred and more usable across age groups. As of 2026, M3 Expressive is the default look-and-feel target for new Android apps. Evidence: `knowledge/design-languages/material-3.md` - **Empty States & Bottom Primary Actions iOS** (documentation): Empty States & Bottom Primary Actions iOS Evidence: `knowledge/patterns/mobile/empty-states-buttons.md` - **Product Design Roadmap — From Idea to Shipped Interface** (documentation): Product Design Roadmap — From Idea to Shipped Interface Evidence: `knowledge/process/product-design-roadmap.md` - **UX Principles & Heuristics** (documentation): The evaluation backbone. Every design review should walk these. Evidence: `knowledge/ux/principles-heuristics.md` - **Tsconfig** (structured_config): { "compilerOptions": { "target": "ES2022", "module": "Node16", "moduleResolution": "Node16", "outDir": "dist", "rootDir": "src", "strict": true, "esModuleInterop": true, "skipLibCheck": true, "forceConsistentCasingInFileNames": true, "declaration": false, "sourceMap": false, "resolveJsonModule": true }, "include": "src/ / " } Evidence: `tsconfig.json` - **.gitignore** (source_file): node modules/ dist/ .log .DS Store knowledge/examples/images/ Evidence: `.gitignore` - **A11Y** (source_file): import { normalizeHex } from "./tokens.js"; ⋮---- function channelLuminance c: number : number ⋮---- function relativeLuminance hex: string : number ⋮---- export function contrastRatio fg: string, bg: string : number ⋮---- export interface ContrastPair { foreground: string; background: string; label?: string; large text?: boolean; ui component?: boolean; } ⋮---- export interface TapTarget { label?: string; width: number; height: number; platform?: "ios" "android" "web"; } ⋮---- export interface CheckResult { label: string; detail: string; required: string; actual: string; pass: boolean; fix?: string; } ⋮---- export function checkContrast pairs: ContrastPair : CheckResult ⋮---- export functi… Evidence: `src/a11y.ts` - **Examples** (source_file): import { readdirSync, readFileSync, existsSync } from "node:fs"; import { join, extname } from "node:path"; ⋮---- export interface DesignExample { id: string; title: string; platform: string; app: string; pattern: string; description: string; tags: string ; mobbin url: string; image: string; } ⋮---- export function loadExamples examplesDir: string : DesignExample ⋮---- // skip malformed files ⋮---- export function searchExamples examples: DesignExample , query: string, opts: { platform?: string; limit?: number } = {}, : DesignExample ⋮---- export function imageMime path: string : string Evidence: `src/examples.ts` - **Index** (source_file): import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"; import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"; import { z } from "zod"; import { fileURLToPath } from "node:url"; import { dirname, join } from "node:path"; import { existsSync, readFileSync } from "node:fs"; import { loadKnowledge, searchKnowledge, sections, type KnowledgeDoc } from "./knowledge.js"; import { loadExamples, searchExamples, imageMime } from "./examples.js"; import { registerPrompts } from "./prompts.js"; import { generateTokens, validateColors, DEFAULT SPACING, DEFAULT RADII, DEFAULT FONT SIZES, DEFAULT FONT FAMILIES, type TokenSpec, type TokenFormat, } from "./tokens.js";… Evidence: `src/index.ts` - **Knowledge** (source_file): import { readdirSync, readFileSync, statSync } from "node:fs"; import { join, extname } from "node:path"; ⋮---- export interface KnowledgeDoc { id: string; title: string; category: string; platform: string; tags: string ; sources: string ; updated: string; body: string; path: string; } ⋮---- function parseFrontmatter raw: string : ⋮---- function walk dir: string, out: string = : string ⋮---- export function loadKnowledge rootDir: string : KnowledgeDoc ⋮---- function tokenize text: string : string ⋮---- export interface SearchResult { doc: KnowledgeDoc; score: number; excerpt: string; } ⋮---- export function sections doc: KnowledgeDoc : Array< ⋮---- export function searchKnowledge docs: Know… Evidence: `src/knowledge.ts` - **Prompts** (source_file): interface PromptDef { name: string; title: string; description: string; build: brief: string = string; } ⋮---- export function registerPrompts server: { registerPrompt: name: string, config: { title: string; description: string; argsSchema: Record }, cb: args: { brief?: string } = { messages: Array }, Evidence: `src/prompts.ts` - **Tokens** (source_file): export interface TokenSpec { name: string; colors: Record ; spacing: number ; radii: Record ; fontSizes: Record ; fontFamilies: Record ; } ⋮---- export type TokenFormat = "css" "tailwind" "swiftui" "compose" "dtcg" "all"; ⋮---- export function normalizeHex hex: string : string null ⋮---- function hexParts hex: string : ⋮---- function kebab s: string : string function pascal s: string : string function camel s: string : string ⋮---- function toCss s: TokenSpec : string ⋮---- function toTailwind s: TokenSpec : string ⋮---- function toSwiftUI s: TokenSpec : string ⋮---- function toCompose s: TokenSpec : string ⋮---- function toDtcg s: TokenSpec : string ⋮---- export function generateTokens spe… Evidence: `src/tokens.ts` - **Regenerating the visual example library** (documentation): Regenerating the visual example library Evidence: `scripts/regenerate-examples.md` - **Refresh Knowledge** (documentation): Refresh the SaglitzDesign knowledge base. Follow this procedure: Evidence: `.claude/commands/refresh-knowledge.md` - **The Design of Everyday Things — Applied to Screens** (documentation): The Design of Everyday Things — Applied to Screens Evidence: `knowledge/books/design-of-everyday-things.md` - **Don't Make Me Think — Applied Web Usability** (documentation): Don't Make Me Think — Applied Web Usability Evidence: `knowledge/books/dont-make-me-think.md` - **Emotional Design — Making Products Feel Human** (documentation): Emotional Design — Making Products Feel Human Evidence: `knowledge/books/emotional-design.md` - **Grid Systems & Typography Classics — Applied to Screens** (documentation): Grid Systems & Typography Classics — Applied to Screens Evidence: `knowledge/books/grid-typography-classics.md` - **Hooked & Habit Design — Retention Mechanics for Apps** (documentation): Hooked & Habit Design — Retention Mechanics for Apps Evidence: `knowledge/books/hooked-retention.md` - **Influence & Persuasion — Cialdini Applied to Web & App Design** (documentation): Influence & Persuasion — Cialdini Applied to Web & App Design Evidence: `knowledge/books/influence-persuasion.md` - **Interaction Design Classics** (documentation): Two books define the discipline of interaction design as distinct from visual design: Alan Cooper's About Face and Jenifer Tidwell's Designing Interfaces . Cooper tells you how to decide what a product should do and how it should behave; Tidwell gives you a named catalog of solutions to recurring interaction problems. This document distills both into concrete rules an AI design assistant applies to current web and mobile UI. A third, Stephen Anderson's Seductive Interaction Design , contributes a few motivation rules at the end. Evidence: `knowledge/books/interaction-design-classics.md` - **Positioning & Messaging — From Strategy to Homepage** (documentation): Positioning & Messaging — From Strategy to Homepage Evidence: `knowledge/books/positioning-messaging.md` - **Design Psychology — The ~25 Most Actionable Findings** (documentation): Design Psychology — The ~25 Most Actionable Findings Evidence: `knowledge/books/psychology-of-design.md` - **Refactoring UI — Tactical Visual Design Tricks** (documentation): Refactoring UI — Tactical Visual Design Tricks Evidence: `knowledge/books/refactoring-ui.md` - **Website Copywriting Playbook — StoryBrand + SUCCESs + Ogilvy** (documentation): Website Copywriting Playbook — StoryBrand + SUCCESs + Ogilvy Evidence: `knowledge/books/storybrand-copywriting.md` - **Cards, Lists, Modals & Sheets** (documentation): - A card = one self-contained object with one primary destination. If the whole card is tappable, make the whole card the link stretched link and don't nest competing tap targets except explicit secondary actions ⋯ menu, like . - Internal padding 16–24px; consistent radius 12–16px modern default ; either a subtle border or a soft shadow — pick one system-wide borders read better in dark mode; shadows on light . - Card grids: equal heights per row; clamp titles/descriptions 2–3 lines instead of letting content dictate ragged heights. - Don't card everything: cards separate heterogeneous objects. Homogeneous, scannable data belongs in lists or tables — card-grids of identical rows waste 40%+… Evidence: `knowledge/components/cards-lists-modals.md` - **Forms & Inputs — Design Guide** (documentation): Forms are where products lose users. Every field must earn its place. Evidence: `knowledge/components/forms-inputs.md` - **Navigation Patterns — Mobile & Web** (documentation): Navigation is the user's mental model of your product. If they can't predict where things live, nothing else matters. Evidence: `knowledge/components/navigation.md` - **Animation Craft — Motion That Separates Great Interfaces from Slop** (documentation): Animation Craft — Motion That Separates Great Interfaces from Slop Evidence: `knowledge/craft/animation-craft.md` - **Clean App Design** (documentation): Clean design is not "add less stuff." It is a set of disciplined constraints that make an interface feel calm, confident, and easy to act in. The rules below are the working cheat-sheet. Apply them as defaults; break them only with a reason. Evidence: `knowledge/craft/clean-app-design.md` - **Design Engineering — Clean Code for UI, Done Right** (documentation): Design Engineering — Clean Code for UI, Done Right Evidence: `knowledge/craft/design-engineering.md` - **Ethical Design — Avoiding Dark Patterns, Converting Honestly** (documentation): Ethical Design — Avoiding Dark Patterns, Converting Honestly Evidence: `knowledge/craft/ethical-design.md` - **Iconography — Choosing and Using an Icon System** (documentation): Iconography — Choosing and Using an Icon System Evidence: `knowledge/craft/iconography.md` - **Typography Craft — Typesetting Beyond the Basics** (documentation): Typography Craft — Typesetting Beyond the Basics Evidence: `knowledge/craft/typography-craft.md` - **UX Writing — Interface Copy That Reduces Cognitive Load** (documentation): UX Writing — Interface Copy That Reduces Cognitive Load Evidence: `knowledge/craft/ux-writing.md` - **Visual Craft Standards — Expert-Level Polish** (documentation): Visual Craft Standards — Expert-Level Polish Evidence: `knowledge/craft/visual-craft-standards.md` - **Android App Design — Complete Guide Android 16 / Material 3 Expressive era** (documentation): Android App Design — Complete Guide Android 16 / Material 3 Expressive era Evidence: `knowledge/design-languages/android-app-design.md` - **Cross-Platform Design Tokens & Theming — Best Practices** (documentation): Cross-Platform Design Tokens & Theming — Best Practices Evidence: `knowledge/design-languages/design-tokens-theming.md` - **Microsoft Fluent 2 — Essentials** (documentation): Fluent 2 is Microsoft's current cross-platform design system web/React, Windows/WinUI, iOS, Android, macOS , powering Microsoft 365, Teams, and Windows 11. It is the most token-driven of the big-three design languages and the strongest reference for enterprise/productivity UI. Internally ~293 Microsoft design teams use it, with component usage ~4× Fluent 1. Evidence: `knowledge/design-languages/fluent-2.md` - **iOS App Design — Complete Guide iOS 26 era** (documentation): iOS App Design — Complete Guide iOS 26 era Evidence: `knowledge/design-languages/ios-app-design.md` - **macOS App Design — Complete Guide macOS Tahoe 26 era** (documentation): macOS App Design — Complete Guide macOS Tahoe 26 era Evidence: `knowledge/design-languages/macos-app-design.md` - **Web Design Trends 2025–2026 — What Works, What Doesn't** (documentation): Web Design Trends 2025–2026 — What Works, What Doesn't Evidence: `knowledge/design-languages/web-trends-2026.md` - **WWDC Design Principles** (documentation): Apple's WWDC design talks are the most rigorous public treatment of interaction craft that exists. This doc distills the principles into concrete rules you can apply on Apple platforms iOS, iPadOS, macOS and, wherever the physics or the reasoning transfers, on the web . Serve these as design law: when a motion, layout, or feedback decision is ambiguous, resolve it against the rule here. Evidence: `knowledge/design-languages/wwdc-design-principles.md` - **GEO Fundamentals — Generative Engine Optimization state of 2026** (documentation): GEO Fundamentals — Generative Engine Optimization state of 2026 Evidence: `knowledge/geo/geo-fundamentals.md` - **GEO Tactics Checklist — Get Cited by AI Engines 2026** (documentation): GEO Tactics Checklist — Get Cited by AI Engines 2026 Evidence: `knowledge/geo/geo-tactics-checklist.md` - **Ad Creative — Hooks, Formats, Specs & Testing** (documentation): Ad Creative — Hooks, Formats, Specs & Testing Evidence: `knowledge/marketing/ad-creative.md` - **Analytics & Experimentation — North Star, Activation, Retention & A/B Testing** (documentation): Analytics & Experimentation — North Star, Activation, Retention & A/B Testing Evidence: `knowledge/marketing/analytics-experimentation.md` - The remaining 20 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`. ## Rules the Host AI Must Follow - **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `skills/README.md`, `package.json` - **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `skills/README.md`, `package.json` ## Questions the User Should Answer First - Which host AI or local environment do you plan to use it in? - Do you just want to experience the workflow first, or are you ready to actually install? - What matters most to you: install cost, output quality, or conflicts with your existing rules? ## Acceptance Checks - Every capability claim can be traced back to a file path in evidence_refs. - AI_CONTEXT_PACK.md does not package previews as a real run. - The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes. --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Project Overview**: importance `high` - source_paths: README.md, package.json, LICENSE, NOTICE.md - **Server Architecture & Tool Surface**: importance `high` - source_paths: src/index.ts, src/knowledge.ts, src/tokens.ts, src/a11y.ts, src/examples.ts - **Knowledge Base Structure & Extensibility**: importance `high` - source_paths: knowledge/design-languages/material-3.md, knowledge/design-languages/apple-hig-liquid-glass.md, knowledge/components/buttons.md, knowledge/ux/principles-heuristics.md, knowledge/craft/design-critique-scoring.md - **Workflows, Installation & Operations**: importance `medium` - source_paths: src/prompts.ts, package.json, README.md, .gitignore ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `0977d6d2deb9d04b7ef67e5c84d13c6ec6912960` - inspected_files: `README.md`, `package.json`, `src/a11y.ts`, `src/color.ts`, `src/examples.ts`, `src/fonts.ts`, `src/icons.ts`, `src/index.ts`, `src/knowledge.ts`, `src/prompts.ts`, `src/recipes.ts`, `src/tokens.ts` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/HalidSaglam/saglitzdesign-mcp - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: downstream_validation.risk_items | https://github.com/HalidSaglam/saglitzdesign-mcp - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: risks.scoring_risks | https://github.com/HalidSaglam/saglitzdesign-mcp - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/HalidSaglam/saglitzdesign-mcp - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Maintenance risk requires verification - Trigger: release_recency=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/HalidSaglam/saglitzdesign-mcp - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.