ai-qakit 1.0.0

package/templates/.cursor/README.md

@@ -0,0 +1,261 @@
+# Cursor Configuration
+
+AI-assisted development rules and commands for Cursor IDE.
+
+## How It Works
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    INITIALIZATION FLOW                       │
+├─────────────────────────────────────────────────────────────┤
+│                                                              │
+│  1. Run @config/init-backend.md                              │
+│                         ↓                                    │
+│  2. Run /docs:init to generate project documentation        │
+│                         ↓                                    │
+│  3. Extract project config from generated docs              │
+│                         ↓                                    │
+│  4. Copy backend commands to root folder                    │
+│                         ↓                                    │
+│  5. Customize commands for project stack                    │
+│                                                              │
+└─────────────────────────────────────────────────────────────┘
+```
+
+## Quick Start
+
+### 1. Initialize Your Project
+
+```
+@.cursor/commands/devkit/config/init-backend.md
+
+Initialize backend project
+```
+
+This will:
+- Run `/docs:init` to generate project documentation
+- Extract project configuration from generated docs
+- Copy and customize backend commands for your project
+
+### 2. Use Commands
+
+```
+@.cursor/commands/devkit/backend/create-api.md
+
+Create CRUD endpoints for User
+```
+
+## Structure
+
+```
+.cursor/
+├── rules/                      # Auto-applied rules
+│   ├── project.mdc            # Core AI behavior (always)
+│   ├── project-profile.mdc    # YOUR project (generated)
+│   ├── community-rules.mdc    # From cursor.directory (generated)
+│   ├── development-rules.mdc  # Development best practices
+│   ├── javascript-pro/        # JavaScript ES2015+ patterns
+│   ├── typescript-pro/        # TypeScript type system mastery
+│   ├── frontend-development/  # Frontend patterns (React 18+)
+│   ├── backend-development/   # Backend patterns
+│   └── ...                    # Other framework/skill rules
+│
+├── doc-templates/              # Documentation templates
+│
+├── commands/                   # Command templates
+│   ├── devkit/                # AI DevKit commands
+│   │   ├── config/            # Configuration
+│   │   ├── backend/           # Backend commands
+│   │   ├── frontend/          # Frontend commands
+│   │   ├── docs/              # Documentation
+│   │   ├── review/            # Code review
+│   │   ├── spec/              # Specifications
+│   │   ├── spec-lite/         # Lightweight task workflow
+│   │   └── ...                # Core commands (ask, scout, solve, etc.)
+│   ├── update-changelog.md    # Project-level commands
+│   └── update-readme.md
+│
+└── README.md
+```
+
+## Init Commands
+
+### `/devkit/config/init-backend.md`
+
+Simplified workflow that:
+1. Runs `/docs:init` to generate project documentation
+2. Extracts project config from generated docs
+3. Copies backend commands to root folder
+4. Cleans up API-specific commands (REST/GraphQL)
+5. Customizes commands for project stack
+
+## Rules Reference
+
+### Always Active
+
+| Rule | Purpose |
+|------|---------|
+| `project.mdc` | Core AI behavior |
+| `project-profile.mdc` | Your project conventions |
+
+### Auto-Applied (by file type)
+
+| Rule | Applies To |
+|------|------------|
+| `typescript.mdc` | `*.ts`, `*.tsx` |
+| `nextjs.mdc` | `app/`, `pages/`, Next config |
+| `nestjs.mdc` | `*.module.ts`, `*.controller.ts` |
+| `react.mdc` | `*.tsx`, `*.jsx` |
+| `python.mdc` | `*.py` |
+| `testing.mdc` | Test files |
+| `security.mdc` | Auth/API files |
+
+### Generated by Init
+
+| Rule | Source |
+|------|--------|
+| `project-profile.mdc` | Analysis of your codebase |
+| `community-rules.mdc` | Filtered cursor.directory rules |
+
+## Commands Reference
+
+### Quick Reference
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/help.md` | List all devkit commands with descriptions |
+| `/devkit/ask.md` | Smart assistant (routes to best approach) |
+| `/devkit/scout.md` | Codebase exploration |
+
+### Configuration & Setup
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/config/init-backend.md` | Initialize backend commands based on `/docs:init` |
+| `/devkit/config/init-frontend.md` | Initialize frontend project configuration |
+
+### Code Generation
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/create-test.md` | Generate tests (99% coverage) |
+| `/devkit/frontend/create-component.md` | React components |
+| `/devkit/frontend/create-page.md` | Page components |
+| `/devkit/frontend/create-form.md` | Form components with validation |
+| `/devkit/frontend/create-table.md` | Data table with sorting/filtering |
+| `/devkit/frontend/create-storybook.md` | Storybook stories |
+| `/devkit/frontend/create-api-integration.md` | API integration layer |
+| `/devkit/backend/create-api.md` | API endpoints |
+| `/devkit/backend/create-schema.md` | Database models |
+| `/devkit/backend/create-migration.md` | Database migrations |
+
+### API Design
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/backend/design-rest-api.md` | REST API design |
+| `/devkit/backend/design-graphql-api.md` | GraphQL API design |
+
+### Multi-Agent Workflows (Full Spec)
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/spec/task.md` | Create task specifications |
+| `/devkit/spec/brainstorm.md` | Brainstorm requirements |
+| `/devkit/spec/capture-requirement.md` | Analyze requirements and generate knowledge artifacts |
+| `/devkit/spec/deep-capture-requirement.md` | Promax version with extensive codebase analysis |
+| `/devkit/spec/update-requirement.md` | Update existing requirements with new content |
+| `/devkit/spec/plan.md` | Feature planning with specs |
+| `/devkit/spec/update-plan.md` | Update existing plan with new requirements or modifications |
+| `/devkit/spec/implement.md` | Implement from specification (docs-manager removed) |
+| `/devkit/spec/test.md` | Create tests with 100% coverage |
+| `/devkit/spec/cook.md` | Step-by-step implementation |
+| `/devkit/refactor.md` | Code simplification |
+| `/devkit/solve.md` | Multi-technique problem solving |
+
+### Spec Lite (Small Tasks)
+
+Lightweight workflow for small tasks - no research, max 4 phases, token-efficient.
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/spec-lite/task.md [id] [desc]` | Create lightweight task with requirements.md |
+| `/devkit/spec-lite/plan.md [id]` | Quick planning (auto-detects stack, finds reusable resources) |
+| `/devkit/spec-lite/update-plan.md [id] [desc]` | Update existing lite plan with new requirements (max 4 phases) |
+| `/devkit/spec-lite/do.md [id]` | Implement all phases, batch code review after all files created |
+| `/devkit/spec-lite/test.md [id]` | Create tests with 100% coverage |
+
+**Key Features:**
+- **Simplified structure**: Just `requirements.md` and `plan.md` (no reports/subfolders)
+- **Resource reuse**: Finds existing utils/services/patterns to reuse - prevents duplicates
+- **Auto-detect stack**: Automatically detects platform and API approach
+- **Batch code review**: Reviews ALL files at once after implementation complete (not one-by-one)
+- **Separate testing**: Testing handled via `/devkit/spec-lite/test.md` for focused coverage
+- **Active task tracking**: Maintains `.cursor/active-task` for session continuity
+
+### Quality & Review
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/review/codebase.md` | Codebase review |
+| `/devkit/fix.md` | Fix issues |
+
+### Research & Analysis
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/research.md` | Deep research with reports |
+| `/devkit/ask.md` | Smart assistant |
+| `/devkit/scout.md` | Codebase exploration |
+| `/devkit/ui-ux-pro-max.md` | UI/UX design assistance |
+
+### Documentation
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/docs/capture-knowledge.md` | Document code flows |
+| `/devkit/docs/init.md` | Initialize doc structure |
+| `/devkit/docs/update.md` | Update existing docs |
+| `/devkit/docs/summarize.md` | Summarize code/docs |
+
+### Debugging
+
+| Command | Purpose |
+|---------|---------|
+| `/devkit/debug.md` | 7-step systematic debugging |
+
+## Command Features
+
+All commands include:
+
+### ⚠️ Plan Before Executing
+- Shows what will be created/modified
+- Gets user approval before changes
+- Never modifies without confirmation
+
+### Ask for Clarification
+- Asks questions when uncertain
+- Lists specific things to clarify
+- Waits for user response
+
+## Customization
+
+### After Init
+
+Review and customize generated files:
+- `.cursor/rules/project-profile.mdc` - Your project conventions
+- `.cursor/rules/community-rules.mdc` - Filtered community rules
+
+### Manual Rule Addition
+
+Copy rules from [cursor.directory](https://cursor.directory/):
+1. Find a rule that matches your stack
+2. Copy to `.cursor/rules/[name].mdc`
+3. Adjust globs and content as needed
+
+## Tips
+
+1. **Run init first** - Always start with `/devkit/config/init-backend.md`
+2. **Review generated docs** - Check `./docs/` for project documentation
+3. **Combine with @workspace** - Add for full context
+4. **Version control** - Commit `.cursor/` folder

package/templates/.cursor/commands/devkit/ask.md

@@ -0,0 +1,71 @@
+---
+description: Smart Q&A assistant - routes questions to appropriate problem-solving approach
+---
+
+# Ask
+
+Routes your question to the appropriate skill based on question type.
+
+## Usage
+
+`@ask [your question]`
+
+## Question Classification
+
+| Type | Indicators | Approach |
+|------|-----------|----------|
+| **Research** | "what is", "how does", "best practices", "compare" | Research + Web search |
+| **Problem** | "stuck on", "can't figure out", "error", "fix" | Problem-solving techniques |
+| **Complex** | "design", "architect", "plan", multi-step | Sequential thinking |
+| **Quick** | Simple factual, single-step | Direct answer |
+
+## Response Formats
+
+### Research Questions
+```
+📚 RESEARCH FINDINGS
+─────────────────────
+[Summary]
+
+Key Points:
+• Point 1
+• Point 2
+
+Recommendations:
+1. Action 1
+2. Action 2
+```
+
+### Problem Questions
+```
+🔧 PROBLEM ANALYSIS
+─────────────────────
+Stuck-Type: [type]
+Technique: [applied technique]
+
+Analysis: [breakdown]
+Solution: [steps]
+```
+
+### Complex Questions
+```
+🧠 SEQUENTIAL ANALYSIS
+─────────────────────
+Thought 1/N: [analysis]
+...
+Summary: [recommendations]
+```
+
+### Quick Questions
+```
+💡 ANSWER
+─────────────────────
+[Direct answer]
+[Code example if applicable]
+```
+
+## Combining Approaches
+
+- **Research + Problem**: Research context → Apply techniques → Validate
+- **Research + Sequential**: Break down → Research each part → Synthesize
+- **All Three**: Scope → Research → Problem-solve when stuck → Iterate

package/templates/.cursor/commands/devkit/backend/create-api.md

@@ -0,0 +1,207 @@
+# Create API Endpoint
+
+Generate an API endpoint following project conventions.
+
+## ⚠️ Plan Before Executing
+
+**Always create a structured plan and get user approval before making changes.**
+
+1. Show all files that will be created
+2. Display the endpoint structure
+3. List dependencies to add (if any)
+4. Ask for confirmation before generating
+
+## Ask for Clarification
+
+If anything is unclear, **ask the user**:
+- "What fields should the request/response include?"
+- "Does this endpoint require authentication?"
+- "Should this support pagination, filtering, or sorting?"
+- "Are there specific validation rules for input data?"
+- "What HTTP status codes should be used for errors?"
+
+---
+
+## Step 1: Reference Project Profile
+
+Read `@.cursor/rules/project-profile.mdc` to understand:
+- API type (REST or GraphQL)
+- Framework (NestJS, Express, FastAPI, etc.)
+- File structure conventions
+- Naming patterns
+- Authentication patterns
+
+## Step 2: Analyze Request
+
+Parse the endpoint request to identify:
+- Resource name
+- HTTP method(s) / GraphQL operation type
+- Request/response shape
+- Authentication requirements
+- Validation rules
+
+## Step 3: Check Existing Patterns
+
+```bash
+# Find existing controllers/resolvers
+find . -name "*controller*" -o -name "*resolver*" | head -5
+
+# Check existing DTOs/schemas
+find . -name "*dto*" -o -name "*schema*" | head -5
+```
+
+## Step 4: Present API Plan
+
+```
+═══════════════════════════════════════════════
+📋 API ENDPOINT PLAN
+═══════════════════════════════════════════════
+
+Resource: [name]
+Type: [REST / GraphQL]
+Auth: [Required / Optional / None]
+
+Endpoints:
+├── GET    /[resource]       - List all
+├── GET    /[resource]/:id   - Get one
+├── POST   /[resource]       - Create
+├── PUT    /[resource]/:id   - Update
+└── DELETE /[resource]/:id   - Delete
+
+Files to Create:
+├── [controller/resolver file]
+├── [service file]
+├── [dto/input files]
+└── [entity/model file] (if new)
+
+Proceed with generating? (Y/n)
+═══════════════════════════════════════════════
+```
+
+## REST API Generation
+
+### Controller Structure (NestJS)
+
+```typescript
+@Controller('users')
+@UseGuards(JwtAuthGuard)
+export class UsersController {
+  constructor(private readonly usersService: UsersService) {}
+
+  @Get()
+  findAll(@Query() query: PaginationDto) {
+    return this.usersService.findAll(query)
+  }
+
+  @Get(':id')
+  findOne(@Param('id', ParseUUIDPipe) id: string) {
+    return this.usersService.findOne(id)
+  }
+
+  @Post()
+  create(@Body() dto: CreateUserDto) {
+    return this.usersService.create(dto)
+  }
+
+  @Put(':id')
+  update(
+    @Param('id', ParseUUIDPipe) id: string,
+    @Body() dto: UpdateUserDto,
+  ) {
+    return this.usersService.update(id, dto)
+  }
+
+  @Delete(':id')
+  @HttpCode(HttpStatus.NO_CONTENT)
+  remove(@Param('id', ParseUUIDPipe) id: string) {
+    return this.usersService.remove(id)
+  }
+}
+```
+
+### Express.js Structure
+
+```typescript
+const router = Router()
+
+router.get('/', authenticate, controller.findAll)
+router.get('/:id', authenticate, controller.findOne)
+router.post('/', authenticate, validate(createSchema), controller.create)
+router.put('/:id', authenticate, validate(updateSchema), controller.update)
+router.delete('/:id', authenticate, controller.remove)
+```
+
+## GraphQL API Generation
+
+### Resolver Structure
+
+```typescript
+@Resolver(() => User)
+export class UsersResolver {
+  constructor(private readonly usersService: UsersService) {}
+
+  @Query(() => [User])
+  async users(@Args() args: PaginationArgs) {
+    return this.usersService.findAll(args)
+  }
+
+  @Query(() => User)
+  async user(@Args('id') id: string) {
+    return this.usersService.findOne(id)
+  }
+
+  @Mutation(() => User)
+  async createUser(@Args('input') input: CreateUserInput) {
+    return this.usersService.create(input)
+  }
+
+  @Mutation(() => User)
+  async updateUser(
+    @Args('id') id: string,
+    @Args('input') input: UpdateUserInput,
+  ) {
+    return this.usersService.update(id, input)
+  }
+
+  @Mutation(() => Boolean)
+  async deleteUser(@Args('id') id: string) {
+    return this.usersService.remove(id)
+  }
+}
+```
+
+## Step 5: Generate Files
+
+Create in order:
+1. **DTO/Input types** - Request validation
+2. **Entity/Model** - Data structure (if new)
+3. **Service** - Business logic
+4. **Controller/Resolver** - API layer
+5. **Tests** - Unit tests for service
+
+## Step 6: Summary
+
+```
+═══════════════════════════════════════════════
+✅ API ENDPOINT CREATED
+═══════════════════════════════════════════════
+
+Files Created:
+├── [controller file]
+├── [service file]
+├── [dto files]
+└── [test files]
+
+Endpoints Available:
+├── GET    /api/[resource]
+├── GET    /api/[resource]/:id
+├── POST   /api/[resource]
+├── PUT    /api/[resource]/:id
+└── DELETE /api/[resource]/:id
+
+Next steps:
+1. Review generated files
+2. Add to module imports
+3. Test endpoints
+═══════════════════════════════════════════════
+```

package/templates/.cursor/commands/devkit/backend/create-migration.md

@@ -0,0 +1,169 @@
+# Create Database Migration
+
+Generate a database migration for the specified change.
+
+## ⚠️ Plan Before Executing
+
+**Always create a structured plan and get user approval before making changes.**
+
+1. Show what migration will be created
+2. Display the SQL/schema changes
+3. Highlight any destructive operations
+4. Ask for confirmation before generating
+
+## Ask for Clarification
+
+If anything is unclear, **ask the user**:
+- "What is the exact data type for this column?"
+- "Should this column be nullable or have a default value?"
+- "Is this a breaking change that requires special handling?"
+- "Do we need an index on this column?"
+- "What's the foreign key relationship here?"
+
+---
+
+## Step 1: Reference Project Profile
+
+Read `@.cursor/rules/project-profile.mdc` to understand:
+- Migration tool (Prisma, TypeORM, Alembic, etc.)
+- Database type (PostgreSQL, MySQL, SQLite)
+- Migration directory
+- Naming conventions
+
+## Step 2: Analyze Request
+
+Parse the migration request to identify:
+- Tables to create/modify
+- Columns to add/remove/change
+- Indexes needed
+- Foreign key relationships
+- Data type mappings
+
+## Step 3: Check Current Schema
+
+**Prisma:**
+```bash
+cat prisma/schema.prisma
+```
+
+**TypeORM:**
+```bash
+find . -name "*.entity.ts" -exec head -50 {} \;
+```
+
+**Alembic:**
+```bash
+ls alembic/versions/
+```
+
+## Step 4: Present Migration Plan
+
+```
+═══════════════════════════════════════════════
+📋 MIGRATION PLAN
+═══════════════════════════════════════════════
+
+Migration: [name]
+Type: [CREATE TABLE / ALTER TABLE / etc.]
+
+Changes:
+├── [operation 1]
+├── [operation 2]
+└── [operation 3]
+
+⚠️ Warnings:
+├── [any destructive operations]
+└── [data loss risks]
+
+SQL Preview:
+```sql
+[generated SQL]
+```
+
+Proceed with creating migration? (Y/n)
+═══════════════════════════════════════════════
+```
+
+## Step 5: Generate Migration
+
+**For Prisma:**
+```bash
+# Update schema first
+# Then generate migration
+npx prisma migrate dev --name [migration_name]
+```
+
+**For TypeORM:**
+```bash
+npx typeorm migration:generate -n [MigrationName]
+```
+
+**For Alembic:**
+```bash
+alembic revision --autogenerate -m "[description]"
+```
+
+## Step 6: Show Migration Content
+
+Display the generated migration with:
+- Up migration (apply changes)
+- Down migration (rollback)
+- Any manual adjustments needed
+
+## Step 7: Provide Commands
+
+```
+═══════════════════════════════════════════════
+✅ MIGRATION CREATED
+═══════════════════════════════════════════════
+
+File: [migration file path]
+
+Commands:
+├── Apply:   [command to run migration]
+├── Rollback: [command to rollback]
+└── Status:  [command to check status]
+
+Next steps:
+1. Review the migration file
+2. Test in development environment
+3. Apply: [command]
+═══════════════════════════════════════════════
+```
+
+## Common Patterns
+
+### Add Column
+```sql
+ALTER TABLE users ADD COLUMN profile_url VARCHAR(255);
+```
+
+### Add Index
+```sql
+CREATE INDEX idx_users_email ON users(email);
+```
+
+### Add Foreign Key
+```sql
+ALTER TABLE orders
+ADD CONSTRAINT fk_orders_user
+FOREIGN KEY (user_id) REFERENCES users(id);
+```
+
+### Rename Column
+```sql
+ALTER TABLE users RENAME COLUMN name TO full_name;
+```
+
+## Safety Checks
+
+🔴 **Destructive Operations - Require Confirmation:**
+- DROP TABLE
+- DROP COLUMN
+- TRUNCATE
+- Data type changes that may lose data
+
+🟢 **Safe Operations:**
+- ADD COLUMN (nullable)
+- CREATE INDEX
+- ADD CONSTRAINT