Fergana-Labs

Brief the user on what they saved in a period — the thread running through it, not a list.

Find duplicates, dead links and untagged items in a saved library and propose what to do about each.

Chart what's in the library — topics, sources, saves over time — and say what the shape means.

Pick a few old saves worth revisiting now, and say why now.

How to build presentation slide decks as HTML pages. Covers the slide format, canvas dimensions, and recommended libraries.

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other…

Create, read, edit, and analyze Microsoft Excel spreadsheets (.xlsx files). Use for spreadsheet data, calculations, formulas, charts, and tabular data analysis.

Create and manipulate Microsoft PowerPoint presentations (.pptx files). Use for creating slides, presentations, pitch decks, and visual content with text, bullets, tables, and charts.

Create, read, edit, and manipulate Microsoft Word documents (.docx files). Use when users ask to work with Word files, create documents, read .docx files, or format text documents.

Compile agent session transcripts and connected MCP integrations into a small memory wiki of terms, events, and procedures. Surveys the available data sources and writes a source map on the first run, verifies it on later runs, then fans out subagents per…

Answer questions that depend on the user's own terms, people, systems, history, or working methods by reading their curated memory wiki — index first, then pages, then raw sources. Use whenever a request contains a name, acronym, project, or phrase that…

Install and verify Stash, interview a person about the context they keep re-explaining, inventory the data sources reachable through their connected integrations, write the onboarding brief, run the first curation pass into a memory wiki, and prove value on a…

How this person wants to be communicated with. Use when writing anything they will read — a summary, a PR description, a status update, an explanation of a change — or when deciding how much to ask versus decide yourself.

Standing constraints on how work gets done in this codebase — what to verify before claiming done, what needs permission, what to never do. Use at the start of any task that changes files, and before reporting completion.

Working-style protocol for substantive engineering work: calibrated rigor, pre-ship verification, root-cause discipline, hypothesis testing, documented-intent-driven fixes, and terse token-efficient output. On first activation, offers (with consent) to…