Bottle Shop End of Trade Web Application

Created By
Diadems666a year ago
Cursor AI SSOT & Rule Engine Template: A comprehensive framework for integrating Cursor AI's advanced features into any project. Includes Single Source of Truth (SSOT) tracking, custom project rules, and Model Context Protocol (MCP) with Knowledge Graph for intelligent context management.
Overview

What is the SSOT-RULE-ENGINE-TEMPLATE?

The SSOT-RULE-ENGINE-TEMPLATE is a comprehensive framework designed to integrate Cursor AI's advanced features into any project, focusing on Single Source of Truth (SSOT) tracking, custom project rules, and Model Context Protocol (MCP) with a Knowledge Graph for intelligent context management.

How to use the SSOT-RULE-ENGINE-TEMPLATE?

To use the template, copy the .cursor directory into your project, configure the mcp.json file, and follow the initialization steps for either a new or existing project. Commands can be executed in the Cursor chat to set up and manage the system.

Key features of the SSOT-RULE-ENGINE-TEMPLATE?

  • Centralized AI logic and workflow instructions.
  • Dual initialization for new and existing projects.
  • Integration with MCP servers for Knowledge Graph management.
  • Structured SSOT file management for project state tracking.
  • Staged project rules for manual review and integration.
  • GitHub ready with version control considerations.

Use cases of the SSOT-RULE-ENGINE-TEMPLATE?

  1. Streamlining project management with centralized AI logic.
  2. Automating documentation updates based on project state.
  3. Building and managing a Knowledge Graph for enhanced context understanding.

FAQ from the SSOT-RULE-ENGINE-TEMPLATE?

  • What is SSOT?
    SSOT stands for Single Source of Truth, which ensures that everyone in the project is working with the same data and information.

  • Can I use this template for any project?
    Yes! The template is designed to be flexible and can be integrated into various types of projects.

  • Is there support for additional MCP servers?
    Yes, the template includes commands for installing and configuring standard MCP servers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Diadems666
Star
0
Language
Python
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