Propose Forge Improvement

/propose-forge-improvement        # Analyze and propose improvements
/propose-forge-improvement --save # Save proposal to ~/.claude/learnings/

Analyze session for Product Forge opportunities
                    ↓
┌─────────────────────────────────────────────┐
│ Could an existing component be improved?    │
│                                             │
│ Check:                                      │
│ - Skills used → Missing guidance?           │
│ - Commands run → Missing options?           │
│ - Agents spawned → Missing capabilities?    │
│ - Docs referenced → Outdated/incomplete?    │
└─────────────────────────────────────────────┘
                    ↓
         ┌─────────┴─────────┐
         ↓                   ↓
   Improvement          New Component
   to existing          proposal

# Search Product Forge for existing components
find ~/.claude/plugins/cache -name "*.md" | xargs grep -l "{component-name}" 2>/dev/null

# Proposed Improvement to Product Forge

## Target Component

**Type**: skill | command | agent | doc
**Location**: plugins/python-experts/skills/django-api/SKILL.md
**Component**: django-api skill

## Current Gap

The django-api skill covers endpoint creation but lacks guidance on:
- Pagination patterns for large datasets
- Cursor-based vs offset pagination trade-offs
- Integration with Django REST Framework pagination classes

## Observed Need

During this session, we implemented pagination for a user listing endpoint.
Had to research DRF pagination classes manually - this knowledge should be
in the skill.

## Suggested Addition

Add a "Pagination Patterns" section:

```python
# Cursor-based pagination (preferred for large datasets)
class UserPagination(CursorPagination):
    page_size = 50
    ordering = '-created_at'

# Offset pagination (simpler, but slower for deep pages)
class UserPagination(PageNumberPagination):
    page_size = 50
    max_page_size = 100

#### For New Components

```markdown
# Proposed New Component for Product Forge

## Component Type

**Type**: skill | command | agent
**Suggested Name**: migration-safety
**Target Plugin**: python-experts

## Problem Statement

When modifying Django models, there's risk of creating migrations that:
- Lock tables for extended periods
- Cause data loss
- Break backwards compatibility

No current skill covers migration safety patterns.

## Proposed Solution

### If Skill

Create `migration-safety` skill that Claude applies when:
- Modifying Django models
- Creating or reviewing migrations
- Planning database schema changes

Key guidance:
- Additive-only changes for zero-downtime
- Separate deploy for column removal
- Index creation with CONCURRENTLY

### If Command

Create `/check-migration` command that:
- Analyzes pending migrations for safety issues
- Flags risky operations (column drops, type changes)
- Suggests safer alternatives

### If Agent

Create `migration-reviewer` agent that:
- Reviews migration files
- Checks for backwards compatibility
- Suggests deployment order

## Evidence from Session

[What happened in the session that prompted this suggestion]

Next steps:
  [1] Create/modify the component now (I'll help implement)
  [2] Save for later review (/propose-forge-improvement --save)
  [3] Open GitHub issue (if Product Forge repo accessible)
  [4] Dismiss

Select option: