chore: format, lint, github ignore

Author: bhouston

.github/workflows/deploy-docs.yml

@@ -56,4 +56,4 @@ jobs:
           flags: '--allow-unauthenticated'
 
       - name: Show Output
-        run: echo ${{ steps.deploy.outputs.url }}
+        run: echo ${{ steps.deploy.outputs.url }}

.npmignore

@@ -12,3 +12,4 @@ eslint.config.js
 pnpm-lock.yaml
 tsconfig.json
 vitest.config.js
+build

eslint.config.js

@@ -76,6 +76,8 @@ export default ts.config(
       '**/pnpm-lock.yaml',
       '**/routeTree.gen.ts',
       'scripts/verify-release-config.js',
+      '**/.docusaurus',
+      '**/build',
     ],
   },
 );

packages/docs/README.md

@@ -57,4 +57,4 @@ This project is licensed under the MIT License - see the LICENSE file for detail
 
 ## Contact
 
-If you have questions or feedback, please join our [Discord community](https://discord.gg/5K6TYrHGHt).
+If you have questions or feedback, please join our [Discord community](https://discord.gg/5K6TYrHGHt).

packages/docs/blog/authors.yml

@@ -5,7 +5,7 @@ ben:
   image_url: https://github.com/bhouston.png
   socials:
     github: bhouston
-    x: BenHouston3D  # Updated from twitter
+    x: BenHouston3D # Updated from twitter
     bluesky: benhouston3d.com
     mastodon: '[email protected]'
 

packages/docs/blog/github-mode-productivity.md

@@ -60,6 +60,7 @@ slow down development? If so, we should optimize it.
 ```
 
 **Why this works well:**
+
 - Asks MyCoder to analyze its own previous work
 - Focuses on optimization and developer experience
 - Treats MyCoder as a teammate who can explain their decisions
@@ -73,6 +74,7 @@ simultaneously. Once done, submit the PR and link both issues.
 ```
 
 **Why this works well:**
+
 - Groups related tasks for efficient implementation
 - Provides clear instructions on the desired outcome
 - Leverages GitHub references to maintain context
@@ -89,6 +91,7 @@ independent PR to address it.
 ```
 
 **Why this works well:**
+
 - Asks MyCoder to independently investigate a problem
 - Provides context about potential causes
 - Gives clear guidance on how to proceed based on findings
@@ -103,4 +106,4 @@ Using GitHub Mode doesn't just increase productivity—it fundamentally changes
 - **Increased autonomy**: MyCoder can work independently on well-defined tasks
 - **Better accountability**: All changes are tracked, reviewed, and properly attributed
 
-By structuring work through GitHub, you're providing MyCoder with a system of record that ensures continuity across tasks and makes it easy to revisit past work, turning your AI assistant into a true coding collaborator rather than a tool you need to micromanage.
+By structuring work through GitHub, you're providing MyCoder with a system of record that ensures continuity across tasks and makes it easy to revisit past work, turning your AI assistant into a true coding collaborator rather than a tool you need to micromanage.

packages/docs/docs/examples/_category_.json

@@ -5,4 +5,4 @@
     "type": "doc",
     "id": "examples/index"
   }
-}
+}

packages/docs/docs/examples/code-development.md

@@ -20,6 +20,7 @@ lint, etc for this repo.
 ```
 
 **Why this works well:**
+
 - References specific recommendations from an existing issue
 - Points to an example implementation in another repository as a reference
 - Clearly defines the scope (recommendations 2 and 3)
@@ -86,6 +87,7 @@ Vercel AI SDK.
 ```
 
 **Why this works well:**
+
 - Provides detailed background on the current implementation
 - References specific PRs for context
 - Clearly outlines the desired architecture with specific components
@@ -117,6 +119,7 @@ package to its non-built state.
 ```
 
 **Why this works well:**
+
 - Describes the specific command that's failing
 - Explains the expected behavior and the actual outcome
 - Shares the developer's hypothesis about the cause
@@ -136,9 +139,9 @@ action to complete before declaring success.
 ```
 
 **Why this works well:**
+
 - Identifies a specific problem (GitHub action failure)
 - Requests a complete workflow: investigation, issue creation, and fix implementation
 - Sets clear expectations for verification (waiting for the GitHub action to complete)
 
 **Technique:** Asking MyCoder to handle the full cycle from investigation to fix helps ensure that the problem is properly understood and addressed.
-

packages/docs/docs/examples/code-review.md

@@ -22,6 +22,7 @@ thing? Won't that slow things down?
 ```
 
 **Why this works well:**
+
 - References a specific PR and issue
 - Quotes specific text from the PR description
 - Asks a focused question about a potential issue (duplication)
@@ -39,12 +40,13 @@ docker build are still making assumptions about using
 npm rather than pnpm. Can you look at
 ../Business/drivecore/mycoder-websites as an example
 of docker files that use pnpm and also github action
-workflows that use pnpm and adapt the current project 
+workflows that use pnpm and adapt the current project
 yo use that style. Please create a github issue and
 then once the task is complete please submit a PR.
 ```
 
 **Why this works well:**
+
 - Identifies a specific concern (npm vs. pnpm assumptions)
 - Points to a reference implementation with the desired approach
 - Clearly defines the expected deliverables (GitHub issue and PR)
@@ -64,6 +66,7 @@ a Github issue for this and a PR.
 ```
 
 **Why this works well:**
+
 - Makes specific, focused requests for UI changes
 - Clearly describes the desired outcome
 - Specifies the process (create an issue and PR)

packages/docs/docs/examples/devops.md

@@ -20,6 +20,7 @@ the build and runs lint, etc for this repo.
 ```
 
 **Why this works well:**
+
 - References specific recommendations from an existing issue
 - Points to an example implementation in another repository
 - Clearly defines the expected outcome (CI action for build validation and linting)
@@ -42,6 +43,7 @@ then once the task is complete please submit a PR.
 ```
 
 **Why this works well:**
+
 - Identifies a specific configuration issue (npm vs. pnpm)
 - Points to a reference implementation with the desired approach
 - Clearly defines the expected deliverables (GitHub issue and PR)
@@ -64,11 +66,12 @@ that are depended upon.
 I must have some part of the configuration of the
 current project incorrect right? Can you create an
 issue for this and then investigate. You can use
-the command \"pnpm clean:dist\" to reset the package 
+the command \"pnpm clean:dist\" to reset the package
 to its non-built state.
 ```
 
 **Why this works well:**
+
 - Describes the specific command that's failing
 - Explains the expected behavior and the actual outcome
 - Shares the developer's hypothesis about the cause
@@ -89,6 +92,7 @@ success.
 ```
 
 **Why this works well:**
+
 - Identifies a specific problem (GitHub action failure)
 - Requests a complete workflow: investigation, issue creation, and fix implementation
 - Sets clear expectations for verification