@etus/bhono-app 0.1.1

package/templates/base/.claude/skills/linear/templates/bug-report.md

@@ -0,0 +1,99 @@
+# Bug Report Template
+
+## Template Configuration
+
+| Property | Value |
+|----------|-------|
+| **Name** | Bug Report |
+| **Labels** | `bug` |
+| **Priority** | 2 (High) or use triage |
+| **Default Status** | Triage |
+
+## Description Template
+
+```markdown
+## Summary
+<!-- Brief description of the bug -->
+
+## Environment
+- **Browser/App**:
+- **OS**:
+- **Device**:
+- **User Account**:
+
+## Steps to Reproduce
+1.
+2.
+3.
+
+## Expected Behavior
+<!-- What should have happened -->
+
+## Actual Behavior
+<!-- What actually happened -->
+
+## Screenshots/Videos
+<!-- Attach visual evidence if applicable -->
+
+## Console Errors
+<!-- Paste any relevant error messages -->
+
+## Additional Context
+<!-- Any other relevant information -->
+```
+
+## CLI Usage
+
+```bash
+# Create bug report
+npx tsx scripts/issues/create.ts \
+  --title "Bug: [Component] - Brief description" \
+  --description "## Summary
+Login button does not respond on mobile Safari.
+
+## Environment
+- **Browser/App**: Safari 17.2
+- **OS**: iOS 17.1
+- **Device**: iPhone 15 Pro
+
+## Steps to Reproduce
+1. Open app on mobile Safari
+2. Navigate to login page
+3. Tap login button
+
+## Expected Behavior
+Login form should submit and redirect to dashboard.
+
+## Actual Behavior
+Nothing happens when tapping the button.
+
+## Console Errors
+\`\`\`
+TypeError: Cannot read property 'submit' of null
+\`\`\`" \
+  --priority 2 \
+  --json
+```
+
+## Best Practices
+
+1. **Title Format**: `Bug: [Component/Feature] - Brief description`
+   - `Bug: Cart - Cannot add items on mobile`
+   - `Bug: Auth - Session expires unexpectedly`
+
+2. **Include Visual Evidence**: Screenshots or screen recordings significantly speed up debugging
+
+3. **Capture Console Logs**: JavaScript errors help developers reproduce issues
+
+4. **Specify Environment**: Bugs often only appear in specific browsers/devices
+
+5. **Be Specific**: "Button doesn't work" → "Login button doesn't respond to tap events on iOS Safari"
+
+## Severity Guidelines
+
+| Severity | Description | Example |
+|----------|-------------|---------|
+| **Urgent (1)** | App unusable, data loss | Payment processing fails |
+| **High (2)** | Major feature broken | Cannot login |
+| **Medium (3)** | Feature degraded | Slow page load |
+| **Low (4)** | Minor issue | Typo in UI |

package/templates/base/.claude/skills/linear/templates/feature-request.md

@@ -0,0 +1,118 @@
+# Feature Request Template
+
+## Template Configuration
+
+| Property | Value |
+|----------|-------|
+| **Name** | Feature Request |
+| **Labels** | `enhancement` |
+| **Priority** | 3 (Medium) or use triage |
+| **Default Status** | Backlog |
+
+## Description Template
+
+```markdown
+## Problem Statement
+<!-- What problem does this solve? Who is affected? -->
+
+## Proposed Solution
+<!-- Describe the feature you'd like -->
+
+## User Stories
+<!-- As a [user type], I want [feature] so that [benefit] -->
+
+- As a user, I want to...
+- As an admin, I want to...
+
+## Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
+
+## Design/Mockups
+<!-- Link to designs or describe UI expectations -->
+
+## Technical Considerations
+<!-- Any known technical constraints or dependencies -->
+
+## Alternatives Considered
+<!-- What other solutions were explored? -->
+
+## Additional Context
+<!-- Business value, customer requests, competitive analysis -->
+```
+
+## CLI Usage
+
+```bash
+# Create feature request
+npx tsx scripts/issues/create.ts \
+  --title "Feature: Add dark mode toggle" \
+  --description "## Problem Statement
+Users have requested dark mode support, especially for nighttime usage. Currently, the app only supports light theme which causes eye strain in low-light environments.
+
+## Proposed Solution
+Add a dark mode toggle in Settings that switches the app theme. The preference should persist across sessions.
+
+## User Stories
+- As a user, I want to switch to dark mode so that I can use the app comfortably at night
+- As a user, I want my theme preference saved so that I don't have to toggle it each session
+
+## Acceptance Criteria
+- [ ] Toggle switch in Settings page
+- [ ] Dark theme applied to all components
+- [ ] Preference persisted in localStorage
+- [ ] Respects system preference by default
+- [ ] Smooth transition animation
+
+## Design/Mockups
+https://www.figma.com/file/abc123
+
+## Technical Considerations
+- Use CSS variables for theme colors
+- Consider prefers-color-scheme media query
+- Test with all existing components
+
+## Alternatives Considered
+- Auto-detect only (no manual toggle) - rejected: users want control
+- Scheduled dark mode - future enhancement" \
+  --priority 3 \
+  --json
+```
+
+## Best Practices
+
+1. **Title Format**: `Feature: Brief description`
+   - `Feature: Add export to CSV functionality`
+   - `Feature: Enable two-factor authentication`
+
+2. **Focus on the Problem**: Explain the "why" before the "what"
+
+3. **Include User Stories**: Helps team understand user perspective
+
+4. **Define Done**: Clear acceptance criteria prevent scope creep
+
+5. **Link Designs**: Visual references accelerate development
+
+6. **Mention Alternatives**: Shows you've thought through options
+
+## Priority Guidelines
+
+| Priority | Criteria |
+|----------|----------|
+| **Urgent (1)** | Critical for launch, blocking revenue |
+| **High (2)** | High customer demand, competitive feature |
+| **Medium (3)** | Nice to have, improves UX |
+| **Low (4)** | Future consideration, minor enhancement |
+
+## Linking Related Issues
+
+Reference related issues in the description:
+```markdown
+## Related Issues
+- Blocked by: https://linear.app/workspace/issue/AA-100
+- Related: https://linear.app/workspace/issue/AA-101
+- Parent epic: https://linear.app/workspace/issue/AA-50
+```
+
+Linear will automatically convert these URLs to clickable issue links.

package/templates/base/.claude/skills/linear/templates/security-issue.md

@@ -0,0 +1,162 @@
+# Security Issue Template
+
+## Template Configuration
+
+| Property | Value |
+|----------|-------|
+| **Name** | Security Issue |
+| **Labels** | `security`, `vulnerability` |
+| **Priority** | 1 (Urgent) or 2 (High) |
+| **Default Status** | Triage |
+
+## Description Template
+
+```markdown
+## Vulnerability Summary
+<!-- Brief description of the security issue -->
+
+## Severity
+<!-- Critical / High / Medium / Low -->
+
+## CVSS Score (if applicable)
+<!-- e.g., 7.5 (High) -->
+
+## Affected Components
+<!-- Which systems/services are affected? -->
+
+-
+-
+
+## Attack Vector
+<!-- How could this be exploited? -->
+
+## Impact
+<!-- What's the potential damage? -->
+
+- **Confidentiality**:
+- **Integrity**:
+- **Availability**:
+
+## Steps to Reproduce
+<!-- How to verify the vulnerability exists -->
+
+1.
+2.
+3.
+
+## Proof of Concept
+<!-- Code or demonstration if safe to share -->
+
+## Recommended Fix
+<!-- Proposed remediation -->
+
+## References
+<!-- CVE IDs, security advisories, documentation -->
+
+-
+
+## Discovery
+- **Discovered by**:
+- **Discovered date**:
+- **Disclosure deadline**:
+```
+
+## CLI Usage
+
+```bash
+# Create security issue (CONFIDENTIAL - be careful with details)
+npx tsx scripts/issues/create.ts \
+  --title "Security: SQL Injection in search endpoint" \
+  --description "## Vulnerability Summary
+SQL injection vulnerability in the /api/search endpoint allows unauthorized database access.
+
+## Severity
+High
+
+## CVSS Score
+8.6 (High)
+
+## Affected Components
+- \`/api/search\` endpoint
+- \`src/services/search.ts\`
+
+## Attack Vector
+User-supplied search query is concatenated directly into SQL without parameterization.
+
+## Impact
+- **Confidentiality**: High - Attacker can read any database records
+- **Integrity**: High - Attacker can modify database records
+- **Availability**: Medium - Potential for data deletion
+
+## Steps to Reproduce
+1. Navigate to search page
+2. Enter: \`'; DROP TABLE users; --\`
+3. Observe SQL error in response
+
+## Recommended Fix
+Use parameterized queries:
+\`\`\`typescript
+// Before (vulnerable)
+const query = \\\`SELECT * FROM items WHERE name = '\${searchTerm}'\\\`;
+
+// After (safe)
+const query = 'SELECT * FROM items WHERE name = $1';
+const result = await db.query(query, [searchTerm]);
+\`\`\`
+
+## References
+- OWASP SQL Injection: https://owasp.org/www-community/attacks/SQL_Injection
+- CWE-89: https://cwe.mitre.org/data/definitions/89.html
+
+## Discovery
+- **Discovered by**: Security audit
+- **Discovered date**: 2025-01-15
+- **Disclosure deadline**: 2025-01-22" \
+  --priority 1 \
+  --json
+```
+
+## Best Practices
+
+1. **Title Format**: `Security: Brief description (no exploit details)`
+   - `Security: Authentication bypass in admin panel`
+   - `Security: XSS vulnerability in comments`
+
+2. **Handle Sensitively**:
+   - Don't include full exploit code in public channels
+   - Use private issues if available
+   - Follow responsible disclosure practices
+
+3. **Include Severity**: Use standard severity ratings (Critical/High/Medium/Low)
+
+4. **Provide Remediation**: Security issues should include fix recommendations
+
+5. **Set Deadline**: Security issues often have disclosure timelines
+
+## Severity Guidelines
+
+| Severity | CVSS | Response Time | Examples |
+|----------|------|---------------|----------|
+| **Critical** | 9.0-10.0 | Immediate | RCE, auth bypass, data breach |
+| **High** | 7.0-8.9 | 24-48 hours | SQL injection, privilege escalation |
+| **Medium** | 4.0-6.9 | 1 week | XSS, CSRF, info disclosure |
+| **Low** | 0.1-3.9 | Next sprint | Missing headers, minor leaks |
+
+## Common Vulnerability Types
+
+| Type | Label | Example |
+|------|-------|---------|
+| Injection | `injection` | SQL, NoSQL, Command, LDAP |
+| Authentication | `auth` | Broken auth, session issues |
+| XSS | `xss` | Reflected, Stored, DOM-based |
+| Access Control | `access-control` | IDOR, privilege escalation |
+| Cryptography | `crypto` | Weak encryption, key exposure |
+| Configuration | `misconfiguration` | Default creds, open ports |
+
+## Responsible Disclosure
+
+If external:
+1. Acknowledge receipt within 24 hours
+2. Provide timeline for fix
+3. Credit reporter (if desired)
+4. Coordinate disclosure date

package/templates/base/.claude/skills/linear/templates/sprint-task.md

@@ -0,0 +1,175 @@
+# Sprint Task Template
+
+## Template Configuration
+
+| Property | Value |
+|----------|-------|
+| **Name** | Sprint Task |
+| **Labels** | (varies by task type) |
+| **Priority** | 3 (Medium) |
+| **Default Status** | Todo |
+| **Estimate** | (set per task) |
+
+## Description Template
+
+```markdown
+## Objective
+<!-- What needs to be accomplished? -->
+
+## Background
+<!-- Why are we doing this? Context and motivation -->
+
+## Requirements
+- [ ] Requirement 1
+- [ ] Requirement 2
+- [ ] Requirement 3
+
+## Technical Approach
+<!-- How will this be implemented? -->
+
+## Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Tests written and passing
+- [ ] Code reviewed
+
+## Dependencies
+<!-- What needs to happen first? -->
+
+## Out of Scope
+<!-- What are we NOT doing? -->
+
+## Links
+- Design:
+- Spec:
+- Parent issue:
+```
+
+## CLI Usage
+
+```bash
+# Create sprint task
+npx tsx scripts/issues/create.ts \
+  --title "Implement user avatar upload" \
+  --description "## Objective
+Add the ability for users to upload and update their profile avatar.
+
+## Background
+Users have requested the ability to personalize their profiles. Currently, we only show initials.
+
+## Requirements
+- [ ] Upload button on profile settings page
+- [ ] Support JPEG, PNG, WebP formats
+- [ ] Max file size: 5MB
+- [ ] Auto-resize to 256x256
+- [ ] Store in S3 bucket
+
+## Technical Approach
+1. Add file input component to ProfileSettings
+2. Create \`/api/users/avatar\` endpoint
+3. Use sharp for image processing
+4. Upload to S3 with user ID as key
+5. Update user record with avatar URL
+
+## Acceptance Criteria
+- [ ] User can upload image from profile settings
+- [ ] Image is resized and optimized
+- [ ] Avatar displays throughout app
+- [ ] Invalid files show error message
+- [ ] Unit tests for upload service
+- [ ] E2E test for upload flow
+
+## Dependencies
+- S3 bucket configured (already done)
+- sharp package installed
+
+## Out of Scope
+- Avatar cropping UI (future enhancement)
+- Gravatar integration
+- Avatar history
+
+## Links
+- Design: https://www.figma.com/file/abc123
+- Parent epic: https://linear.app/workspace/issue/AA-50" \
+  --priority 3 \
+  --estimate 3 \
+  --json
+```
+
+## Best Practices
+
+1. **Title Format**: Imperative verb + what
+   - `Implement user avatar upload`
+   - `Add pagination to user list`
+   - `Fix memory leak in WebSocket handler`
+
+2. **Define "Done"**: Clear acceptance criteria prevent ambiguity
+
+3. **List Dependencies**: Helps with sprint planning
+
+4. **Scope Boundaries**: "Out of Scope" prevents creep
+
+5. **Link Related Issues**: Reference parent epics, blockers, related work
+
+## Estimate Guidelines
+
+Use Fibonacci or T-shirt sizing consistently:
+
+| Points | Effort | Example |
+|--------|--------|---------|
+| 1 | Few hours | Config change, copy update |
+| 2 | Half day | Simple component, small fix |
+| 3 | 1 day | Feature with tests |
+| 5 | 2-3 days | Complex feature |
+| 8 | 1 week | Large feature, multiple components |
+| 13 | 2 weeks | Epic-level work (should be broken down) |
+
+## Task Breakdown Pattern
+
+For larger tasks, create sub-issues:
+
+```bash
+# Parent task
+npx tsx scripts/issues/create.ts \
+  --title "Epic: User profile system" \
+  --description "..." \
+  --json
+
+# Sub-tasks (using parent ID)
+npx tsx scripts/issues/create.ts \
+  --title "Add profile settings page" \
+  --parent AA-100 \
+  --estimate 3 \
+  --json
+
+npx tsx scripts/issues/create.ts \
+  --title "Implement avatar upload" \
+  --parent AA-100 \
+  --estimate 5 \
+  --json
+
+npx tsx scripts/issues/create.ts \
+  --title "Add profile API endpoints" \
+  --parent AA-100 \
+  --estimate 3 \
+  --json
+```
+
+## Status Workflow
+
+Typical sprint task flow:
+```
+Todo → In Progress → In Review → Done
+```
+
+Update status as you work:
+```bash
+# Start working
+npx tsx scripts/status/update.ts AA-101 "in-progress-state-id" --json
+
+# Submit for review
+npx tsx scripts/status/update.ts AA-101 "in-review-state-id" --json
+
+# Complete
+npx tsx scripts/status/update.ts AA-101 "done-state-id" --json
+```

package/templates/base/.claude/skills/linear/templates/tech-debt.md

@@ -0,0 +1,137 @@
+# Technical Debt Template
+
+## Template Configuration
+
+| Property | Value |
+|----------|-------|
+| **Name** | Technical Debt |
+| **Labels** | `tech-debt`, `refactor` |
+| **Priority** | 4 (Low) or 3 (Medium) |
+| **Default Status** | Backlog |
+
+## Description Template
+
+```markdown
+## Summary
+<!-- Brief description of the technical debt -->
+
+## Current State
+<!-- What's the problem with the current implementation? -->
+
+## Impact
+<!-- How does this affect development, performance, or maintainability? -->
+
+- **Development velocity**:
+- **Performance**:
+- **Security risk**:
+- **Test coverage**:
+
+## Proposed Solution
+<!-- How should this be refactored? -->
+
+## Files/Components Affected
+<!-- List the areas of code that need changes -->
+
+- `src/components/...`
+- `src/utils/...`
+
+## Migration Strategy
+<!-- If breaking changes, how will we migrate? -->
+
+## Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Tests updated
+- [ ] Documentation updated
+
+## Effort Estimate
+<!-- T-shirt size: XS, S, M, L, XL -->
+
+## Risk Assessment
+<!-- What could go wrong? -->
+```
+
+## CLI Usage
+
+```bash
+# Create tech debt issue
+npx tsx scripts/issues/create.ts \
+  --title "Tech Debt: Migrate from moment.js to date-fns" \
+  --description "## Summary
+Replace moment.js with date-fns to reduce bundle size and improve tree-shaking.
+
+## Current State
+We're using moment.js (300KB gzipped) for date formatting throughout the app. It's imported wholesale and doesn't tree-shake.
+
+## Impact
+- **Development velocity**: Neutral
+- **Performance**: -300KB bundle size potential savings
+- **Security risk**: moment.js is in maintenance mode
+- **Test coverage**: Need to update date-related tests
+
+## Proposed Solution
+1. Install date-fns
+2. Create adapter layer with same API
+3. Migrate components incrementally
+4. Remove moment.js when complete
+
+## Files/Components Affected
+- \`src/utils/date.ts\`
+- \`src/components/DatePicker/\`
+- \`src/components/Timeline/\`
+- \`src/hooks/useFormatDate.ts\`
+
+## Migration Strategy
+1. Add date-fns alongside moment.js
+2. Create \`src/utils/date-adapter.ts\` with unified API
+3. Migrate one component at a time
+4. Remove moment.js after all migrations complete
+
+## Acceptance Criteria
+- [ ] All date operations use date-fns
+- [ ] Bundle size reduced by >200KB
+- [ ] All existing tests pass
+- [ ] No moment.js imports remain
+
+## Effort Estimate
+Medium (M) - 2-3 days
+
+## Risk Assessment
+- Date format inconsistencies during migration
+- Timezone handling differences between libraries" \
+  --priority 4 \
+  --json
+```
+
+## Best Practices
+
+1. **Title Format**: `Tech Debt: Brief description`
+   - `Tech Debt: Remove deprecated API calls`
+   - `Tech Debt: Add TypeScript to utils folder`
+
+2. **Quantify Impact**: "Reduces build time by 30%" is better than "Makes build faster"
+
+3. **Include Migration Path**: Especially for breaking changes
+
+4. **List Affected Files**: Helps estimate scope
+
+5. **Link to Related Issues**: Tech debt often blocks feature work
+
+## Priority Guidelines
+
+| Priority | When to Use |
+|----------|-------------|
+| **High (2)** | Blocks feature development, security risk |
+| **Medium (3)** | Significant performance/DX improvement |
+| **Low (4)** | Nice to have, long-term improvement |
+
+## Common Tech Debt Categories
+
+| Category | Examples |
+|----------|----------|
+| **Dependencies** | Outdated packages, deprecated libraries |
+| **Code Quality** | Missing types, inconsistent patterns |
+| **Performance** | Bundle size, slow queries, memory leaks |
+| **Testing** | Missing tests, flaky tests, low coverage |
+| **Documentation** | Outdated docs, missing API docs |
+| **Infrastructure** | CI/CD improvements, build optimization |

package/templates/base/.claude/skills/linear/tsconfig.json

@@ -0,0 +1,17 @@
+{
+  "compilerOptions": {
+    "target": "ESNext",
+    "module": "ESNext",
+    "moduleResolution": "node",
+    "esModuleInterop": true,
+    "strict": true,
+    "skipLibCheck": true,
+    "forceConsistentCasingInFileNames": true,
+    "resolveJsonModule": true,
+    "declaration": true,
+    "outDir": "./dist",
+    "rootDir": "."
+  },
+  "include": ["**/*.ts"],
+  "exclude": ["node_modules", "dist"]
+}