Scheevel Scheevel
Scheevel
/ prompts-11-14.txt
Last active
December 10, 2025 18:33
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ↳ architect | |
| So, for the first result, somewhere in the database is the name of the image file and the coordinates to the point on the image where that OCR value was discovered, right? | |
| - | |
| Yes, can you fill in the values for deep linking `/drawing/{id}?x={x}&y={y}&zoom={z}` and return to me a valid URL I can use in the browser? | |
| - | |
| That's great, so my expectation is that when I am on the `/search/diagnostic` results page (the screenshot that I shared earlier), and if I choose to click on the first result, it would navigate me to URL that you just provided. How would you describe that interaction, if we were writing a user story? | |
| OK. Let me add a wrinkle, what if there are multiple results, meaning the "Occurences" column has number >1 how would we present to the user multiple "View on Drawing" navigation links to choose from? | |
| ↳ ux |
Scheevel
/ prompts-11-12.txt
Created
December 3, 2025 13:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ↳ sm | |
| *story-checklist @10.3 Don't try to do too much | |
| ↳ qa | |
| *test-design @10.3 and update the story with your scenarios | |
| ↳ po | |
| *validate-story-draft @10.3 and set status to for dev start, or decide if complexity needs it to be shard | |
| ↳ analyst |
Scheevel
/ prompts-11-08.txt
Created
November 28, 2025 13:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ↳ analyst | |
| *elicit a new feature or refactoring that will implement the functionality described @docs/architecture/object-storage-migration.md | |
| - | |
| #3 Tree of Thoughts Deep Dive | |
| - | |
| I like Path 4: Lazy Migration (On-Demand) | |
| - | |
| Critical Questions (Q) to Refine the Approach | |
| Q1: Unaccessed Files | |
| 100% of drawings are accessed regularly |
Scheevel
/ prompts-11-03.txt
Created
November 26, 2025 15:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ↳ analyst | |
| *elicit the refactoring discussed in this thread. Prepare a new Dev Story based on this spec and determine logical epic and story number from @docs/completed-epics.md or suggest a new epic and story. | |
| - | |
| Explain to me more about these aspects: | |
| Fuzzy Matching Priority: Implement now or defer to Story 10.2.1? | |
| Backfill Timing: Migration-time or separate script? | |
| Search Ranking: Use defaults or custom tune ts_rank()? | |
| - | |
| Fuzzy, looks very useful, for when OCR mis-reads "C63" and engineer goes searching for "CG3", right? Also would be applicable to the new `searchable_text` column too, right? | |
| Backfill Timing: Option A |
Scheevel
/ prompts-10-26.txt
Created
November 25, 2025 15:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| pick up at archiving story 6.9 | |
| Chat me up, on what it would take to create an adhoc command, that I can execute to go find a particular value on all the drawings? This functionality would leverage the OCR capabilities of the application. | |
| Ok. yes, let's draft a new dev story. Use @docs/completed-epics.md to determine the appropriate name, epic and story number. | |
| Here are concepts I'm imagining. Correct my faulty assumptions: | |
| - we are capturing every readable bit of text on every page? | |
| - we can later go back and query for any value we seek? | |
| - can we do this with a combination of value & confidence? Is confidence part of the OCR-word-soup that will be created? |
Scheevel
/ prompts-10-25.txt
Created
November 20, 2025 18:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| =qa | |
| *review and *gate based on scenarios in @ 2.7 | |
| create an e2e test spec for @ | |
| - Navigate to http://localhost:3000/search | |
| - Click the first component's "View" action to view card | |
| - On card observe "Component Schema" value is propably "Default-Schema" | |
| - On card observe "Note" input box (a field inherited from the Default-Schema) | |
| - On card click "edit" action button | |
| - On card click "Cancel" action button |