@fermindi/pwn-cli 0.1.1 → 0.3.0

package/templates/workspace/.ai/patterns/backend/README.md

@@ -1,126 +1,126 @@
-# Backend Patterns
-
-This directory contains design patterns and best practices for backend development.
-
-## Overview
-
-Backend patterns cover:
-- Express.js route structure
-- REST API design
-- Database queries and migrations
-- Error handling and logging
-- Authentication and authorization
-- Data validation
-- Performance optimization
-- Middleware patterns
-- Integration patterns
-
-## Structure
-
-```
-backend/
-├── README.md                  # This file
-├── express/                   # Express.js patterns
-│   └── README.md             # Express routing and middleware
-├── database/                  # Database patterns
-│   └── README.md             # Query and ORM patterns
-├── api-design/                # REST API patterns
-│   └── README.md             # API structure and conventions
-├── security/                  # Security patterns
-│   └── README.md             # Auth, validation, sanitization
-└── integration/               # Integration patterns
-    └── README.md             # Working with external services
-```
-
-## Auto-Apply Triggers
-
-These patterns are automatically loaded when:
-
-- **File:** `*.routes.ts`, `routes/*.ts` (Express routes)
-- **Import:** `from.*express`, `import.*Router`
-- **Path:** `src/routes/`, `src/api/`
-- **Keyword:** `app.get`, `app.post`, `router.use`
-
-See `patterns/index.md` for trigger configuration.
-
-## Common Patterns
-
-### Route Structure
-```typescript
-// Group related routes together
-// Use middleware for common operations (auth, logging)
-// Keep route handlers thin, logic in services
-// Consistent error handling
-```
-
-### Express Middleware
-- Authentication middleware early in chain
-- Error handling middleware last
-- Logging middleware for all requests
-- Request validation middleware
-- CORS middleware appropriately configured
-
-### API Design
-- RESTful conventions (GET, POST, PUT, DELETE)
-- Consistent response format
-- Proper HTTP status codes
-- Pagination for list endpoints
-- Filtering and sorting support
-
-### Database Queries
-- Use ORM/query builder (not raw SQL)
-- Eager load relationships when needed
-- Avoid N+1 query problems
-- Index frequently-queried columns
-- Use transactions for multi-step operations
-
-### Error Handling
-- Custom error classes for different error types
-- Consistent error response format
-- Log errors with full context
-- Don't expose internal errors to clients
-- Use HTTP status codes correctly
-
-### Validation
-- Validate all user input
-- Use schema validation (Zod, Joi, etc.)
-- Sanitize input to prevent injection
-- Custom validation rules for domain logic
-- Clear error messages for users
-
-### Authentication
-- Use industry-standard auth (JWT, OAuth, etc.)
-- Secure token storage
-- Token expiration and refresh strategy
-- Role-based access control (RBAC)
-- Audit logging of auth events
-
-## Usage
-
-1. Read the relevant sub-directory README for your task
-2. Check code examples for reference implementations
-3. Follow patterns in new routes and services
-4. Update patterns if you discover improvements
-
-## Contributing
-
-Found a better pattern?
-
-1. Document it with examples
-2. Add to appropriate subdirectory
-3. Update this README
-4. Commit with message: `docs: add [pattern name] pattern`
-5. Update triggers in `patterns/index.md` if widely applicable
-
-## Links
-
-- [Express Patterns](express/README.md)
-- [Database Patterns](database/README.md)
-- [API Design](api-design/README.md)
-- [Security Patterns](security/README.md)
-- [Integration Patterns](integration/README.md)
-
-## Version
-
-**Last Updated:** (Set on template injection)
-**Maintained By:** Development Team
+# Backend Patterns
+
+This directory contains design patterns and best practices for backend development.
+
+## Overview
+
+Backend patterns cover:
+- Express.js route structure
+- REST API design
+- Database queries and migrations
+- Error handling and logging
+- Authentication and authorization
+- Data validation
+- Performance optimization
+- Middleware patterns
+- Integration patterns
+
+## Structure
+
+```
+backend/
+├── README.md                  # This file
+├── express/                   # Express.js patterns
+│   └── README.md             # Express routing and middleware
+├── database/                  # Database patterns
+│   └── README.md             # Query and ORM patterns
+├── api-design/                # REST API patterns
+│   └── README.md             # API structure and conventions
+├── security/                  # Security patterns
+│   └── README.md             # Auth, validation, sanitization
+└── integration/               # Integration patterns
+    └── README.md             # Working with external services
+```
+
+## Auto-Apply Triggers
+
+These patterns are automatically loaded when:
+
+- **File:** `*.routes.ts`, `routes/*.ts` (Express routes)
+- **Import:** `from.*express`, `import.*Router`
+- **Path:** `src/routes/`, `src/api/`
+- **Keyword:** `app.get`, `app.post`, `router.use`
+
+See `patterns/index.md` for trigger configuration.
+
+## Common Patterns
+
+### Route Structure
+```typescript
+// Group related routes together
+// Use middleware for common operations (auth, logging)
+// Keep route handlers thin, logic in services
+// Consistent error handling
+```
+
+### Express Middleware
+- Authentication middleware early in chain
+- Error handling middleware last
+- Logging middleware for all requests
+- Request validation middleware
+- CORS middleware appropriately configured
+
+### API Design
+- RESTful conventions (GET, POST, PUT, DELETE)
+- Consistent response format
+- Proper HTTP status codes
+- Pagination for list endpoints
+- Filtering and sorting support
+
+### Database Queries
+- Use ORM/query builder (not raw SQL)
+- Eager load relationships when needed
+- Avoid N+1 query problems
+- Index frequently-queried columns
+- Use transactions for multi-step operations
+
+### Error Handling
+- Custom error classes for different error types
+- Consistent error response format
+- Log errors with full context
+- Don't expose internal errors to clients
+- Use HTTP status codes correctly
+
+### Validation
+- Validate all user input
+- Use schema validation (Zod, Joi, etc.)
+- Sanitize input to prevent injection
+- Custom validation rules for domain logic
+- Clear error messages for users
+
+### Authentication
+- Use industry-standard auth (JWT, OAuth, etc.)
+- Secure token storage
+- Token expiration and refresh strategy
+- Role-based access control (RBAC)
+- Audit logging of auth events
+
+## Usage
+
+1. Read the relevant sub-directory README for your task
+2. Check code examples for reference implementations
+3. Follow patterns in new routes and services
+4. Update patterns if you discover improvements
+
+## Contributing
+
+Found a better pattern?
+
+1. Document it with examples
+2. Add to appropriate subdirectory
+3. Update this README
+4. Commit with message: `docs: add [pattern name] pattern`
+5. Update triggers in `patterns/index.md` if widely applicable
+
+## Links
+
+- [Express Patterns](express/README.md)
+- [Database Patterns](database/README.md)
+- [API Design](api-design/README.md)
+- [Security Patterns](security/README.md)
+- [Integration Patterns](integration/README.md)
+
+## Version
+
+**Last Updated:** (Set on template injection)
+**Maintained By:** Development Team

package/templates/workspace/.ai/patterns/frontend/README.md

@@ -1,103 +1,103 @@
-# Frontend Patterns
-
-This directory contains design patterns and best practices for frontend development.
-
-## Overview
-
-Frontend patterns cover:
-- React component architecture
-- TypeScript type definitions
-- Styling and CSS strategies
-- State management
-- Performance optimization
-- Accessibility (a11y)
-- Component composition
-- Hook patterns
-
-## Structure
-
-```
-frontend/
-├── README.md                  # This file
-├── react/                     # React-specific patterns
-│   └── README.md             # React component patterns
-├── styling/                   # CSS and styling patterns
-│   └── README.md             # Styling strategies
-├── component-libs/            # UI component library patterns
-│   └── README.md             # Working with component libraries
-└── accessibility/             # A11y patterns
-    └── README.md             # Accessibility patterns
-```
-
-## Auto-Apply Triggers
-
-These patterns are automatically loaded when:
-
-- **File:** `*.tsx`, `*.jsx` (React components)
-- **Import:** `import.*React`, `from.*react`
-- **Path:** `src/components/`
-- **Keyword:** `function Component`, `export default`
-
-See `patterns/index.md` for trigger configuration.
-
-## Common Patterns
-
-### Component Architecture
-- Functional components with hooks (not class components)
-- One component per file
-- Props interfaces at top of file
-- Hooks (useState, useEffect, useContext)
-- Custom hooks for reusable logic
-
-### TypeScript
-- Define interfaces for component props
-- Use `React.FC<Props>` for component type
-- Strict null checks enabled
-- Export types alongside components
-
-### State Management
-- Local state with `useState` for component-only state
-- Context API for shared state
-- Consider Redux/Zustand for complex state
-- Avoid prop drilling (use Context instead)
-
-### Performance
-- Memoize expensive components with `React.memo`
-- Use `useCallback` for stable function references
-- Use `useMemo` for expensive computations
-- Lazy load routes with `React.lazy`
-
-### Styling
-- TailwindCSS for utility-first styling
-- CSS modules for scoped styles
-- Avoid inline styles except for dynamic values
-- Use design tokens for consistency
-
-## Usage
-
-1. Read the relevant sub-directory README for your task
-2. Check code examples for reference implementations
-3. Follow patterns in new components
-4. Update patterns if you discover improvements
-
-## Contributing
-
-Found a better pattern?
-
-1. Document it with examples
-2. Add to appropriate subdirectory
-3. Update this README
-4. Commit with message: `docs: add [pattern name] pattern`
-5. Update triggers in `patterns/index.md` if widely applicable
-
-## Links
-
-- [React Component Patterns](react/README.md)
-- [Styling Strategies](styling/README.md)
-- [Component Libraries](component-libs/README.md)
-- [Accessibility Patterns](accessibility/README.md)
-
-## Version
-
-**Last Updated:** (Set on template injection)
-**Maintained By:** Development Team
+# Frontend Patterns
+
+This directory contains design patterns and best practices for frontend development.
+
+## Overview
+
+Frontend patterns cover:
+- React component architecture
+- TypeScript type definitions
+- Styling and CSS strategies
+- State management
+- Performance optimization
+- Accessibility (a11y)
+- Component composition
+- Hook patterns
+
+## Structure
+
+```
+frontend/
+├── README.md                  # This file
+├── react/                     # React-specific patterns
+│   └── README.md             # React component patterns
+├── styling/                   # CSS and styling patterns
+│   └── README.md             # Styling strategies
+├── component-libs/            # UI component library patterns
+│   └── README.md             # Working with component libraries
+└── accessibility/             # A11y patterns
+    └── README.md             # Accessibility patterns
+```
+
+## Auto-Apply Triggers
+
+These patterns are automatically loaded when:
+
+- **File:** `*.tsx`, `*.jsx` (React components)
+- **Import:** `import.*React`, `from.*react`
+- **Path:** `src/components/`
+- **Keyword:** `function Component`, `export default`
+
+See `patterns/index.md` for trigger configuration.
+
+## Common Patterns
+
+### Component Architecture
+- Functional components with hooks (not class components)
+- One component per file
+- Props interfaces at top of file
+- Hooks (useState, useEffect, useContext)
+- Custom hooks for reusable logic
+
+### TypeScript
+- Define interfaces for component props
+- Use `React.FC<Props>` for component type
+- Strict null checks enabled
+- Export types alongside components
+
+### State Management
+- Local state with `useState` for component-only state
+- Context API for shared state
+- Consider Redux/Zustand for complex state
+- Avoid prop drilling (use Context instead)
+
+### Performance
+- Memoize expensive components with `React.memo`
+- Use `useCallback` for stable function references
+- Use `useMemo` for expensive computations
+- Lazy load routes with `React.lazy`
+
+### Styling
+- TailwindCSS for utility-first styling
+- CSS modules for scoped styles
+- Avoid inline styles except for dynamic values
+- Use design tokens for consistency
+
+## Usage
+
+1. Read the relevant sub-directory README for your task
+2. Check code examples for reference implementations
+3. Follow patterns in new components
+4. Update patterns if you discover improvements
+
+## Contributing
+
+Found a better pattern?
+
+1. Document it with examples
+2. Add to appropriate subdirectory
+3. Update this README
+4. Commit with message: `docs: add [pattern name] pattern`
+5. Update triggers in `patterns/index.md` if widely applicable
+
+## Links
+
+- [React Component Patterns](react/README.md)
+- [Styling Strategies](styling/README.md)
+- [Component Libraries](component-libs/README.md)
+- [Accessibility Patterns](accessibility/README.md)
+
+## Version
+
+**Last Updated:** (Set on template injection)
+**Maintained By:** Development Team