proagents 1.0.0

package/proagents/config/standards/README.md

@@ -0,0 +1,58 @@
+# Project Standards Configuration
+
+Place your project-specific coding standards here. These override the default templates.
+
+---
+
+## How It Works
+
+1. Copy templates from `/proagents/standards/examples/`
+2. Customize for your project
+3. ProAgents will use your standards during code generation and review
+
+---
+
+## Files to Create
+
+| File | Purpose |
+|------|---------|
+| `coding-standards.md` | Code style and conventions |
+| `architecture-rules.md` | Architectural patterns and constraints |
+| `naming-conventions.md` | Naming rules for files, functions, variables |
+| `testing-standards.md` | Testing requirements and patterns |
+
+---
+
+## Quick Start
+
+```bash
+# Copy example standards
+cp proagents/standards/examples/react-nextjs.md \
+   proagents/config/standards/coding-standards.md
+
+# Edit for your project
+vim proagents/config/standards/coding-standards.md
+```
+
+---
+
+## Example Structure
+
+```
+proagents/config/standards/
+├── README.md                    # This file
+├── coding-standards.md          # Your coding standards
+├── architecture-rules.md        # Your architecture rules
+├── naming-conventions.md        # Your naming conventions
+└── testing-standards.md         # Your testing standards
+```
+
+---
+
+## Priority Order
+
+When standards conflict, priority is:
+
+1. `config/standards/` (highest - your project)
+2. `standards/examples/` (framework defaults)
+3. Auto-detected patterns (lowest)

package/proagents/config/standards/architecture-rules.template.md

@@ -0,0 +1,124 @@
+# Architecture Rules Template
+
+Copy this file to `architecture-rules.md` and customize for your project.
+
+---
+
+## Project Type: [Web Frontend | Full-Stack | Backend | Mobile]
+
+---
+
+## Directory Structure
+
+```
+[Define your expected directory structure]
+
+src/
+├── [folder]/     # [purpose]
+├── [folder]/     # [purpose]
+└── [folder]/     # [purpose]
+```
+
+---
+
+## Dependency Rules
+
+### Allowed Dependencies
+
+| Layer | Can Import From |
+|-------|-----------------|
+| Components | hooks, utils, types, services |
+| Pages | components, hooks, services |
+| Services | utils, types |
+| Utils | types only |
+
+### Forbidden Dependencies
+
+- Components CANNOT import from pages
+- Utils CANNOT import from services
+- No circular dependencies
+
+---
+
+## State Management
+
+**Approach:** [Redux | Zustand | Context | MobX | None]
+
+Rules:
+- Global state for: [list what goes in global state]
+- Local state for: [list what stays local]
+- Server state managed by: [React Query | SWR | Apollo | etc.]
+
+---
+
+## API Patterns
+
+**Style:** [REST | GraphQL | tRPC | gRPC]
+
+Rules:
+- All API calls through: `[service layer path]`
+- Error handling: [centralized | per-call]
+- Authentication: [how auth is handled]
+
+---
+
+## Component Patterns
+
+**Style:** [Functional only | Class allowed]
+
+Rules:
+- Props interface above component
+- Destructure props in signature
+- Use memo() for: [criteria]
+- Max component size: [lines or recommendation]
+
+---
+
+## Database Access
+
+**ORM/Query Builder:** [Prisma | TypeORM | Drizzle | Raw SQL]
+
+Rules:
+- All queries in: `[repository/service path]`
+- Transactions for: [multi-table operations]
+- No raw SQL in: [controllers/routes]
+
+---
+
+## Authentication & Authorization
+
+**Method:** [JWT | Session | OAuth]
+
+Rules:
+- Auth middleware on: [which routes]
+- Role checks in: [where]
+- Token storage: [localStorage | httpOnly cookie | memory]
+
+---
+
+## Error Handling
+
+**Strategy:** [Error boundaries | Global handler | Per-component]
+
+Rules:
+- All errors logged to: [service]
+- User-facing errors: [how handled]
+- API errors: [format and handling]
+
+---
+
+## Performance Requirements
+
+- Bundle size limit: [size]
+- Initial load time: [target]
+- API response time: [target]
+- Core Web Vitals targets: [LCP, FID, CLS]
+
+---
+
+## Security Requirements
+
+- Input validation: [where and how]
+- Output encoding: [XSS prevention]
+- CSRF protection: [method]
+- Rate limiting: [requirements]

package/proagents/config/standards/coding-standards.template.md

@@ -0,0 +1,107 @@
+# Coding Standards Template
+
+Copy this file to `coding-standards.md` and customize for your project.
+
+---
+
+## Language: [JavaScript/TypeScript/Python/Go/etc.]
+
+### Code Style
+
+```yaml
+indentation: [2 spaces | 4 spaces | tabs]
+max_line_length: [80 | 100 | 120]
+quotes: [single | double]
+semicolons: [required | omit]
+trailing_commas: [always | never | es5]
+```
+
+### Formatting
+
+- Use [Prettier | Black | gofmt | etc.] for auto-formatting
+- Configuration file: [.prettierrc | pyproject.toml | etc.]
+
+---
+
+## TypeScript Specific
+
+```yaml
+strict_mode: true
+no_any: true
+explicit_return_types: [always | public_only | never]
+prefer_const: true
+no_unused_variables: true
+```
+
+---
+
+## Import Organization
+
+Order imports as follows:
+1. [Built-in modules]
+2. [External dependencies]
+3. [Internal absolute imports]
+4. [Relative imports]
+5. [Style imports]
+
+Example:
+```typescript
+// 1. Built-in
+import { useState } from 'react';
+
+// 2. External
+import axios from 'axios';
+
+// 3. Internal absolute
+import { Button } from '@/components';
+
+// 4. Relative
+import { helper } from './utils';
+
+// 5. Styles
+import styles from './Component.module.css';
+```
+
+---
+
+## Comments
+
+- Use JSDoc/docstrings for public APIs
+- Inline comments only for non-obvious logic
+- TODO format: `// TODO(author): description`
+- No commented-out code in production
+
+---
+
+## Error Handling
+
+- Always handle errors explicitly
+- Use typed error classes
+- Log errors with context
+- User-facing errors should be friendly
+
+---
+
+## File Organization
+
+```
+src/
+├── components/     # UI components
+├── hooks/          # Custom hooks
+├── services/       # API/business logic
+├── utils/          # Pure utility functions
+├── types/          # TypeScript types
+└── constants/      # Constants and config
+```
+
+---
+
+## Naming Conventions
+
+See `naming-conventions.md` for detailed rules.
+
+---
+
+## Testing Requirements
+
+See `testing-standards.md` for detailed rules.

package/proagents/config/standards/naming-conventions.template.md

@@ -0,0 +1,114 @@
+# Naming Conventions Template
+
+Copy this file to `naming-conventions.md` and customize for your project.
+
+---
+
+## File Naming
+
+| Type | Convention | Example |
+|------|------------|---------|
+| Components | [PascalCase | kebab-case] | `UserProfile.tsx` or `user-profile.tsx` |
+| Hooks | camelCase with `use` prefix | `useUserData.ts` |
+| Utilities | [camelCase | kebab-case] | `formatDate.ts` or `format-date.ts` |
+| Constants | [UPPER_SNAKE | camelCase] | `API_ENDPOINTS.ts` |
+| Types | PascalCase | `UserTypes.ts` |
+| Tests | Same as source + `.test` | `UserProfile.test.tsx` |
+| Styles | Same as component + `.module` | `UserProfile.module.css` |
+
+---
+
+## Variable Naming
+
+| Type | Convention | Example |
+|------|------------|---------|
+| Variables | camelCase | `userName`, `isLoading` |
+| Constants | UPPER_SNAKE_CASE | `MAX_RETRIES`, `API_URL` |
+| Booleans | `is`, `has`, `can` prefix | `isActive`, `hasPermission` |
+| Arrays | Plural nouns | `users`, `items` |
+| Objects | Singular nouns | `user`, `config` |
+
+---
+
+## Function Naming
+
+| Type | Convention | Example |
+|------|------------|---------|
+| Functions | camelCase, verb prefix | `getUserData`, `calculateTotal` |
+| Event handlers | `handle` + Event | `handleClick`, `handleSubmit` |
+| Async functions | Verb describing action | `fetchUser`, `saveData` |
+| Predicates | `is`, `has`, `can` prefix | `isValid`, `hasAccess` |
+| Transformers | `to` or `format` prefix | `toUpperCase`, `formatDate` |
+
+---
+
+## Component Naming
+
+| Type | Convention | Example |
+|------|------------|---------|
+| Components | PascalCase, noun-based | `UserCard`, `NavigationMenu` |
+| Pages | PascalCase + `Page` suffix | `HomePage`, `ProfilePage` |
+| Layouts | PascalCase + `Layout` suffix | `MainLayout`, `AuthLayout` |
+| Providers | PascalCase + `Provider` suffix | `AuthProvider`, `ThemeProvider` |
+| HOCs | `with` prefix | `withAuth`, `withLoading` |
+
+---
+
+## Type/Interface Naming
+
+| Type | Convention | Example |
+|------|------------|---------|
+| Interfaces | PascalCase (no `I` prefix) | `User`, `ApiResponse` |
+| Types | PascalCase | `UserStatus`, `RequestConfig` |
+| Props | Component name + `Props` | `UserCardProps` |
+| Enums | PascalCase | `UserRole`, `OrderStatus` |
+| Generics | Single uppercase or descriptive | `T`, `TData`, `TResponse` |
+
+---
+
+## API/Database Naming
+
+| Type | Convention | Example |
+|------|------------|---------|
+| Endpoints | kebab-case, plural | `/api/users`, `/api/order-items` |
+| Table names | snake_case, plural | `users`, `order_items` |
+| Column names | snake_case | `created_at`, `user_id` |
+| Foreign keys | Referenced table + `_id` | `user_id`, `order_id` |
+
+---
+
+## CSS/Styling Naming
+
+| Type | Convention | Example |
+|------|------------|---------|
+| CSS Classes | [BEM | camelCase | kebab-case] | `.user-card__title` |
+| CSS Variables | kebab-case with `--` | `--primary-color` |
+| Tailwind | Standard Tailwind | `bg-blue-500` |
+
+---
+
+## Test Naming
+
+```typescript
+// Test files
+UserProfile.test.tsx
+
+// Describe blocks
+describe('UserProfile', () => {
+
+// Test cases - should describe behavior
+it('renders user name when provided', () => {
+it('shows loading state while fetching', () => {
+it('calls onEdit when edit button clicked', () => {
+```
+
+---
+
+## Git Branch Naming
+
+| Type | Convention | Example |
+|------|------------|---------|
+| Features | `feature/[ticket]-description` | `feature/PROJ-123-user-auth` |
+| Bug fixes | `fix/[ticket]-description` | `fix/PROJ-456-login-error` |
+| Hotfixes | `hotfix/description` | `hotfix/critical-payment-bug` |
+| Releases | `release/version` | `release/1.2.0` |

package/proagents/config/standards/testing-standards.template.md

@@ -0,0 +1,213 @@
+# Testing Standards Template
+
+Copy this file to `testing-standards.md` and customize for your project.
+
+---
+
+## Testing Framework
+
+**Unit Tests:** [Jest | Vitest | Mocha | pytest]
+**Integration Tests:** [Jest | Supertest | pytest]
+**E2E Tests:** [Playwright | Cypress | Selenium]
+**Component Tests:** [Testing Library | Enzyme]
+
+---
+
+## Coverage Requirements
+
+| Type | Minimum Coverage |
+|------|------------------|
+| Overall | [80% | 85% | 90%] |
+| Critical paths | [95% | 100%] |
+| New code | [80% | 90%] |
+| Utilities | [90% | 100%] |
+
+---
+
+## Test File Organization
+
+```
+src/
+├── components/
+│   ├── UserCard.tsx
+│   └── UserCard.test.tsx      # Co-located
+└── __tests__/                  # Or centralized
+    └── integration/
+        └── user-flow.test.ts
+```
+
+**Approach:** [Co-located | Centralized | Both]
+
+---
+
+## Unit Test Structure
+
+```typescript
+describe('ComponentName', () => {
+  // Setup
+  beforeEach(() => {
+    // Common setup
+  });
+
+  // Group related tests
+  describe('when [condition]', () => {
+    it('should [expected behavior]', () => {
+      // Arrange
+      // Act
+      // Assert
+    });
+  });
+});
+```
+
+---
+
+## What to Test
+
+### Components
+- [ ] Renders without crashing
+- [ ] Renders correct content based on props
+- [ ] Handles user interactions
+- [ ] Shows correct states (loading, error, empty)
+- [ ] Accessibility (labels, roles)
+
+### Hooks
+- [ ] Returns correct initial state
+- [ ] Updates state correctly
+- [ ] Handles edge cases
+- [ ] Cleans up properly
+
+### Services/API
+- [ ] Makes correct API calls
+- [ ] Handles success responses
+- [ ] Handles error responses
+- [ ] Handles loading states
+
+### Utilities
+- [ ] Returns correct output for valid input
+- [ ] Handles edge cases
+- [ ] Throws/returns appropriate errors for invalid input
+
+---
+
+## Mocking Guidelines
+
+### Do Mock
+- External API calls
+- Third-party services
+- Time/date functions
+- Random values
+- File system operations
+
+### Don't Mock
+- The component/function under test
+- Simple utility functions
+- React hooks (use Testing Library's approach)
+
+---
+
+## Test Data
+
+```typescript
+// Use factories for test data
+const createUser = (overrides = {}): User => ({
+  id: 'user-1',
+  name: 'Test User',
+  email: 'test@example.com',
+  ...overrides,
+});
+
+// Usage
+const user = createUser({ name: 'Custom Name' });
+```
+
+---
+
+## Async Testing
+
+```typescript
+// Always await async operations
+it('fetches user data', async () => {
+  render(<UserProfile userId="1" />);
+
+  // Wait for loading to finish
+  await waitFor(() => {
+    expect(screen.getByText('John Doe')).toBeInTheDocument();
+  });
+});
+```
+
+---
+
+## Integration Test Patterns
+
+```typescript
+describe('User Authentication Flow', () => {
+  it('allows user to log in and view dashboard', async () => {
+    // 1. Navigate to login
+    // 2. Fill in credentials
+    // 3. Submit form
+    // 4. Verify redirect to dashboard
+    // 5. Verify user data displayed
+  });
+});
+```
+
+---
+
+## E2E Test Patterns
+
+```typescript
+// Playwright example
+test('complete checkout flow', async ({ page }) => {
+  // 1. Add item to cart
+  await page.goto('/products/1');
+  await page.click('[data-testid="add-to-cart"]');
+
+  // 2. Go to checkout
+  await page.click('[data-testid="checkout"]');
+
+  // 3. Fill shipping info
+  // 4. Complete payment
+  // 5. Verify confirmation
+});
+```
+
+---
+
+## Snapshot Testing
+
+**When to use:**
+- UI components with stable output
+- Error messages
+- Generated content
+
+**When NOT to use:**
+- Dynamic content
+- Frequently changing components
+- Large component trees
+
+---
+
+## Performance Testing
+
+- Measure render times for critical components
+- Test with realistic data volumes
+- Monitor bundle size changes
+- Set performance budgets
+
+---
+
+## CI/CD Integration
+
+```yaml
+# Example CI config
+test:
+  script:
+    - npm run test:unit
+    - npm run test:integration
+    - npm run test:e2e
+  coverage:
+    minimum: 80%
+    fail_under: true
+```

package/proagents/config/templates/README.md

@@ -0,0 +1,74 @@
+# Project Templates Configuration
+
+Place your project-specific code templates here. ProAgents uses these when generating new code.
+
+---
+
+## How It Works
+
+1. Create templates for your common patterns
+2. ProAgents uses these templates when generating code
+3. Templates support variables and conditionals
+
+---
+
+## Template Files
+
+| File | Purpose |
+|------|---------|
+| `component.template.tsx` | React component template |
+| `hook.template.ts` | Custom hook template |
+| `api-route.template.ts` | API route/endpoint template |
+| `test.template.ts` | Test file template |
+| `service.template.ts` | Service class template |
+
+---
+
+## Quick Start
+
+```bash
+# Copy a template
+cp proagents/config/templates/component.template.tsx \
+   proagents/config/templates/component.template.tsx
+
+# Edit for your project
+vim proagents/config/templates/component.template.tsx
+```
+
+---
+
+## Template Variables
+
+Templates support these variables:
+
+| Variable | Description |
+|----------|-------------|
+| `{{ComponentName}}` | PascalCase name |
+| `{{componentName}}` | camelCase name |
+| `{{component-name}}` | kebab-case name |
+| `{{COMPONENT_NAME}}` | UPPER_SNAKE_CASE name |
+| `{{description}}` | Component description |
+| `{{date}}` | Current date |
+| `{{author}}` | Current user |
+
+---
+
+## Conditional Sections
+
+```typescript
+// {{#if hasProps}}
+interface {{ComponentName}}Props {
+  // Props here
+}
+// {{/if}}
+```
+
+---
+
+## Example Usage
+
+When you ask ProAgents to create a new component, it will:
+1. Load your `component.template.tsx`
+2. Replace variables with actual values
+3. Apply your coding standards
+4. Generate the file