io.github.layoza/layoza

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.

5 of 16 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

• inspect_projecton 7 other serversreads or searches

  “Read-only inspection of a local project directory to extract Site DNA, routes, CSS tokens, framework, and component inventory.”

  2 inputs

  • pathstring“Relative or approved project path (defaults to '.').”
  • screenshot_onlyboolean
• inspect_siteon 4 other serversreads or searches

  “Loads a live http(s) URL in headless Chromium (desktop/tablet/mobile) and returns its rendered Site DNA (palette, fonts, type scale, radii, CSS custom properties, framework and motion hints) plus mea…”

  2 inputs, 1 required

  • urlstringrequired“http(s) URL, e.g.”
  • pathstring“Optional local project path whose source DNA should be compared with the live render.”
• extract_site_dnacreates or changes datadescribed as changing data

  “Extracts Site DNA and writes DESIGN.md, BRAND.md, MOTION.md, SITE-DNA.json, COMPONENT-INVENTORY.json, and DESIGN-DECISIONS.md (requires write_approved=true).”

  2 inputs, 1 required

  • pathstring“Project-relative path (file or directory) inside the approved project root; defaults to '.'.”
  • write_approvedbooleanrequired“Must be true to write DNA files to disk.”
• get_design_systemon 6 other serversgenerates contentdescribed as changing data

  “Design system for a brief or a project.”

  7 inputs

  • actionstring“`recommend` (default when `query` is set) builds the system from the brief; `generate` (default otherwise) derives DESIGN.md from the project at `path`; `lint`…”
  • querystring“The design brief, e.g.”
  • modestring
  • variantinteger“0 (default) is the stable answer for this brief.”
  • pathstring“Project-relative path (file or directory) inside the approved project root; defaults to '.'.”
  • design_md_contentstring
  • after_design_md_contentstring
• recommend_layoutgenerates content

  “Recommends layout archetypes, typography, color palettes, and 3 distinct creative directions for Modes A/B/C/D.”

  5 inputs, 1 required

  • querystringrequired
  • modestring
  • design_varianceinteger
  • motion_intensityinteger
  • visual_densityinteger
• recommend_animationgenerates content

  “Recommends accessible GSAP, Motion, WAAPI, Three.js/R3F, or conditional Lenis animation recipes with reduced-motion and cleanup guarantees.”

  3 inputs

  • categorystring“Restrict recipes to one motion category; omit or `all` for every category.”
  • recipestring“Return exactly one recipe by id (e.g.”
  • motion_intensityinteger“Motion dial 0-10 (default 6); 0 means motion off and returns no recipes.”
• discover_components

  “Discovers existing project UI components and generates framework-native component patterns.”

  3 inputs

  • pathstring“Project-relative path (file or directory) inside the approved project root; defaults to '.'.”
  • frameworkstring
  • titlestring
• capture_screenshotsdescribed as changing data

  “Loads a local HTML file or http(s) URL in headless Chromium at 1440x900, 768x1024 and 375x812, waits for motion to settle, saves full-page, 1:1 mobile-hero and menu-open screenshots, and returns a co…”

  4 inputs, 1 required

  • target_url_or_filestringrequired“http(s) URL, or an HTML file / directory (uses its index.html) inside the project.”
  • write_approvedboolean“Local files only: true writes screenshots and the report into `<dir>/qa/` inside the project and returns the merged release-gate audit.”
  • sketchboolean“true returns only the screenshot paths per viewport plus error/warning counts (no findings, metrics, Site DNA or release-gate audit); the full report is still …”
  • detailstring“"summary" (default) returns the compact result and writes the full detail to `capture-full.json`; "full" returns the full verbose report inline (quality, every…”
• compare_before_afterreads or searches

  “Compares the current audit of `path` against the audit report saved when `safe_rollback` created `baseline_id`, separating intended changes from regressions (new error rules, WCAG or Core Web Vitals …”

  4 inputs, 1 required

  • pathstring“Project-relative path (file or directory) inside the approved project root; defaults to '.'.”
  • baseline_idstringrequired
  • pixel_diff_rationumber“Optional pixel diff ratio you measured yourself.”
  • intended_changesarray
• audit_accessibilityon 5 other serversreads or searches

  “Audits WCAG 2.2 AA accessibility compliance, reporting automated violations separately from manual review requirements.”

  1 input

  • pathstring“Project-relative path (file or directory) inside the approved project root; defaults to '.'.”
• audit_performanceon 2 other serversreads or searches

  “Evaluates Core Web Vitals targets (LCP <= 2.5s, INP <= 200ms, CLS <= 0.1).”

  5 inputs

  • pathstring“Project-relative path (file or directory) inside the approved project root; defaults to '.'.”
  • target_url_or_filestring“http(s) URL or project-relative HTML file to measure live.”
  • lab_lcp_msnumber
  • lab_inp_msnumber
  • lab_clsnumber
• verify_functionalruns code or commandsdescribed as changing data

  “Runs full release-gate verification and optional bounded auto-repair (requires write_approved=true when auto_repair=true).”

  3 inputs

  • pathstring“Project-relative path (file or directory) inside the approved project root; defaults to '.'.”
  • auto_repairboolean
  • write_approvedboolean

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.