Produktivita
Pokročilý
Claude
Personal wiki a knowledge base system
Vytvoř personal wiki pro centralizaci všech znalostí a poznámek s tagging a linking.
Prompt text
Délka: Dlouhý
Navrhni personal wiki a knowledge base systém pro [USE CASE]. Nástroje: [OBSIDIAN/NOTION/ROAM/LOGSEQ]. Struktura: 1) **Wiki Philosophy** - single source of truth (all knowledge in one place), linked thinking (connect related notes), atomic notes (one idea per note), evergreen content (timeless not timestamped), searchable (full-text search), 2) **Note Types** - permanent notes (core insights, refined knowledge), literature notes (from books/articles with source), fleeting notes (quick captures, to be processed), project notes (tied to specific projects), reference (facts, data, definitions), 3) **Folder/Tag Structure** - MOCs (Maps of Content as entry points), categories (by topic: Tech, Business, Personal, Health), tags system (hierarchical tags, metadata tags like #status/draft, #type/tutorial), avoid deep folders (max 2-3 levels), 4) **Note Template** - title (descriptive clear title), metadata (date created, tags, status, source), summary (TL;DR one paragraph), body (main content markdown), connections (linked notes, related topics), backlinks (notes linking here), 5) **Linking Strategy** - bi-directional links ([[Note Title]]), contextual links (explain why linked), hub notes (central topics with many connections), orphan cleanup (find unlinked notes), graph view analysis (identify clusters), 6) **Capture Workflow** - quick capture (fleeting notes immediately), daily note (journal + capture), processing routine (review fleeting notes daily, convert to permanent weekly), inbox (temporary holding), archive (processed old notes), 7) **Search & Retrieval** - full-text search (find any content), tag search (filter by multiple tags), backlink navigation (how is this note used elsewhere), random note (discover forgotten knowledge), recent notes (what was I working on?), 8) **Content Types** - how-to guides (step-by-step instructions), concepts explained (definitions and examples), decision logs (why we chose X), learning notes (from courses/books), meeting notes (with action items), code snippets (reusable code), 9) **Maintenance Routine** - weekly review (process fleeting notes, refine permanent notes), monthly pruning (delete outdated, consolidate duplicates), quarterly reorganization (restructure categories, update MOCs), link audit (fix broken links, add missing connections), 10) **Integration** - bookmark saving (web clipper for articles), email-to-note (important emails), API connections (sync from other tools), export options (markdown/PDF for backup), mobile sync (access anywhere). Včetně: Obsidian vault structure example, template notes, tagging philosophy, workflow diagrams, plugin recommendations.
Příklad použití
Vstup:
Use case: Software developer chce centralizovat coding notes, learning notes, troubleshooting solutions. Nástroj: Obsidian.
Výstup:
[15,000+ word personal wiki system with Obsidian vault structure showing folder organization (00-Inbox/ for fleeting notes, 10-Projects/ for active work, 20-Areas/ for ongoing topics, 30-Resources/ for reference, 40-Archives/ for completed, MOCs/ for hub notes like "React MOC" linking to all React content), note types implementation (permanent notes: "useEffect Hook Explained" with refined explanation examples code, literature notes: "Clean Code by Robert Martin Ch3" with key insights and source citation, fleeting notes: "Quick thought about component composition" timestamped to be processed, project notes: "Dashboard Redesign 2025" with tasks and progress, reference: "HTTP Status Codes Cheatsheet" with table of codes), tagging system (hierarchical: #tech/frontend/react #tech/backend/node, metadata: #status/draft #status/published, type: #type/tutorial #type/bug-fix #type/concept, difficulty: #level/beginner #level/advanced), template for technical note showing YAML frontmatter (title, created, tags, status, type), TL;DR summary paragraph, main content with code blocks, related notes section with links, backlinks footer, linking strategy demonstrated ("When building React apps, understanding [[useEffect Hook]] is crucial for side effects. It relates to [[Component Lifecycle]] and [[React Hooks]]" showing contextual links with explanation why linked), hub MOC notes like "React MOC" containing structured index (Fundamentals: [[JSX]], [[Components]], [[Props]], [[State]]; Hooks: [[useState]], [[useEffect]], [[Custom Hooks]]; Advanced: [[Context API]], [[Redux]], [[Testing]]), capture workflow (quick capture via Obsidian hotkey Cmd+N dumps into 00-Inbox/, daily note template for journaling what learned today and quick captures, weekly Sunday review processes 20+ inbox notes converting to permanent/deleting, monthly archives completed project notes), search examples (full-text "async await error handling" finds 15 notes, tag search #tech/react AND #type/tutorial finds 12 tutorials, backlinks on "useEffect Hook" shows 25 notes referencing it revealing how concept is used across wiki), content types with examples (how-to: "How to Set Up React Testing Library" with step-by-step, concept: "What is Closure in JavaScript" with definition examples use cases, decision log: "Why We Chose PostgreSQL Over MongoDB" with criteria comparison outcome, learning notes: "Frontend Masters React Course" with 50+ notes from videos, troubleshooting: "Fix CORS Error in Express" with problem solution code, code snippets: "React Custom Hook for API Fetching" with reusable useFetch code), maintenance routine (weekly: process 20 inbox notes, refine 5 permanent notes, add backlinks; monthly: deleted 10 outdated notes, merged 3 duplicate notes about Redux; quarterly: restructured MOCs, created new "TypeScript MOC", updated folder structure), integrations (Obsidian Web Clipper saves articles with metadata, important work emails forwarded to Obsidian via Readwise Reader, sync via iCloud 2-way between Mac and iPhone, daily export to GitHub for backup), Obsidian plugins used (Dataview for queries showing "List all #type/bug-fix from last month", Graph Analysis to find note clusters, Templater for consistent formatting, Calendar for daily notes, Quick Switcher for fast navigation), example graph showing React notes cluster connected to TypeScript notes cluster connected to Testing notes cluster revealing knowledge domains)]
Kde použít tento prompt?
Najděte vhodné AI nástroje pro použití tohoto promptu a maximalizujte jeho efektivitu.
Podobné prompty
AI Tool Limitations & Workarounds - Překonávání Omezení
Praktický průvodce známými omezeními AI nástrojů (hallucinations, context limits, reasoning failures) a efektivními workaroundy pro produktivní práci i při těchto omezeních.
Produktivita
Zobrazit
Asynchronous communication framework
Implementuj async-first komunikační strategie pro remote work a deep work protection.
Produktivita
Zobrazit
Automatický plán projektu v Motion
Komplexní instrukce pro AI nástroj Motion, který má autonomně naplánovat a rozvrhnout složitý pracovní projekt na základě priorit, termínů a vašich preferencí.
Produktivita
Zobrazit
Automatizace a workflow optimization
Identifikuj repetitivní úkoly a navrhni automatizační workflow pro zvýšení efektivity.
Produktivita
Zobrazit
Objevte další AI prompty
Prozkoumejte naši sbírku Produktivita promptů a najděte ty, které vám pomohou dosáhnout lepších výsledků.