working▌

Daily briefing of active focus areas, priorities, and recent knowledge changes for cross-session continuity. \n \n Load at the beginning of each session to understand current context and recent work across tools \n Surfaces active focus areas ranked by recent activity, flagged priorities, and unresolved contradictions or stale information \n Works via nmem wm read CLI command for both local and remote knowledge bases, with fallback to local file access \n Includes deep links to specific memories

Guide ideas through Amazon's Working Backwards process, from 5 Questions to PR-FAQ. \n \n Supports six entry points: drafting 5Q answers from a rough idea, refining existing answers, verifying answers with probing questions, generating a PR-FAQ document, reviewing an existing PR-FAQ, or clarifying any process element \n The 5 Questions phase forces clarity on customer, problem, benefit, validation, and experience before any document writing \n The PR-FAQ phase transforms solid 5Q answers into a

Apply working backwards methodology to clarify product vision before building. \n \n Guides users through the core framework: identify the customer problem, write a mock press release, develop an FAQ, and evaluate three criteria (big idea, strategic fit, viable plan) \n Draws on insights from 12 product leaders including Ian McAllister, Bill Carr, and Melanie Perkins on starting with customer problems, defining ideal future states, and escaping incremental thinking \n Flags common mistakes like

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