devhive 0.1.22__tar.gz → 0.1.24__tar.gz

{devhive-0.1.22 → devhive-0.1.24}/MANIFEST.in

@@ -1,2 +1,4 @@
 recursive-include skills *
 recursive-include community_skills *
+recursive-include templates *
+

{devhive-0.1.22/devhive.egg-info → devhive-0.1.24}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: devhive
-Version: 0.1.22
+Version: 0.1.24
 Summary: CLI to manage DevHive skills and autonomous AI agents for OpenCode.
 Home-page: https://github.com/ramBlanco/devhive
 Author: ramBlanco
 Classifier: Programming Language :: Python :: 3
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
-Requires-Python: >=3.8
+Requires-Python: >=3.7
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: click>=8.0.0
@@ -65,6 +65,9 @@ devhive install
 
 # Update your existing skills to the latest versions
 devhive update-skill
+
+# Initialize a modern Next.js/React frontend AI guidelines file in your current project
+devhive init-frontend
 ```
 
 ## Usage (The `@devhive` Agent)

{devhive-0.1.22 → devhive-0.1.24}/README.md

@@ -42,6 +42,9 @@ devhive install
 
 # Update your existing skills to the latest versions
 devhive update-skill
+
+# Initialize a modern Next.js/React frontend AI guidelines file in your current project
+devhive init-frontend
 ```
 
 ## Usage (The `@devhive` Agent)

{devhive-0.1.22 → devhive-0.1.24/devhive.egg-info}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: devhive
-Version: 0.1.22
+Version: 0.1.24
 Summary: CLI to manage DevHive skills and autonomous AI agents for OpenCode.
 Home-page: https://github.com/ramBlanco/devhive
 Author: ramBlanco
 Classifier: Programming Language :: Python :: 3
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
-Requires-Python: >=3.8
+Requires-Python: >=3.7
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: click>=8.0.0
@@ -65,6 +65,9 @@ devhive install
 
 # Update your existing skills to the latest versions
 devhive update-skill
+
+# Initialize a modern Next.js/React frontend AI guidelines file in your current project
+devhive init-frontend
 ```
 
 ## Usage (The `@devhive` Agent)

{devhive-0.1.22 → devhive-0.1.24}/devhive.egg-info/SOURCES.txt

@@ -45,4 +45,5 @@ skills/devhive_qa/SKILL.md
 skills/devhive_releaser/SKILL.md
 skills/devhive_sast/SKILL.md
 skills/devhive_taskplanner/SKILL.md
-skills/devhive_techwriter/SKILL.md
+skills/devhive_techwriter/SKILL.md
+templates/AGENTS.frontend.md

{devhive-0.1.22 → devhive-0.1.24}/devhive_cli/main.py

@@ -9,6 +9,7 @@ CLI_DIR = Path(__file__).resolve().parent
 ROOT_DIR = CLI_DIR.parent
 LOCAL_SKILLS_DIR = ROOT_DIR / "skills"
 COMMUNITY_SKILLS_DIR = ROOT_DIR / "community_skills"
+TEMPLATES_DIR = ROOT_DIR / "templates"
 TARGET_DIR = Path.home() / ".config" / "opencode" / "skills"
 
 @click.group()
@@ -75,5 +76,22 @@ def update_skill():
     install_remote_skills()
     click.secho("\nUpdate Complete! 🚀", fg="green", bold=True)
 
+@cli.command()
+def init_frontend():
+    """Initialize a modern frontend AGENTS.md template in the current directory."""
+    template_path = TEMPLATES_DIR / "AGENTS.frontend.md"
+    dest_path = Path.cwd() / "AGENTS.md"
+    
+    if not template_path.exists():
+        click.secho("Error: Frontend template not found in the devhive package.", fg="red")
+        return
+        
+    if dest_path.exists():
+        click.secho("AGENTS.md already exists in this directory. Aborting to prevent overwrite.", fg="yellow")
+        return
+        
+    shutil.copy2(template_path, dest_path)
+    click.secho("✅ Successfully created AGENTS.md with modern Next.js/React frontend guidelines!", fg="green", bold=True)
+
 if __name__ == "__main__":
     cli()

{devhive-0.1.22 → devhive-0.1.24}/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.22",  # Bumping from the last deployed version 0.1.21
+    version="0.1.24",
     packages=find_packages(),
     include_package_data=True,
     install_requires=[
@@ -29,5 +29,5 @@ setup(
         "License :: OSI Approved :: MIT License",
         "Operating System :: OS Independent",
     ],
-    python_requires='>=3.8',
+    python_requires='>=3.7',
 )

{devhive-0.1.22 → devhive-0.1.24}/skills/devhive_taskplanner/SKILL.md

@@ -23,6 +23,7 @@ Read `.devhive/specs/03-architecture.md` and `.devhive/specs/02-proposal.md`.
 8. **Define Documentation Tasks**: Write tasks for the Tech Writer (e.g., update README, Swagger, OpenAPI specs).
 9. **Define Release Tasks**: Write tasks for the Release Manager (e.g., update package.json version, CHANGELOG.md, create local git tag).
 10. **Format the Output**: Ensure you strictly separate the output into the corresponding sections.
+11. **Empty Domains**: If a specific domain (e.g., Backend, Data, Infrastructure) is not needed for the project, DO NOT use checkboxes (`[ ]`). Instead, simply write "*None required*" under that section. This prevents the orchestrator from launching unnecessary agents.
 
 ## Output
 You MUST use the `Write` tool to save your plan to `.devhive/specs/04-tasks.md`.
@@ -36,30 +37,35 @@ The markdown file should be structured as follows:
 [1-3 sentences summarizing the execution plan]
 
 ## Design Tasks
+[If applicable, list tasks with `- [ ] **Task Name**`. Otherwise, write "*None required*"]
 - [ ] **Task 1: [Name]**
   - Description: [CSS vars, framework configuration]
   - Files: [Files to modify/create]
   - Skills: [Comma-separated list of suggested opencode skills, or None]
 
 ## Infrastructure Tasks
+[If applicable, list tasks with `- [ ] **Task Name**`. Otherwise, write "*None required*"]
 - [ ] **Task 1: [Name]**
   - Description: [What infrastructure needs to be provisioned]
   - Files: [Files to modify/create]
   - Skills: [Comma-separated list of suggested opencode skills, or None]
 
 ## Data Tasks
+[If applicable, list tasks with `- [ ] **Task Name**`. Otherwise, write "*None required*"]
 - [ ] **Task 1: [Name]**
   - Description: [Migrations, seeders, schema definitions]
   - Files: [Files to modify/create]
   - Skills: [Comma-separated list of suggested opencode skills, or None]
 
 ## Backend Tasks
+[If applicable, list tasks with `- [ ] **Task Name**`. Otherwise, write "*None required*"]
 - [ ] **Task 1: [Name]**
   - Description: [Initial project setup, API routes, server logic]
   - Files: [Files to modify/create]
   - Skills: [Comma-separated list of suggested opencode skills, or None]
 
 ## Frontend Tasks
+[If applicable, list tasks with `- [ ] **Task Name**`. Otherwise, write "*None required*"]
 - [ ] **Task 1: [Name]**
   - Description: [UI components, consuming backend APIs]
   - Files: [Files to modify/create]

devhive-0.1.24/templates/AGENTS.frontend.md

@@ -0,0 +1,160 @@
+# Frontend Architecture & AI Agent Guidelines
+
+This `AGENTS.md` (or `GUIDELINES.md`) file serves as the strict instruction manual for OpenCode and DevHive agents. It defines the technical stack, architectural patterns, and coding conventions for this frontend project.
+
+## 🛠️ 1. Tech Stack
+- **Framework**: Next.js 15 (App Router)
+- **Library**: React 19
+- **Language**: TypeScript (Strict Mode)
+- **Styling**: Tailwind CSS v3/v4 + `clsx` + `tailwind-merge`
+- **Components**: shadcn/ui (Radix UI primitives)
+- **Icons**: Lucide React
+- **Data Fetching**: React Server Components (RSC) & Server Actions
+
+## 🧠 2. OpenCode Skills to Load
+Agents **MUST** load the following specialized skills before executing tasks:
+- `frontend-developer`: For modern React 19 / Next.js 15 patterns.
+- `frontend-design`: For high-quality, non-generic UI aesthetics.
+- `shadcn`: For proper installation and composition of shadcn/ui components.
+- `theme-factory`: For applying cohesive color palettes and typography.
+- `architecture-patterns`: For maintaining clean separation of concerns.
+
+## 📂 3. Project Structure (Feature-Based Architecture)
+For maximum scalability and maintainability, the project follows a feature-based architecture within the `src/` directory. 
+
+```text
+src/
+├── app/                  # Next.js App Router (Pages, Layouts, API Routes)
+│   ├── (auth)/           # Route groups for logical separation
+│   ├── dashboard/        # Dashboard routes
+│   └── layout.tsx        # Root layout (Providers, Fonts, Metadata)
+├── components/           
+│   ├── ui/               # Pure shadcn/ui components (DO NOT EDIT DIRECTLY unless styling)
+│   └── shared/           # Reusable global components (Navbar, Footer, etc.)
+├── features/             # Feature-based modules (THE CORE OF THE APP)
+│   ├── users/            # "Users" feature module
+│   │   ├── actions.ts    # Server Actions for this feature
+│   │   ├── components/   # Feature-specific React components
+│   │   └── types.ts      # Feature-specific TypeScript interfaces
+│   └── products/         # "Products" feature module
+├── lib/                  # Utility functions (utils.ts, formatting, constants)
+└── hooks/                # Global custom React hooks
+```
+
+## 📐 4. Architectural Rules & Best Practices
+
+1. **Default to Server Components (RSC)**: 
+   - All components inside `app/` and `features/` MUST be Server Components by default to optimize bundle size and SEO.
+   - ONLY add the `"use client"` directive at the very top of a file if the component requires interactivity (`useState`, `useEffect`, `onClick`, browser APIs).
+   - Keep Client Components as low in the tree (leaf nodes) as possible.
+
+2. **Server Actions for Mutations**:
+   - Do NOT build traditional API routes (`route.ts`) for internal app data mutations.
+   - Use Next.js Server Actions (`"use server"`) placed in `src/features/[name]/actions.ts`.
+   - Always validate inputs inside Server Actions (using Zod or similar) before mutating data.
+
+3. **Shadcn/ui Usage**:
+   - Use the OpenCode CLI or `npx shadcn@latest add [component]` to install components.
+   - Combine UI components to build complex blocks (e.g., combining `Card`, `Button`, and `Input` to make a LoginForm).
+
+4. **Type Safety**:
+   - Avoid `any`. Define interfaces/types in `types.ts` files.
+   - Export types and reuse them across Server Actions and Client Components.
+
+## 💻 5. Code Examples
+
+### Example A: Data Fetching in a Server Component (RSC)
+*File: `src/app/dashboard/page.tsx`*
+```tsx
+import { Suspense } from "react";
+import { getUserProfile } from "@/features/users/actions";
+import { UserProfileCard } from "@/features/users/components/user-profile-card";
+import { Skeleton } from "@/components/ui/skeleton";
+
+// This is a Server Component (no "use client")
+export default async function DashboardPage() {
+  // Fetch data directly on the server
+  const user = await getUserProfile();
+
+  return (
+    <main className="container mx-auto p-6">
+      <h1 className="text-3xl font-bold mb-6">Dashboard</h1>
+      <Suspense fallback={<Skeleton className="h-[200px] w-full rounded-xl" />}>
+        <UserProfileCard user={user} />
+      </Suspense>
+    </main>
+  );
+}
+```
+
+### Example B: Server Action for Data Mutation
+*File: `src/features/users/actions.ts`*
+```typescript
+"use server";
+
+import { revalidatePath } from "next/cache";
+
+export type UpdateUserResponse = {
+  success: boolean;
+  message: string;
+};
+
+export async function updateUserName(formData: FormData): Promise<UpdateUserResponse> {
+  const newName = formData.get("name") as string;
+  
+  if (!newName || newName.length < 3) {
+    return { success: false, message: "Name must be at least 3 characters." };
+  }
+
+  // Perform database mutation here...
+  // await db.user.update(...)
+
+  // Revalidate the cache so the UI updates instantly
+  revalidatePath("/dashboard");
+
+  return { success: true, message: "Profile updated successfully." };
+}
+```
+
+### Example C: Client Component using Shadcn/ui & Server Actions
+*File: `src/features/users/components/edit-name-form.tsx`*
+```tsx
+"use client";
+
+import { useState, useTransition } from "react";
+import { updateUserName } from "@/features/users/actions";
+import { Button } from "@/components/ui/button";
+import { Input } from "@/components/ui/input";
+import { toast } from "@/components/ui/use-toast"; // shadcn toast
+
+export function EditNameForm() {
+  const [isPending, startTransition] = useTransition();
+
+  const handleSubmit = (formData: FormData) => {
+    startTransition(async () => {
+      const result = await updateUserName(formData);
+      
+      if (result.success) {
+        toast({ title: "Success", description: result.message });
+      } else {
+        toast({ title: "Error", description: result.message, variant: "destructive" });
+      }
+    });
+  };
+
+  return (
+    <form action={handleSubmit} className="flex gap-4 items-center">
+      <Input 
+        name="name" 
+        placeholder="Enter new name" 
+        required 
+        disabled={isPending} 
+        className="max-w-sm"
+      />
+      <Button type="submit" disabled={isPending}>
+        {isPending ? "Saving..." : "Save Name"}
+      </Button>
+    </form>
+  );
+}
+```