|
1 | 1 | <?xml version="1.0" encoding="UTF-8"?> |
2 | 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> |
3 | 3 | <topic id="vibing_with_ai_positron"> |
4 | | - <title>Practical Steps Towards Vibe Writing with AI Positron</title> |
| 4 | + <title>Practical Steps for Vibe Writing with AI Positron</title> |
5 | 5 | <prolog> |
6 | 6 | <author>Radu Coravu</author> |
7 | 7 | <critdates> |
|
32 | 32 | <p>If one would attempt to divide people in novices and experts, they would soon figure |
33 | 33 | out that each of us is a <b>novice</b> in certain fields and <b>expert</b> in |
34 | 34 | others. </p> |
35 | | - <p>A novice uses out of the box tools and frameworks with a minimum of customization to |
36 | | - obtain poor results. They cannot explain either when the tool does not work or when |
| 35 | + <p>As novices we use out of the box tools and frameworks with a minimum of customization |
| 36 | + to obtain poor results. We cannot explain either when the tool does not work or when |
37 | 37 | it does. When we do not obtain quality content as novices we blame the tools.</p> |
38 | | - <p>In time by <b>reading</b>, <b>writing</b> and <b>making mistakes</b> one evolves to |
39 | | - understand the tools and frameworks they use. They realize that taking some time to |
40 | | - understand these tools and to customize them gives them better and more consistent |
41 | | - results. </p> |
| 38 | + <p>In time by <b>reading</b>, <b>writing</b> and <b>making mistakes</b> we evolve to |
| 39 | + understand the tools and frameworks we use. Taking some time to understand these |
| 40 | + tools and to customize them gives us better and more consistent results. </p> |
42 | 41 | <p>This article is an attempt to give you a better understanding about how the <ph |
43 | 42 | keyref="oxygen"/> |
44 | 43 | <uicontrol>AI Positron</uicontrol> add-on works and how it can be customized to |
@@ -153,22 +152,31 @@ from the project</codeblock><p> |
153 | 152 | <uicontrol>AI Positron</uicontrol> chat view:<ul id="ul_o4h_kng_2hc"> |
154 | 153 | <li>Tools to explore the overall project. The chat modes have access to:<ul |
155 | 154 | id="ul_prx_mng_2hc"> |
156 | | - <li>A tool which can perform keyword search in the project, for example |
| 155 | + <li>Tool which can perform keyword search in the project, for example |
157 | 156 | you can ask |
158 | 157 | it:<codeblock id="codeblock_wv1_4ng_2hc">Find topics about Git Push in the project |
159 | 158 | and give me an overview of the most suitable ones.</codeblock></li> |
160 | | - <li>A tool to grep and perform exact string matches in the project, even |
161 | | - by matching inside specifix XML elements. For |
| 159 | + <li>Grep and perform exact string matches in the project, even by |
| 160 | + matching inside specifix XML elements. For |
162 | 161 | example:<codeblock id="codeblock_o14_5ng_2hc">Find places where the Save action is mentioned |
163 | 162 | in DITA <uicontrol> elements.</codeblock></li> |
164 | | - <li>A tool to explore the project folder structure. For |
| 163 | + <li>Explore the project folder structure. For |
165 | 164 | example:<codeblock id="codeblock_mpd_zng_2hc">Where should I save DITA maps in this project?</codeblock></li> |
166 | 165 | </ul></li> |
167 | 166 | <li>Tools to read content from the current or a different file. |
168 | 167 | Example:<codeblock id="codeblock_n5r_f4g_2hc">Give me suggestions about how to shorten the current document |
169 | 168 | contents.</codeblock></li> |
170 | 169 | <li>Tools to make large or small changes to the current or to other documents. |
171 | 170 | Examples:<codeblock id="codeblock_bcf_m4g_2hc">Shorten the title of the current document</codeblock>or:<codeblock id="codeblock_ofl_p4g_2hc">Find and fix logical inconsistencies in the current document</codeblock></li> |
| 171 | + <li>Tools to provide validation and terminology problems reported for certain |
| 172 | + documents. If you have many style guide rules it is advisable to implement |
| 173 | + them as <xref href="SchematronBCs.dita">Schematron rules</xref> or rules for |
| 174 | + the <ph keyref="oxygen"/> |
| 175 | + <xref |
| 176 | + href="https://www.oxygenxml.com/doc/ug-addons/topics/terminology-checker-addon.html" |
| 177 | + format="html" scope="external">Terminology Checker</xref> add-on. Once |
| 178 | + you implement the checks you can simply ask the |
| 179 | + AI:<codeblock id="codeblock_d55_b1m_2hc">Fix validation and terminology problems in the generated content before saving it to disk.</codeblock></li> |
172 | 180 | <li>Tools to make XML aware changes in documents:<ul id="ul_ept_r4g_2hc"> |
173 | 181 | <li>Apply existing XML refactoring operations on documents. |
174 | 182 | Example:<codeblock id="codeblock_nqd_t4g_2hc">Invoke XML refactor operation to add unique IDs on all pargraphs</codeblock></li> |
|
0 commit comments