@vodailoc/kilo-kit-mcp 1.1.0

package/skills/engineering/setup-matt-pocock-skills/domain.md

@@ -0,0 +1,51 @@
+# Domain Docs
+
+How the engineering skills should consume this repo's domain documentation when exploring the codebase.
+
+## Before exploring, read these
+
+- **`CONTEXT.md`** at the repo root, or
+- **`CONTEXT-MAP.md`** at the repo root if it exists — it points at one `CONTEXT.md` per context. Read each one relevant to the topic.
+- **`docs/adr/`** — read ADRs that touch the area you're about to work in. In multi-context repos, also check `src/<context>/docs/adr/` for context-scoped decisions.
+
+If any of these files don't exist, **proceed silently**. Don't flag their absence; don't suggest creating them upfront. The producer skill (`/grill-with-docs`) creates them lazily when terms or decisions actually get resolved.
+
+## File structure
+
+Single-context repo (most repos):
+
+```
+/
+├── CONTEXT.md
+├── docs/adr/
+│   ├── 0001-event-sourced-orders.md
+│   └── 0002-postgres-for-write-model.md
+└── src/
+```
+
+Multi-context repo (presence of `CONTEXT-MAP.md` at the root):
+
+```
+/
+├── CONTEXT-MAP.md
+├── docs/adr/                          ← system-wide decisions
+└── src/
+    ├── ordering/
+    │   ├── CONTEXT.md
+    │   └── docs/adr/                  ← context-specific decisions
+    └── billing/
+        ├── CONTEXT.md
+        └── docs/adr/
+```
+
+## Use the glossary's vocabulary
+
+When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `CONTEXT.md`. Don't drift to synonyms the glossary explicitly avoids.
+
+If the concept you need isn't in the glossary yet, that's a signal — either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for `/grill-with-docs`).
+
+## Flag ADR conflicts
+
+If your output contradicts an existing ADR, surface it explicitly rather than silently overriding:
+
+> _Contradicts ADR-0007 (event-sourced orders) — but worth reopening because…_

package/skills/engineering/setup-matt-pocock-skills/issue-tracker-github.md

@@ -0,0 +1,22 @@
+# Issue tracker: GitHub
+
+Issues and PRDs for this repo live as GitHub issues. Use the `gh` CLI for all operations.
+
+## Conventions
+
+- **Create an issue**: `gh issue create --title "..." --body "..."`. Use a heredoc for multi-line bodies.
+- **Read an issue**: `gh issue view <number> --comments`, filtering comments by `jq` and also fetching labels.
+- **List issues**: `gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'` with appropriate `--label` and `--state` filters.
+- **Comment on an issue**: `gh issue comment <number> --body "..."`
+- **Apply / remove labels**: `gh issue edit <number> --add-label "..."` / `--remove-label "..."`
+- **Close**: `gh issue close <number> --comment "..."`
+
+Infer the repo from `git remote -v` — `gh` does this automatically when run inside a clone.
+
+## When a skill says "publish to the issue tracker"
+
+Create a GitHub issue.
+
+## When a skill says "fetch the relevant ticket"
+
+Run `gh issue view <number> --comments`.

package/skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md

@@ -0,0 +1,23 @@
+# Issue tracker: GitLab
+
+Issues and PRDs for this repo live as GitLab issues. Use the [`glab`](https://gitlab.com/gitlab-org/cli) CLI for all operations.
+
+## Conventions
+
+- **Create an issue**: `glab issue create --title "..." --description "..."`. Use a heredoc for multi-line descriptions. Pass `--description -` to open an editor.
+- **Read an issue**: `glab issue view <number> --comments`. Use `-F json` for machine-readable output.
+- **List issues**: `glab issue list --state opened -F json` with appropriate `--label` filters. Note that GitLab uses `opened` (not `open`) for the state value.
+- **Comment on an issue**: `glab issue note <number> --message "..."`. GitLab calls comments "notes".
+- **Apply / remove labels**: `glab issue update <number> --label "..."` / `--unlabel "..."`. Multiple labels can be comma-separated or by repeating the flag.
+- **Close**: `glab issue close <number>`. `glab issue close` does not accept a closing comment, so post the explanation first with `glab issue note <number> --message "..."`, then close.
+- **Merge requests**: GitLab calls PRs "merge requests". Use `glab mr create`, `glab mr view`, `glab mr note`, etc. — the same shape as `gh pr ...` with `mr` in place of `pr` and `note`/`--message` in place of `comment`/`--body`.
+
+Infer the repo from `git remote -v` — `glab` does this automatically when run inside a clone.
+
+## When a skill says "publish to the issue tracker"
+
+Create a GitLab issue.
+
+## When a skill says "fetch the relevant ticket"
+
+Run `glab issue view <number> --comments`.

package/skills/engineering/setup-matt-pocock-skills/issue-tracker-local.md

@@ -0,0 +1,19 @@
+# Issue tracker: Local Markdown
+
+Issues and PRDs for this repo live as markdown files in `.scratch/`.
+
+## Conventions
+
+- One feature per directory: `.scratch/<feature-slug>/`
+- The PRD is `.scratch/<feature-slug>/PRD.md`
+- Implementation issues are `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01`
+- Triage state is recorded as a `Status:` line near the top of each issue file (see `triage-labels.md` for the role strings)
+- Comments and conversation history append to the bottom of the file under a `## Comments` heading
+
+## When a skill says "publish to the issue tracker"
+
+Create a new file under `.scratch/<feature-slug>/` (creating the directory if needed).
+
+## When a skill says "fetch the relevant ticket"
+
+Read the file at the referenced path. The user will normally pass the path or the issue number directly.

package/skills/engineering/setup-matt-pocock-skills/triage-labels.md

@@ -0,0 +1,15 @@
+# Triage Labels
+
+The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
+
+| Label in mattpocock/skills | Label in our tracker | Meaning                                  |
+| -------------------------- | -------------------- | ---------------------------------------- |
+| `needs-triage`             | `needs-triage`       | Maintainer needs to evaluate this issue  |
+| `needs-info`               | `needs-info`         | Waiting on reporter for more information |
+| `ready-for-agent`          | `ready-for-agent`    | Fully specified, ready for an AFK agent  |
+| `ready-for-human`          | `ready-for-human`    | Requires human implementation            |
+| `wontfix`                  | `wontfix`            | Will not be actioned                     |
+
+When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table.
+
+Edit the right-hand column to match whatever vocabulary you actually use.

package/skills/engineering/shopify/README.md

@@ -0,0 +1,66 @@
+# Shopify API Research Documentation
+
+This directory contains comprehensive research and analysis of various APIs for integration purposes.
+
+## Contents
+
+### Shopify GraphQL Admin API Analysis
+**File:** `shopify-graphql-admin-api-analysis.md`  
+**Date:** 2025-10-25  
+**Status:** Complete  
+**Thoroughness:** Very Thorough
+
+A comprehensive analysis of Shopify's GraphQL Admin API covering:
+- API overview and capabilities
+- Key features and operations
+- Common query and mutation patterns
+- Best practices and optimization strategies
+- Authentication and security considerations
+- Rate limiting and performance optimization
+- Typical use cases and implementation patterns
+- Troubleshooting guide
+- Code examples in multiple languages
+- Resources and further learning
+
+**Key Sections:**
+1. Executive Summary
+2. API Overview
+3. Key Features
+4. Common Operations (Queries & Mutations)
+5. API Structure (Types, Connections, Errors)
+6. Best Practices
+7. Typical Use Cases
+8. API Versions and Deprecation
+9. Tools and SDKs
+10. Security Considerations
+11. Performance Optimization
+12. Common Patterns
+13. Troubleshooting
+14. Resources and Further Learning
+
+**Size:** 1,348 lines, ~26KB
+
+---
+
+## Usage
+
+These documents are intended for:
+- Development planning and architecture decisions
+- Team onboarding and training
+- Integration implementation reference
+- Best practices guidance
+- Troubleshooting support
+
+---
+
+## Maintenance
+
+- Documents should be reviewed quarterly
+- Update when API versions change
+- Add new findings from implementation experience
+- Keep code examples current with latest SDK versions
+
+---
+
+**Last Updated:** 2025-10-25  
+**Maintained By:** Claude Code Engineering Team

package/skills/engineering/shopify/SKILL.md

@@ -0,0 +1,319 @@
+---
+name: shopify
+description: Build Shopify applications, extensions, and themes using GraphQL/REST APIs, Shopify CLI, Polaris UI components, and Liquid templating. Capabilities include app development with OAuth authentication, checkout UI extensions for customizing checkout flow, admin UI extensions for dashboard integration, POS extensions for retail, theme development with Liquid, webhook management, billing API integration, product/order/customer management. Use when building Shopify apps, implementing checkout customizations, creating admin interfaces, developing themes, integrating payment processing, managing store data via APIs, or extending Shopify functionality.
+---
+
+# Shopify Development
+
+Comprehensive guide for building on Shopify platform: apps, extensions, themes, and API integrations.
+
+## Platform Overview
+
+**Core Components:**
+- **Shopify CLI** - Development workflow tool
+- **GraphQL Admin API** - Primary API for data operations (recommended)
+- **REST Admin API** - Legacy API (maintenance mode)
+- **Polaris UI** - Design system for consistent interfaces
+- **Liquid** - Template language for themes
+
+**Extension Points:**
+- Checkout UI - Customize checkout experience
+- Admin UI - Extend admin dashboard
+- POS UI - Point of Sale customization
+- Customer Account - Post-purchase pages
+- Theme App Extensions - Embedded theme functionality
+
+## Quick Start
+
+### Prerequisites
+
+```bash
+# Install Shopify CLI
+npm install -g @shopify/cli@latest
+
+# Verify installation
+shopify version
+```
+
+### Create New App
+
+```bash
+# Initialize app
+shopify app init
+
+# Start development server
+shopify app dev
+
+# Generate extension
+shopify app generate extension --type checkout_ui_extension
+
+# Deploy
+shopify app deploy
+```
+
+### Theme Development
+
+```bash
+# Initialize theme
+shopify theme init
+
+# Start local preview
+shopify theme dev
+
+# Pull from store
+shopify theme pull --live
+
+# Push to store
+shopify theme push --development
+```
+
+## Development Workflow
+
+### 1. App Development
+
+**Setup:**
+```bash
+shopify app init
+cd my-app
+```
+
+**Configure Access Scopes** (`shopify.app.toml`):
+```toml
+[access_scopes]
+scopes = "read_products,write_products,read_orders"
+```
+
+**Start Development:**
+```bash
+shopify app dev  # Starts local server with tunnel
+```
+
+**Add Extensions:**
+```bash
+shopify app generate extension --type checkout_ui_extension
+```
+
+**Deploy:**
+```bash
+shopify app deploy  # Builds and uploads to Shopify
+```
+
+### 2. Extension Development
+
+**Available Types:**
+- Checkout UI - `checkout_ui_extension`
+- Admin Action - `admin_action`
+- Admin Block - `admin_block`
+- POS UI - `pos_ui_extension`
+- Function - `function` (discounts, payment, delivery, validation)
+
+**Workflow:**
+```bash
+shopify app generate extension
+# Select type, configure
+shopify app dev  # Test locally
+shopify app deploy  # Publish
+```
+
+### 3. Theme Development
+
+**Setup:**
+```bash
+shopify theme init
+# Choose Dawn (reference theme) or start fresh
+```
+
+**Local Development:**
+```bash
+shopify theme dev
+# Preview at localhost:9292
+# Auto-syncs to development theme
+```
+
+**Deployment:**
+```bash
+shopify theme push --development  # Push to dev theme
+shopify theme publish --theme=123  # Set as live
+```
+
+## When to Build What
+
+### Build an App When:
+- Integrating external services
+- Adding functionality across multiple stores
+- Building merchant-facing admin tools
+- Managing store data programmatically
+- Implementing complex business logic
+- Charging for functionality
+
+### Build an Extension When:
+- Customizing checkout flow
+- Adding fields/features to admin pages
+- Creating POS actions for retail
+- Implementing discount/payment/shipping rules
+- Extending customer account pages
+
+### Build a Theme When:
+- Creating custom storefront design
+- Building unique shopping experiences
+- Customizing product/collection pages
+- Implementing brand-specific layouts
+- Modifying homepage/content pages
+
+### Combination Approach:
+**App + Theme Extension:**
+- App handles backend logic and data
+- Theme extension provides storefront UI
+- Example: Product reviews, wishlists, size guides
+
+## Essential Patterns
+
+### GraphQL Product Query
+
+```graphql
+query GetProducts($first: Int!) {
+  products(first: $first) {
+    edges {
+      node {
+        id
+        title
+        handle
+        variants(first: 5) {
+          edges {
+            node {
+              id
+              price
+              inventoryQuantity
+            }
+          }
+        }
+      }
+    }
+    pageInfo {
+      hasNextPage
+      endCursor
+    }
+  }
+}
+```
+
+### Checkout Extension (React)
+
+```javascript
+import { reactExtension, BlockStack, TextField, Checkbox } from '@shopify/ui-extensions-react/checkout';
+
+export default reactExtension('purchase.checkout.block.render', () => <Extension />);
+
+function Extension() {
+  const [message, setMessage] = useState('');
+
+  return (
+    <BlockStack>
+      <TextField label="Gift Message" value={message} onChange={setMessage} />
+    </BlockStack>
+  );
+}
+```
+
+### Liquid Product Display
+
+```liquid
+{% for product in collection.products %}
+  <div class="product-card">
+    <img src="{{ product.featured_image | img_url: 'medium' }}" alt="{{ product.title }}">
+    <h3>{{ product.title }}</h3>
+    <p>{{ product.price | money }}</p>
+    <a href="{{ product.url }}">View Details</a>
+  </div>
+{% endfor %}
+```
+
+## Best Practices
+
+**API Usage:**
+- Prefer GraphQL over REST for new development
+- Request only needed fields to reduce costs
+- Implement pagination for large datasets
+- Use bulk operations for batch processing
+- Respect rate limits (cost-based for GraphQL)
+
+**Security:**
+- Store API credentials in environment variables
+- Verify webhook signatures
+- Use OAuth for public apps
+- Request minimal access scopes
+- Implement session tokens for embedded apps
+
+**Performance:**
+- Cache API responses when appropriate
+- Optimize images in themes
+- Minimize Liquid logic complexity
+- Use async loading for extensions
+- Monitor query costs in GraphQL
+
+**Testing:**
+- Use development stores for testing
+- Test across different store plans
+- Verify mobile responsiveness
+- Check accessibility (keyboard, screen readers)
+- Validate GDPR compliance
+
+## Reference Documentation
+
+Detailed guides for advanced topics:
+
+- **[App Development](references/app-development.md)** - OAuth, APIs, webhooks, billing
+- **[Extensions](references/extensions.md)** - Checkout, Admin, POS, Functions
+- **[Themes](references/themes.md)** - Liquid, sections, deployment
+
+## Scripts
+
+**[shopify_init.py](scripts/shopify_init.py)** - Initialize Shopify projects interactively
+```bash
+python scripts/shopify_init.py
+```
+
+## Troubleshooting
+
+**Rate Limit Errors:**
+- Monitor `X-Shopify-Shop-Api-Call-Limit` header
+- Implement exponential backoff
+- Use bulk operations for large datasets
+
+**Authentication Failures:**
+- Verify access token validity
+- Check required scopes granted
+- Ensure OAuth flow completed
+
+**Extension Not Appearing:**
+- Verify extension target correct
+- Check extension published
+- Ensure app installed on store
+
+**Webhook Not Receiving:**
+- Verify webhook URL accessible
+- Check signature validation
+- Review logs in Partner Dashboard
+
+## Resources
+
+**Official Documentation:**
+- Shopify Docs: https://shopify.dev/docs
+- GraphQL API: https://shopify.dev/docs/api/admin-graphql
+- Shopify CLI: https://shopify.dev/docs/api/shopify-cli
+- Polaris: https://polaris.shopify.com
+
+**Tools:**
+- GraphiQL Explorer (Admin → Settings → Apps → Develop apps)
+- Partner Dashboard (app management)
+- Development stores (free testing)
+
+**API Versioning:**
+- Quarterly releases (YYYY-MM format)
+- Current: 2025-01
+- 12-month support per version
+- Test before version updates
+
+---
+
+**Note:** This skill covers Shopify platform as of January 2025. Refer to official documentation for latest updates.