No Clocks Vault

AGENTS

3 min read

Vault Agentic AI Setup

Overview

This note documents the AI tooling and configuration for the No Clocks Knowledge Vault. The vault leverages multiple AI assistants and tools to enhance note-taking, content generation, and knowledge management.

Cursor IDE Configuration

The .cursor/ folder contains all Cursor-specific configuration:

Directory Structure

.cursor/
├── commands/          # workflow automation commands
├── mcp.json          # MCP server configuration
├── plans/            # planning documents
├── prompts/          # reusable AI prompts
├── rules/            # context rules for AI
└── settings.json     # Cursor settings

Rules

Rules provide context to Cursor about vault conventions:

Rule FilePurpose
obsidian-vault.mdcCore vault structure, frontmatter, linking conventions
quartz-publishing.mdcQuartz publishing workflow and configuration
templater-syntax.mdcTemplater plugin syntax reference

Prompts

Reusable prompts for common operations:

PromptPurpose
create-definition.mdGenerate definition/glossary notes
create-code-snippet.mdGenerate code snippet documentation
create-moc.mdGenerate Maps of Content
summarize-note.mdSummarize existing notes
improve-note.mdAnalyze and improve note quality

Commands

Workflow automation commands:

CommandPurpose
create-daily-note.mdGenerate daily journal entries
generate-backlinks.mdAdd backlinks sections to notes
launch-quartz.mdSync content and start Quartz server
process-inbox.mdOrganize inbox notes
update-readme.mdUpdate README with vault statistics
validate-frontmatter.mdCheck and fix frontmatter

Audit and cleanup commands:

CommandPurpose
audit-full.mdComprehensive vault health check
audit-tags.mdReview tag consistency and conventions
audit-frontmatter.mdValidate frontmatter completeness
audit-links.mdFind broken links and orphaned notes
audit-structure.mdCheck note structure and formatting
audit-content-gaps.mdIdentify areas needing content
audit-templates.mdValidate template syntax and usage
audit-naming.mdReview file naming consistency

Plans

Planning documents for vault maintenance:

PlanPurpose
vault-maintenance.mdWeekly/monthly/quarterly maintenance tasks
content-expansion.mdAreas for content growth

MCP Servers

Model Context Protocol (MCP) servers extend AI capabilities:

ServerPurposeType
exaWeb search with AIHTTP
firecrawlWeb scraping and crawlingstdio
tavilyReal-time web searchstdio
repomixRepository packaging for AI analysisstdio
context7Library documentation retrievalHTTP
obsidianObsidian vault interaction via Local REST APIstdio

Obsidian MCP Server

The Obsidian MCP server requires the Local REST API community plugin:

  1. Install “Local REST API” from Community Plugins
  2. Enable the plugin and note the API key
  3. Configure in .cursor/mcp.json:
{
  "obsidian": {
    "command": "uvx",
    "args": ["mcp-obsidian"],
    "env": {
      "OBSIDIAN_API_KEY": "your-api-key",
      "OBSIDIAN_HOST": "http://127.0.0.1",
      "OBSIDIAN_PORT": "27123"
    }
  }
}

Obsidian Copilot

The vault also uses Obsidian Copilot for in-editor AI assistance.

Custom Prompts Location

Custom prompts are stored in 05-SYSTEM/Copilot/copilot-custom-prompts/:

PromptFunction
SummarizeCreate bullet-point summaries
Generate glossaryExtract terms and definitions
SimplifySimplify complex text
Fix grammar and spellingProofread content
Make shorter/longerAdjust content length
Generate table of contentsCreate TOC from headings

Conversation History

Copilot conversations are saved in 05-SYSTEM/Copilot/copilot-conversations/.

AGENTS.md

The root AGENTS.md file provides comprehensive instructions for AI agents working with this vault. It covers:

  • Vault structure and purpose
  • Frontmatter conventions
  • Tag system
  • Linking rules
  • Template usage
  • Quartz publishing
  • Writing guidelines

This file is automatically read by AI tools that support the AGENTS.md convention.

Key Conventions for AI

When AI generates or modifies content:

  1. Preserve frontmatter - Maintain existing YAML structure
  2. Use wikilinks - Prefer [[Note]] over markdown links
  3. Match tags - Follow Status/Type/Topic conventions
  4. No emojis - Unless explicitly requested
  5. Templater awareness - Preserve Templater syntax in templates
  6. Dataview compatibility - Ensure valid query syntax

Appendix

Created: 2024-12-20 | Modified: 2024-12-20

See Also

Graph View

Backlinks