kiro-kit 0.1.0

package/dist/presets/fullstack/skills/.env.example

@@ -0,0 +1,10 @@
+# Skills environment variables
+# Copy this file to .env and fill in your values.
+
+# Google Gemini API key (for ai-multimodal skill)
+# GEMINI_API_KEY=<your-gemini-api-key>
+
+# Shopify credentials (for shopify skill)
+# SHOPIFY_API_KEY=<your-shopify-api-key>
+# SHOPIFY_API_SECRET=<your-shopify-api-secret>
+# SHOPIFY_STORE_URL=<your-store>.myshopify.com

package/dist/presets/fullstack/skills/INSTALLATION.md

@@ -0,0 +1,28 @@
+# Installing New Skills
+
+## Adding a Skill
+
+1. Create a new directory under `.kiro/skills/<skill-name>/`
+2. Add a `SKILL.md` file with required front-matter:
+
+```yaml
+---
+name: my-skill
+description: Brief description of when to activate this skill
+---
+```
+
+3. Add content describing the skill's capabilities and usage
+4. Optionally add `references/`, `scripts/`, `assets/` subdirectories
+
+## Front-matter Requirements
+
+- `name`: kebab-case identifier (required)
+- `description`: When to activate this skill (required)
+
+## Best Practices
+
+- Keep `SKILL.md` concise (token-efficient)
+- Put detailed documentation in `references/` for progressive disclosure
+- Use `scripts/` for automation that the skill provides
+- Test that the skill activates correctly in Kiro

package/dist/presets/fullstack/skills/README.md

@@ -0,0 +1,38 @@
+# Skills
+
+Skills provide specialized knowledge and workflows that agents can activate on demand. Each skill has a `SKILL.md` with front-matter metadata and activation instructions.
+
+## Available Skills
+
+| Skill | Description |
+|-------|-------------|
+| frontend-design | Production-grade frontend interface design |
+| frontend-development | React/Next.js component development patterns |
+| ui-styling | Tailwind CSS, shadcn/ui, and design systems |
+| web-frameworks | Next.js App Router, Server Components, routing |
+| backend-development | Node.js/Python/Go API and service development |
+| databases | PostgreSQL, MongoDB, Redis schema and queries |
+| devops | Docker, CI/CD, cloud deployment |
+| better-auth | Authentication and authorization patterns |
+| shopify | Shopify app development and Liquid templating |
+| payment-integration | Stripe, Polar, SePay payment processing |
+| debugging | Systematic debugging and root cause analysis |
+| sequential-thinking | Structured multi-step problem solving |
+| problem-solving | Techniques for complexity and innovation blocks |
+| planning | Technical solution planning and architecture |
+| research | Technology research and evaluation |
+| docs-seeker | Documentation search and discovery |
+| repomix | Repository packaging for AI analysis |
+| ai-multimodal | Gemini API for image/audio/video processing |
+| code-review | Code review practices and feedback |
+| skill-creator | Guide for creating new skills |
+| template-skill | Template for new skill creation |
+| mcp-builder | Building MCP servers for tool integration |
+
+## Structure
+
+Each skill folder contains:
+- `SKILL.md` - Main skill file with front-matter and instructions
+- `references/` - Detailed documentation (loaded on demand)
+- `scripts/` - Automation scripts (optional)
+- `assets/` - Static assets (optional)

package/dist/presets/fullstack/skills/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,22 @@
+# Third Party Notices
+
+This directory contains skills that reference or integrate with third-party tools and services. All third-party trademarks and copyrights belong to their respective owners.
+
+## Referenced Services
+
+- Next.js - Vercel Inc.
+- React - Meta Platforms Inc.
+- Tailwind CSS - Tailwind Labs Inc.
+- shadcn/ui - shadcn
+- Prisma - Prisma Data Inc.
+- Drizzle - Drizzle Team
+- Stripe - Stripe Inc.
+- Shopify - Shopify Inc.
+- PostgreSQL - The PostgreSQL Global Development Group
+- Redis - Redis Ltd.
+- Docker - Docker Inc.
+- Google Gemini - Google LLC
+
+## License
+
+Skills in this directory are provided under the same license as the parent project (MIT). References to third-party documentation are for educational purposes.

package/dist/presets/fullstack/skills/agent_skills_spec.md

@@ -0,0 +1,39 @@
+# Agent Skills Specification
+
+## Overview
+
+Skills extend agent capabilities with specialized knowledge. They follow progressive disclosure: `SKILL.md` provides a concise overview, while `references/` contains detailed documentation loaded only when needed.
+
+## Activation
+
+Agents activate skills by reading the `SKILL.md` file. The front-matter `name` and `description` fields help agents decide when to activate.
+
+## Directory Structure
+
+```
+skills/<skill-name>/
+  SKILL.md              Required. Front-matter + concise instructions.
+  references/           Optional. Detailed docs loaded on demand.
+  scripts/              Optional. Automation scripts.
+  assets/               Optional. Static files.
+```
+
+## Front-matter Schema
+
+```yaml
+---
+name: skill-name        # kebab-case, required
+description: When to use # required, helps agent decide activation
+---
+```
+
+## Sub-skill Containers
+
+A skill directory without its own `SKILL.md` but containing subdirectories with `SKILL.md` files is a sub-skill container. Example:
+
+```
+skills/document-skills/
+  docx/SKILL.md
+  pdf/SKILL.md
+  xlsx/SKILL.md
+```

package/dist/presets/fullstack/skills/ai-multimodal/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: ai-multimodal
+description: Process and generate multimedia content using Google Gemini API. Use when working with images, audio, video, or documents that need AI analysis or generation.
+---
+
+# AI Multimodal
+
+Activate when working with multimedia content that needs AI processing or generation.
+
+## When to Use
+
+- Analyzing images (captioning, OCR, object detection)
+- Processing audio files (transcription, summarization)
+- Understanding video content (scene detection, Q&A)
+- Extracting data from documents (PDF tables, forms)
+- Generating images from text prompts
+
+## Capabilities
+
+- Image analysis: captioning, OCR, visual Q&A, segmentation
+- Audio processing: transcription with timestamps, summarization
+- Video understanding: scene detection, temporal analysis
+- Document extraction: PDF tables, forms, charts, diagrams
+- Image generation: text-to-image, editing, composition
+
+## Usage Notes
+
+- Requires GEMINI_API_KEY environment variable
+- Supports models: Gemini 2.5, Gemini 2.0
+- Context window up to 2M tokens
+- Audio support up to 9.5 hours
+- Video support up to 6 hours

package/dist/presets/fullstack/skills/backend-development/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: backend-development
+description: Build robust backend systems with Node.js, Python, or Go. Use when implementing APIs, services, middleware, or server-side logic following production-grade patterns.
+---
+
+# Backend Development
+
+Activate when building backend services, APIs, or server-side logic.
+
+## When to Use
+
+- Implementing REST or GraphQL API endpoints
+- Building middleware (auth, logging, rate limiting, CORS)
+- Designing service layer architecture
+- Integrating with databases and external services
+- Implementing background jobs and queues
+- Setting up application configuration and environment management
+
+## Architecture Patterns
+
+- Layered: Controller -> Service -> Repository
+- Clean Architecture: separate domain from infrastructure
+- CQRS: separate read and write models for complex domains
+
+## Implementation Guidelines
+
+- Validate all input at the boundary (controller/handler layer)
+- Use dependency injection for testability
+- Implement structured logging with correlation IDs
+- Handle errors at appropriate layers
+- Use environment variables for configuration (12-factor app)
+- Implement health check endpoints (/health, /ready)
+- Use connection pooling for database connections
+- Implement graceful shutdown handling
+
+## Testing Strategy
+
+- Unit tests for service/business logic (no I/O)
+- Integration tests for database and external service interactions
+- API tests for endpoint behavior verification

package/dist/presets/fullstack/skills/better-auth/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: better-auth
+description: Implement authentication and authorization with modern patterns including OAuth 2.1, JWT, sessions, RBAC, and multi-factor authentication. Use when building auth systems.
+---
+
+# Better Auth
+
+Activate when implementing authentication or authorization systems.
+
+## When to Use
+
+- Adding authentication to an application
+- Implementing OAuth flows (Google, GitHub, Discord)
+- Setting up JWT or session-based auth
+- Implementing role-based access control (RBAC)
+- Adding multi-factor authentication (TOTP, SMS)
+- Managing user sessions and token refresh
+
+## Authentication Patterns
+
+### Session-Based (Recommended for Next.js)
+- Store sessions server-side (Redis for distributed)
+- Use httpOnly, secure, sameSite cookies
+- Implement session rotation on privilege escalation
+- Set absolute and idle timeouts
+
+### JWT (Stateless)
+- Short-lived access tokens (15-60 minutes)
+- Long-lived refresh tokens (7-30 days, stored securely)
+- Rotate refresh tokens on use
+- Include minimal claims (user ID, roles)
+
+### OAuth 2.1
+- Use PKCE for all flows
+- Validate state parameter to prevent CSRF
+- Store tokens encrypted at rest
+- Handle provider-specific scopes and claims
+
+## Security Rules
+
+- Hash passwords with bcrypt (cost 12+) or argon2id
+- Use constant-time comparison for tokens
+- Implement account lockout after failed attempts
+- Log all auth events for audit trail
+- Never store plain-text passwords or tokens

package/dist/presets/fullstack/skills/code-review/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: code-review
+description: Code review practices for receiving feedback, requesting reviews, and verification gates. Use when completing tasks or receiving review feedback.
+---
+
+# Code Review
+
+Activate when receiving code review feedback, completing tasks requiring review, or before making completion claims.
+
+## Practices
+
+### Receiving Feedback
+- Evaluate feedback with technical rigor
+- Do not agree performatively -- verify claims
+- Ask for clarification on unclear suggestions
+- Prioritize correctness over politeness
+
+### Requesting Reviews
+- Provide context: what changed and why
+- Highlight areas of uncertainty
+- Include test results and verification steps
+- Note any trade-offs or known limitations
+
+### Verification Gates
+- Do not claim completion without evidence
+- Run tests and show passing output
+- Verify the change works in context (not just in isolation)
+- Check for regressions in related functionality

package/dist/presets/fullstack/skills/databases/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: databases
+description: Work with PostgreSQL, MongoDB, and Redis for schema design, query optimization, migrations, and data modeling. Use when designing or optimizing data layers.
+---
+
+# Databases
+
+Activate when working with database design, queries, migrations, or optimization.
+
+## When to Use
+
+- Designing database schemas and relationships
+- Writing complex queries or aggregation pipelines
+- Optimizing slow queries with indexes and execution plans
+- Planning and executing database migrations
+- Configuring replication, backups, or sharding
+
+## PostgreSQL
+
+- Use EXPLAIN ANALYZE for query optimization
+- Create indexes based on WHERE, JOIN, ORDER BY patterns
+- Use partial indexes for filtered queries
+- Prefer UUID or ULID for distributed primary keys
+- Use transactions for multi-statement operations
+
+## Migration Rules
+
+- Migrations must be reversible (up and down)
+- Never modify a deployed migration -- create a new one
+- Test migrations against production-like data volumes
+- Use zero-downtime migration patterns for live systems
+- Back up data before destructive migrations
+
+## Redis
+
+- Use appropriate data structures (strings, hashes, sorted sets)
+- Set TTL on all cache entries
+- Use Redis transactions (MULTI/EXEC) for atomic operations
+- Implement pub/sub for real-time messaging

package/dist/presets/fullstack/skills/debugging/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: debugging
+description: Systematic debugging framework for root cause investigation. Use when encountering bugs, test failures, unexpected behavior, or performance issues.
+---
+
+# Debugging
+
+Activate when encountering bugs, test failures, or unexpected behavior that needs systematic investigation.
+
+## When to Use
+
+- Tests failing unexpectedly
+- Runtime errors in development or production
+- Performance degradation
+- Unexpected behavior that does not match specifications
+- Integration failures between components
+
+## Four-Phase Process
+
+### 1. Observe
+- Reproduce the issue reliably
+- Collect error messages, stack traces, logs
+- Note the exact conditions (input, environment, timing)
+
+### 2. Hypothesize
+- Form 2-3 possible explanations
+- Rank by likelihood based on evidence
+- Identify what evidence would confirm/deny each
+
+### 3. Test
+- Validate hypotheses with minimal changes
+- Use breakpoints, logging, or isolated tests
+- Eliminate possibilities systematically
+
+### 4. Fix and Verify
+- Implement targeted fix for confirmed root cause
+- Verify fix resolves the original issue
+- Check for regressions in related functionality
+- Add test to prevent recurrence
+
+## Rules
+
+- Never apply random fixes without understanding the cause
+- Always reproduce before attempting to fix
+- Check recent changes first (git log, deployments)
+- Verify the fix does not mask a deeper issue

package/dist/presets/fullstack/skills/devops/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: devops
+description: Deploy and manage infrastructure with Docker, CI/CD pipelines, and cloud services. Use when containerizing, deploying, or managing production infrastructure.
+---
+
+# DevOps
+
+Activate when working with containers, deployments, CI/CD, or cloud infrastructure.
+
+## When to Use
+
+- Writing or optimizing Dockerfiles
+- Configuring docker-compose for local development
+- Setting up CI/CD pipelines (GitHub Actions, GitLab CI)
+- Managing cloud infrastructure (Vercel, AWS, GCP)
+- Implementing deployment strategies
+
+## Docker Best Practices
+
+- Use multi-stage builds to minimize image size
+- Run as non-root user in production
+- Pin base image versions (not :latest)
+- Use .dockerignore to exclude unnecessary files
+- Order layers for optimal caching
+
+## CI/CD Pipeline Stages
+
+1. Lint and typecheck
+2. Unit tests
+3. Build artifacts
+4. Integration tests
+5. Security scan
+6. Deploy to staging
+7. Smoke tests
+8. Deploy to production
+
+## Deployment Strategies
+
+- Blue-green: instant rollback, double resources
+- Canary: gradual rollout, early detection
+- Rolling: zero-downtime, incremental replacement
+- Feature flags: decouple deploy from release

package/dist/presets/fullstack/skills/docs-seeker/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: docs-seeker
+description: Search and discover technical documentation using llms.txt sources and context7.com. Use when you need library or framework documentation.
+---
+
+# Docs Seeker
+
+Activate when you need to find specific documentation for libraries, frameworks, or APIs.
+
+## When to Use
+
+- Looking up API documentation for a specific library
+- Finding usage examples for a framework feature
+- Discovering configuration options for a tool
+- Verifying correct usage of a function or method
+
+## Process
+
+1. Identify the library/framework and version
+2. Search documentation sources (llms.txt, context7.com)
+3. Find the specific section relevant to the question
+4. Extract actionable information (code examples, config)
+5. Verify information is current for the version in use
+
+## Sources
+
+- Official documentation sites
+- llms.txt files from library repositories
+- context7.com for aggregated documentation
+- GitHub repository READMEs and wikis

package/dist/presets/fullstack/skills/frontend-design/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, or applications that need polished visual design.
+---
+
+# Frontend Design
+
+Activate when creating UI components, pages, or layouts requiring high visual quality.
+
+## When to Use
+
+- Building new pages or features that need visual design decisions
+- Creating component libraries or design systems
+- Implementing responsive layouts with mobile-first approach
+- Designing interactive elements with proper states and transitions
+
+## Design Principles
+
+- Mobile-first responsive design (320px, 768px, 1024px, 1440px breakpoints)
+- Visual hierarchy through typography scale, spacing, and color
+- Consistent spacing using 4px/8px grid system
+- Accessible color contrast (WCAG 2.1 AA minimum)
+- Progressive disclosure of complex information
+
+## Implementation
+
+- Use semantic HTML elements for structure
+- Apply Tailwind CSS utility classes for styling
+- Implement proper focus states for keyboard navigation
+- Add hover/active states for interactive elements
+- Use CSS transitions for smooth state changes (150-300ms)
+- Respect prefers-reduced-motion for animations

package/dist/presets/fullstack/skills/frontend-development/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: frontend-development
+description: Build React/Next.js components, pages, and features with TypeScript. Use when implementing frontend UI, hooks, state management, or client-side logic.
+---
+
+# Frontend Development
+
+Activate when building React components, pages, hooks, or client-side features.
+
+## When to Use
+
+- Implementing React components with TypeScript
+- Building Next.js pages with rendering strategies
+- Creating custom hooks for reusable logic
+- Integrating with APIs using TanStack Query or SWR
+- Optimizing performance (code splitting, memoization)
+
+## Patterns
+
+- Functional components with hooks exclusively
+- Server Components by default, Client Components only when needed
+- Colocate related files (component, test, types)
+- Use Suspense for async data loading
+- Single responsibility principle for components
+- Keep components under 150 lines
+
+## State Management
+
+- Local state: useState for simple, useReducer for complex
+- Server state: TanStack Query or SWR
+- Global state: Zustand (small stores)
+- URL state: useSearchParams for shareable state
+- Form state: React Hook Form + Zod validation

package/dist/presets/fullstack/skills/mcp-builder/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: mcp-builder
+description: Build MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when creating MCP integrations.
+---
+
+# MCP Builder
+
+Activate when building MCP servers to integrate external APIs or services with LLM agents.
+
+## When to Use
+
+- Creating new MCP server integrations
+- Exposing external APIs as MCP tools
+- Building custom tool interfaces for agents
+- Implementing MCP resources and prompts
+
+## Server Structure (TypeScript)
+
+```typescript
+import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
+
+const server = new McpServer({ name: 'my-server', version: '1.0.0' });
+
+server.tool('tool-name', { param: z.string() }, async ({ param }) => {
+  // Implementation
+  return { content: [{ type: 'text', text: result }] };
+});
+```
+
+## Best Practices
+
+- Keep tools focused and single-purpose
+- Validate all inputs with Zod schemas
+- Return structured, parseable responses
+- Handle errors gracefully with descriptive messages
+- Document each tool with clear descriptions
+- Use environment variables for credentials

package/dist/presets/fullstack/skills/payment-integration/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: payment-integration
+description: Implement payment processing with Stripe, Polar, or SePay. Use when building checkout flows, subscriptions, usage-based billing, or handling payment webhooks.
+---
+
+# Payment Integration
+
+Activate when implementing payment processing, subscriptions, or billing systems.
+
+## When to Use
+
+- Integrating Stripe for card payments and subscriptions
+- Using Polar for SaaS monetization and automated benefits
+- Implementing SePay for Vietnamese bank transfers and VietQR
+- Building checkout flows and pricing pages
+- Handling payment webhooks and event processing
+- Managing subscription lifecycle (create, upgrade, cancel)
+
+## Stripe
+
+- Use Stripe Checkout for hosted payment pages
+- Implement Payment Intents for custom flows
+- Handle webhooks for payment confirmation (checkout.session.completed)
+- Use Stripe Billing for subscriptions (price IDs, metered billing)
+- Implement customer portal for self-service management
+- Always verify webhook signatures before processing
+
+## Polar
+
+- Use Polar for subscription management and benefit delivery
+- Implement OAuth2 for user authentication
+- Handle webhooks for subscription events
+- Automate benefit delivery (GitHub repo access, Discord roles)
+- Use Polar as Merchant of Record for tax compliance
+
+## Webhook Best Practices
+
+- Verify signatures on all incoming webhooks
+- Implement idempotency (store processed event IDs)
+- Return 200 quickly, process asynchronously
+- Handle retries gracefully (events may arrive multiple times)
+- Log all webhook events for debugging
+
+## Security
+
+- Never log full card numbers or CVVs
+- Use Stripe.js or Elements for PCI compliance
+- Store only Stripe customer/subscription IDs in your database
+- Use test mode keys in development (sk_test_, pk_test_)
+- Rotate API keys periodically

package/dist/presets/fullstack/skills/planning/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: planning
+description: Plan technical solutions that are scalable, secure, and maintainable. Use when you need to create implementation plans, evaluate architectures, or break down complex features.
+---
+
+# Planning
+
+Activate when creating implementation plans, evaluating architectures, or decomposing complex features.
+
+## When to Use
+
+- Starting a new feature that spans multiple files/modules
+- Evaluating architectural approaches
+- Breaking down epics into implementable tasks
+- Estimating effort and identifying dependencies
+- Creating phased delivery plans
+
+## Process
+
+1. Define the problem and success criteria
+2. Identify constraints (time, team, technology)
+3. Research relevant patterns and prior art
+4. Decompose into phases with clear deliverables
+5. Identify risks and dependencies
+6. Create prioritized task list
+
+## Output Structure
+
+- Problem statement and constraints
+- Evaluated approaches with trade-offs
+- Recommended approach with rationale
+- Phased implementation plan
+- Risk assessment and mitigations
+- Success criteria for each phase
+
+## Principles
+
+- YAGNI: do not plan for features not yet needed
+- KISS: prefer simple solutions over clever ones
+- Incremental delivery: working software at each phase
+- Reversible decisions: prefer approaches that are easy to change

package/dist/presets/fullstack/skills/problem-solving/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: problem-solving
+description: Apply systematic problem-solving techniques for complexity spirals, innovation blocks, recurring patterns, and assumption constraints.
+---
+
+# Problem Solving
+
+Activate when stuck on complex problems, facing innovation blocks, or dealing with recurring patterns.
+
+## Techniques
+
+### Simplification Cascade
+When complexity spirals: remove features until the core works, then add back one at a time.
+
+### Collision-Zone Thinking
+When innovation is blocked: combine two unrelated concepts to find novel solutions.
+
+### Meta-Pattern Recognition
+When patterns recur: identify the underlying pattern and solve at a higher abstraction level.
+
+### Inversion Exercise
+When constrained by assumptions: invert the problem. Ask "what if the opposite were true?"
+
+### Scale Game
+When uncertain about scale: solve for 1 user, 100 users, 10000 users. See where the design breaks.
+
+## When to Dispatch
+
+- Stuck for more than 15 minutes on the same approach
+- Third attempt at the same fix without progress
+- Solution feels overly complex for the problem size
+- Requirements seem contradictory