AGENT SKILL

ams-notion-pro

暂无简介

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

03 SKILL.md 正文

Notion Pro

Overview

Notion is a block-based workspace where every page can also be a database row.

Beginners make pages; power users build small applications from a handful of interconnected databases.

The pro move: design a small schema (4-8 databases), link them with relations, and surface them through filtered views.

Formulas, rollups, templates, buttons, and native automations turn those databases into a working system.

Mental shift: stop asking 'where should I put this page?' and ask 'which database does this belong to, and which views need it?'

A well-built workspace runs projects, CRM, content pipelines, and meeting notes from one source of truth.

When to use

  • Setting up or restructuring a Notion workspace for an individual or team
  • Designing databases with relations, rollups, and formulas that compute useful state
  • Building dashboards, templates, and button-driven capture workflows
  • Automating repetitive Notion work with native automations or the API
  • Migrating from scattered docs and spreadsheets to one structured system
  • Auditing a workspace that has become slow, sprawling, or confusing

Core concepts

  • Databases, not pages. One Tasks database with Kanban, calendar, and 'my week' views beats five separate task lists that drift out of sync.
  • Relations and rollups. Link Projects <-> Tasks or People <-> Meetings, then roll up counts, sums, and latest dates across the link.
  • Views as interfaces. Same database, many lenses: Kanban for execution, calendar for scheduling, table for bulk edits, timeline for planning.
  • Formulas. Derive status ('Overdue'), scores, progress bars, and auto-titles. Keep them readable; document the clever ones.
  • Templates. Pre-fill new rows with checklists, owners, and relative dates so the happy path is the default path.
  • Buttons. One-click multi-step actions: create a project with its tasks, log a meeting, move an item through stages.
  • Native automations. Trigger on page-added or property-changed: notify in Slack, stamp dates, sync statuses. No third-party tool needed.
  • Synced blocks and linked views. Reuse the same filtered view on your home page, weekly review, and team standup page. Edit once, update everywhere.
  • Permissions as architecture. Share pages, not the whole workspace. Use groups for teams, guests for externals, and lock schemas once stable.

Practical workflow

  1. Map the schema on paper. List entities (projects, tasks, notes, people) and their relationships. If it doesn't fit one page, it's too complex.
  2. Build core databases minimally. Start with title, status, owner, dates, relations. Add properties only when a real workflow demands them.
  3. Wire relations, then rollups. Add the links first, then the aggregates you actually check in reviews: open counts, totals, completion %.
  4. Design daily views. Create the 2-4 views you'll open every day. Name them by job ('This week's focus'), not by view type.
  5. Add database templates. Meeting notes, project kickoff, bug report, content brief — each with pre-filled structure and checklists.
  6. Build one home dashboard. Linked views filtered to 'me + this week', capture buttons, links to full databases. Your daily driver.
  7. Automate the boring parts. Status transitions, assignment notifications, date stamping, archiving. API only when native automations fall short.
  8. Set permissions deliberately. Default-private, share deliberately. Audit guests quarterly, especially on client or HR-adjacent databases.
  9. Schedule maintenance. Monthly: archive done items, merge duplicate tags, fix broken relations. Quarterly: does each database still earn its place?

Common pitfalls

  • Database sprawl. Twenty micro-databases with no relations is worse than one spreadsheet. Consolidate aggressively.
  • Over-formula-ing. Clever formulas nobody understands become maintenance debt. Simple and readable wins.
  • No archive strategy. Stale rows slow everything. Add an Archived status, filter it from views, archive quarterly.
  • Templates without defaults. A template that pre-fills nothing saves no time. Defaults should encode the correct workflow.
  • Sharing everything. Default-open workspaces leak. Audit sharing quarterly, especially external guests.
  • Automating before stabilizing. Automate only after doing a workflow manually for weeks, or you entrench the wrong process.
  • Views nobody opens. Twelve linked views look impressive and get ignored. Three daily views beat twelve decorative ones.
  • Property creep. Every 'just in case' property adds friction to every future row. Unused in a month? Delete it.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

★ 0