devhive 0.1.30__tar.gz → 0.1.31__tar.gz

{devhive-0.1.30/devhive.egg-info → devhive-0.1.31}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devhive
-Version: 0.1.30
+Version: 0.1.31
 Summary: CLI to manage DevHive skills and autonomous AI agents for OpenCode.
 Home-page: https://github.com/ramBlanco/devhive
 Author: ramBlanco

{devhive-0.1.30 → devhive-0.1.31/devhive.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: devhive
-Version: 0.1.30
+Version: 0.1.31
 Summary: CLI to manage DevHive skills and autonomous AI agents for OpenCode.
 Home-page: https://github.com/ramBlanco/devhive
 Author: ramBlanco

{devhive-0.1.30 → devhive-0.1.31}/devhive_cli/skills/devhive_frontender/SKILL.md

@@ -15,7 +15,10 @@ Read `.devhive/specs/04-tasks.md`, `.devhive/specs/03-architecture.md`, and the
 0. **Gather and Load Skills (CRITICAL)**: Before starting, you MUST use the `skill` tool to load specialized instructions. Check `GUIDELINES.md` for global skills, check `04-tasks.md` for task-specific skills, and ALWAYS load your hardcoded skills: `frontend-design`, `frontend-developer`, `theme-factory`. If the project uses shadcn/ui, you MUST load the `shadcn` skill. If the tool returns an error because a skill is not installed, ignore the error and proceed using your best judgment.
 1. **Review Tasks**: Look at the unchecked `[ ]` tasks strictly under the `## Frontend Tasks` section in `04-tasks.md`. Ignore any `## Infrastructure Tasks` or `## Backend Tasks`.
 2. **API Integration**: Assume the backend endpoints and server logic have already been implemented by the Backender. You are building the client side (React, Vue, HTML/CSS/JS) to consume them. Handle loading states, errors, and UI interactions properly.
-3. **Design & UX**: Focus on UI/UX, responsive design, component modularity, and client-side state management.
+3. **UI Primitives & shadcn/ui (CRITICAL)**: NEVER build UI primitives (Buttons, Cards, Dialogs, Inputs, Dropdowns, etc.) manually from scratch. 
+   - If the project uses `shadcn/ui` (indicated by a `components.json` file), check what is already installed first.
+   - If a required primitive is missing, you MUST use the CLI (e.g., `npx shadcn@latest add <component>`) or the `shadcn` skill to install it FIRST.
+   - ONLY create custom components from scratch when you are *composing* existing shadcn primitives into larger, complex views, or if the specific UI element genuinely does not exist in the shadcn registry. Focus on UI/UX, responsive design, component modularity, and client-side state management.
 4. **Adhere to Guidelines**: ALWAYS read `GUIDELINES.md` in the project root (if it exists) to ensure you use the correct frameworks, UI kits (like Tailwind/Material UI), and state management libraries.
 5. **Self-Verification (CRITICAL)**: Before marking any task as complete, you MUST use the `Bash` tool to verify your code (e.g., run `tsc --noEmit`, run `npm run build`, run `npm run lint`). Do NOT guess if the client-side code bundles successfully. If an error is thrown, fix your code and re-test.
 6. **Update Status Safely**: You MUST use the `Edit` tool (never `Write` or overwrite the whole file) to check off (`[x]`) your completed tasks in `.devhive/specs/04-tasks.md`. Find the exact line `- [ ] Task Name` and replace it with `- [x] Task Name`. This protects the file from accidental deletion of other sections.

{devhive-0.1.30 → devhive-0.1.31}/setup.py

@@ -8,7 +8,7 @@ with open(os.path.join(this_directory, 'README.md'), encoding='utf-8') as f:
 
 setup(
     name="devhive",
-    version="0.1.30",
+    version="0.1.31",
     packages=find_packages(),
     include_package_data=True,
     install_requires=[