@codihaus/claude-skills 1.6.20 → 1.6.22

package/skills/debrief/references/file-patterns.md

@@ -1,173 +0,0 @@
-# File Patterns for Codebase Discovery
-
-Patterns for lightweight scanning of existing codebases.
-
-## Frontend File Patterns
-
-### Include
-
-```
-# Vue.js
-**/*.vue
-
-# React / Next.js
-**/*.tsx
-**/*.jsx
-**/pages/**/*.ts
-**/pages/**/*.tsx
-**/app/**/page.tsx
-**/app/**/layout.tsx
-
-# Svelte
-**/*.svelte
-
-# Angular
-**/*.component.ts
-
-# General
-**/views/**/*
-**/screens/**/*
-```
-
-### Exclude
-
-```
-# Dependencies
-node_modules/**
-vendor/**
-bower_components/**
-
-# Build output
-dist/**
-build/**
-.next/**
-.nuxt/**
-.output/**
-out/**
-
-# Bundled files
-*.min.js
-*.bundle.js
-*.chunk.js
-
-# Tests
-__tests__/**
-**/*.test.*
-**/*.spec.*
-**/test/**
-**/tests/**
-
-# Config & misc
-.git/**
-coverage/**
-.cache/**
-```
-
-## Documentation Patterns
-
-Look for existing docs:
-
-```
-# Root docs
-README.md
-CLAUDE.md
-CONTRIBUTING.md
-
-# Doc folders
-docs/**/*.md
-documentation/**/*.md
-plans/**/*.md
-specifications/**/*.md
-specs/**/*.md
-.github/**/*.md
-```
-
-## Feature Inference
-
-Map file/folder names to features:
-
-| Pattern | Feature |
-|---------|---------|
-| `auth/`, `login.*`, `signin.*`, `signup.*` | Authentication |
-| `user/`, `users/`, `profile.*`, `account.*` | User Management |
-| `dashboard.*`, `dashboard/` | Dashboard |
-| `payment/`, `payments/`, `checkout.*`, `billing.*` | Payments |
-| `subscription/`, `subscriptions/`, `plans.*` | Subscriptions |
-| `settings.*`, `settings/`, `preferences.*` | Settings |
-| `admin/`, `admin.*` | Admin Panel |
-| `notification/`, `notifications/`, `alerts/` | Notifications |
-| `search.*`, `search/` | Search |
-| `cart.*`, `cart/`, `basket.*` | Shopping Cart |
-| `order/`, `orders/` | Orders |
-| `product/`, `products/`, `catalog/` | Products |
-| `message/`, `messages/`, `chat/`, `inbox/` | Messaging |
-| `report/`, `reports/`, `analytics/` | Reporting |
-| `upload/`, `files/`, `media/` | File Management |
-| `team/`, `teams/`, `organization/` | Team Management |
-| `onboarding/`, `wizard/`, `setup/` | Onboarding |
-| `help/`, `support/`, `faq/` | Help/Support |
-
-## Tech Stack Detection
-
-### Package Managers
-
-```
-# Check for these files
-package.json      → Node.js / JavaScript
-requirements.txt  → Python
-Gemfile           → Ruby
-go.mod            → Go
-Cargo.toml        → Rust
-composer.json     → PHP
-```
-
-### Framework Detection (from package.json)
-
-| Dependency | Framework |
-|------------|-----------|
-| `next` | Next.js |
-| `nuxt` | Nuxt.js |
-| `vue` | Vue.js |
-| `react` | React |
-| `@angular/core` | Angular |
-| `svelte` | Svelte |
-| `express` | Express.js |
-| `fastify` | Fastify |
-| `nestjs` | NestJS |
-
-## Folder Structure Hints
-
-```
-# Next.js App Router
-app/
-├── page.tsx          → Home page
-├── layout.tsx        → Root layout
-├── (auth)/           → Auth group
-│   ├── login/
-│   └── register/
-└── dashboard/        → Dashboard
-
-# Nuxt.js
-pages/
-├── index.vue         → Home
-├── login.vue         → Login
-└── dashboard/
-    └── index.vue     → Dashboard
-
-# Standard React
-src/
-├── pages/            → Routes
-├── components/       → UI components
-├── hooks/            → Custom hooks
-├── services/         → API calls
-└── utils/            → Helpers
-```
-
-## Scan Strategy
-
-1. **Find package.json** → Detect framework
-2. **Glob for frontend files** → List all pages/components
-3. **Group by folder** → pages/, components/, views/
-4. **Match patterns** → Infer features
-5. **Check for docs** → Read README, CLAUDE.md
-6. **Summarize** → Create feature table

package/skills/debrief/references/group-codes.md

@@ -1,72 +0,0 @@
-# Use Case Group Codes
-
-Standard codes for grouping use cases. Use these for consistency across BRDs.
-
-## Standard Codes
-
-| Code | Domain | Examples |
-|------|--------|----------|
-| **AUTH** | Authentication | Login, logout, password reset, SSO |
-| **USER** | User Management | Registration, profile, settings |
-| **PAY** | Payments | Checkout, refunds, payment methods |
-| **SUB** | Subscriptions | Plans, upgrades, cancellation |
-| **BILL** | Billing | Invoices, receipts, statements |
-| **NOTIF** | Notifications | Email, push, in-app alerts |
-| **ADMIN** | Administration | Dashboard, settings, config |
-| **RPT** | Reporting | Analytics, exports, dashboards |
-| **INTG** | Integrations | API, webhooks, third-party |
-| **SRCH** | Search | Search, filters, browse |
-| **INV** | Inventory | Stock, catalog, products |
-| **ORD** | Orders | Cart, checkout, order history |
-| **SHIP** | Shipping | Delivery, tracking, returns |
-| **MSG** | Messaging | Chat, comments, threads |
-| **FILE** | Files | Upload, storage, sharing |
-| **TEAM** | Teams | Organizations, roles, permissions |
-| **ONBD** | Onboarding | Setup, tutorials, first-run |
-| **SUPP** | Support | Help, tickets, FAQ |
-
-## Choosing Codes
-
-1. **Use existing code** if it fits
-2. **Create new code** if domain is distinct
-3. **Keep codes 3-5 characters**
-4. **Make it obvious** - anyone should guess the domain
-
-## Custom Codes
-
-For project-specific domains, define in BRD README:
-
-```markdown
-## Custom Group Codes
-
-| Code | Domain | Description |
-|------|--------|-------------|
-| PROP | Properties | Real estate listings |
-| BOOK | Bookings | Reservation system |
-```
-
-## Grouping Strategy
-
-**Group by user intent**, not by feature:
-
-Good:
-- `UC-PAY-001-checkout.md` - User paying
-- `UC-PAY-002-refund-request.md` - User requesting money back
-
-Avoid:
-- `UC-STRIPE-001-...` - Implementation detail, not user intent
-- `UC-BUTTON-001-...` - UI element, not user goal
-
-## Cross-Group Dependencies
-
-Note dependencies in use case files:
-
-```markdown
-> **Related**: [UC-AUTH-001](./UC-AUTH-001-login.md), [UC-PAY-001](./UC-PAY-001-checkout.md)
-```
-
-Common patterns:
-- AUTH → all authenticated features
-- USER → TEAM (user creates team)
-- PAY → SUB (payment enables subscription)
-- ORD → SHIP (order triggers shipping)

package/skills/debrief/references/research-queries.md

@@ -1,106 +0,0 @@
-# Research Query Templates
-
-Use these to gather **references for engineers**, not to prescribe solutions.
-
-## Goal
-
-Populate `references.md` with:
-- Official documentation links
-- Industry examples
-- Implementation case studies
-- Compliance/standards resources
-
-## Query Templates
-
-### Documentation
-```
-"{feature} official documentation"
-"{service} API documentation"
-"{feature} developer guide"
-"{service} SDK documentation"
-```
-
-### Industry Examples
-```
-"how {company} implements {feature}"
-"{feature} case study"
-"{industry} {feature} examples"
-"best {feature} implementations"
-```
-
-### User Flows
-```
-"{feature} user flow examples"
-"{feature} UX patterns"
-"{feature} wireframe examples"
-```
-
-### Compliance & Standards
-```
-"{feature} {regulation} compliance"
-"{feature} security requirements"
-"{industry} {feature} standards"
-"GDPR {feature} requirements"
-"PCI DSS {feature}"
-```
-
-### Open Source / Tutorials
-```
-"{feature} open source implementation"
-"{feature} tutorial github"
-"building {feature} from scratch"
-```
-
-## By Domain
-
-### SaaS / B2B
-```
-"enterprise {feature} requirements"
-"B2B SaaS {feature} examples"
-"{feature} multi-tenant considerations"
-```
-
-### E-commerce
-```
-"{feature} e-commerce best practices"
-"shopify {feature} documentation"
-"stripe {feature} guide"
-```
-
-### Marketplace
-```
-"two-sided marketplace {feature}"
-"platform {feature} patterns"
-```
-
-## Search Strategy
-
-1. **Start broad**: "{feature} documentation"
-2. **Get specific**: "{service} {feature} API"
-3. **Find examples**: "how {leader} does {feature}"
-4. **Check compliance**: "{feature} {regulation}"
-5. **Gather tutorials**: "{feature} implementation guide"
-
-## What to Capture
-
-For each useful result, note:
-- **Title**: Page/article title
-- **URL**: Direct link
-- **Why relevant**: 1-line note for engineers
-- **Applies to**: Which use cases benefit
-
-## Example Output
-
-```markdown
-## Documentation
-| Topic | Link | Notes |
-|-------|------|-------|
-| Stripe Billing | [Stripe Subscriptions](https://stripe.com/docs/billing) | Core billing API |
-| Usage metering | [Stripe Usage Records](https://stripe.com/docs/billing/subscriptions/usage-based) | For usage-based billing |
-
-## Industry Examples
-| Company | Link | What to Learn |
-|---------|------|---------------|
-| Notion | [How Notion Prices](https://www.notion.so/pricing) | Freemium + team pricing |
-| Slack | [Slack Billing](https://slack.com/pricing) | Per-seat model |
-```

package/skills/debrief/references/use-case-template.md

@@ -1,141 +0,0 @@
-# Use Case Template
-
-Standard template for use case files.
-
-## File Naming
-
-Format: `UC-{GROUP}-{NNN}-{slug}.md`
-
-Examples:
-- `UC-PAY-001-checkout.md`
-- `UC-AUTH-002-password-reset.md`
-
-## Template
-
-```markdown
-# UC-{GROUP}-{NNN}: {Title}
-
-> **Feature**: [[feature-{name}]]
-> **Related**: [[uc-xxx-nnn]], [[uc-xxx-nnn]]
-> **Priority**: Must | Should | Could
-> **Status**: Draft | Confirmed | Updated
-
-## User Story
-
-As a {role},
-I want {goal},
-so that {benefit}.
-
-## Acceptance Criteria
-
-- [ ] Given {precondition}, when {action}, then {expected result}
-- [ ] Given {precondition}, when {action}, then {expected result}
-- [ ] Given {precondition}, when {action}, then {expected result}
-
-## Business Rules
-
-- {Rule 1: condition → outcome}
-- {Rule 2: condition → outcome}
-
-## Edge Cases
-
-| Scenario | Expected Behavior |
-|----------|-------------------|
-| {Edge case 1} | {How to handle} |
-| {Edge case 2} | {How to handle} |
-
-## Open Questions
-
-- [ ] {Question requiring stakeholder input}
-- [ ] {Question for engineering to answer}
-
-## References
-
-- [{Relevant doc}]({url})
-- [{Related example}]({url})
-```
-
-## Priority Levels
-
-| Priority | Meaning | Scope Tier |
-|----------|---------|------------|
-| **Must** | Core functionality, cannot launch without | Core |
-| **Should** | Expected by users, standard feature | Standard |
-| **Could** | Nice to have, differentiator | Full |
-
-## Status Values
-
-| Status | Meaning |
-|--------|---------|
-| **Draft** | Initial version, needs review |
-| **Confirmed** | Stakeholder approved |
-| **Updated** | Changed after initial confirmation |
-
-## Writing Tips
-
-### User Stories
-- Keep role specific: "As a **paying customer**" not "As a user"
-- Goal should be concrete: "change my subscription plan"
-- Benefit explains the "why"
-
-### Acceptance Criteria
-- Use Given/When/Then format
-- Each criterion is independently testable
-- Cover happy path + key error paths
-
-### Business Rules
-- Rules that constrain behavior
-- Not implementation details
-- "Users cannot downgrade during trial period"
-
-### Open Questions
-- Mark with `[ ]` so they can be checked off
-- Tag who needs to answer: "(Stakeholder)" or "(Engineering)"
-
-## Example
-
-```markdown
-# UC-PAY-001: Checkout
-
-> **Feature**: [[feature-billing]]
-> **Related**: [[uc-pay-002]], [[uc-cart-001]]
-> **Priority**: Must
-> **Status**: Draft
-
-## User Story
-
-As a customer with items in cart,
-I want to complete my purchase,
-so that I receive my order.
-
-## Acceptance Criteria
-
-- [ ] Given valid cart, when I click checkout, then I see payment form
-- [ ] Given payment details, when I submit, then payment is processed
-- [ ] Given successful payment, when complete, then I see confirmation
-- [ ] Given failed payment, when error occurs, then I see clear error message
-
-## Business Rules
-
-- Minimum order value: $10
-- Maximum items per order: 50
-- Payment must complete within 30 minutes of cart creation
-
-## Edge Cases
-
-| Scenario | Expected Behavior |
-|----------|-------------------|
-| Cart expires during checkout | Show message, redirect to cart |
-| Item goes out of stock | Remove item, notify user |
-| Network error during payment | Retry option, no duplicate charge |
-
-## Open Questions
-
-- [ ] (Stakeholder) Do we support guest checkout?
-- [ ] (Engineering) Which payment processor to use?
-
-## References
-
-- [Stripe Checkout](https://stripe.com/docs/checkout)
-- [Baymard Checkout UX](https://baymard.com/checkout-usability)
-```