Pro-Sanity: Your Go-To Repository for All Things Sanity

Created By
Shubx23a year ago
Total Sanity Project-perfect repository for defining utilities, fields, component schemas, documents in sanity. Here everything you need for sanity configuration, project building.
Overview

What is Pro-Sanity?

Pro-Sanity is a comprehensive repository designed for defining utilities, fields, component schemas, and documents in Sanity, an intelligent content platform. It aims to streamline the configuration and building of Sanity projects.

How to use Pro-Sanity?

To use Pro-Sanity, download the necessary files from the releases page and execute them to enhance your Sanity experience.

Key features of Pro-Sanity?

  • Simplified Sanity configurations
  • Comprehensive utility functions
  • Well-defined component schemas
  • Extensive documentation resources

Use cases of Pro-Sanity?

  1. Configuring Sanity projects efficiently.
  2. Building robust applications with predefined schemas.
  3. Enhancing collaboration among developers working on Sanity projects.

FAQ from Pro-Sanity?

  • Is Pro-Sanity suitable for beginners?

Yes! Pro-Sanity is designed to assist both newcomers and experienced users in configuring Sanity projects.

  • How can I contribute to Pro-Sanity?

Contributions are welcome! You can submit pull requests or open issues to help improve the project.

  • Where can I find the latest releases?

You can find the latest releases on the releases page.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Shubx23
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago