## 4 Results
### Examples of Tagged Queries  
This section provides examples of tagged queries for each category to illustrate further the types of queries used. These examples showcase the specificity and focus of well-tagged queries, which likely contributed to the improved performance observed in specific categories. Note: For clarity, all prompts are translated from the Slovenian language.  
Feature Implementation (FI) example prompt: \"Implement an application for managing task lists with support for user accounts. Use React, React Router, and TypeScript. Requirements include allowing users to log into the system using the API: [[https://reqres.in/](https://reqres.in/)]([https://reqres.in/](https://reqres.in/)) (accessed on 14 June 2025). Once logged in, the username should be saved in localStorage.\"  
This prompt directly asks for developing a task management application using specific technologies like React, React Router, and TypeScript. It entails creating features such as user authentication, task list display, and interactions with an external API. These elements align with the core tasks in feature implementation, as the user must build an application from a conceptual requirement into a functional software solution. In this context, the need to integrate user login and task management implies a significant level of application design and coding.  
Error Fixing (EF) example prompt: \"react-router-dom\" has no exported member 'Switch'.ts(2305) Module'react-router-dom' has no exported member 'useHistory'. Fix these import errors.\"  
The presented prompt showcases a clear case of debugging and error resolution, focusing on fixing TypeScript import errors with the React Router library. It reflects the user's struggle with module imports, a common issue developers face when library updates affect existing codebases. Solving such errors requires an understanding of the library's current API and how to adapt the existing code accordingly. In this scenario, the emphasis is on identifying the discrepancies between expected and available exports in react-router-dom, marking it as an EF task.  
Code Understanding (CU) example prompt: \"How do I set it up so that when a user opens the application, they are immediately redirected to /login and only then able to access other routes?\"  
This prompt highlights the user's challenge in understanding how to implement routing logic within React that aligns with the user's authentication status. It illustrates a need to grasp how React Router can be utilized to conditionally redirect users based on their login state, navigating between different parts of the application accordingly. The pursuit of this knowledge reflects the user's requirement to internalize effective routing strategies that are central to building user-friendly navigational flows within web applications, deeming it a CU task.  
Code Optimization (CO) example prompt: \"Use React routing for navigation between different parts of the application, including login, main page, and task adding page.\"  
Although this prompt primarily addresses implementation, it inherently suggests optimizing and structuring the application's routing system. The prompt encourages the developer to consider efficient routing practices and component organization by emphasizing the use of React's routing capabilities for seamless navigation. Hence, while not overtly focused on optimization, there is an implicit call to improve the routing architecture, making the application more scalable and maintainable.  
Concept Clarification (CC) example prompt: \"What is Axios, and can I achieve this without using Axios?\"  
This question arises when the developer is uncertain about the necessity of a specific library (Axios) for performing HTTP requests in their application.