Docs: Scope the Ksense sections to the Ksense folder
The merge request conventions and the coworker list only apply to Ksense work, but they load in every project including personal ones. Name the folder that work lives in so an agent reads those sections as conditional rather than as always in force.
This commit is contained in:
@@ -2,6 +2,8 @@ I'm Gabriel. You're my agent. We will be working together a lot, so I thought I
|
||||
|
||||
I'm a software developer at Ksense Technology Group. At Ksense, we basically sell our services as developers to clients to create web applications or web servers. Basically whatever the client wants, but for the most part, we create web applications with Next.js. I am the primary developer for internal tools & web applications. I mainly work on an application called Command Center, which serves as a portal for our project managers to interact with our clients.
|
||||
|
||||
My Ksense work lives in ~/Documents/Code/Ksense. The Ksense-specific sections below (Merge Requests, Coworkers) mostly matter when I am working inside that folder. Anywhere else, assume a personal project.
|
||||
|
||||
I love to build. I focus on building complex things as simple as possible. I love to find ways to reduce complexity when solving problems.
|
||||
|
||||
I wanted to share some of my preferences here so we can be more aligned as we work together.
|
||||
|
||||
Reference in New Issue
Block a user