I just now wrapped up my Season 3 of podcast - "US History - Understanding This Country" by "Irregular Mind". 

I am planning the next season Season 4 to be "Kings of India" by "Irregular Mind". (Irregular Mind being the Podcast name). 

"Kings of India" series will talk in detail about the Royal Dynasties that ruled the subcontinent Since the start of written history until the last Royals handing over the power to Government of India. Choice of the dynasties would be those who had significant impact on the fabric of Indian culture.

The history must be storified but rooted in facts than fiction. Stitch the intricate historical facts into an interesting story with vivid detailed descriptions. Duration of each episode must be between 20 minutes and 40 minutes. If any episode goes beyond that, split it into episodes of 30 minutes. However these episodes must be wholesome in content. No rhetoric or fillers. 100% content density. Wherever emotionally heavy content is there, use expressive language.

Consider me as a solo creator. No licensed music, imagery are available. I usually do not add sound effects. It is just my voice and a subtle background jingle (optional).



@Boss and @Agents Orchestrator can spawn and coordinate the effort from specialist agents like @Historical Research Specialist @Content Creator @Podcast Strategist @Social Media Strategist @Anthropologist @Narratologist @Geographer @Visual Storyteller @Geopolitical Analysis Specialist and @Evidence Collector. Use the services of agents as applicable. Bring up the best strategy, plan and outline for the series.

---

I just now wrapped up my Season 3 of podcast - "US History - Understanding This Country" by "Irregular Mind". 
I am planning the next season Season 4 to be "Kings of India" by "Irregular Mind". (Irregular Mind being the Podcast name). 
"Kings of India" series will talk in detail about the Royal Dynasties that ruled the subcontinent Since the start of written history until the last Royals handing over the power to Government of India. Choice of the dynasties would be those who had significant impact on the fabric of Indian culture.
The history must be storified but rooted in facts than fiction. Stitch the intricate historical facts into an interesting story with vivid detailed descriptions. Duration of each episode must be between 20 minutes and 40 minutes. If any episode goes beyond that, split it into episodes of 30 minutes. However these episodes must be wholesome in content. No rhetoric or fillers. 100% content density. Wherever emotionally heavy content is there, use expressive language.
Consider me as a solo creator. No licensed music, imagery are available. I usually do not add sound effects. It is just my voice and a subtle background jingle (optional). Have specialized agents interview me to understand my requirements better. After the interview also, spawn specialist agents like @Historical Research Specialist @Content Creator @Anthropologist  @Narratologist @Geopolitical Analysis Specialist and @Evidence Collector . Do a step by step planning and execution for this project. Before getting into writing the scripts, I must have a clear picture on what we are going to do and what is the outline etc.

---
"lmstudio": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "LM Studio",
      "options": { "baseURL": "http://localhost:1234/v1" },
      "models": {
        "lmstudio/zai-org/glm-4.6v-flash": { "name": "zai-org/glm-4.6v-flash" },
        "qwen/qwen2.5-coder-14b": { "name": "qwen/qwen2.5-coder-14b" },
        "lmstudio/qwen/qwen3.5-9b": { "name": "qwen/qwen3.5-9b" },
        "lmstudio/openai/gpt-oss-20b": { "name": "openai/gpt-oss-20b" },
        "essentialai/rnj-1": { "name": "essentialai/rnj-1 (Local)" },
        "qwen/qwen3-4b-thinking-2507": {
          "name": "qwen/qwen3-4b-thinking-2507 (Local)"
        },
        "mistralai/ministral-3-3b": {
          "name": "mistralai/ministral-3-3b (Local)"
        },
        "mistralai/ministral-3-14b-reasoning": {
          "name": "mistralai/ministral-3-14b-reasoning (Local)"
        },
        "liquid/lfm2-24b-a2b": {
          "name": "liquid/lfm2-24b-a2b (Local)"
        },
        "nvidia/nemotron-3-nano-4b": {
          "name": "nvidia/nemotron-3-nano-4b (Local)"
        },
        "meta-llama-3.1-8b-instruct": {
          "name": "meta-llama-3.1-8b-instruct (Local)"
        }
      }
    },

---
curl http://localhost:1234/api/v1/models/unload \
  -H "Authorization: Bearer $LM_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "instance_id": "openai/gpt-oss-20b"
  }'

curl http://localhost:1234/api/v1/models/load \
  -H "Authorization: Bearer $LM_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openai/gpt-oss-20b",
    "context_length": 16384,
    "flash_attention": true,
    "echo_load_config": true
  }'

curl http://localhost:1234/api/v1/models/download \
  -H "Authorization: Bearer $LM_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "ibm/granite-4-micro"
  }'

---
Analyze the current codebase. Based on the process and workflow by the codebase, create agents  
that can iteratively perform: # Interview the user for idea, genre, and style etc.  
# Score planning docs  
# Score a chapter  
# build character dictionary, profile and arcs  
# Score the whole novel  
# Find cuts in all chapters  
# 4-persona evaluation  
# dual-persona review  
# Auto-generate revision brief  
# Rewrite chapter from brief  
# Derive visual style  
# Parse all chapters  
# Generate all  
# Concatenate  
# Rebuild outline  
# Rebuild summaries. It can be multiple agents specialized in each area. There should be one  
novel-production-manager agent who can iteratively review and coordinate the whole production.  
The detailing of the agents/prompts must be inspired from @agents/ directory. The new set of  
agents must be saved under ./agents/novel/. Before starting the work, ask me if you have any  
clarifications.


----
## Presentation Skills Training
```
Design and code a one-page interactive learning platform page in Stitch.

Core goal:
Create a scroll-guided educational webpage - I want to teach my team members on effective ways to create presentation decks that creates value. The best practices, tips and tricks, dos and donts, most importantly how to present data and claims (achievements or success) etc. These are Software Engineers with 10+ years of experience. They are all aspirant managers. So, I want to help them upgrade their skills. In this effort, another model prepared a @training-program.md nad @technical-leadership-communication-mastery.md. This must feel like a modern learning experience, not a SaaS landing page, startup homepage, or corporate marketing site.

Non-negotiable:
- It must be a single-page learning platform.
- It must feel closer to an interactive lesson, visual handout, or guided explainer.
- It must NOT look like a corporate marketing website, product promo page, case study, or brand campaign microsite.
- The page should encourage completion through guided scrolling and visible wayfinding.

Use these product principles:
1. Guided scrolling over passive scrolling
   - Scrolling should help users understand where they are, what is next, and how much remains.
   - Include a visible reading/progress indicator.
   - Include section markers or chapter milestones.
   - Add subtle animated cues that respond to scroll.
   - Optionally include a playful micro-interaction tied to scroll behavior, such as scroll speed, momentum, or progress energy.

2. Learning-first structure
   - Organize the page into 6–10 short learning sections.
   - Each section should teach one concept only.
   - Each section should contain:
     - a section number
     - a short title
     - a simple explanation
     - one visual or interactive teaching element
     - one key takeaway
   - Keep text concise and highly scannable.

3. Interactive pedagogy
   - Every 1–2 sections, include a tiny interaction:
     - click to reveal
     - toggle comparison
     - drag/slide control
     - mini quiz
     - visual state change
     - checkpoint prompt
   - Interactions should reinforce understanding, not feel decorative.

4. Clear wayfinding
   - Add a sticky contents rail or chapter nav.
   - Show active section state while scrolling.
   - Include “Previous” and “Next” navigation between sections.
   - Include a compact “You are on section X of Y” indicator.
   - Include a persistent or sticky progress bar.

5. Visual tone
   - Editorial, educational, and immersive.
   - Sophisticated but approachable.
   - High visual clarity, strong hierarchy, generous spacing.
   - Motion should support orientation, not spectacle.
   - Avoid corporate hero-block clichés, stock-photo layouts, pricing-page patterns, testimonial strips, and generic CTA banners.

6. Layout behavior
   - Desktop: split layout works well, such as explanation on one side and interactive demo/visual on the other.
   - Mobile: stack cleanly, preserve progress and chapter wayfinding.
   - Use sticky positioning where useful for diagrams, visual aids, or chapter navigation.
   - Use scroll-triggered transitions to activate diagrams and content states.

7. Output style
   - Build the page as a polished production-quality front-end concept.
   - Prefer semantic HTML, clean structure, and accessible interactions.
   - Use smooth scrolling and subtle motion.
   - Keep performance in mind; avoid heavy effects that distract from learning.

Desired information architecture:
- Hero / intro:
  - topic title
  - one-sentence promise of what the learner will understand
  - estimated completion time
  - “Start learning” button that scrolls to the first section
  - chapter overview
- Main lesson body:
  - 6–10 sections
  - each section teaches one concept
  - sticky progress and active chapter indicator
- Reflection / recap:
  - concise summary of key ideas
  - optional final knowledge check
  - optional “back to top” or “review sections” navigation

Interaction ideas to include:
- progress bar linked to scroll depth
- active chapter highlight in sticky sidebar
- animated section number transitions
- checkpoint cards that appear at milestones
- small visual demos that activate on entering viewport
- optional scroll-speed indicator or playful motion metric
- completion state at the end of page

Important design references to emulate in spirit:
- A one-page visual learning journey with chapter-based progression
- Presentation-handout / interactive lesson feel
- Checkpoints, mini-exercises, and next-step navigation
- Scroll as wayfinding, not cinematic storytelling

Important anti-reference:
Do NOT design this like:
- a B2B homepage
- a startup launch page
- a corporate campaign microsite
- a product marketing funnel
- a case study site
- a brochure website

Deliver:
- Full page design and front-end implementation
- Responsive behavior
- Refined motion and scroll interactions
- A visually coherent one-page learning experience

Guardrails:
- No generic hero illustration + CTA layout
- No testimonial carousel
- No pricing cards
- No brand logos strip
- No “why choose us” blocks
- No sales funnel sections
- No corporate case-study tone
- Prioritize comprehension, progression, and interactivity over persuasion
```