omgkit 2.9.1 → 2.10.1

package/plugin/workflows/fullstack/authentication.md

@@ -0,0 +1,153 @@
+---
+name: authentication
+description: Implement authentication system
+category: fullstack
+complexity: high
+estimated-time: 4-12 hours
+agents:
+  - planner
+  - fullstack-developer
+  - security-auditor
+  - tester
+skills:
+  - oauth
+  - better-auth
+  - owasp
+  - security-hardening
+commands:
+  - /planning:plan
+  - /dev:feature
+  - /quality:security-scan
+  - /dev:test
+prerequisites:
+  - Auth strategy chosen
+  - User model defined
+---
+
+# Authentication Workflow
+
+## Overview
+
+The Authentication workflow guides implementation of secure authentication systems including registration, login, session management, and OAuth.
+
+## When to Use
+
+- Adding auth to new projects
+- Implementing OAuth
+- Upgrading auth security
+- Adding MFA
+
+## Steps
+
+### Step 1: Auth Planning
+**Agent:** planner
+**Command:** `/planning:plan "authentication"`
+**Duration:** 30-60 minutes
+
+Plan authentication:
+- Choose auth method
+- Define user flow
+- Plan security measures
+- Identify providers
+
+**Output:** Auth plan
+
+### Step 2: Backend Auth
+**Agent:** fullstack-developer
+**Duration:** 2-4 hours
+
+Implement backend:
+- Auth endpoints
+- Password hashing
+- Session management
+- Token handling
+
+**Output:** Backend auth
+
+### Step 3: OAuth Integration
+**Agent:** fullstack-developer
+**Duration:** 1-2 hours (if needed)
+
+Add OAuth:
+- Configure providers
+- Implement callbacks
+- Handle tokens
+- Link accounts
+
+**Output:** OAuth integration
+
+### Step 4: Frontend Auth
+**Agent:** fullstack-developer
+**Duration:** 2-3 hours
+
+Build frontend:
+- Login/signup forms
+- Auth state management
+- Protected routes
+- Error handling
+
+**Output:** Frontend auth
+
+### Step 5: Security Review
+**Agent:** security-auditor
+**Command:** `/quality:security-scan`
+**Duration:** 1-2 hours
+
+Security audit:
+- Password security
+- Session security
+- CSRF protection
+- XSS prevention
+
+**Output:** Security report
+
+### Step 6: Testing
+**Agent:** tester
+**Command:** `/dev:test`
+**Duration:** 1-2 hours
+
+Auth testing:
+- Registration tests
+- Login tests
+- Session tests
+- Security tests
+
+**Output:** Test suite
+
+## Quality Gates
+
+- [ ] Auth method implemented
+- [ ] Passwords securely hashed
+- [ ] Sessions properly managed
+- [ ] OAuth working (if used)
+- [ ] Security review passed
+- [ ] All tests passing
+
+## Auth Security Checklist
+
+```
+Authentication Security
+=======================
+[ ] Passwords hashed (bcrypt/argon2)
+[ ] Rate limiting implemented
+[ ] Account lockout after failures
+[ ] Session tokens secure
+[ ] HTTPS enforced
+[ ] CSRF protection
+[ ] Secure cookie settings
+[ ] Password requirements
+[ ] Email verification
+[ ] Password reset secure
+```
+
+## Example Usage
+
+```bash
+/workflow:authentication "JWT-based auth with Google OAuth"
+/workflow:authentication "session-based auth with MFA"
+```
+
+## Related Workflows
+
+- `security-audit` - For security review
+- `full-feature` - For complete features

package/plugin/workflows/fullstack/full-feature.md

@@ -0,0 +1,217 @@
+---
+name: full-feature
+description: End-to-end feature with frontend and backend
+category: fullstack
+complexity: very-high
+estimated-time: 8-24 hours
+agents:
+  - planner
+  - database-admin
+  - api-designer
+  - ui-ux-designer
+  - fullstack-developer
+  - tester
+  - code-reviewer
+  - git-manager
+skills:
+  - writing-plans
+  - database-schema-design
+  - api-architecture
+  - frontend-design
+commands:
+  - /planning:plan-detailed
+  - /dev:feature
+  - /dev:test
+  - /dev:review
+  - /git:pr
+prerequisites:
+  - Feature requirements clear
+  - Technology stack defined
+---
+
+# Full Feature Workflow
+
+## Overview
+
+The Full Feature workflow orchestrates development of complete features spanning database, backend API, and frontend UI with comprehensive testing.
+
+## When to Use
+
+- Building major features
+- Creating new modules
+- Full-stack user stories
+- Complex integrations
+
+## Steps
+
+### Step 1: Detailed Planning
+**Agent:** planner
+**Command:** `/planning:plan-detailed "$ARGUMENTS"`
+**Duration:** 1-2 hours
+
+Create detailed plan:
+- Break down into tasks
+- Define database changes
+- Plan API endpoints
+- Design UI components
+
+**Output:** Detailed plan
+
+### Step 2: Database Design
+**Agent:** database-admin
+**Duration:** 1-2 hours
+
+Database work:
+- Schema design
+- Create migrations
+- Add indexes
+- Test migrations
+
+**Output:** Database changes
+
+### Step 3: Backend Development
+**Agent:** fullstack-developer
+**Duration:** 2-4 hours
+
+Build backend:
+- Implement API endpoints
+- Business logic
+- Validation
+- Error handling
+
+**Output:** Backend implementation
+
+### Step 4: Frontend Design
+**Agent:** ui-ux-designer
+**Duration:** 1-2 hours
+
+Design UI:
+- Component design
+- User flows
+- Responsive layout
+- Accessibility
+
+**Output:** UI designs
+
+### Step 5: Frontend Development
+**Agent:** fullstack-developer
+**Duration:** 2-4 hours
+
+Build frontend:
+- Implement components
+- State management
+- API integration
+- Loading/error states
+
+**Output:** Frontend implementation
+
+### Step 6: Integration
+**Agent:** fullstack-developer
+**Duration:** 1-2 hours
+
+Integrate:
+- Connect frontend to backend
+- End-to-end flows
+- Error handling
+- Optimizations
+
+**Output:** Integrated feature
+
+### Step 7: Testing
+**Agent:** tester
+**Command:** `/dev:test`
+**Duration:** 2-4 hours
+
+Comprehensive testing:
+- Unit tests
+- Integration tests
+- E2E tests
+- Visual tests
+
+**Output:** Test suite
+
+### Step 8: Review
+**Agent:** code-reviewer
+**Command:** `/dev:review`
+**Duration:** 1-2 hours
+
+Code review:
+- Architecture review
+- Security check
+- Performance review
+- Best practices
+
+**Output:** Review approval
+
+### Step 9: Deployment
+**Agent:** git-manager
+**Command:** `/git:pr`
+**Duration:** 30-60 minutes
+
+Create PR:
+- Create branch
+- Commit changes
+- Create PR
+- Request review
+
+**Output:** PR ready
+
+## Quality Gates
+
+- [ ] Plan approved
+- [ ] Database migrated successfully
+- [ ] Backend API complete
+- [ ] Frontend UI complete
+- [ ] Integration working
+- [ ] All tests passing
+- [ ] Review approved
+- [ ] PR created
+
+## Full Feature Checklist
+
+```
+Full Feature Checklist
+======================
+PLANNING:
+[ ] Requirements documented
+[ ] Tasks broken down
+[ ] Estimates provided
+
+DATABASE:
+[ ] Schema designed
+[ ] Migrations created
+[ ] Indexes added
+
+BACKEND:
+[ ] Endpoints implemented
+[ ] Validation complete
+[ ] Error handling done
+
+FRONTEND:
+[ ] Components built
+[ ] State managed
+[ ] API connected
+
+TESTING:
+[ ] Unit tests written
+[ ] Integration tests done
+[ ] E2E tests passing
+
+REVIEW:
+[ ] Code reviewed
+[ ] Security checked
+[ ] Performance ok
+```
+
+## Example Usage
+
+```bash
+/workflow:full-feature "user profile with avatar upload and preferences"
+/workflow:full-feature "shopping cart with checkout and payment"
+```
+
+## Related Workflows
+
+- `feature` - For simpler features
+- `authentication` - For auth features
+- `api-design` - For API focus

package/plugin/workflows/omega/1000x-innovation.md

@@ -0,0 +1,167 @@
+---
+name: 1000x-innovation
+description: Find breakthrough innovations
+category: omega
+complexity: very-high
+estimated-time: 8-40 hours
+agents:
+  - oracle
+  - researcher
+  - brainstormer
+  - architect
+skills:
+  - omega-thinking
+  - omega-architecture
+commands:
+  - /omega:1000x
+  - /planning:research
+  - /planning:brainstorm
+prerequisites:
+  - Domain identified
+  - Open to paradigm shifts
+---
+
+# 1000x Innovation Workflow
+
+## Overview
+
+The 1000x Innovation workflow explores breakthrough innovations and paradigm shifts that can deliver 1000x improvements. It challenges fundamental assumptions and explores transformative approaches.
+
+## When to Use
+
+- Seeking breakthrough solutions
+- Exploring new paradigms
+- Disrupting existing approaches
+- Creating new categories
+
+## Steps
+
+### Step 1: Domain Exploration
+**Agent:** oracle
+**Command:** `/omega:1000x "$ARGUMENTS"`
+**Duration:** 2-4 hours
+
+Explore domain:
+- Map current paradigm
+- Identify constraints
+- Question assumptions
+- Find first principles
+
+**Output:** Domain analysis
+
+### Step 2: Research
+**Agent:** researcher
+**Command:** `/planning:research`
+**Duration:** 2-4 hours
+
+Research innovations:
+- Emerging technologies
+- Adjacent industries
+- Academic research
+- Startup innovations
+
+**Output:** Research findings
+
+### Step 3: Ideation
+**Agent:** brainstormer
+**Command:** `/planning:brainstorm`
+**Duration:** 2-4 hours
+
+Generate innovations:
+- Apply transcendence mode
+- Question fundamentals
+- Explore impossibilities
+- Combine concepts
+
+**Output:** Innovation ideas
+
+### Step 4: Evaluation
+**Agent:** oracle
+**Duration:** 1-2 hours
+
+Evaluate ideas:
+- Feasibility assessment
+- Impact potential
+- Risk analysis
+- Resource requirements
+
+**Output:** Evaluation report
+
+### Step 5: Prototyping
+**Agent:** architect
+**Duration:** 2-4 hours
+
+Design prototype:
+- Minimum viable innovation
+- Key experiments
+- Success criteria
+- Learning goals
+
+**Output:** Prototype design
+
+### Step 6: Validation
+**Agent:** researcher
+**Duration:** 2-4 hours
+
+Validate concept:
+- User validation
+- Technical feasibility
+- Market potential
+- Strategic fit
+
+**Output:** Validation report
+
+## Quality Gates
+
+- [ ] Domain deeply understood
+- [ ] Research comprehensive
+- [ ] Ideas genuinely innovative
+- [ ] Evaluation rigorous
+- [ ] Prototype designed
+- [ ] Concept validated
+
+## 1000x Thinking
+
+```
+1000x Innovation Principles
+===========================
+
+1. QUESTION EVERYTHING
+   - Why does this exist?
+   - What if it didn't?
+   - What's the real problem?
+
+2. FIRST PRINCIPLES
+   - What's fundamentally true?
+   - What can't change?
+   - What can change?
+
+3. TRANSCENDENCE
+   - What's the next paradigm?
+   - What technology enables it?
+   - When will it be possible?
+
+4. COMBINATORIAL
+   - What + What = New?
+   - Cross-industry insights
+   - Unexpected connections
+
+5. INVERSION
+   - What's the opposite?
+   - What if we're wrong?
+   - What's the contrarian view?
+```
+
+## Example Usage
+
+```bash
+/workflow:1000x-innovation "software development productivity"
+/workflow:1000x-innovation "customer support automation"
+/workflow:1000x-innovation "data processing pipelines"
+```
+
+## Related Workflows
+
+- `10x-improvement` - For incremental gains
+- `100x-architecture` - For scaling improvements
+- `technology-research` - For research component

package/plugin/workflows/omega/100x-architecture.md

@@ -0,0 +1,150 @@
+---
+name: 100x-architecture
+description: Design systems that scale 100x
+category: omega
+complexity: high
+estimated-time: 4-16 hours
+agents:
+  - oracle
+  - architect
+  - planner
+  - researcher
+skills:
+  - omega-architecture
+  - omega-thinking
+commands:
+  - /omega:100x
+  - /planning:plan-detailed
+prerequisites:
+  - System architecture exists
+  - Scaling requirements known
+---
+
+# 100x Architecture Workflow
+
+## Overview
+
+The 100x Architecture workflow helps design and plan systems capable of scaling 100x from current capacity. It applies Omega thinking to architecture decisions.
+
+## When to Use
+
+- Planning for major growth
+- Redesigning bottlenecked systems
+- Preparing for scale
+- Modernizing architecture
+
+## Steps
+
+### Step 1: Current State Analysis
+**Agent:** oracle
+**Command:** `/omega:100x "$ARGUMENTS"`
+**Duration:** 1-2 hours
+
+Analyze current architecture:
+- Map system components
+- Identify bottlenecks
+- Measure current capacity
+- Document constraints
+
+**Output:** Architecture analysis
+
+### Step 2: Bottleneck Identification
+**Agent:** architect
+**Duration:** 1-2 hours
+
+Find scaling limits:
+- Database bottlenecks
+- Compute limitations
+- Network constraints
+- Storage limits
+
+**Output:** Bottleneck report
+
+### Step 3: Future State Design
+**Agent:** architect
+**Duration:** 2-4 hours
+
+Design scalable architecture:
+- Apply scaling patterns
+- Design for 100x capacity
+- Plan data partitioning
+- Design service boundaries
+
+**Output:** Future architecture
+
+### Step 4: Migration Planning
+**Agent:** planner
+**Command:** `/planning:plan-detailed "migration"`
+**Duration:** 2-4 hours
+
+Plan migration:
+- Phased approach
+- Risk mitigation
+- Rollback strategy
+- Timeline
+
+**Output:** Migration plan
+
+### Step 5: Validation
+**Agent:** researcher
+**Duration:** 1-2 hours
+
+Validate design:
+- Review against requirements
+- Check industry patterns
+- Assess feasibility
+- Identify risks
+
+**Output:** Validation report
+
+## Quality Gates
+
+- [ ] Current architecture documented
+- [ ] Bottlenecks identified
+- [ ] Future architecture designed
+- [ ] Migration plan created
+- [ ] Design validated
+
+## Scaling Patterns
+
+```
+100x Scaling Patterns
+=====================
+
+DATABASE:
+- Read replicas
+- Sharding
+- Caching layers
+- Event sourcing
+
+COMPUTE:
+- Horizontal scaling
+- Serverless functions
+- Container orchestration
+- Auto-scaling
+
+NETWORK:
+- CDN distribution
+- Load balancing
+- API gateways
+- Edge computing
+
+DATA:
+- Partitioning
+- Archiving
+- Tiered storage
+- Data lakes
+```
+
+## Example Usage
+
+```bash
+/workflow:100x-architecture "e-commerce platform for 100x order volume"
+/workflow:100x-architecture "API gateway for 100x request throughput"
+```
+
+## Related Workflows
+
+- `10x-improvement` - For smaller improvements
+- `1000x-innovation` - For paradigm shifts
+- `database-optimization` - For database scaling