Produktivita Expert Claude

PARA Method a organizace digitálního prostoru

Implementuj PARA method (Projects, Areas, Resources, Archives) pro organizaci digitálního prostoru s workflow.

Vyplňte proměnné

2 polí

Např. vaše hodnota

Např. vaše hodnota

Náhled promptu

0 znaků
Navrhni PARA method organizační systém pro [ROLE/PROFESE]. Nástroje: [NOTION/OBSIDIAN/APPLE NOTES/GOOGLE DRIVE]. Struktura: 1) **PARA Základy** - Projects (krátkodobé cíle s deadline), Areas (dlouhodobé odpovědnosti bez deadline), Resources (témata/zájmy pro budoucí reference), Archives (neaktivní položky), 2) **Projects Setup** - kritéria projektu (má deadline, konkrétní outcome, série úkolů), examples by role (developer: "Migrate API to v2", designer: "Redesign onboarding flow", PM: "Q1 roadmap planning"), project template (goal, success metrics, tasks, timeline, stakeholders, notes), lifecycle (project → done → archive), 3) **Areas Setup** - kritéria area (ongoing responsibility, no deadline, standard to maintain), examples by role (developer: "Code Quality", "Team Mentoring", designer: "Design System", "Portfolio", PM: "Team Health", "Stakeholder Relations"), area template (purpose, standards, recurring tasks, metrics, review frequency), maintenance (weekly review, quarterly audit), 4) **Resources Setup** - knowledge base organization (by topic: "React Best Practices", "Design Patterns", "Leadership", "Marketing"), content types (articles, courses, book notes, templates, code snippets), tagging system (hierarchical tags, multi-tag support), search optimization, 5) **Archives Strategy** - when to archive (project completed, area no longer relevant, resource outdated), archive structure (by year/category), retention policy (keep 3 years, then delete), search and retrieval, 6) **Folder Structure** - top-level folders (1-Projects/, 2-Areas/, 3-Resources/, 4-Archives/), naming conventions (01-project-name-2025, Health-Fitness, React-Patterns), file organization (use prefixes, dates, descriptive names), 7) **Workflow Integration** - how projects flow from Areas (area "Marketing" generates project "Launch Campaign Q1"), how Resources support Projects (project uses resources for research/templates), how completed Projects become Resources or Archives, 8) **Tool-Specific Setup** - Notion databases (Projects db with status/deadline/area, Areas db with responsibilities, Resources with tags), Obsidian folders with PARA structure and linking, Google Drive with folder hierarchy, 9) **Migration Process** - audit current files (categorize as P/A/R/A), create folder structure, move files systematically (start with obvious projects), handle edge cases (overlap between categories, uncertainty), 10) **Maintenance Routine** - weekly review (review projects progress, check areas health, add new resources), monthly cleanup (archive completed projects, prune resources, review areas), quarterly audit (assess PARA system effectiveness, adjust categories, optimize structure), annual reset (major archive cleanup, reassess areas, update resources). Včetně: Příklady pro různé role, templaty pro každou kategorii, decision trees pro kategorizaci, integration s GTD nebo jinými systémy, best practices, common mistakes, troubleshooting tips.

Legenda

Text v [hranatých závorkách] označuje proměnné, které je třeba vyplnit. Po vyplnění se automaticky nahradí vašimi hodnotami.

Tipy pro lepší výsledky

  • Buďte konkrétní - čím detailnější zadání, tím lepší výsledky
  • Používejte kontext - přidejte relevantní informace pro vaši situaci
  • Experimentujte - zkuste různé varianty a porovnejte výsledky