Productivity & Workflow
1,947 results
- Sync GuideNotionOfficialComprehensive guide to building Notion Workers syncs — covers the two-sync architecture (backfill+delta), replace mode, pagination, consistency buffers, pacers, deletion strategies, and common pitfalls. Auto-loads when sync-related work is detected.
- WorkflowNotionOfficialBuild or review Notion App workflows for typed triggers, durable replay-safe steps, and idempotent effects.
- WorkflowNotionOfficialScaffold a Notion Worker Workflow with typed triggers and replay-safe durable steps.
- Workflow GuideNotionOfficialReference for typed triggers, durable steps, replay-safe data flow, and idempotent Workflow effects.
- Workflow ValidateNotionOfficialReview Notion Worker Workflows for trigger typing and retry safety.
- Notion AppsNotionOfficialSet up and scaffold Notion Apps with the Notion Apps SDK and `ntn`; use when starting a Notion App project.
- AutoshipVercelOfficialCLI tool for automated changeset-based releases with AI-generated descriptions. Use when the user needs to release a package, create changesets, bump versions, or automate npm publishing workflows. Triggers include requests to "release a package", "create a changeset", "publish to npm", "bump the version", "automate releases", or any task involving version management and package publishing for…
- Holiday RecapMicrosoftOfficialReturn-from-leave catch-up briefing across Outlook mail, meetings and Teams. Asks which areas to cover and only the scoping questions those areas need, then reports each item once, deep-linked and prioritised. Suggests replies as text; creates drafts, sends, posts and meeting responses only on explicit approval.
- Work Iq SignalboardMicrosoftOfficialBuild a lively, quantitative Work IQ Signalboard as a self-contained HTML dashboard of the signed-in user's last 28 days of Calendar, Mail, and Teams chat activity. Use whenever the user asks "show me my Work IQ signals", "build my Work IQ Signalboard", "make a Work IQ dashboard", or wants a visual of recent Microsoft 365 work patterns.
- Prisma Mongodb UpgradePrismaOfficialDecision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when "upgrade to prisma 7" comes up in a project with provider = "mongodb", or when evaluating a move to Prisma 8. Triggers on "upgrade prisma mongodb", "prisma 7 mongodb", "mongodb prisma migration", "prisma 8 mongodb".
- Prisma Upgrade V7PrismaOfficialComplete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".
- Batch ModernizationMicrosoftOfficialDeterministic local control-plane utilities for parsing, preflighting, validating, and tracking multi-repository modernization batches.
- Building Java Knowledge GraphMicrosoftOfficialAnalyzes JVM projects (Java/Kotlin/Scala/Groovy) and generates knowledge graphs with tree-sitter parsing. Requires Python 3 on the host and a JVM project with Maven/Gradle/Ant/Ivy build files. Skips gracefully if either prerequisite is missing. Triggers when asked to "build knowledge graph", "analyze project structure", "parse Java codebase", or "generate dependency graph".
- Dag GenerationMicrosoftOfficialGenerate task DAGs for modernization projects — select fragments from task catalog, produce initial DAG (Stage 1), and execute/validate DAG from plan artifacts (Stage 2).
- Dependency MapMicrosoftOfficialGenerate dependency map diagram from project build files
- List PlansMicrosoftOfficialDiscovers valid migration plans in the workspace and returns the selected plan path. A valid plan is a subdirectory of .github/modernize/ that contains plan.md AND tasks.json (tasks.json may be in the plan folder or in a .metadata subfolder). Handles 0, 1, or multiple plans and returns structured NEEDS_INPUT when a choice is needed.
- Project ReconMicrosoftOfficialZero-dependency shell recon for any code repository — detect languages, count LOC, and report project scale. Pure POSIX find/wc or PowerShell, no Python or third-party tools required. Triggers: "how big is this project", "what languages", "project sizing", "repo recon", "LOC count", "scope check".
- Setting Up ConstitutionMicrosoftOfficialCreates or updates the project constitution that defines migration principles, constraints, and conventions. Triggers: "set up constitution", "define migration principles", "create project rules", "establish conventions", "establish migration constitution". NOT for: implementation, implementation planning, task generation.
- Analyzing Cross Host Route OwnershipMicrosoftOfficialDetermines which URLs a partly migrated app is still served by the old .NET Framework host and which the new ASP.NET Core host already answers, by reading both projects and the YARP route table. Use when planning the next wave of a side-by-side migration, before deleting or moving a Framework route, or when deciding whether a route has finished migrating.
- Aspire Version UpgradeMicrosoftOfficialUpgrade existing Aspire projects to a newer Aspire version. Also handles TFM upgrades — preferred when the solution contains Aspire projects, since the Aspire version drives the required TFM. Triggers for "upgrade Aspire", "update Aspire version", "move to latest Aspire", or any .NET upgrade request on a solution with Aspire artifacts.
- Converting To CpmMicrosoftOfficialConverts .NET projects and solutions to NuGet Central Package Management (CPM) with Directory.Packages.props. Use when the user wants to centralize, convert, align, or sync NuGet package versions across multiple projects, resolve version conflicts or mismatches, or get versions consistent across a solution or repository. Also triggers when packages are out of sync or drifting across projects.
- Converting To Sdk StyleMicrosoftOfficialConverts legacy non-SDK-style .NET project files (.csproj, .vbproj, .fsproj) to modern SDK-style format while preserving target frameworks, dependencies, and build behavior. Use when converting old-format .NET projects, migrating from packages.config to PackageReference, or modernizing project files.
- Dotnet Framework Version UpgradeMicrosoftOfficialUpgrade .NET Framework projects to .NET Framework 4.8.1 (net481), staying on full .NET Framework without migrating to modern .NET (net8.0+). Use when user explicitly asks to upgrade to .NET Framework 4.8.1, upgrade to the latest .NET Framework version, or stay on full/Windows .NET Framework. Preserves legacy vs SDK-style project format unless the user explicitly requests SDK-style conversion.
- Dotnet Version UpgradeMicrosoftOfficialUpgrade .NET projects to newer .NET versions, including guidance on current release status, support lifecycle (LTS/STS), and recommended upgrade targets.