obsidian-plugin/lossless-group_perplexed-plugin
1
0
Fork 0
mirror of https://github.com/lossless-group/perplexed-plugin.git synced 2026-07-22 06:49:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
lossless-group_perplexed-pl.../context-v/specs/Using-Files-as-Prompt-Outlines.md
mpstaton 19b300c10c improve(modals): upgrade Perplexical Modal UI, context and changelogs 
On branch development
 Your branch is up to date with 'origin/development'.
 Changes to be committed:
	new file:   changelog/2026-04-30_01.md
	new file:   changelog/2026-05-01_01.md
	modified:   changelog/2026-05-02_01.md
	modified:   context-v/specs/Using-Files-as-Prompt-Outlines.md
	modified:   src/modals/PerplexicaModal.ts
	modified:   src/styles/perplexica-modal.css
	modified:   styles.css
2026-05-02 17:07:10 -05:00

1.8 KiB
Raw Blame History

Using Files as Prompt Outlines

Development Goals

  • New command: "Generate Prompt Outline from Template"
  • New command: "Generate Prompt from Outline" opens a modal with: outline picker
  • ArticleGeneratorModal becomes one built-in outline (deep-research one-pager) — same flow, no special-casing.

User Goals

An Obsidian user can create a folder that will host prompt outlines as markdown files.

Sketch

  • New plugin settings
  • contentDevFolderPath (default Content-Dev) // nested folder for content development
  • outlinesFolderPath (default Content-Dev/Outlines)
  • templatesFolderPath (default Content-Dev/Templates)
  • Each .md file in that folder = one outline. Frontmatter declares
title: String
main_inquriy: String
description: String
providers_models: Array<string> // ("perplexity: {model}" | "perplexica: {model}" | "claude: {model}")

Body is the prompt with optional preferred structure:

  # Example Content
  {Obsidian backlink syntax to other files, optional}

  # Background

  {paragraph context eg background info, goals, user situation, model role eg analyst, academic, marketer, scientist, newsroom, columnist, optional}
  
  # Section Outline for Response
  
  {## Section Headers} // optional // must be level 2 headers or greater. No Level 1 headers, as it will mess with the LLM's ability to nest/parse the outline for the response with other elements.
  
  {ul or li list guiding questions, optional}
  
  {preferences or spectations for response eg dos and donts, optional}
  
  {preferences on research sources, include exclude ul, optional}

This decouples your prompt library from the codebase entirely. Add a new template = drop a .md in the folder, no rebuild needed. It ALSO means when Claude does work, you can author Claude-specific outlines without touching code.