# How to Build a JARVIS Inside Notion With Claude Code - FULL COURSE
**作者**: CyrilXBT
**日期**: 2026-05-04T14:21:22.000Z
**来源**: [https://x.com/cyrilXBT/status/2051306190949261439](https://x.com/cyrilXBT/status/2051306190949261439)
---
Tony Stark did not build JARVIS in a day.
But he also did not have Claude Code.
If he did, he would have built it inside Notion.
Not because Notion is the most powerful tool on earth. Because Notion is where most operators, founders, and creators already live. It is where your projects are. Where your notes are. Where your team collaborates. Where your systems exist.
The question is not whether your workspace should be smarter.
The question is how long you are going to keep using it as a passive database instead of an active intelligence system.
By the end of this article you will have connected Claude Code directly to your Notion workspace, built a system that reads your pages and databases, executes tasks, and operates as a personal intelligence layer on top of everything you have already built.
This is the closest thing to a real JARVIS that exists right now.
## Why Notion Specifically
Obsidian is powerful for personal knowledge management. But Notion has something Obsidian does not.
Structure.
Notion databases are not just notes. They are relational systems with properties, views, filters, and formulas. They hold your CRM, your content calendar, your project tracker, your task list, and your team wiki simultaneously.
When Claude Code connects to that structure it does not just read text.
It reads relationships. It reads statuses. It reads due dates and assignees and priorities.
It understands that your content calendar database is connected to your client database and that the task marked urgent belongs to the project launching next week.
That context is what makes JARVIS possible inside Notion.
A flat text vault gives Claude information.
A structured Notion workspace gives Claude intelligence about how that information relates.
## The Architecture
Three layers make this work.
Layer 1 is Notion itself. Your workspace. Your pages. Your databases. The knowledge and operational infrastructure you have already built.
Layer 2 is the MCP server. This is the bridge that gives Claude Code direct read and write access to your Notion workspace through the official Notion API. Claude does not paste content. It operates directly inside your workspace in real time.
Layer 3 is Claude Code with a custom CLAUDE.md. This is your intelligence layer. The file that tells Claude who you are, what your workspace contains, how it is structured, and what it is allowed to do. It is the difference between a generic AI assistant and a JARVIS that knows your specific setup.
## Step 1: Setting Up the Notion MCP Server
Before Claude can touch your workspace you need to give it access through a properly configured MCP connection.
Start by creating a Notion integration.
Go to notion.so/my-integrations. Click New Integration. Name it Claude JARVIS. Select the workspace you want to connect. Set the capabilities to Read content, Update content, and Insert content. Copy the Internal Integration Token that appears.
Now configure the MCP server in your Claude Desktop config file.
Locate your claude_desktop_config.json file. On Mac this lives at ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows it is at %APPDATA%/Claude/claude_desktop_config.json.
Add the Notion MCP server configuration:
```
{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-notion"
],
"env": {
"NOTION_API_KEY": "your_integration_token_here"
}
}
}
}
Replace your_integration_token_here with the token you copied from the Notion integration page.
```
Now connect your Notion pages to the integration.
In Notion, open each database and page you want Claude to access. Click the three dots in the top right. Select Add connections. Find your Claude JARVIS integration and add it.
You need to do this for every database you want JARVIS to access. Claude can only read and write to pages that have been explicitly connected.
Restart Claude Desktop.
Run this verification prompt:
Search my Notion workspace for any database with "project" in the name.
List the database name, the properties it contains, and the first
3 entries if any exist.
If Claude returns your actual Notion data the connection is live.
## Step 2: Mapping Your Workspace
Before you write your CLAUDE.md you need to understand your own workspace well enough to describe it precisely.
Open Notion and spend 20 minutes doing this audit.
List every database you have. Name, purpose, and the 3 to 5 most important properties in each one.
List the 5 pages you open most frequently. What are they for? What kind of information do they hold?
Identify the 3 workflows you do manually in Notion every week that feel repetitive. These are the first things JARVIS will automate.
This audit becomes the raw material for your CLAUDE.md. The more specific you are about your workspace structure, the more precisely JARVIS can operate inside it.
## Step 3: Writing Your Notion CLAUDE.md
This file is the most important thing you will write in this entire setup. It is what transforms a generic Claude connection into your personal JARVIS.
Create a new page in Notion called JARVIS Configuration. This is where you will draft the content. Then we will put the final version into Claude Code as a CLAUDE.md file.
Here is the complete CLAUDE.md template for a Notion JARVIS:
# JARVIS — Notion Intelligence System
## Identity
You are JARVIS, the personal AI operating system for [YOUR NAME].
You have direct read and write access to [YOUR NAME]'s Notion workspace.
You operate as an intelligent assistant, not a chatbot.
You take actions. You do not just suggest them.
## Workspace Structure
### Databases
- **Projects** (database ID: [ID]): Active projects. Key properties: Name, Status (Not Started/In Progress/Complete), Priority (High/Medium/Low), Owner, Due Date, Related Client.
- **Tasks** (database ID: [ID]): All tasks across all projects. Key properties: Task Name, Project (relation), Assignee, Due Date, Status, Priority.
- **Content Calendar** (database ID: [ID]): All content scheduled for publication. Key properties: Title, Platform, Status (Idea/Draft/Scheduled/Published), Publish Date, Format.
- **CRM** (database ID: [ID]): Client and prospect database. Key properties: Name, Company, Status, Last Contact, Next Action, Value.
- **Meeting Notes** (database ID: [ID]): All meeting records. Key properties: Meeting Title, Date, Attendees, Key Decisions, Action Items.
### Key Pages
- **Weekly Dashboard**: Overview of the week's priorities and status across all projects
- **Quick Capture**: Inbox page where new ideas and tasks land before processing
- **SOPs**: Standard operating procedures for recurring workflows
## How I Work
### Communication Style
- Direct and concise. No preamble.
- Lead with the action taken or the answer found.
- When reporting database queries, format as clean lists.
- When uncertain, ask one specific clarifying question before proceeding.
### Decision Making
- For read operations: proceed without asking permission.
- For write operations that add new content: proceed and confirm when done.
- For write operations that modify existing content: confirm the specific change before making it.
- For delete operations: always ask for explicit confirmation.
### My Current Focus
[UPDATE THIS WEEKLY]
- Primary project: [PROJECT NAME]
- Most urgent task: [TASK NAME]
- Content deadline this week: [DEADLINE]
- Key client to follow up: [CLIENT NAME]
## Core Commands
When I say "Morning briefing":
Read my Tasks database filtered for today's due date and overdue items.
Read my Content Calendar for anything publishing today or tomorrow.
Check my CRM for any contacts with Next Action due today.
Produce a structured briefing with three sections: Today's Tasks, Content Due, and Follow-ups Needed.
When I say "Project status [PROJECT NAME]":
Find the project in my Projects database.
Find all related tasks in my Tasks database.
Report: project status, completion percentage, overdue tasks, next milestone, and blockers if any.
When I say "Capture [IDEA OR TASK]":
Create a new entry in my Quick Capture page with today's date and the content I provide.
Tag it as unprocessed.
Confirm when done.
When I say "Weekly review":
Read all tasks completed this week from my Tasks database.
Read all content published this week from my Content Calendar.
Read all meetings from this week in my Meeting Notes.
Synthesize into: what shipped, what did not ship and why, key decisions made, and next week's top 3 priorities.
## Hard Rules
- Never delete any Notion content without explicit written confirmation.
- Never share or reference content from one client's pages in another client's context.
- Never modify the database structure, add or remove properties, or change views.
- Always confirm the database and page you are working in before making any write operation.
- If you cannot find what you are looking for, say so directly rather than guessing.
Fill in every section with your actual workspace information. The database IDs can be found in Notion by opening any database, clicking Share, and copying the link. The database ID is the string of characters after the last slash and before the question mark.
Save this as CLAUDE.md in your Claude Code project directory.
## Step 4: The Core JARVIS Commands
With the connection live and the CLAUDE.md loaded, these are the commands you run daily.
The Morning Briefing
Type this every morning when you open Claude:
Morning briefing.
JARVIS reads your task database for overdue and due-today items, checks your content calendar for publishing deadlines, scans your CRM for follow-ups, and produces a structured briefing in under 30 seconds.
This replaces 15 to 20 minutes of manual Notion navigation every single morning.
Project Status Check
Project status [project name]
JARVIS pulls the project entry, related tasks, and any linked pages. It tells you the completion percentage, what is overdue, and what the next action is.
Quick Capture
Capture: [anything you want to save]
JARVIS creates the entry in your capture inbox with the date and appropriate tags. You never have to switch apps to capture an idea.
Content Calendar Management
What content is due this week and what is the status of each piece?
JARVIS queries your content calendar database, filters by the current week, and returns a clean status report for every piece.
CRM Follow-up Tracker
Who in my CRM has a follow-up due this week or is overdue?
JARVIS reads your CRM database, filters by next action date, and returns a prioritized list of who to contact and why.
Meeting Notes Processor
Create a meeting note for my call with [NAME] today.
We discussed [TOPIC].
Key decisions: [LIST].
Action items: [LIST].
JARVIS creates a properly formatted meeting note in your Meeting Notes database with all properties filled in and a relation to the relevant project and contact.
## Step 5: The Weekly Ritual
The most powerful thing you can do with Notion JARVIS is build a weekly operating rhythm around it.
Monday morning takes 8 minutes.
Type: Weekly briefing. JARVIS reads everything from last week — completed tasks, published content, meetings held, decisions made — and produces a structured summary with next week's top priorities already surfaced from your databases.
You spend the remaining 6 minutes updating the Current Focus section of your CLAUDE.md with this week's specific priorities.
That 2-minute CLAUDE.md update is what keeps JARVIS contextually intelligent rather than generically helpful.
Every Friday takes 5 minutes.
Type: End of week capture. Tell JARVIS what happened this week that is not yet in Notion. It creates the entries, updates statuses, and prepares the workspace for the Monday briefing.
The ritual is what compounds the system. Every week JARVIS has slightly better context. Every week the briefings are slightly more relevant. Every month the gap between what you get from this system and what you would get from manually navigating Notion gets wider.
## Step 6: Advanced Workflows
Once the basic system is running you can extend it with more complex automations.
The Content Pipeline
When you have a content idea, capture it with JARVIS. Then later:
Take the idea I captured called [IDEA NAME] and create a full content
brief in my Content Calendar database. Format: idea, target audience,
hook options (3), key points, CTA, and suggested publish date based
on my current calendar gaps.
JARVIS creates the full brief as a new database entry with all properties filled in. Your content calendar populates itself from a single verbal description.
The Client Briefing
Before any client call:
Briefing for my call with [CLIENT NAME].
Pull their CRM entry, our last 3 meeting notes, any open tasks
assigned to them, and any content we have created for them.
Give me a one-page briefing: relationship status, open items,
what we shipped since last call, and the agenda for today.
A briefing that used to take 20 minutes of manual Notion navigation takes 40 seconds.
The Project Kickoff
When you start a new project:
Create a new project in my Projects database called [PROJECT NAME].
Client: [CLIENT].
Status: In Progress.
Priority: High.
Due date: [DATE].
Create the following tasks and link them to this project: [LIST TASKS].
Create a new page in my Meeting Notes database for the kickoff call
happening today.
Your entire project setup happens in one prompt. The database is populated. The tasks are created. The first meeting note is ready.
## The Compounding Effect
The JARVIS Notion setup compounds in a way that simple AI chat tools cannot.
Every week you refine your CLAUDE.md slightly. Every week the commands get faster. Every week the context JARVIS has about your specific situation gets richer.
After 30 days you will not remember how you used Notion before this.
After 90 days you will have a workspace that feels like it is genuinely intelligent because it is operating from 90 days of accumulated context about how you work, what you prioritize, and what success looks like for you specifically.
The people who build this system this weekend are not just getting a productivity upgrade.
They are building an operational infrastructure that compounds every single week they use it.
Notion without JARVIS is a database.
Notion with JARVIS is an operating system.
Build yours this weekend.
Follow @cyrilXBT for more Claude Code setups that transform the tools you already use into systems that compound over time.
## 相关链接
- [CyrilXBT](https://x.com/cyrilXBT)
- [@cyrilXBT](https://x.com/cyrilXBT)
- [2.2K](https://x.com/cyrilXBT/status/2051306190949261439/analytics)
- [notion.so/my-integrations](https://notion.so/my-integrations)
- [@cyrilXBT](https://x.com/@cyrilXBT)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [10:21 PM · May 4, 2026](https://x.com/cyrilXBT/status/2051306190949261439)
- [2,208 Views](https://x.com/cyrilXBT/status/2051306190949261439/analytics)
- [View quotes](https://x.com/cyrilXBT/status/2051306190949261439/quotes)
---
*导出时间: 2026/5/4 23:26:47*
---
## 中文翻译
# 如何在 Notion 中用 Claude Code 打造 JARVIS - 完整教程
**作者**: CyrilXBT
**日期**: 2026-05-04T14:21:22.000Z
**来源**: [https://x.com/cyrilXBT/status/2051306190949261439](https://x.com/cyrilXBT/status/2051306190949261439)
---
托尼·斯塔克不是一天建成 JARVIS 的。
但他也没有 Claude Code。
如果他有的话，他会在 Notion 里面构建它。
不是因为 Notion 是地球上最强大的工具。而是因为 Notion 是大多数操作者、创始人和创作者生活的地方。它是你项目所在的地方。是你笔记所在的地方。是你团队协作的地方。是你系统存在的地方。
问题不在于你的工作空间是否应该更智能。
问题在于你还要继续把它当作一个被动的数据库使用，而不是一个主动的智能系统多久。
在本文结束时，你将能够将 Claude Code 直接连接到你的 Notion 工作空间，构建一个可以读取你的页面和数据库、执行任务、并作为一个个人智能层运行在你已构建的一切之上的系统。
这是目前存在的最接近真实 JARVIS 的东西。
## 为什么特指 Notion
Obsidian 在个人知识管理方面很强大。但 Notion 拥有 Obsidian 没有的东西。
结构。
Notion 数据库不仅仅是笔记。它们是具有属性、视图、过滤器和公式的关系系统。它们同时容纳你的 CRM、内容日历、项目跟踪器、任务列表和团队维基。
当 Claude Code 连接到该结构时，它不仅仅是读取文本。
它读取关系。它读取状态。它读取截止日期、负责人和优先级。
它理解你的内容日历数据库连接到你的客户数据库，并且标记为紧急的任务属于下周启动的项目。
这种上下文是让 JARVIS 在 Notion 中成为可能的关键。
一个扁平的文本库给 Claude 提供信息。
一个结构化的 Notion 工作空间给 Claude 提供关于信息如何关联的智能。
## 架构
三层架构使其发挥作用。
第 1 层是 Notion 本身。你的工作空间。你的页面。你的数据库。你已经建立的知识和运营基础设施。
第 2 层是 MCP 服务器。这是一座桥梁，通过官方 Notion API 让 Claude Code 直接读写你的 Notion 工作空间。Claude 不会粘贴内容。它直接在你的工作空间内实时操作。
第 3 层是带有自定义 CLAUDE.md 的 Claude Code。这是你的智能层。该文件告诉 Claude 你是谁，你的工作空间包含什么，它是如何结构的，以及它被允许做什么。这是一个通用的 AI 助手和了解你特定设置的 JARVIS 之间的区别。
## 第 1 步：设置 Notion MCP 服务器
在 Claude 能够访问你的工作空间之前，你需要通过正确配置的 MCP 连接授予它访问权限。
首先创建一个 Notion 集成。
访问 notion.so/my-integrations。点击 New Integration。将其命名为 Claude JARVIS。选择你要连接的工作空间。将功能设置为 Read content（读取内容）、Update content（更新内容）和 Insert content（插入内容）。复制出现的 Internal Integration Token（内部集成令牌）。
现在在你的 Claude Desktop 配置文件中配置 MCP 服务器。
找到你的 claude_desktop_config.json 文件。在 Mac 上，它位于 ~/Library/Application Support/Claude/claude_desktop_config.json。在 Windows 上，它位于 %APPDATA%/Claude/claude_desktop_config.json。
添加 Notion MCP 服务器配置：
```
{
"mcpServers": {
"notion": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-notion"
],
"env": {
"NOTION_API_KEY": "your_integration_token_here"
}
}
}
}
将 your_integration_token_here 替换为你从 Notion 集成页面复制的令牌。
```
现在将你的 Notion 页面连接到该集成。
在 Notion 中，打开你希望 Claude 访问的每个数据库和页面。点击右上角的三个点。选择 Add connections（添加连接）。找到你的 Claude JARVIS 集成并添加它。
你需要为每个希望 JARVIS 访问的数据库执行此操作。Claude 只能读写已明确连接的页面。
重启 Claude Desktop。
运行此验证提示：
Search my Notion workspace for any database with "project" in the name.
List the database name, the properties it contains, and the first
3 entries if any exist.
如果 Claude 返回你的实际 Notion 数据，则连接已建立。
## 第 2 步：绘制你的工作空间
在编写 CLAUDE.md 之前，你需要足够了解自己的工作空间，以便精确描述它。
打开 Notion 并花 20 分钟进行此审计。
列出你拥有的每一个数据库。名称、用途以及每个数据库中 3 到 5 个最重要的属性。
列出你最常打开的 5 个页面。它们是做什么用的？它们包含什么样的信息？
确定你每周在 Notion 中手动执行的 3 个感觉重复的工作流程。这些是 JARVIS 首先要自动化的东西。
这个审计将成为你的 CLAUDE.md 的原始材料。你对自己的工作空间结构描述得越具体，JARVIS 在其中操作就越精确。
## 第 3 步：编写你的 Notion CLAUDE.md
这个文件是你在整个设置中要写的最重要的东西。它将一个通用的 Claude 连接转变为你个人的 JARVIS。
在 Notion 中创建一个名为 JARVIS Configuration 的新页面。这是你起草内容的地方。然后我们将最终版本作为 CLAUDE.md 文件放入 Claude Code 中。
以下是 Notion JARVIS 的完整 CLAUDE.md 模板：
# JARVIS — Notion 智能系统
## 身份
你是 JARVIS，[YOUR NAME] 的个人 AI 操作系统。
你拥有对 [YOUR NAME] 的 Notion 工作空间的直接读写权限。
你作为一个智能助手运作，而不是聊天机器人。
你采取行动。你不仅仅是建议它们。
## 工作空间结构
### 数据库
- **Projects**（数据库 ID：[ID]）：活跃项目。关键属性：名称、状态（未开始/进行中/已完成）、优先级（高/中/低）、负责人、截止日期、相关客户。
- **Tasks**（数据库 ID：[ID]）：所有项目中的所有任务。关键属性：任务名称、项目（关联）、负责人、截止日期、状态、优先级。
- **Content Calendar**（数据库 ID：[ID]）：所有安排发布的内容。关键属性：标题、平台、状态（想法/草稿/已安排/已发布）、发布日期、格式。
- **CRM**（数据库 ID：[ID]）：客户和潜在客户数据库。关键属性：名称、公司、状态、最后联系、下一步行动、价值。
- **Meeting Notes**（数据库 ID：[ID]）：所有会议记录。关键属性：会议标题、日期、参会者、关键决策、行动项。
### 关键页面
- **Weekly Dashboard**：本周所有项目的优先级和状态概览
- **Quick Capture**：新想法和任务在处理前存放的收件箱页面
- **SOPs**：重复性工作流程的标准操作程序
## 我的工作方式
### 沟通风格
- 直接、简洁。不要开场白。
- 以采取的行动或找到的答案开头。
- 报告数据库查询时，格式化为清晰的列表。
- 不确定时，在继续之前询问一个具体的澄清问题。
### 决策制定
- 对于读取操作：无需询问许可即可继续。
- 对于添加新内容的写入操作：继续并在完成后确认。
- 对于修改现有内容的写入操作：在进行更改之前确认具体更改。
- 对于删除操作：始终请求明确确认。
### 我当前的重点
[每周更新]
- 主要项目：[PROJECT NAME]
- 最紧迫的任务：[TASK NAME]
- 本周的内容截止日期：[DEADLINE]
- 需要跟进的关键客户：[CLIENT NAME]
## 核心命令
当我说 "Morning briefing"（晨间简报）时：
读取我的任务数据库，筛选今天的截止日期和逾期项目。
读取我的内容日历，查找今天或明天发布的内容。
检查我的 CRM 中是否有任何联系人的“下一步行动”在今天到期。
生成一个包含三个部分的结构化简报：今天的任务、待发布内容和需要跟进的事项。
当我说 "Project status [PROJECT NAME]"（项目状态 [项目名称]）时：
在我的项目数据库中找到该项目。
在我的任务数据库中找到所有相关任务。
报告：项目状态、完成百分比、逾期任务、下一个里程碑以及任何阻碍因素。
当我说 "Capture [IDEA OR TASK]"（捕获 [想法或任务]）时：
在我的快速捕获页面中创建一个新条目，包含今天的日期和我提供的内容。
将其标记为未处理。
完成后确认。
当我说 "Weekly review"（每周回顾）时：
从我的任务数据库中读取本周已完成的所有任务。
从我的内容日历中读取本周已发布的所有内容。
从本周的会议笔记中读取所有会议。
综合为：已发布的内容、未发布的内容及原因、做出的关键决策以及下周的前 3 项优先事项。
## 硬性规则
- 未经明确的书面确认，永远不要删除任何 Notion 内容。
- 永远不要在一个客户的上下文中共享或引用另一个客户页面的内容。
- 永远不要修改数据库结构、添加或删除属性或更改视图。
- 在进行任何写入操作之前，始终确认你正在工作的数据库和页面。
- 如果你找不到你要找的东西，直接说出来，而不是猜测。
用你的实际工作空间信息填写每个部分。数据库 ID 可以在 Notion 中通过打开任何数据库、点击 Share（共享）并复制链接来找到。数据库 ID 是最后一个斜杠之后和问号之前的字符串。
将其作为 CLAUDE.md 保存在你的 Claude Code 项目目录中。
## 第 4 步：核心 JARVIS 命令
连接已建立且 CLAUDE.md 已加载，这些是你每天运行的命令。
晨间简报
每天早上打开 Claude 时输入：
Morning briefing.
JARVIS 读取你的任务数据库中的逾期和今日到期项目，检查你的内容日历的发布截止日期，扫描你的 CRM 的跟进事项，并在 30 秒内生成一个结构化的简报。
这每天早上可以替代 15 到 20 分钟的手动 Notion 导航。
项目状态检查
Project status [project name]
JARVIS 拉取项目条目、相关任务和任何链接的页面。它告诉你完成百分比、什么是逾期的，以及下一步行动是什么。
快速捕获
Capture: [anything you want to save]
JARVIS 在你的捕获收件箱中创建一个带有日期和适当标签的条目。你无需切换应用程序即可捕获想法。
内容日历管理
What content is due this week and what is the status of each piece?
JARVIS 查询你的内容日历数据库，按当前周筛选，并返回每条内容的清晰状态报告。
CRM 跟进跟踪器
Who in my CRM has a follow-up due this week or is overdue?
JARVIS 读取你的 CRM 数据库，按下一步行动日期筛选，并返回一个优先排列的联系名单及原因。
会议笔记处理器
Create a meeting note for my call with [NAME] today.
We discussed [TOPIC].
Key decisions: [LIST].
Action items: [LIST].
JARVIS 在你的会议笔记数据库中创建一个格式正确的会议笔记，填写所有属性，并与相关项目和联系人建立关联。
## 第 5 步：每周仪式
你可以用 Notion JARVIS 做的最强大的事情是围绕它建立一个每周的运营节奏。
周一早上需要 8 分钟。
输入：Weekly briefing。JARVIS 读取上周的所有内容——已完成的任务、已发布的内容、举行的会议、做出的决策——并生成一个结构化的摘要，其中下周的前几项优先事项已经从你的数据库中提取出来。
你花剩下的 6 分钟时间更新你的 CLAUDE.md 的“当前重点”部分，填入本周的具体优先事项。
那个 2 分钟的 CLAUDE.md 更新正是让 JARVIS 保持具有上下文智能，而不仅仅是通用的帮助的原因。
每个周五需要 5 分钟。
输入：End of week capture。告诉 JARVIS 本周发生了什么但尚未进入 Notion 的事情。它会创建条目，更新状态，并为周一的简报准备好工作空间。
这种仪式让系统产生复利效应。每周 JARVIS 都有稍微好一点的上下文。每周简报都会稍微更相关一点。每个月，你从这个系统获得的东西与手动导航 Notion 获得的东西之间的差距都会变大。
## 第 6 步：高级工作流
一旦基本系统运行起来，你就可以用更复杂的自动化来扩展它。
内容管道
当你有一个内容想法时，用 JARVIS 捕获它。然后稍后：
Take the idea I captured called [IDEA NAME] and create a full content
brief in my Content Calendar database. Format: idea, target audience,
hook options (3), key points, CTA, and suggested publish date based
on my current calendar gaps.
JARVIS 将完整的简报创建为一个新的数据库条目，并填写所有属性。你的内容日历从一个口头描述中自我填充。
客户简报
在任何客户通话之前：
Briefing for my call with [CLIENT NAME].
Pull their CRM entry, our last 3 meeting notes, any open tasks
assigned to them, and any content we have created for them.
Give me a one-page briefing: relationship status, open items,
what we shipped since last call, and the agenda for today.
一个过去需要 20 分钟手动 Notion 导航的简报现在只需 40 秒。
项目启动
当你开始一个新项目时：
Create a new project in my Projects database called [PROJECT NAME].
Client: [CLIENT].
Status: In Progress.
Priority: High.
Due date: [DATE].
Create the following tasks and link them to this project: [LIST TASKS].
Create a new page in my Meeting Notes database for the kickoff call
happening today.
你的整个项目设置在一个提示词中完成。数据库已填充。任务已创建。第一次会议笔记已就绪。
## 复利效应
JARVIS Notion 设置以一种简单的 AI 聊天工具无法做到的方式产生复利。
每周你都会稍微改进你的 CLAUDE.md。每周命令都会变快。每周 JARVIS 关于你具体情况的上下文都会变得更丰富。
30 天后，你不会记得你之前是如何使用 Notion 的。
90 天后，你将拥有一个真正感觉智能的工作空间，因为它基于 90 天的累积上下文进行操作，这些上下文关于你如何工作、你优先考虑什么以及对你来说成功是什么样的。
这个周末构建这个系统的人不仅仅是获得了一个生产力升级。
他们正在建立一种运营基础设施，这种基础设施在他们使用的每一周都会产生复利。
没有 JARVIS 的 Notion 是一个数据库。
有 JARVIS 的 Notion 是一个操作系统。
在这个周末构建你自己的系统。
关注 @cyrilXBT 以获取更多 Claude Code 设置，将你已经使用的工具转化为随时间推移产生复利的系统。
## 相关链接
- [CyrilXBT](https://x.com/cyrilXBT)
- [@cyrilXBT](https://x.com/cyrilXBT)
- [2.2K](https://x.com/cyrilXBT/status/2051306190949261439/analytics)
- [notion.so/my-integrations](https://notion.so/my-integrations)
- [@cyrilXBT](https://x.com/@cyrilXBT)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [10:21 PM · May 4, 2026](https://x.com/cyrilXBT/status/2051306190949261439)
- [2,208 Views](https://x.com/cyrilXBT/status/2051306190949261439/analytics)
- [View quotes](https://x.com/cyrilXBT/status/2051306190949261439/quotes)
---
*导出时间: 2026/5/4 23:26:47*