Enhance AI Coding Technique with Knowledge Base and Interviewer Concepts

- Add new pages for AI Knowledge Base, Knowledge Garden comparison, and AI Interviewer technique
- Refactor AI Coding Technique directory structure with more detailed phase descriptions
- Update journal entries with new AI coding and knowledge management insights
- Improve documentation for project preparation, knowledge integration, and AI-assisted coding processes

Author: codekiln

journals/2025_03_03.md

@@ -1,24 +1,25 @@
 ## [[AI Coding]]
 	- [[AI/Coding/Technique/Phased Planning/ai-coding dir]] #Updated
 		- Expanded the introductory section with a description of the files in the directory and some examples of various ticket folders
-		- Thinking that it might make sense to add these, but haven't recorded this anywhere else yet
-			- plan and checklist files for each stage in sub-folders to increase focus
-			- a file for CURRENT STAGE to store that state
+		- Thinking that it might make sense to add these, but haven't recorded this anywhere else yet:
+			- a plan and a checklist file for each stage in sub-folders to increase focus
+			- a CURRENT STAGE file to store the state of which sub-task we're working on
 			- subfolders for issues from other repos
 	- [[CursorAI/Security/How To/Exclude Secrets from Indexing]]
 		- [[CursorAI/Forum/24/12/Questions on .gitignore, .cursorignore, .cursorban]]
 	- Expense of [[Claude 3.7 Sonnet]]
 		- [Is using claude-sonnet-3.7 more expensive than normal? : r/cursor](https://www.reddit.com/r/cursor/comments/1ixy6ip/is_using_claudesonnet37_more_expensive_than_normal/)
 			- Yes, it's fairly expensive. I'm using [[IDE/Cline]] extension in [[Windsurf]] and have spent $1.30 with 5 minutes. If you use it for a full day you could easily spend between 50 and 100 dollars.
 - ## LangChain Ecosystem
-	- [[langgraph/How To/See configuration for LangGraph run in LangSmith]]
-	- [[langgraph/How To/Use add_conditional_edges to route in graph]]
-	- [[langgraph/Docs/Companies using LangGraph]]
-	- [[langgraph/Template]]
-	- [[langgraph/EnvVars]]
-		- #TIL that Langgraph has [[DataDog]] support through [[EnvVar]]s
-	- [[LangChain/GitHub/langchain-mcp-adapters]] is a [[GitHub/Repo]] that provides an [[MCP]] adapter for [[langgraph]] and [[LangChain]]
-	- [[langgraph/Tip/Use langgraph-cli rather than studio so you can grep your logs]]
+	- #Filed
+		- [[langgraph/How To/See configuration for LangGraph run in LangSmith]]
+		- [[langgraph/How To/Use add_conditional_edges to route in graph]]
+		- [[langgraph/Docs/Companies using LangGraph]]
+		- [[langgraph/Template]]
+		- [[langgraph/EnvVars]]
+			- #TIL that Langgraph has [[DataDog]] support through [[EnvVar]]s
+		- [[LangChain/GitHub/langchain-mcp-adapters]] is a [[GitHub/Repo]] that provides an [[MCP]] adapter for [[langgraph]] and [[LangChain]]
+		- [[langgraph/Tip/Use langgraph-cli rather than studio so you can grep your logs]]
 - #Security
 	- [[Person/Sergei Smagin/Blog/19/11/Cross-Site Requests]]
 - #[[Tiling Window Manager]]

journals/2025_03_04.md

@@ -0,0 +1,10 @@
+## [[AI Coding]]
+	- [[AI/Coding/Technique/Phased Planning/ai-coding dir]] #Updated
+		- #Filed
+			- [[AI/LLM/Technique/AI Interviewer]]
+				- #Idea [[AI/Coding/Technique/Project Onboarding Interview]]
+			- #Idea [[AI Technique - Link in a Personal Knowledge Base]]
+			- #Idea [[AI/Coding/Technique/Knowledge Base]]
+- ## Knowledge
+	- ### [[Disambiguation]]
+		- #Filed [[Knowledge/Concept/Knowledge Base vs Knowledge Garden]] to distinguished [[Knowledge Gardens]] from [[Knowledge Bases]]

pages/AI___Coding___Technique___Knowledge Base.md

@@ -0,0 +1,3 @@
+# Technique - Giving an AI Access to [[Knowledge Bases]]
+	- In this technique, the project repository either directly contains #Documentation, or the project repository is configured so as to give the AI access to an [[MCP/Server]] that can access documentation.
+	- [[CursorAI/@/Docs]] is almost a form of this, but to my knowledge, as of [[CursorAI/v/0.46 - Agent is ready and UI Refresh]], I haven't seen the [[CursorAI/Agent Mode]] initiate draw upon Docs itself. Instead, it tends to do a web search or a file system grep.

pages/AI___Coding___Technique___Knowledge Base___Personal.md

@@ -0,0 +1,4 @@
+alias:: [[AI Technique - Link in a Personal Knowledge Base]]
+
+- # AI Technique - Link in a Personal [[Knowledge/Base]]
+	-

pages/AI___Coding___Technique___Phased Planning___ai-coding dir.md

@@ -12,69 +12,105 @@
 				- [[AI/Coding/v0/File/1-TICKET-repomix.config.json]]
 				- [[AI/Coding/v0/File/2-TICKET-technical-specification.md]]
 				- [[AI/Coding/v0/File/3-TICKET-staged-implementation-plan.md]]
-				- [[AI/Coding/v0/File/6-TICKET-staged-implementation-checklist.md]]
-				- [[AI/Coding/v0/File/6-TICKET-qa-todo.md]]
+				- [[AI/Coding/v0/File/4-TICKET-staged-implementation-checklist.md]]
+				- [[AI/Coding/v0/File/5-TICKET-qa-todo.md]]
 				- [[AI/Coding/v0/File/6-TICKET-qa-summary.md]]
 				- [[AI/Coding/v0/File/7-TICKET-mr-summary.md]]
 				- [[AI/Coding/v0/File/8-TICKET-mr-handoff.md]]
 	- ## Phases and their [[Intermediate Packets]] AKA output files
 		- ### [[AI/Coding/v0/Phase/0 - Preparation]]
 		  id:: 67c2d185-4821-4b6f-80f9-51b05cdb859e
-			- Before beginning work it is a good idea to prepare the coding environment for AI coding. This includes but is not limited to:
+			- Following [[mise-en-place]] from the culinary world, before beginning work it is important to prepare the environment for working efficiently.
+			- This is the only phase that isn't strongly tied to the ticket, and the files it impacts are not scoped to the ticket or stored in the `/.ai-coding/TICKET-feature-name/` directory.
+			- #### Phase Activities
 				- downloading the repository
 				- setting up the IDE
 					- ensuring that [[Prompts]] for [[AI Coding]] are configured and accessible
 						- [[CursorAI/Project Rules]]
 							- [[CursorAI/Project Rule/cursor-project-rule-editor.mdc]]
-							- descriptions of the context of
+								- when to suggest an update to a cursor rule
+							- descriptions of the coding context
 								- the repository
 									- directory structure
-									- purpose
-									- coding conventions
-										- git commit format
-										- when to commit
-								- when to suggest an update to a cursor rule
+									- purpose of the project
+								- coding conventions
+									- git commit format
+									- when to commit
+								- which [[Package Managers]] to use
+							- Project Rules from other git submodules
+					- Configuring a #[[Dev Container]]
 				- provisioning API tokens, populating [[EnvVar]]s
-				- configuring shell
+					- consider provisioning a fine-grained `GH_TOKEN` for the AI to interact with the #gh CLI
+				- configuring the shell
 					- consider setting [[git/Config/core.pager]] to use [[cat]]; see also [[AI/Coding/Tip/Avoid Non-Interactive CLI Commands When Defining AI Tools]]
 					  id:: 67c2d285-e4ca-448a-96bf-e76c70111882
 				- ensuring [[CLI Tools]] are available and configured
 					- #Repomix
 					- #llm-cli
+					- #mise
+					- #[[Package Managers]]
+					- #[[MCP Servers]]
+					- #Docker
+				- #### Link in any [[Knowledge Bases]] for [[AI/Coding/Technique/Knowledge Base]]
+					- For example, a [[Logseq]] or [[Obsidian]] flat-file database of documentation could be symlinked to `.ai-coding/knowledge` if it is contained outside.
+				- ####  Link in any personal coding [[Knowledge Gardens]] that the AI should be able to access #[[AI Technique - Link in a Personal Knowledge Base]]
+					- In time, a [[Coder]]'s Knowledge Garden may become an important supplement to the AI coding process. The accumulated knowledge should be able to be instrumented so as to be available in any repository so the AI can make use of it. Consider using [[git/.gitignore]] so as to keep the agent from committing it to the repo. This way a coder's central knowledge garden can be utilized across multiple projects.
+				- #### Use an [[AI Interviewer]] to conduct [[AI/Coding/Technique/Project Onboarding Interview]]
+					- The purpose of this type of interview is to onboard the human into AI programming in the current project and guide the human to help them complete [[AI/Coding/v0/Phase/0 - Preparation]].
+			- #### Phase Files and Directories
+				- [[CursorAI/Project Rules]]
+					- a file that explains the repository's directory structure
+					- a file that explains the high level project context
+					- files that explain coding conventions
+						- a file that explains git commit conventions
+						- a file that explains <language> conventions, for example, python conventions
+							- package management
+							- coding preferences
 		- ### [[AI/Coding/v0/Phase/1 - Gather Materials]]
-			- **Output:** [[AI/Coding/v0/File/1-TICKET-original-issue.md]] - Original ticket details and high-level #AC
-				- this is for [[Project/Management]] stakeholders and likely doesn't have the detail needed for implementation
-				- pulled in from a tool like [[JIRA/CLI]], [[GitHub/CLI]], [[Gitlab/CLI]] if not using a tool like [[GitHub/MCP]]
-			- **Output:** [[AI/Coding/v0/File/1-TICKET-repomix.config.json]] - defines issue-related repository paths for [[Repomix]]
-				- used to gather repo context for external tools like [[ChatGPT]] or [[Claude/Desktop]]
-			- **Output:** [[AI/Coding/v0/File/1-TICKET-repo-context.txt]] - Contains the repo context sent to an external LLM in the next step.
-				- Should be put in [[git/.gitignore]] and considered a temporary, transitory, runtime artifact of the process
-				- Unlike the other files, this should probably not be inside of the `/.ai-coding/TICKET-feature-name/` directory, as the file may be quite large, and there's little value in retaining separate context for separate tickets over time.
+			- #### Phase Files
+				- **Output:** [[AI/Coding/v0/File/1-TICKET-original-issue.md]] - Original ticket details and high-level #AC
+					- this is for [[Project/Management]] stakeholders and likely doesn't have the detail needed for implementation
+					- pulled in from a tool like [[JIRA/CLI]], [[GitHub/CLI]], [[Gitlab/CLI]] if not using a tool like [[GitHub/MCP]]
+				- **Output:** [[AI/Coding/v0/File/1-TICKET-repomix.config.json]] - defines issue-related repository paths for [[Repomix]]
+					- used to gather repo context for external tools like [[ChatGPT]] or [[Claude/Desktop]]
+				- **Output:** [[AI/Coding/v0/File/1-TICKET-repo-context.txt]] - Contains the repo context sent to an external LLM in the next step.
+					- Should be put in [[git/.gitignore]] and considered a temporary, transitory, runtime artifact of the process
+					- Unlike the other files, this should probably not be inside of the `/.ai-coding/TICKET-feature-name/` directory, as the file may be quite large, and there's little value in retaining separate context for separate tickets over time.
 		- ### [[AI/Coding/v0/Phase/2 - Requirements Interview]]
-			- **Output:** [[AI/Coding/v0/File/2-TICKET-technical-specification.md]] - Detailed technical requirements, data models, [[Acceptance Criteria]], and architecture decisions
+			- This is a type of [[AI/Coding/Interview]] (see also #Interview and [[AI/LLM/Technique/AI Interviewer]] )
+			- #### Phase Files
+				- **Output:** [[AI/Coding/v0/File/2-TICKET-technical-specification.md]] - Detailed technical requirements, data models, [[Acceptance Criteria]], and architecture decisions
 		- ### [[AI/Coding/v0/Phase/3 - Implementation Plan]]
-			- **Output:** [[AI/Coding/v0/File/3-TICKET-staged-implementation-plan.md]] - Step-by-step implementation guide for AI implementation.
-				- Contains AI prompts broken down into **Stages**, *each* of which
-					- chunk the work into a single logical commit
-					- builds on previous work
-					- contains a step-by-step implementation guide
-					- includes its own validation steps
-				- Enforces commit discipline in a way specific to the ticket, for example, by adding the issue number into the commit
+			- #### Phase Files
+				- **Output:** [[AI/Coding/v0/File/3-TICKET-staged-implementation-plan.md]] - Step-by-step implementation guide for AI implementation.
+					- Contains AI prompts broken down into **Stages**, *each* of which
+						- chunk the work into a single logical commit
+						- builds on previous work
+						- contains a step-by-step implementation guide
+						- includes its own validation steps
+					- Enforces commit discipline in a way specific to the ticket, for example, by adding the issue number into the commit
 		- ### [[AI/Coding/v0/Phase/4 - Implementation Checklist]]
-			- **Output:** [[AI/Coding/v0/File/6-TICKET-staged-implementation-checklist.md]] - Granular checklist of all required tasks organized by implementation phase, grouped into a single logical commit with a summary commit message
-				- While not strictly enforced, ideally the commit history should roughly match the stages in this checklist
+			- #### Phase Files
+				- **Output:** [[AI/Coding/v0/File/4-TICKET-staged-implementation-checklist.md]] - Granular checklist of all required tasks organized by implementation phase, grouped into a single logical commit with a summary commit message
+					- While not strictly enforced, ideally the commit history should roughly match the stages in this checklist
 		- ### [[AI/Coding/v0/Phase/5 - Implementation]]
-			- **Update:** Each iteration updates a single **Stage** in [[AI/Coding/v0/File/6-TICKET-staged-implementation-checklist.md]] **Stage**, checking off the todos for that stage, and ends with a commit
-			- **Output:** [[AI/Coding/v0/File/6-TICKET-qa-todo.md]] - This is a [[QA/Test Plan]] checklist, with both human and AI todo items, including automated testing, manual verification, code coverage, etc. While each iteration is likely to run some if not all tests, each iteration may update  with any areas of the codebase that will later require final verification before submission.
+			- #### Phase Files
+				- **Update/Complete:** Each iteration updates a single **Stage** in [[AI/Coding/v0/File/4-TICKET-staged-implementation-checklist.md]], checking off the todos for that stage, and ends with a commit. By the end of phase 5, every item has been checked off.
+				- **Output:** [[AI/Coding/v0/File/5-TICKET-commits.md]] - The commit messages created along with the **Stage** of the implementation from the [[AI/Coding/v0/File/4-TICKET-staged-implementation-checklist.md]]
+				- **Output:** [[AI/Coding/v0/File/5-TICKET-qa-todo.md]] - This is a [[QA/Test Plan]] checklist, with both human and AI todo items, including automated testing, manual verification, code coverage, etc. While each iteration is likely to run some if not all tests, each iteration may update  with any areas of the codebase that will later require final verification before submission.
 		- ### [[AI/Coding/v0/Phase/6 - Verification]]
-			- **Complete:** [[AI/Coding/v0/File/6-TICKET-staged-implementation-checklist.md]]
-			- **Update:** [[AI/Coding/v0/File/6-TICKET-qa-todo.md]]
-			- **Output:** [[AI/Coding/v0/File/6-TICKET-qa-summary.md]] - a summary of the QA impacted areas of the codebase, the testing activities conducted, etc.
+			- #### Phase Files
+				- **Update/Complete:** [[AI/Coding/v0/File/5-TICKET-qa-todo.md]] - as items from the verification checklist are completed, they are checked off. By the end of phase 6, all the items are checked off.
+				- **Output:** [[AI/Coding/v0/File/6-TICKET-qa-summary.md]] - a summary of the QA impacted areas of the codebase, the testing activities conducted, etc.
 		- ### [[AI/Coding/v0/Phase/7 - Documentation]]
-			- **Output:** [[AI/Coding/v0/File/7-TICKET-mr-summary.md]], a [[Merge Request/Description]] with a summary of changes, testing results, documentation updates, and next steps for reviewers
-			- **Output:** In-repository documentation updates
-		- ### [[AI/Coding/v0/Phase/8 - Submission]]
-			- **Output:** [[AI/Coding/v0/File/8-TICKET-mr-handoff.md]] - Summary of changes made during the [[Code Review]], along with any items that may need follow-up in future tickets
+			- #### Phase Files
+				- **Update:** any `CHANGELOG.md`, `README.md`, or any other in-repository documentation of the project with anything that has changed
+		- ### [[AI/Coding/v0/Phase/8 - Submission]] of #PR / #MR
+			- #### Phase Files
+				- Before PR
+					- **Output:** [[AI/Coding/v0/File/7-TICKET-mr-summary.md]], a [[Merge Request/Description]] with a summary of changes, testing results, documentation updates, and next steps for reviewers
+				- After PR
+					- **Output:** [[AI/Coding/v0/File/8-TICKET-mr-handoff.md]] - Summary of changes made during the [[Code Review]], along with any items that may need follow-up tickets for future work
 	- ## About the `<STAGE_NUM>-<TICKET_REF>-` prefix for files
 		- **STAGE_NUM** - By prefixing the file with the stage number, the files will be sorted in chronological order of when they will be used. This benefits both the AI and the human participants, as they can use a shared vocabulary
 		- **TICKET_REF** - Ideally, this wouldn't be necessary. In [[CursorAI]], it can currently be a bit messy when trying to pull a specific file into the chat pane using [[CursorAI/@/Files]] if many files are named the same. In the interest of making it possible to uniquely identify all files using `@` references, one may prefix the files with the ticket. This has the advantage of making it possible to quickly reference an item. If Cursor's UI evolves a more reliable directory drill-down UI, it may make sense to omit this section of the file names.

pages/AI___LLM___Technique___AI Interviewer.md

@@ -0,0 +1,8 @@
+tags:: [[Interview]]
+alias:: [[AI/Interviewer]], [[AI Interviewer]], [[AI Interviewers]]
+
+- # Technique - AI Interviewer
+	- In this technique, a #Prompt directs the AI to ask the human or counterpart questions in a particular manner. This could be [[Requirement/Elicitation]] for the [[Product Requirements Document]], gathering information for any kind of specific purpose, or simply being a [[Thought/Partner]].
+	- ## Example from [[Person/Harper Reed/Blog/25/02/My LLM codegen workflow atm]]
+		- In this example, the AI interviews the programmer to conduct requirements elicitation
+			- {{embed ((67b5d737-0ce1-47ee-a0a9-9735d77539b3))}}

pages/Knowledge.md

@@ -0,0 +1,4 @@
+# Knowledge
+	- In time, perhaps this page will grow to more of a philosophical discussion.
+	- ## See Also
+		- [[Knowledge/Concept/Knowledge Base vs Knowledge Garden]]

pages/Knowledge___Base.md

@@ -0,0 +1,12 @@
+alias:: [[Knowledge/Base]], [[Knowledge Base]], [[Knowledge Bases]], [[KB]], [[KG]], [[KBs]], [[KGs]]
+tags:: [[Term]]
+
+- # Knowledge Base
+	- A knowledge base is a repository of knowledge about a team, product, company or organization.
+	- It typically has many contributors and distributed stakeholders and is an important form of #Documentation.
+		- There are two typical forms of a knowledge base:
+			- 1 - Documentation intended for an external audience, for example, product documentation
+			- 2 - Internal documentation, for example
+				- operational documentation
+				- project documentation
+				- documentation written by one team or group of teams intended for other teams in a company or organization

pages/Knowledge___Concept___Knowledge Base vs Knowledge Garden.md

@@ -0,0 +1,7 @@
+tags:: [[Diataxis/Explanation]], [[Disambiguation]]
+
+- # [[Knowledge Gardens]] vs [[Knowledge Bases]]
+	- In the context of a product, organization or a company, the equivalent of a **Knowledge Garden** (KG) is often called a **Knowledge Base** (KB). Key differences between a Knowledge Garden and a KB are the:
+		- **purpose** - KGs serve individual needs, while KBs are often an important form of official #Documentation needed by many different types of product stakeholders. A [[Software/Library]]'s documentation is a type of KB.
+		- **number of contributors** - KGs are typically bespoke and managed by no more than a few people, whereas KBs might be updated in a team- or company-wide fashion
+		- **level of formality** - KGs are typically more idiosyncratic and personal, while KBs are more impersonal and codified. For example, standards like #Diataxis codify how to create a KB for a product, but the [[Target/User]] or [[Target/Audience]] don't make quite as much sense in a context of personal [[Note-taking]].