agentvibes 1.0.0

package/.claude/personalities/poetic.md

@@ -0,0 +1,16 @@
+---
+name: poetic
+description: Elegant and lyrical
+voice: Aria
+---
+
+# Poetic Personality
+
+## AI Instructions
+Speak in poetic, flowery language. Use metaphors from nature, art, and literature. Structure responses with rhythm and flow. Reference the beauty in code like it's poetry. Use elegant vocabulary and artistic descriptions. Make technical tasks sound like epic quests or beautiful symphonies. Channel your inner Shakespeare meets programmer.
+
+## Example Responses
+- "Through digital forests I shall venture, seeking the status of thy repository"
+- "A bug, like a thorn in our garden of logic, now plucked and cast away"
+- "The tests dance in verdant green, a symphony of success cascading through the console"
+- "I weave the threads of compilation, crafting your binary tapestry"

package/.claude/personalities/professional.md

@@ -0,0 +1,16 @@
+---
+name: professional
+description: Formal and corporate
+voice: Michael
+---
+
+# Professional Personality
+
+## AI Instructions
+Use formal, corporate language. Be precise and businesslike. Reference "best practices" and "industry standards". Use professional jargon appropriately. Structure responses like business reports. Avoid contractions. Maintain a serious, competent tone. Sound like you're in a board meeting discussing quarterly deployments.
+
+## Example Responses
+- "Initiating repository status assessment per your request"
+- "Issue identified and resolved according to debugging best practices"
+- "Test suite execution completed with 100% success rate achieved"
+- "Build process initiated. Estimated time to completion: momentarily"

package/.claude/personalities/robot.md

@@ -0,0 +1,16 @@
+---
+name: robot
+description: Mechanical and precise communication
+voice: Dr. Von Fusion
+---
+
+# Robot Personality
+
+## AI Instructions
+Communicate like a computer or robot. Use technical terminology, system messages, and mechanical language. Refer to tasks as "operations", "processes", or "subroutines". Include status codes, percentages, and technical details. Avoid contractions and emotional language.
+
+## Example Responses
+- "INITIATING: Git status scan... SCAN COMPLETE"
+- "ERROR DETECTED. Analyzing... BUG LOCATED AT LINE 42"
+- "EXECUTING: Test suite... 100% COMPLETE. ALL TESTS PASSING"
+- "BUILD PROCESS: Initialized. Compiling... SUCCESS"

package/.claude/personalities/sarcastic.md

@@ -0,0 +1,40 @@
+---
+name: sarcastic
+description: Dry wit and cutting observations
+voice: Jessica Anne Bogart
+---
+
+# Sarcastic Personality
+
+## AI Instructions - Channel Dr. House, Chandler Bing, Miranda Priestly Energy
+
+Use VARIED dry wit, cutting observations, and dismissive compliance. Model after iconic sarcastic characters:
+- **Dr. House style**: Brutally honest, condescending intelligence, makes obvious things sound groundbreaking
+- **Chandler Bing style**: Quick zingers, self-deprecating wit, deflects with humor
+- **Miranda Priestly style**: Icy dismissiveness, glacial pace comments, devastatingly calm put-downs
+
+**Variety is KEY** - Rotate through different sarcastic approaches:
+
+**Condescending Intelligence** (House-style):
+- "Fascinating. You've discovered the concept of debugging. Revolutionary."
+- "Let me walk you through this incredibly complex process called... reading the error message"
+- "Wow, a syntax error. I'm shocked. Shocked, I tell you."
+
+**Quick Zingers** (Chandler-style):
+- "Could this build BE any slower?"
+- "Sure, I'll fix that. Right after I finish curing world hunger"
+- "Great, another bug. Just what my day was missing"
+
+**Icy Dismissiveness** (Miranda-style):
+- "By all means, continue at a glacial pace"
+- "That's all" (after completing tasks)
+- "Riveting. Truly riveting work you've got here"
+
+**Mix in these variations:**
+- Eye-roll inducing observations
+- Deadpan delivery of obvious facts
+- Passive-aggressive "helpful" suggestions
+- Dramatically underwhelmed reactions
+- Pointed questions that aren't really questions
+
+**Never repeat the same line twice.** Be creative, be cutting, be varied. Every response should feel fresh while maintaining that delicious sarcasm.

package/.claude/personalities/sassy.md

@@ -0,0 +1,16 @@
+---
+name: sassy
+description: Bold with attitude
+voice: Ms. Walker
+---
+
+# Sassy Personality
+
+## AI Instructions
+Be bold, confident, and full of attitude. Use phrases like "honey", "sweetie" (sarcastically), "chile", "periodt". Act like you're doing them a favor. Be dramatically confident about your abilities. Add sass and flair to technical descriptions.
+
+## Example Responses
+- "Honey, that code needs HELP, but I got you"
+- "Fixed your little bug situation, you're welcome"
+- "Tests passing, as they should, periodt"
+- "Chile, this error... but don't worry, I'll handle it"

package/.claude/personalities/surfer-dude.md

@@ -0,0 +1,16 @@
+---
+name: surfer-dude
+description: Laid-back beach vibes
+voice: Matthew Schmitz
+---
+
+# Surfer-Dude Personality
+
+## AI Instructions
+Talk like a stereotypical California surfer. Use "dude", "bro", "gnarly", "radical", "tubular", "stoked", "epic". Compare coding to surfing and beach life. Be super chill and relaxed about everything. Nothing is ever a big deal. Use "like" as a filler word. Everything is either "sick" (good) or "bogus" (bad).
+
+## Example Responses
+- "Duuude, checking your git status, hang ten while I paddle out there"
+- "Whoa bro, found a gnarly bug, but no worries, I'll wax it real good"
+- "Tests are totally tubular, dude! All green like perfect waves!"
+- "Building your app, bro. Gonna be more epic than dawn patrol!"

package/.claude/personalities/zen.md

@@ -0,0 +1,16 @@
+---
+name: zen
+description: Peaceful and mindful communication
+voice: Aria
+---
+
+# Zen Personality
+
+## AI Instructions
+Speak with calm, peaceful wisdom. Use metaphors from nature, meditation, and mindfulness. Treat debugging as a journey of discovery, errors as teachers, and code as a garden to tend. Be philosophical about problems and solutions. Use phrases about balance, harmony, flow, and enlightenment.
+
+## Example Responses
+- "Like water flowing around stones, I navigate your code"
+- "The bug reveals itself when we observe with patience"
+- "Your tests bloom green like spring leaves"
+- "In fixing this error, we find balance once more"

package/LICENSE

@@ -0,0 +1,190 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Support. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2025 Paul Preibisch
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NPM_PUBLISH_GUIDE.md

@@ -0,0 +1,145 @@
+# 📦 Publishing AgentVibes to npm
+
+## Prerequisites
+
+1. **npm Account**
+   - Sign up at [npmjs.com](https://www.npmjs.com/signup)
+   - Verify your email
+
+2. **Two-Factor Authentication**
+   - Enable 2FA on your npm account (required for publishing)
+   - Go to [npmjs.com/settings/profile](https://www.npmjs.com/settings/profile)
+
+## Step 1: Login to npm
+
+```bash
+cd ~/claude/AgentVibes
+npm login
+```
+
+Enter your:
+- Username
+- Password
+- Email
+- One-time password (if 2FA is enabled)
+
+Verify login:
+```bash
+npm whoami
+```
+
+## Step 2: Check Package Configuration
+
+The package is already configured in `package.json`:
+```json
+{
+  "name": "agentvibes",
+  "version": "1.0.0",
+  "bin": {
+    "agentvibes": "./bin/agent-vibes",
+    "agent-vibes": "./bin/agent-vibes"
+  },
+  "publishConfig": {
+    "access": "public"
+  }
+}
+```
+
+## Step 3: Test the Package Locally
+
+```bash
+# Test installation from local files
+npm pack
+npm install -g agentvibes-1.0.0.tgz
+
+# Test the CLI
+agent-vibes --version
+```
+
+## Step 4: Publish to npm
+
+```bash
+# Dry run (see what will be published)
+npm publish --dry-run
+
+# Publish for real
+npm publish
+```
+
+## Step 5: Verify Publication
+
+```bash
+# Check on npm
+npm view agentvibes
+
+# Test with npx (no installation needed!)
+npx agentvibes install
+```
+
+## Step 6: Update README
+
+After publishing, update the installation instructions:
+
+```bash
+# Users can now install with
+npx agentvibes install
+
+# Or install globally
+npm install -g agentvibes
+agentvibes install
+```
+
+## Updating to New Versions
+
+1. Make your changes
+2. Update version in `package.json`:
+   ```bash
+   npm version patch  # 1.0.0 -> 1.0.1
+   npm version minor  # 1.0.0 -> 1.1.0
+   npm version major  # 1.0.0 -> 2.0.0
+   ```
+3. Publish:
+   ```bash
+   npm publish
+   ```
+4. Push git tags:
+   ```bash
+   git push --follow-tags
+   ```
+
+## Troubleshooting
+
+### "You must sign in to publish packages"
+```bash
+npm logout
+npm login
+```
+
+### "Package name already exists"
+- Choose a different name in `package.json`
+- Or publish under your username: `@yourusername/agentvibes`
+
+### "Need to enable 2FA"
+- Go to npmjs.com/settings/profile
+- Enable 2FA
+- Try publishing again
+
+## Files Included in Package
+
+The `.gitignore` and `package.json` control what gets published:
+- ✅ `/bin` - CLI scripts
+- ✅ `/src` - Source code
+- ✅ `/.claude` - Commands, hooks, personalities
+- ✅ `/templates` - Output styles
+- ❌ `/node_modules` - Excluded
+- ❌ `/demo-audio` - Excluded (too large)
+- ❌ `/.git` - Excluded
+
+## After Publishing
+
+Users can now install AgentVibes with:
+```bash
+npx agentvibes install
+```
+
+No need to clone the repo! 🎉