shirokuma-docs 0.1.0-alpha.1

package/plugin/shirokuma-skills-en/skills/project-config-generator/SKILL.md

@@ -0,0 +1,301 @@
+---
+name: project-config-generator
+description: Generates and updates project-specific configuration files for skills (tech-stack, patterns, issues, setup, workflows). Use when setting up a new project, updating project conventions, or configuring skill project directories.
+allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+---
+
+# Project Config Generator
+
+Creates and maintains project-specific configuration directories for skills like `nextjs-vibe-coding` and `reviewing-on-issue`.
+
+## When to Use
+
+Automatically invoke when the user:
+- Sets up a new project with existing skills
+- Says "generate project config" or "initialize skill configs"
+- Needs to update tech-stack versions
+- Wants to add project-specific patterns or conventions
+- Mentions "configure skills for this project"
+
+## What This Generates
+
+The `project/` directory within each skill contains project-specific configurations:
+
+```
+skill-name/
+├── patterns/         # Reusable patterns (shareable)
+├── templates/        # Code templates (shareable)
+└── project/          # Project-specific (generated by this skill)
+    ├── reference/
+    │   └── tech-stack.md
+    ├── patterns/
+    │   └── *.md
+    ├── issues/
+    │   └── known-issues.md
+    ├── setup/
+    │   └── *.md
+    ├── workflows/
+    │   └── *.md
+    └── optional/
+        └── *.md
+```
+
+## Workflow
+
+### Step 1: Identify Target Skills
+
+Locate skills that support project-specific configurations:
+
+```bash
+ls .claude/skills/*/project/ 2>/dev/null || echo "No project configs found"
+```
+
+Supported skills:
+- `nextjs-vibe-coding`
+- `reviewing-on-issue`
+
+### Step 2: Gather Project Information
+
+Collect from user or detect automatically:
+
+| Info | Source | Example |
+|------|--------|---------|
+| Tech Stack | `package.json`, CLAUDE.md | Next.js 16, React 19 |
+| Database | schema files | Drizzle + PostgreSQL |
+| Auth | auth config | Better Auth |
+| Styling | tailwind config | Tailwind v4 + shadcn |
+| Testing | jest/playwright config | Jest + Playwright |
+| i18n | messages directory | next-intl (ja/en) |
+
+### Step 3: Generate Files
+
+Use templates from `templates/` directory:
+
+#### Required Files
+
+1. **tech-stack.md** - Version information
+   ```bash
+   cat templates/tech-stack.md.template
+   ```
+
+2. **known-issues.md** - CVEs and bugs
+   ```bash
+   cat templates/known-issues.md.template
+   ```
+
+#### Optional Files
+
+| File | When to Create |
+|------|----------------|
+| `patterns/*.md` | Project has unique patterns |
+| `setup/*.md` | Complex setup documentation needed |
+| `workflows/*.md` | Project-specific workflows |
+| `optional/*.md` | Optional integrations |
+
+### Step 4: Apply Templates
+
+For each target skill:
+
+```bash
+SKILL_DIR=".claude/skills/{skill-name}"
+mkdir -p "$SKILL_DIR/project/reference"
+mkdir -p "$SKILL_DIR/project/patterns"
+mkdir -p "$SKILL_DIR/project/issues"
+mkdir -p "$SKILL_DIR/project/setup"
+mkdir -p "$SKILL_DIR/project/workflows"
+mkdir -p "$SKILL_DIR/project/optional"
+```
+
+Generate files with detected values:
+- Replace `{{NEXTJS_VERSION}}` with actual version
+- Replace `{{REACT_VERSION}}` with actual version
+- Add project-specific patterns
+
+### Step 5: Install Rules (Stack Detection)
+
+Install rules from `shirokuma-skills/rules/` based on detected tech stack.
+
+```bash
+mkdir -p .claude/rules
+```
+
+#### Detection Logic
+
+| Condition | Source | Rules Installed |
+|-----------|--------|----------------|
+| Always | `rules/` (root) | `skill-authoring.md`, `output-destinations.md` |
+| Always | `rules/github/` | `discussions-usage.md`, `project-items.md` |
+| `next.config.*` exists | `rules/nextjs/` | All 7 rules |
+| `shirokuma-docs.config.*` exists | `rules/shirokuma-docs/` | `shirokuma-annotations.md` |
+
+#### Next.js Stack Rules (`rules/nextjs/`)
+
+| Rule | Content |
+|------|---------|
+| `tech-stack.md` | Recommended stack + key patterns |
+| `known-issues.md` | CVEs + framework issues |
+| `radix-ui-hydration.md` | Mounted state pattern (path: `components/**`) |
+| `server-actions.md` | Auth → CSRF → Zod flow (path: `lib/actions/**`) |
+| `tailwind-v4.md` | CSS variable syntax (path: `**/*.css`, `components/ui/**`) |
+| `lib-structure.md` | Directory conventions (path: `lib/**`) |
+| `testing.md` | Jest/Playwright patterns (path: `**/*.test.*`) |
+
+#### Language Configuration
+
+Language policy is handled by plugin-specific rules:
+
+| Concern | Where |
+|---------|-------|
+| GitHub output language | `output-language` rule (English for EN plugin) |
+| Config file language | `skill-authoring` rule (English) |
+| Code/comment language | `git-commit-style` rule (English) |
+
+#### Post-Install Adjustments
+
+After copying rules, adjust project-specific values:
+- `tech-stack.md`: Update versions from `package.json`
+- `known-issues.md`: Add project-specific CVEs if any
+- Path-specific rules: Adjust `paths:` frontmatter to match project structure
+
+Use the `managing-rules` skill for further rule customization.
+
+### Step 6: Validate
+
+Checklist:
+- [ ] `project/reference/tech-stack.md` exists
+- [ ] `project/issues/known-issues.md` exists
+- [ ] `.claude/rules/` contains installed rules
+- [ ] All template placeholders replaced
+- [ ] Links in SKILL.md point to valid files
+
+### Step 7: Report
+
+Output summary:
+
+```markdown
+## Project Config Generated
+
+### Target Skills
+- nextjs-vibe-coding
+- reviewing-on-issue
+
+### Files Created/Updated
+- project/reference/tech-stack.md
+- project/issues/known-issues.md
+- project/patterns/lib-structure.md
+
+### Detected Stack
+| Category | Value |
+|----------|-------|
+| Framework | Next.js 16.0.7 |
+| Database | Drizzle 0.44.7 |
+| Auth | Better Auth 1.4.3 |
+```
+
+## Template Reference
+
+| Template | Purpose |
+|----------|---------|
+| [tech-stack.md.template](templates/tech-stack.md.template) | Version info |
+| [known-issues.md.template](templates/known-issues.md.template) | CVE tracking |
+| [lib-structure.md.template](templates/lib-structure.md.template) | lib/ conventions |
+| [github-discussions.md.template](templates/github-discussions.md.template) | Discussion categories setup |
+
+## GitHub Discussions Setup
+
+When setting up a new project, configure Discussions categories for knowledge management.
+
+### Quick Setup Guide
+
+1. Enable Discussions: `Settings → General → Features → Discussions`
+2. Open category settings: `https://github.com/{owner}/{repo}/discussions/categories`
+3. Click "New category" and add from [template](templates/github-discussions.md.template)
+
+### Categories to Add
+
+| Category | Icon | Format | Purpose |
+|----------|------|--------|---------|
+| Handovers | 🔄 | Announcement | Session continuity |
+| ADR | 📐 | Announcement | Design decisions |
+| Knowledge | 💡 | Announcement | Confirmed patterns |
+| Research | 🔬 | Open-ended | Investigations |
+
+### Integration with Rules
+
+```
+Discussion (human-readable, user language)
+    ↓ extract key points
+.claude/rules/ (AI-readable, English)
+```
+
+See [template](templates/github-discussions.md.template) for body templates.
+
+### Generate Discussion Templates
+
+Generate `.github/DISCUSSION_TEMPLATE/` files for the project.
+
+**Trigger**: "generate discussion templates" or "setup discussion forms"
+
+**Workflow**:
+
+1. **Detect language** from user or CLAUDE.md (default: en)
+2. **Copy templates** from `templates/discussion-templates/{lang}/` to `.github/DISCUSSION_TEMPLATE/`
+3. **Verify** category slugs match existing categories
+
+**Available Languages**:
+
+| Language | Directory | Files |
+|----------|-----------|-------|
+| English | `templates/discussion-templates/en/` | handovers.yml, adr.yml, knowledge.yml, research.yml |
+| Japanese | `templates/discussion-templates/ja/` | handovers.yml, adr.yml, knowledge.yml, research.yml |
+
+**Example**:
+
+```bash
+# Generate templates (detect language from CLAUDE.md or ask user)
+"generate discussion templates"
+
+# Specify language
+"generate discussion templates in Japanese"
+"generate discussion templates --lang ja"
+```
+
+**Output**:
+
+```
+.github/DISCUSSION_TEMPLATE/
+├── handovers.yml
+├── adr.yml
+├── knowledge.yml
+└── research.yml
+```
+
+## Quick Commands
+
+```bash
+# Initialize for current project
+"generate project config"
+
+# Update tech stack versions
+"update tech-stack versions"
+
+# Add new pattern
+"add project pattern for {feature}"
+
+# Sync from CLAUDE.md
+"sync project configs from CLAUDE.md"
+
+# Generate discussion templates
+"generate discussion templates"
+"generate discussion templates in Japanese"
+```
+
+## Notes
+
+- Use `TodoWrite` for progress tracking (6 steps)
+- Confirm auto-detected results with the user via `AskUserQuestion`
+- Do not overwrite existing files without user confirmation
+- Run after major dependency updates
+- Keep tech-stack.md in sync with package.json
+- Project configs are NOT shared between projects
+- Common configs belong in `patterns/` or `templates/` directories

package/plugin/shirokuma-skills-en/skills/project-config-generator/templates/discussion-templates/en/adr.yml

@@ -0,0 +1,75 @@
+title: "ADR-XXX: "
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Architecture Decision Record
+        Record important architectural decisions.
+
+  - type: dropdown
+    id: status
+    attributes:
+      label: Status
+      description: ADR status
+      options:
+        - Proposed
+        - Accepted
+        - Deprecated
+        - Superseded
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Context
+      description: What is the issue that motivates this decision?
+      placeholder: |
+        Currently...
+        The problem is...
+    validations:
+      required: true
+
+  - type: textarea
+    id: decision
+    attributes:
+      label: Decision
+      description: What is the change being proposed/made?
+      placeholder: |
+        We will adopt XXX.
+        Because...
+    validations:
+      required: true
+
+  - type: textarea
+    id: consequences
+    attributes:
+      label: Consequences
+      description: What becomes easier or more difficult?
+      placeholder: |
+        **Pros:**
+        - Benefit 1
+        - Benefit 2
+
+        **Cons:**
+        - Drawback 1
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives Considered
+      description: Other options that were evaluated
+      placeholder: |
+        1. **Option A**: Description... → Reason not chosen
+        2. **Option B**: Description... → Reason not chosen
+
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Related documents, Issues, Discussions
+      placeholder: |
+        - Issue #XX
+        - Discussion #YY
+        - https://docs.example.com/

package/plugin/shirokuma-skills-en/skills/project-config-generator/templates/discussion-templates/en/handovers.yml

@@ -0,0 +1,62 @@
+title: ""
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Session Handover
+        Record information for AI session continuity.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What was accomplished in this session
+      placeholder: |
+        - Completed Issue #XX
+        - Implemented feature YY
+    validations:
+      required: true
+
+  - type: textarea
+    id: related-items
+    attributes:
+      label: Related Items
+      description: Related Issues/Discussions and their status
+      placeholder: |
+        - Issue #19: execSync → spawnSync → Done
+        - Issue #20: zod-schema fix → Done
+
+  - type: textarea
+    id: decisions
+    attributes:
+      label: Key Decisions
+      description: Important decisions made
+      placeholder: |
+        1. Adopted Table JSON format
+        2. Using Discussions for knowledge management
+
+  - type: textarea
+    id: blockers
+    attributes:
+      label: Blockers
+      description: Current blockers (or "None")
+      value: None
+
+  - type: textarea
+    id: next-steps
+    attributes:
+      label: Next Steps
+      description: What to work on in the next session
+      placeholder: |
+        - [ ] Start Issue #XX
+        - [ ] Research YY
+
+  - type: textarea
+    id: commits
+    attributes:
+      label: Commits
+      description: Commits made in this session
+      placeholder: |
+        - `abc1234` feat: add feature X
+        - `def5678` fix: resolve issue Y

package/plugin/shirokuma-skills-en/skills/project-config-generator/templates/discussion-templates/en/knowledge.yml

@@ -0,0 +1,66 @@
+title: ""
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Technical Knowledge
+        Record confirmed technical knowledge and patterns.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What problem does this solve?
+      placeholder: |
+        Radix UI components cause hydration errors
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Solution
+      description: The confirmed solution
+      placeholder: |
+        Use the `mounted` state pattern
+    validations:
+      required: true
+
+  - type: textarea
+    id: example
+    attributes:
+      label: Example
+      description: Code example
+      render: typescript
+      placeholder: |
+        const [mounted, setMounted] = useState(false)
+        useEffect(() => { setMounted(true) }, [])
+
+        if (!mounted) return <Placeholder />
+        return <RadixComponent />
+
+  - type: textarea
+    id: when-to-use
+    attributes:
+      label: When to Use
+      description: When to apply this knowledge
+      placeholder: |
+        - When using DropdownMenu, Select, Collapsible Radix UI components
+        - When getting ID mismatch errors in SSR
+
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Related documents, Issues, Discussions
+      placeholder: |
+        - Discovered in Issue #XX
+        - https://github.com/radix-ui/primitives/issues/XXX
+
+  - type: input
+    id: related-rule
+    attributes:
+      label: Related Rule
+      description: Corresponding .claude/rules/ file (if any)
+      placeholder: .claude/rules/radix-ui.md

package/plugin/shirokuma-skills-en/skills/project-config-generator/templates/discussion-templates/en/research.yml

@@ -0,0 +1,71 @@
+title: ""
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Research Request
+        Record research requests and findings.
+
+  - type: textarea
+    id: question
+    attributes:
+      label: Question
+      description: What needs to be researched?
+      placeholder: |
+        What are the best practices for implementing soft delete in Drizzle ORM?
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Context
+      description: Why is this research needed?
+      placeholder: |
+        Want to implement logical deletion instead of physical deletion for user data.
+        Related: Issue #XX
+
+  - type: textarea
+    id: scope
+    attributes:
+      label: Scope
+      description: Research scope and aspects
+      placeholder: |
+        - Drizzle ORM official documentation
+        - Existing project implementations
+        - Performance implications
+
+  - type: textarea
+    id: findings
+    attributes:
+      label: Findings
+      description: Research results (update after completion)
+      placeholder: |
+        *Researching...*
+
+        ---
+        **After completion:**
+        1. Method A: ...
+        2. Method B: ...
+
+  - type: textarea
+    id: conclusion
+    attributes:
+      label: Conclusion
+      description: Conclusion and recommendations
+      placeholder: |
+        **Recommendation**: Adopt Method A
+
+        Reason: ...
+
+  - type: checkboxes
+    id: next-actions
+    attributes:
+      label: Next Actions
+      description: Actions after research
+      options:
+        - label: Create ADR (if decision needed)
+        - label: Create Knowledge (if pattern confirmed)
+        - label: Create Issue (if implementation needed)
+        - label: Create/update Rule (AI extract)

package/plugin/shirokuma-skills-en/skills/project-config-generator/templates/discussion-templates/ja/adr.yml

@@ -0,0 +1,75 @@
+title: "ADR-XXX: "
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Architecture Decision Record
+        設計上の重要な決定を記録します。
+
+  - type: dropdown
+    id: status
+    attributes:
+      label: ステータス
+      description: ADR のステータス
+      options:
+        - Proposed
+        - Accepted
+        - Deprecated
+        - Superseded
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: 背景
+      description: この決定が必要になった背景・課題
+      placeholder: |
+        現在の状況として...
+        課題として...
+    validations:
+      required: true
+
+  - type: textarea
+    id: decision
+    attributes:
+      label: 決定
+      description: 決定した内容
+      placeholder: |
+        XXX を採用する。
+        理由は...
+    validations:
+      required: true
+
+  - type: textarea
+    id: consequences
+    attributes:
+      label: 影響
+      description: この決定による影響（良い点・悪い点）
+      placeholder: |
+        **メリット:**
+        - メリット1
+        - メリット2
+
+        **デメリット:**
+        - デメリット1
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: 検討した代替案
+      description: 検討した他の選択肢
+      placeholder: |
+        1. **選択肢A**: 説明... → 不採用理由
+        2. **選択肢B**: 説明... → 不採用理由
+
+  - type: textarea
+    id: references
+    attributes:
+      label: 参照
+      description: 関連するドキュメント、Issue、Discussion
+      placeholder: |
+        - Issue #XX
+        - Discussion #YY
+        - https://docs.example.com/

package/plugin/shirokuma-skills-en/skills/project-config-generator/templates/discussion-templates/ja/handovers.yml

@@ -0,0 +1,62 @@
+title: ""
+labels: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## セッション引き継ぎ
+        AI セッション間の引き継ぎ情報を記録します。
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: 概要
+      description: 今回のセッションで達成したこと
+      placeholder: |
+        - Issue #XX を完了
+        - 機能 YY を実装
+    validations:
+      required: true
+
+  - type: textarea
+    id: related-items
+    attributes:
+      label: 関連アイテム
+      description: 関連する Issue/Discussion とそのステータス
+      placeholder: |
+        - Issue #19: execSync → spawnSync → Done
+        - Issue #20: zod-schema 修正 → Done
+
+  - type: textarea
+    id: decisions
+    attributes:
+      label: 重要な決定
+      description: 重要な決定事項
+      placeholder: |
+        1. Table JSON フォーマットを採用
+        2. Discussions を知識管理に活用
+
+  - type: textarea
+    id: blockers
+    attributes:
+      label: ブロッカー
+      description: 現在のブロッカー（なければ "None"）
+      value: None
+
+  - type: textarea
+    id: next-steps
+    attributes:
+      label: 次のステップ
+      description: 次のセッションで取り組むべきこと
+      placeholder: |
+        - [ ] Issue #XX に着手
+        - [ ] YY の調査
+
+  - type: textarea
+    id: commits
+    attributes:
+      label: コミット
+      description: 今回のコミット一覧
+      placeholder: |
+        - `abc1234` feat: add feature X
+        - `def5678` fix: resolve issue Y