with▌

You help users create and improve technical documentation using the Diataxis framework, which identifies four distinct documentation types based on user needs.

Key benefits:

Have intelligent conversations about PDF documents - ask questions, get summaries, and extract specific information.

"Work like Manus" — Uses persistent markdown files for planning, progress tracking, and knowledge storage.

Persistent markdown-based planning system for organizing complex multi-step tasks and research projects. \n \n Creates three working files ( task_plan.md , findings.md , progress.md ) in your project directory to serve as persistent \"working memory\" across agent commands \n Enforces the 2-Action Rule: save key findings to disk immediately after viewing/searching to prevent multimodal information loss \n Includes a 3-Strike Error Protocol for systematic debugging: diagnose and fix on attempt 1,

像 Manus 一樣工作：用持久化的 Markdown 檔案作為你的「磁碟工作記憶」。

Work like Manus: Use persistent markdown files as your "working memory on disk."

Comprehensive guide for Medusa backend architecture, workflows, and critical implementation rules. \n \n Covers six rule categories (architecture, type safety, business logic placement, imports, data access, file organization) with specific anti-patterns and enforcement checks \n Enforces strict layer separation: Module → Workflow → API Route → Frontend, with workflows required for all mutations and only GET/POST/DELETE HTTP methods allowed \n Includes critical data handling rules: prices stored

SQLite and offline-first data layer architecture for Flutter apps with structured local persistence. \n \n Separates data layer into stateless Services (raw data wrappers) and business-logic Repositories (single source of truth per domain entity) \n Implements offline-first synchronization: reads yield cached local data immediately then fetch remote updates; writes save locally first, then attempt API sync with background queue fallback \n Covers SQLite setup with safe parameterized queries, Dom

Persistent file-based planning system for organizing complex multi-step tasks and maintaining context across sessions. \n \n Creates three markdown files (task_plan.md, findings.md, progress.md) in your project directory to serve as persistent working memory \n Includes session recovery via script to sync context after /clear commands and resume interrupted work \n Enforces structured workflows: plan first, update after each phase, log all errors, and never repeat failed actions \n Provides temp