<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>flove making-of — Skills questions</title>
    <link>https://flove.org/making-of.html</link>
    <description>New Skills design questions from flove interviews.</description>
    <language>en</language>
    <item>
      <title>What do you want to do with the writing-skills workflow?</title>
      <link>https://flove.org/making-of.html#talk2web-design_q1</link>
      <guid isPermaLink="false">talk2web-design_q1</guid>
      <category>Skills</category>
      <category>Process</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Create a new skill — Author a brand-new skill from scratch, starting with a baseline (RED) test.
• Edit an existing skill — Modify or improve a skill you already have.
• Test / verify a skill — Run pressure scenarios against an existing skill.

★ decided: Create a new skill</description>
    </item>
    <item>
      <title>What's the skill about?</title>
      <link>https://flove.org/making-of.html#talk2web-design_q2</link>
      <guid isPermaLink="false">talk2web-design_q2</guid>
      <category>Skills</category>
      <category>Process</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• A flove/frontend pattern — A reusable design/code technique from the flove work.
• A workflow/process rule — A discipline future agents should follow.
• Something else — A different technique or reference.

★ decided: A workflow/process rule</description>
    </item>
    <item>
      <title>When should the form replace asking inline?</title>
      <link>https://flove.org/making-of.html#talk2web-design_q3</link>
      <guid isPermaLink="false">talk2web-design_q3</guid>
      <category>Skills</category>
      <category>UX</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Many questions (~4+) — Use the form whenever there are roughly 4+ questions; ask 1–3 inline.
• Always in brainstorm/plan — Always render the form when there are questions.
• Only when I offer it — I propose the form and you opt in each time.

★ decided: Only when I offer it · ◇ recommended: Many questions (~4+)</description>
    </item>
    <item>
      <title>Where is the generated form saved?</title>
      <link>https://flove.org/making-of.html#talk2web-design_q4</link>
      <guid isPermaLink="false">talk2web-design_q4</guid>
      <category>Skills</category>
      <category>Process</category>
      <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
      <description>• Alongside the work — Into the relevant project's docs/, then I hand over the path.
• A fixed scratch folder — Always one place regardless of project.
• Current working directory — Wherever we're working, dated filename.

★ decided: Alongside the work · ◇ recommended: Alongside the work</description>
    </item>
  </channel>
</rss>
