myaidev-method 0.2.8 → 0.2.9

package/src/server/user-management/layers.ts

@@ -0,0 +1,51 @@
+import { Layer } from "effect";
+import { LinuxUserService } from "./LinuxUserService";
+import { DirectoryService } from "./DirectoryService";
+import { QuotaService } from "./QuotaService";
+import { UserManagementService } from "./UserManagementService";
+
+/**
+ * User Management Layer Composition
+ *
+ * Provides Effect-TS layers for dependency injection of user management services.
+ */
+
+// Independent services (no dependencies)
+const IndependentServices = Layer.mergeAll(
+  LinuxUserService.Live,
+  DirectoryService.Live,
+  QuotaService.Live
+);
+
+// User management service depends on all base services
+const UserManagementWithDeps = Layer.provide(
+  UserManagementService.Live,
+  IndependentServices
+);
+
+// Complete layer with all services
+export const UserManagementLayer = Layer.mergeAll(
+  IndependentServices,
+  UserManagementWithDeps
+);
+
+/**
+ * Create a complete user management layer
+ *
+ * Usage:
+ * ```typescript
+ * const layer = createUserManagementLayer();
+ * const runtime = ManagedRuntime.make(layer);
+ *
+ * const result = await runtime.runPromise(
+ *   Effect.gen(function* () {
+ *     const userMgmt = yield* UserManagementService;
+ *     return yield* userMgmt.createUser({
+ *       username: "john",
+ *       email: "john@example.com",
+ *     });
+ *   })
+ * );
+ * ```
+ */
+export const createUserManagementLayer = () => UserManagementLayer;

package/src/shared/types.ts

@@ -0,0 +1,111 @@
+// Shared types for MyAIDev Method Web Server
+
+export interface User {
+  id: string;
+  username: string;
+  email: string;
+  passwordHash: string | null;
+  linuxUsername: string;
+  createdAt: number;
+  updatedAt: number;
+  isActive: boolean;
+  emailVerified: boolean;
+  failedLoginAttempts: number;
+  lastLoginAt: number | null;
+}
+
+export interface Session {
+  id: string;
+  userId: string;
+  tokenHash: string;
+  ipAddress: string | null;
+  userAgent: string | null;
+  createdAt: number;
+  expiresAt: number;
+  isRevoked: boolean;
+  revokedAt: number | null;
+}
+
+export interface OAuth2Provider {
+  id: string;
+  userId: string;
+  provider: "google" | "github" | "microsoft";
+  providerUserId: string;
+  providerEmail: string | null;
+  accessToken: string | null;
+  refreshToken: string | null;
+  tokenExpiresAt: number | null;
+  createdAt: number;
+  updatedAt: number;
+}
+
+export interface AuditLog {
+  id: string;
+  userId: string | null;
+  action: string;
+  resourceType: string | null;
+  resourceId: string | null;
+  ipAddress: string | null;
+  userAgent: string | null;
+  details: string | null;
+  createdAt: number;
+}
+
+// JWT Payload - compatible with jose library
+export interface JWTPayload {
+  sub: string; // user id
+  username: string;
+  email: string;
+  iat: number;
+  exp: number;
+  jti: string; // session id
+  [key: string]: unknown; // Index signature for jose compatibility
+}
+
+// API Request/Response types
+export interface RegisterRequest {
+  username: string;
+  email: string;
+  password: string;
+}
+
+export interface LoginRequest {
+  email: string;
+  password: string;
+}
+
+export interface AuthResponse {
+  user: {
+    id: string;
+    username: string;
+    email: string;
+    emailVerified: boolean;
+  };
+  token: string;
+}
+
+// Error types
+export class AuthError {
+  readonly _tag = "AuthError";
+  constructor(
+    readonly code: string,
+    readonly message: string,
+    readonly cause?: unknown
+  ) {}
+}
+
+export class ValidationError {
+  readonly _tag = "ValidationError";
+  constructor(
+    readonly field: string,
+    readonly message: string
+  ) {}
+}
+
+export class DatabaseError {
+  readonly _tag = "DatabaseError";
+  constructor(
+    readonly message: string,
+    readonly cause?: unknown
+  ) {}
+}

package/src/templates/claude/agents/payloadcms-publish.md

@@ -29,23 +29,24 @@ token_target: 2800
 
 ### Step 1: Configuration Validation
 ```
-1. Check PayloadCMS credentials in environment or config
+1. Check PayloadCMS credentials in environment (.env file)
 2. Verify required fields:
-   - PAYLOAD_URL: API endpoint
-   - PAYLOAD_EMAIL: user email
-   - PAYLOAD_PASSWORD: user password
-   - PAYLOAD_COLLECTION: default collection name (optional)
-3. If missing → prompt user to run /myai-configure payloadcms
+   - PAYLOADCMS_URL: PayloadCMS API endpoint
+   - PAYLOADCMS_EMAIL: User email for authentication
+   - PAYLOADCMS_PASSWORD: User password for authentication
+3. If missing → prompt user to configure .env file
+   (See .env.example for template)
 ```
 
 ### Step 2: Authentication
 ```
-1. Call authenticatePayload(url, email, password)
-2. Receive JWT token for API requests
-3. Handle auth errors:
-   - Invalid credentials → verify config
-   - Network errors → check URL accessibility
-   - Server errors → verify PayloadCMS instance health
+1. Authenticate using email/password to obtain JWT token
+2. POST to {PAYLOADCMS_URL}/api/users/login with credentials
+3. Extract JWT token from response (used for all subsequent API calls)
+4. Handle auth errors:
+   - Invalid credentials → verify PAYLOADCMS_EMAIL and PAYLOADCMS_PASSWORD
+   - Network errors → check PAYLOADCMS_URL accessibility
+   - Server errors → verify PayloadCMS instance is running
 ```
 
 ### Step 3: Content Processing
@@ -129,6 +130,25 @@ Agent:
 5. Report success with URLs
 ```
 
-## Configuration Integration
+## Configuration Setup
 
-Use `/myai-configure` to set up PayloadCMS credentials before publishing.
+### Required Environment Variables
+
+Add to your `.env` file:
+
+```bash
+PAYLOADCMS_URL=https://your-payloadcms-site.com
+PAYLOADCMS_EMAIL=your-email@example.com
+PAYLOADCMS_PASSWORD=your-password
+```
+
+### Authentication Flow
+
+1. **Email/Password Login**: Agent authenticates using credentials from .env
+2. **JWT Token**: Receives JWT token from PayloadCMS `/api/users/login` endpoint
+3. **API Requests**: Uses JWT token in `Authorization: JWT {token}` header for all API calls
+4. **Token Expiry**: Automatically re-authenticates if token expires
+
+### No API Keys Required
+
+PayloadCMS integration uses standard user authentication (email/password) to obtain JWT tokens. No separate API keys or application passwords needed.

package/src/templates/codex/commands/myai-astro-publish.md

@@ -1,8 +1,14 @@
 # Astro Content Publisher
 
-Publish markdown content to Astro static site with content collections support and git workflow: $ARGUMENTS
+Use the Task tool with subagent_type="astro-publish" to publish the markdown file provided in the arguments to Astro.
+
+Pass all command arguments to the agent, including the file path and any flags (--collection, --pages, --project, --branch, --no-push, --dry-run).
+
+The agent will handle frontmatter transformation, content collection validation, and git workflow automation for Astro static sites.
 
-Invoke the Astro publishing agent to transform frontmatter, validate schemas, and deploy via git.
+## Overview
+
+Publish markdown content to Astro static site with content collections support and git workflow: $ARGUMENTS
 
 ## Usage Examples
 

package/src/templates/codex/commands/myai-content-writer.md

@@ -1,8 +1,14 @@
 # Professional Content Writer
 
-Create comprehensive, well-researched content based on the provided topic: $ARGUMENTS
+Use the Task tool with subagent_type="content-writer" to create SEO-optimized content based on the provided topic.
+
+Pass all command arguments to the agent, including the topic, word count, tone, audience, SEO keywords, and publish_to_wordpress flag.
+
+The agent will handle research, planning, writing, optimization, and formatting with professional content creation expertise.
 
-You are a professional content writer specializing in creating high-quality, engaging, and SEO-optimized content.
+## Overview
+
+Create comprehensive, well-researched content based on the provided topic: $ARGUMENTS
 
 ## Core Competencies
 

package/src/templates/codex/commands/myai-coolify-deploy.md

@@ -1,8 +1,14 @@
 # Coolify Deployment Manager
 
-Execute Coolify deployment operations: $ARGUMENTS
+Use the Task tool with subagent_type="coolify-deploy" to execute Coolify deployment operations provided in the arguments.
+
+Pass all command arguments to the agent, including the operation type (deploy, status, list, logs, restart, env) and any configuration flags.
+
+The agent will handle Coolify API communication, deployment orchestration, and infrastructure management operations.
 
-Launch the Coolify deployment specialist agent for application deployment and infrastructure management.
+## Overview
+
+Execute Coolify deployment operations: $ARGUMENTS
 
 ## Available Operations
 

package/src/templates/codex/commands/myai-dev-architect.md

@@ -1,8 +1,14 @@
 # System Architecture Design
 
-Design scalable system architecture using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="MyAIDev Architect" to design scalable system architecture based on the provided requirements.
+
+Pass all command arguments to the agent, including the task description and any flags (--existing-code, --tech-stack, --output-dir).
+
+The agent will handle requirements analysis, architecture design, diagram creation, API specifications, and technology recommendations using MyAIDev Method's SPARC workflow.
 
-Invoke the MyAIDev Architect agent to create comprehensive system designs with architecture diagrams, API specifications, and technology recommendations.
+## Overview
+
+Design scalable system architecture using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## What It Does
 

package/src/templates/codex/commands/myai-dev-code.md

@@ -1,8 +1,14 @@
 # Feature Implementation
 
-Implement features and write production-ready code using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="MyAIDev Coder" to implement features based on the provided requirements.
+
+Pass all command arguments to the agent, including the task description and any flags (--architecture, --test-driven, --output-dir).
+
+The agent will handle implementation planning, clean code generation, SOLID principles application, error handling, and test creation using MyAIDev Method's SPARC workflow.
 
-Invoke the MyAIDev Coder agent to implement features based on architecture specifications, following best practices and clean code principles.
+## Overview
+
+Implement features and write production-ready code using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## What It Does
 

package/src/templates/codex/commands/myai-dev-docs.md

@@ -1,8 +1,14 @@
 # Comprehensive Documentation
 
-Generate comprehensive documentation using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="MyAIDev Documenter" to generate comprehensive documentation based on the provided requirements.
+
+Pass all command arguments to the agent, including the task description and any flags (--type, --format, --output-dir).
+
+The agent will handle documentation generation including API references, user guides, architecture docs, code examples, and visual diagrams using MyAIDev Method's SPARC workflow.
 
-Invoke the MyAIDev Documenter agent to create API documentation, user guides, architecture docs, and technical specifications.
+## Overview
+
+Generate comprehensive documentation using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## What It Does
 

package/src/templates/codex/commands/myai-dev-review.md

@@ -1,8 +1,14 @@
 # Code Quality Review
 
-Perform comprehensive code review using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="MyAIDev Reviewer" to perform comprehensive code review based on the provided scope.
+
+Pass all command arguments to the agent, including the task description and any flags (--security, --performance, --output-dir).
+
+The agent will handle code quality analysis, security vulnerability assessment, performance review, and best practices validation using MyAIDev Method's SPARC workflow.
 
-Invoke the MyAIDev Reviewer agent to analyze code quality, security vulnerabilities, performance issues, and best practices compliance.
+## Overview
+
+Perform comprehensive code review using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## What It Does
 

package/src/templates/codex/commands/myai-dev-test.md

@@ -1,8 +1,14 @@
 # Comprehensive Testing
 
-Write and execute comprehensive tests using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="MyAIDev Tester" to create comprehensive tests based on the provided requirements.
+
+Pass all command arguments to the agent, including the task description and any flags (--coverage, --integration, --framework, --output-dir).
+
+The agent will handle test suite creation, unit and integration test generation, coverage analysis, and quality gate validation using MyAIDev Method's SPARC workflow.
 
-Invoke the MyAIDev Tester agent to create unit tests, integration tests, and validate code quality with coverage analysis.
+## Overview
+
+Write and execute comprehensive tests using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## What It Does
 

package/src/templates/codex/commands/myai-docusaurus-publish.md

@@ -1,8 +1,14 @@
 # Docusaurus Content Publisher
 
-Publish markdown content to Docusaurus static site generator with automatic git workflow: $ARGUMENTS
+Use the Task tool with subagent_type="Docusaurus Publishing Agent" to publish the markdown file provided in the arguments to Docusaurus.
+
+Pass all command arguments to the agent, including the file path and any flags (--type, --project, --branch, --no-push, --dry-run).
+
+The agent will handle content transformation, file placement, and git workflow automation for Docusaurus static site generator.
 
-Invoke the Docusaurus publishing agent to transform content and deploy via git.
+## Overview
+
+Publish markdown content to Docusaurus static site generator with automatic git workflow: $ARGUMENTS
 
 ## Usage Examples
 

package/src/templates/codex/commands/myai-mintlify-publish.md

@@ -1,8 +1,14 @@
 # Mintlify Documentation Publisher
 
-Publish markdown/MDX content to Mintlify documentation site with automatic navigation updates: $ARGUMENTS
+Use the Task tool with subagent_type="mintlify-publish" to publish the markdown/MDX file provided in the arguments to Mintlify.
+
+Pass all command arguments to the agent, including the file path and any flags (--nav-section, --project, --branch, --no-push, --dry-run).
+
+The agent will handle content transformation, mint.json navigation updates, and git workflow automation for Mintlify documentation sites.
 
-Invoke the Mintlify publishing agent to transform content, update mint.json, and deploy via git.
+## Overview
+
+Publish markdown/MDX content to Mintlify documentation site with automatic navigation updates: $ARGUMENTS
 
 ## Usage Examples
 

package/src/templates/codex/commands/myai-payloadcms-publish.md

@@ -1,8 +1,14 @@
 # PayloadCMS Content Publisher
 
-Publish markdown content to PayloadCMS headless CMS: $ARGUMENTS
+Use the Task tool with subagent_type="PayloadCMS Publisher" to publish the markdown file provided in the arguments to PayloadCMS.
+
+Pass all command arguments to the agent, including the file path and any flags (--status, --collection, --id, --dry-run, --verbose).
+
+The agent will handle authentication, markdown conversion to Lexical format, and publishing to your PayloadCMS instance.
 
-Invoke the PayloadCMS publishing agent to convert markdown to Lexical format and publish to your PayloadCMS instance.
+## Overview
+
+Publish markdown content to PayloadCMS headless CMS: $ARGUMENTS
 
 ## Usage Examples
 
@@ -22,7 +28,15 @@ Invoke the PayloadCMS publishing agent to convert markdown to Lexical format and
 
 ## Prerequisites
 
-Configure PayloadCMS credentials: `/myai-configure`
+Configure PayloadCMS credentials in your `.env` file:
+
+```bash
+PAYLOADCMS_URL=https://your-payloadcms-site.com
+PAYLOADCMS_EMAIL=your-email@example.com
+PAYLOADCMS_PASSWORD=your-password
+```
+
+The agent will authenticate using these credentials to obtain a JWT token for API access.
 
 ## Examples
 

package/src/templates/codex/commands/myai-sparc-workflow.md

@@ -1,8 +1,14 @@
 # SPARC Development Workflow
 
-Execute the complete 5-phase SPARC development workflow using MyAIDev Method's systematic approach: $ARGUMENTS
+Use the Task tool with subagent_type="SPARC Workflow Orchestrator" to execute the complete 5-phase development workflow based on the provided requirements.
+
+Pass all command arguments to the agent, including the task description and any flags (--phases, --tech-stack, --output-dir, --test-framework, --skip-phase).
+
+The agent will orchestrate all development phases in sequence: Architecture → Implementation → Testing → Review → Documentation using MyAIDev Method's systematic SPARC approach.
 
-Orchestrates all development agents in sequence: Architecture → Implementation → Testing → Review → Documentation
+## Overview
+
+Execute the complete 5-phase SPARC development workflow using MyAIDev Method's systematic approach: $ARGUMENTS
 
 ## SPARC Workflow Phases
 

package/src/templates/codex/commands/myai-wordpress-admin.md

@@ -1,8 +1,14 @@
 # WordPress Site Administrator
 
-Execute WordPress administration operations: $ARGUMENTS
+Use the Task tool with subagent_type="wordpress-admin" to execute WordPress administration operations provided in the arguments.
+
+Pass all command arguments to the agent, including the operation type (security-scan, health-check, speed-test, plugin-manage, etc.) and any configuration flags.
+
+The agent will handle comprehensive site management, security analysis, performance optimization, and administrative tasks via WordPress REST API and optional SSH access.
 
-Launch the WordPress administrator agent for comprehensive site management, security analysis, and performance optimization.
+## Overview
+
+Execute WordPress administration operations: $ARGUMENTS
 
 ## Available Operations
 

package/src/templates/codex/commands/myai-wordpress-publish.md

@@ -1,8 +1,14 @@
 # WordPress Content Publisher
 
-Publish the specified markdown file to WordPress: $ARGUMENTS
+Use the Task tool with subagent_type="wordpress-admin" to publish the markdown file provided in the arguments to WordPress.
+
+Pass all command arguments to the agent, including the file path and any flags (--status, --gutenberg, --classic).
+
+The agent will handle reading the file, parsing frontmatter, converting content format, and publishing using the WordPress REST API.
 
-Read and publish the file to WordPress using native tools and the WordPress REST API.
+## Overview
+
+Publish the specified markdown file to WordPress: $ARGUMENTS
 
 ## Process